|Products Purchase Publishing Articles Support Company Contact|
support > Product FAQ > NT Service Toolkit > Service Configuration Wizard
Event Log Toolkit
NT Service Toolkit
NT Service Toolkit Support
Frequently Asked Questions - Service Configuration Wizard
1. How do I specify for the batch mode of the Service Configuration Wizard to create a VBR file?
First, you need to have version 126.96.36.199 or later of the Service Configuration Wizard (run the NT Service Toolkit Files Update utility to check for the latest files). To have the Service Configuration Wizard output a VBR file on a batch build, a VBR file having the same file name as the input Service EXE file must exist in the same folder as the input Service EXE file. The Service Configuration Wizard will update the existing VBR file with the new Service EXE file's corresponding information.
2. Sometimes the Service Configuration Wizard does not create a VBR file even though I specify a Service Object Description in the Remote Automation step.
If the output path for the Service EXE (where the VBR file is to be created) includes a "." period, then the VBR file will be created in the wrong folder. Output the Service EXE to a folder that does not contain a period. For Version 2.x, you can run the NT Service Toolkit Files Update utility to download the latest Service Configuration Wizard which fixes this problem.
3. The Service Configuration Wizard does not seem to read the Project name of certain Service EXEs correctly. Part of the project name seems to get truncated.
There was a bug with the Service Configuration Wizard where it would truncate the Project Name read from an existing Service EXE file if the Project Name had a "1" (number one) character in it. The Service EXE was stamped with the correct Project Name, but when the Project Name is read by the Service Configuration Wizard, the Wizard leaves off the rest of the Project Name following the "1" character.4. An error occurs when I try to create a VBR file using the Service Configuration Wizard.
We have fixed this problem. Run the NT Service Toolkit Files Update utility or contact us to retrieve the latest files.
|Products Purchase Articles Support Company Contact