- Created by Unknown User (mvachon), last modified by Unknown User (aduquette) on Feb 21, 2017
LPS Print Service fails to start. This scenario applies specifically to LPS configurations that contain mapped or network drive scan folders that the LPS service is monitoring.
This error occurs when one or more of the mapped/network drives become unavailable (to the LPS server) and the LPS is shut down and restarted after this change occurs. Starting the LPS Print service within the LPS console (WDCplEXE) application may fail to generate an error on restart. Root cause is not obvious or evident to the user. The user will note that label files are not processing as expected. The service launch fails after not being able to connect to the mapped/network locations, regardless of how the service is launched (includes Windows Services control). If a mapped or networked scan folder name/path has been modified while this service is still running, it has no way to detect this at the time of the change. Only when the service is restarted will the system try to verify each of the scan paths and then fail the restart operation. Below is a sample of what a user may see when trying to start the LPS Printer service from Administrative Tools|Services in the Windows operating system:
- Launch LPS Configuration Utility.
- Examine all configured scan paths.
- Note any entries that are either mapped or network drives (any entry other than a local drive).
- User will need to verify all mapped and/or network scan locations configured in LPS. User can independently confirm this using Window Explorer to see if they can navigate to the mapped/network folder and view its contents while logged in as the same user account running the LPS service.
- If any of the assigned folders cannot be reached, the associated LPS scan folder entry should be removed.
- Once all of the mapped/network folders are validated, restart the LPS Print service and verify that jobs are now being processed as expected.
- If the target folder is a required source for production, Loftware Administrator/User should contact their IT group for assistance on regaining access to the identified remote folder location.
All supported LPS family product versions
No specific environment considerations