Exception Message: the Service Did Not Respond to the Start or Control Request in a Timely Fashion

Problem

This artilce features three scenarios that event in a failure to star the Enterprise Vault Admin service.

Error Bulletin

Scenario 1:

 An effort to offset the Enterprise Vault Admin Service after restarting the server, or later restarting all Enterprise Vault Services, will neglect with the post-obit error:

Could non start the Enterprise Vault Admin Service on Local Figurer. Error 1053: The service did not respond to the start or command request in a timely fashion.

---

Scenario 2:

After a successful installation of Enterprise Vault, the following popular up error bulletin appears on screen after restarting the server.

Error registering file: C:\Program Files (x86)\Enterprise Vault\AdminService.exe

 Attempting to start the Admin Service after closing the pop-upwards in a higher place returns the error:

Could not start the Enterprise Vault Admin Service on Local Computer. Fault 1053: The service did not respond to the start or command request in a timely fashion.

---

Scenario three:

An attempt to run the Enterprise Vault batch file, FileReRegister, returns the following mistake while appearing to register AdminService.exe:

The application was unable to outset correctly (0xc0000005). Click OK to close the application.

Cause

Certain 3^rd-party programs employ a serial of registry keys to allow an arbitrary list of DLLs to be loaded into each user mode process on the system.  This list of DLLs is loaded every fourth dimension the DLL_PROCESS_ATTACH process of User32.dll is used, and at that place are very few executables that do not link with User32.dll.  The Enterprise Vault executable AdminService.exe does utilize User32.dll.

The listing of DLLs being loaded tin exist constitute in either location, dependent on whether the program installed in 32-bit or 64-bit:

• For 32-bit installations:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs
• For 64-bit installations:  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs

This listing is enabled and disabled using the post-obit registry key:

• For 32-flake installations:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs
• For 64-chip installations: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs

By default, LoadAppInit_DLLs is set to '0' (disabled).  Withal, if an installed plan wishes to utilize AppInit_DLLs, it will often prepare LoadAppInit_DLLs to a value of '1' (enabled) and may even prescribe its service to reset the value to '1' if information technology were ever moved back to '0'.

Workaround:

1. Change the following registry keys:

'HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs' from 1 to 0

'HKLM\SOFTWARE \Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs' from 1 to 0

two. Restart the server.

3. Verify that both registry keys are still set up to '0'.  If either has reverted to 'i', view the solution beneath.

four. Verify Admin Service is now able to showtime.  If not, view the solution below.

NOTE:  Disabling LoadAppInit_DLLs will inherently cause problems with whatever process or service relies on DLLs being loaded from AppInit_DLLs.  Enterprise Vault, nor any necessary programme utilized in the workings of Enterprise Vault, will employ DLLs written to AppInit_DLLs. with a si

Solution

1. Discover the three^rd-party programs connected with all DLLs listed in AppInit_DLLs.
   
2. Uninstall iii^rd-party programs connected with the DLLs.  Microsoft does non recommend the apply of this registry set, and Veritas does not support 3^rd Party processes attaching additional DLLs to User32.dll via AppInit_DLLs.
   
3. Once uninstalled, verify that there are no DLLs  listed in AppInit_DLLs.
   
4. Kickoff the Admin Service.

 

Share this post