|Summary:||If the Data Replicator service does not start or run as expected, use these suggestions to solve the problem|
I want to run the Data Replicator as a service. How can I avoid the following error when I start the service?
DBMoto Service Monitor has encountered an error starting the DBMotoSrv service. System.InvalidOperationException: Cannot start server DBMotoSrv on computer ‘.’. ---> System.ComponentModel.Win32Exception: The service did not respond to start or control request in a timely fashion
--- End of inner exception stack trace ---
at System.ServiceProcess.ServiceController.Stat(String args)
at cb.d(Object A_0, EventArgs A_1)
Review the following list for possible solutions to the error.
Check Program Permissions and Rights
The problem may be associated with user or program permissions and rights.
Check the service security settings
The error you reported probably concerns the rights assigned to the Data Replicator service. Use the instructions below to check if the service logs on with maximal rights.
- On your Windows desktop, open the Services window.
- Right-click on the Data Replicator Service to open the Properties window.
- Go to the Log On tab.
- Change the account to one with administrator rights.
Check the create/write privileges for the Data Replicator user
It is possible that the Data Replicator is attempting to run as a service with an associated account (the Windows user login account) which does not have enough permissions to create/write files on disk. Try using a different account or changing privileges on the account.
Use the unsigned version of DBMoto
Does your system have Internet access? If not, the Data Replicator is unable to start as a Windows Service. DBMoto is Microsoft certified and, in order to verify the certificate, the .NET framework needs access to the Internet and get the updated revoked list. An unsigned version of the product is available. It is exactly the same as the signed version and 100% Microsoft certified, but it will not check the certificate as the signed version does. Submit a tickect via the Help Center to obtain this version.
Increase the default timeout value for the Windows Service Control Manager
Maybe the system was VERY busy at the time the Data Replicator was starting. When the service starts, the metadata is loaded. If this operation takes more than 30 seconds, you will get the timeout error. Windows uses a default 30 second timeout for starting a service. This value can be changed manually by editing the registry.
To increase this value to 60 seconds, follow these steps.
- On your Windows desktop, click Start, then Run to open the Run Command window.
- Type regedit, then click OK.
- Locate then select the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must create it:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER.
- Right-click ServicesPipeTimeout, and then click Modify.
- Click Decimal, type 60000, and then click OK. This value represents the time in milliseconds before a service times out.
Check to see if the DBReplicator.exe is already running
The Data Replicator executable (DBReplicator.exe) may already be running as a interactive application. Check on your Windows desktop to see if there is already a DBReplicator.exe running, either by using the Windows Task Manager or by using the Service Monitor in the Windows System Tray/Notification Area. If no replications are currently running, stop the Data Replicator. All running replications will be automatically disabled and stopped. Their current status is saved before exiting to avoid errors/inconsistencies on startup.