- Event 7009, Service Control Manager

sebastian vega alvarez 1 Reputation point
2021-02-20T17:38:52.19+00:00

I have a server which does not start some necessary add-ons for its operation as a secondary server, the following errors appear in the registry: - Event 7009, Service Control Manager A timeout was reached (85000 milliseconds) while waiting for the Mobile Partner. OUC service to connect. - Event 7000,, Service Control Manager The Mobile Partner. OUC service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. I changed the registry <ServicesPipeTimeout> this did not work for me, any other recommendations? My server data: Windows Server 2008 r2

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,108 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. MotoX80 31,571 Reputation points
    2021-02-20T18:08:15.01+00:00

    any other recommendations?

    Contact the vendor for support. Or search their support site for instructions on how to enable diagnostic logging so that you can understand what the service is doing when it fails to start.

    You could also trace the process with Process Monitor.

    https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

    Set a filter on the process name and monitor the service starting. Then analyze the files and network calls that it makes. Maybe you have parameter that is set wrong.

    Was the service created by the software installation process, or did you manually define the service?

    0 comments
  2. sebastian vega alvarez 1 Reputation point
    2021-02-20T18:14:23.347+00:00

    It is actually an industrial server from a Rockwell Automation control platform, which acts as a secondary server, this problem occurred after restarting the server.

    0 comments
  3. Xiaowei He 9,871 Reputation points
    2021-02-23T07:07:56.493+00:00

    Hi,

    After restarting the server, please try to open CMD and run sfc /scannow, check if there's any corrupted system files.

    And it's recommended to turn to the add-on vendors, check if the files are correct.

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments