Contact Desaware and order today! 

Sign up for Desaware's Newsletter for the latest news and tech tips.

NT Service Toolkit Support

Frequently Asked Questions - Errors and Debugging

1. AutoStarting a Service generates an error on some systems.
2. When I run my Service in Simulator mode, everything works fine. But when I try running the Service as a Service, the Service does not start.
3. My Service was working fine, but after I recompiled my Service EXE, I cannot remotely access the exposed objects.
4. I'm using the NT Service Toolkit Demo but I keep getting a "Configuration information is missing from this executable" error message .
5. Calling the ReportEvent2 function in my service triggers an exception error of -2147023394 (&H8002705DE).
6. If I set the SetWaitOperation function's bWaitAll parameter = True and is waiting on only 1 event, then the WaitComplete event will not be triggered when the event is completed.

This is most likely a Service Dependency problem. Our Service is dependent on the RPCSS service, and will not start until it is started. If your Service requires any additional services, you can return the service string name in the IdwEasyServConfig_ServiceDependencies function.

We have also verified this problem on NT 4, SP 5 and later on our generic Beeper sample. The order of when services start seemed to have changed starting with SP 5, and may continue to change in future service packs. If you have set your Service to AutoStart and get an error on boot-up, try setting the IdwEasyServConfig_ServiceDependencies function to return ONE of the following:

IdwEasyServConfig_ServiceDependencies = "Browser"
IdwEasyServConfig_ServiceDependencies = "ProtectedStorage"
IdwEasyServConfig_ServiceDependencies = "Replicator"
IdwEasyServConfig_ServiceDependencies = "RasMan" 

or

IdwEasyServConfig_ServiceDependencies = "RasAuto" 

After making the change, uninstall your Service EXE, then recompile the DLL, and install your Service EXE again.

The Service string names are found in the subkeys of the \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services key.

This may be an indication that an unhandled error occurred in your service DLL. First, make sure that your Visual Basic project has the Break on All Errors or Break in Class Module option selected and try running the Visual Basic project before starting the Service. In .NET, use the Debug-Exceptions dialog to break on all errors. For VB6 services, make sure that your Visual Basic project is not set to Compile on Demand (in the Tool's - Options menu, under the General Tab) that your Visual Basic project is set to Apartment Threaded.

Review the Testing and Debugging section in the NT Service Toolkit's help file for additional solutions.

Be sure that you also recreate the VBR file and distribute that along with your new Service EXE file when you recompile your Service EXE. Each time a Service EXE is created, the Service Configuration Wizard creates a new GUID for the exposed objects.

Be sure you are using the latest latest EasyServ.exe file. After downloading and replacing the file, "Run" EasyServ.exe with the "-RegTypeLib" command line argument.

This error message indicates that the Event Log is full. You should add error handing in your service for this particular error number.

We have fixed this problem. Run the NT Service Toolkit Files Update utility or contact us to retrieve the latest files, then run the Service Configuration Wizard and recompile your Service EXE.