Troubleshooting Spindle Professional in unattended mode.

Troubleshooting Spindle in an unattended mode environment presents a number of challenges.

1) Check that the Spindle Professional processes are running in the correct user context (user name and session ID).

a. For Windows 2008R2 and below, this means that the Print Agent process must be running in the same context as SpindlePro6Monitor.exe

b. For Windows 2012 and later this means that the Print Agent process user is the same as the one set in the Logon tab of the Service's Properties window

To check this, use Task Manager. In teh Details tab, add the column for Session ID to confirm.

If there are any SpindlePro6Monitor.exe or SpindleDocDistMonitor.exe processes running in anything other than Session 0, end them

2) Check the Eprinter log file located in C:\Program Files (x86)\Common Files\Draycir\EPrinter\Log

    This will display the name of the temporary job file that is sent to the Spindle Printer, and will also show you (by dint of the path to the temp folder) the user that the print job was sent by. This will tell you where to find the Spindle Log files. If the Eprinter log does not get updated, then check that the Spindle Printer is correctly configured as a destination in the source application.

20150224.122535 : Processing command line '"C:\Users\HODGSO~1.EUP\AppData\Local\Temp\JOB0000200092.INI"'

20150224.122726 : Processing command line '"C:\Users\HODGSO~1.EUP\AppData\Local\Temp\JOB0000400146.INI"'

20150227.095500 : Processing command line '"C:\Users\HODGSO~1.EUP\AppData\Local\Temp\JOB0000200093.INI"'

20150303.110139 : Processing command line '"C:\Users\HODGSO~1.EUP\AppData\Local\Temp\JOB0000200094.INI"'

3) Check the Spindle Monitor log file located in C:\Users\<username gleaned from the above step>\Documents\My Draycir Logs. 

4) This file will show if the monitor is being launched, that the licence check is OK, and whether the User agent has run. It will also show evidence of the print job being submitted:

20150227.090441 04: Launching 'C:\Program Files (x86)\Draycir\Spindle Professional 6\Drivers\SPA Driver x64\dsplpaagent.exe'

20150227.090441 04: ENTERING CheckForUserWizardDLL

20150227.090441 04: ENTERING DoUserSetupWizard

20150227.090441 04: LM SPLHKEY_PRINTERSETUP b36dde89-fbed-4f2e-9e50-05cde0b3f348

20150227.090441 04: SPLHKEY_PRINTERSETUP b36dde89-fbed-4f2e-9e50-05cde0b3f348

20150227.090441 04: Printer GUIDs match

20150227.090441 04: ENTERING IsTerminalServicesEnabled

20150227.090441 04: Terminal Services is not enabled

20150227.090441 04: ENTERING Logon


20150227.095500 04: WP: LO message

20150227.095500 04: SPLMONRUNEXECD message C:\Program Files (x86)\Draycir\Spindle Professional 6\SpindleProfessionalProcessor.exe "Untitled - Notepad" "C:\Users\HODGSO~1.EUP\AppData\Local\Temp\JOB0000200093.INI" "Spindle Pro" "1" "0" "1"

20150227.095500 04: ENTERING Compare LFLMT

20150227.095500 04: ENTERING CSpindleMonitorWnd::GetLFT

20150227.095500 04: WP: LO message

5) If the Monitor Log looks OK, check the Spindle Professional Processor log file and troubleshoot as per a standard Spindle Professional installation.