Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    174
  • Views views
    521
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

restart windows service operation failing for windows 2016 and windows 2019, working on windows 2012

prakash_Kilaparthi

Hi,

I am using Restart Windows Service operation from following location to restart one windows service


/Base [1.19.0]/Library/Operations/Operating Systems/Windows/Services/Restart Windows Service


User which I used is local administrator on the target server.

- I am able to restart the service on any windows operating system when I run the flow from studio (windows 10 laptop)

- I am getting following error when this flow runs from Central, it is only able to restart services on Windows 2012 servers only and failed to restart service for Windows 2016 and windows 2019.

Error : 

Cannot open Service Control Manager on computer 'XXXXXX'. This operation might require other privileges.

I double checked, the user which is used in operation is local admin on all target hosts.
 
I am not able to blame OO operation , as it is working when I run from Studio on my laptop.

BTW : My central server is hosted on Windows 2016 OS.
 
 
Can some help me with issue?

Thanks,
Prakash.
  • 0  

    Hi Prakash,

     

    Have you tried to set a privileged user to run the Central service? From Windows Services, look for the Central service, and then right click select Properties and in Log On tab please specify a user with Admin privileges.

     

    Regards! 

    Carlos Rojas

    OpenText Support Agent

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.

  • 0 in reply to   

    Hi Carlos,

    I am back from holiday and upgraded OO to 2020.08 and made OO service running under administrator user.

    Now here are the conclusions of our testings

    -  Running restart windows service operation from OO central to servers in domain where OO server is also belongs to is failed with local administrator  accounts on target servers. 


     - Running restart service restart operation from OO central to servers in domain where OO server is also belongs to  is working with domain admin accounts on target servers

    - Running  restart service restart operation from OO central to servers in other domains  is working with domain admin accounts or local admin accounts on target servers.

    We were not able to trace what is wrong in preforming restart on his own domain servers is issue with local admininistrator.


    I also opened ticket with support and it is under investigation.

    Thanks,
    Prakash.

  • 0 in reply to 

    I am currently seeing the same issue with 2021.02 and connecting to a Windows 2016 server.  The operations work on other servers, but certain ones with some "policy differences" are failing.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.