The AutoStore service is started, however it stops immediately. This occurs after configuring a new setup, or an upgrade to the version of AutoStore.
There can be many causes for this behavior. Most commonly, a corrupt or incomplete configuration file will cause the issue. Missing local permissions may also cause a service to stop.
To resolve an issue with local account permissions, ensure the AutoStore (batch.exe) service is running using correct network account credentials:
- Click the start button and type services.msc. Microsoft services snap-in console will appear.
- Double right-click on the Autostore service.
- Click the Log in tab.
- Verify or enter the correct network username and password information.
- Click OK to save and apply the changes. A service restart is required to apply the changes.
If a configuration file corruption is causing the fault, be sure the workflow is complete. An AutoStore workflow requires a capture and route component. AutoStore will not start if either component type is missing from the configuration. Check for additional untitled tasks in AutoStore Process Designer in the configuration file. Any empty tasks will also cause an error with configuration file.
Alternatively, run the AutoStore service in command prompt to determine the issue:
- Run a command prompt as administrator.
- Change the current directory to the AutoStore installation directory:
- Type cd "
" to change folder location. Quotation marks are required.
- By default, AutoStore 7 is installed to "C:\Program Files (x86)\Notable Solutions\Autostore 7.
- By default, AutoStore 6 is installed to "C:\Program Files (x86)\NSi\AutoStore 6\
- Type cd "
- Type batch.exe -e -c"cfg file location".
- Press enter to start the AutoStore service using the specified configuration file.
- Take note of any errors encountered during start and the components which fail. Review the Installation Guide section for that component.