If a Virtuoso Windows Service fails to start, take the following action:
1. Determine whether useful information can be gleaned from the error returned by the actual Services utility.
2. Determine whether useful diagnostic information can be found in the virtuoso.log file.
3. Look in the Event Log for useful, diagnostic information.
4. Add "%VIRTUOSO_HOME%\bin;%VIRTUOSO_HOME%\lib" to the System PATH variable, and test again, after restarting Services.
5. Determine whether or not Virtuoso Virtuoso can be started on the commandline. If you are able to start Virtuoso from the commandline, use the Services control manager to edit the Path to Executable, so that it is identical to what you see on the commandline.
6. Determine whether or not a locall firewall is preventing Virtuoso from starting.
7.
Make sure the virtuoso server binary returns a version string on the commandline.
If it fails to return a version string, important dependency issues may be shown.
.\virtuoso.exe -?
8. Use the Dependency Walker program to load the virtuoso-t.exe binary and determine whether or not there are any unresolved .dll dependencies.
9. Determine whether you are creating the service using an operating system user with permissions issues.
10. Determine whether your service is running as the "Local system account" when viewed in the service manager "Logon" tab for the service.
NOTE: DWMAPI.DLL dependency errors are not significant.
This DLL is required by one of the Microsoft DLLs and not virtuoso directly.