Micros 3700 Schedule Class

[cobbler9]

I'm hoping someone can help me or point me in the right direction. Running Micros 3700 v5.2 on Win 7 Pro server. I have created an AutoSeq which runs weekly reports based on a Schedule Class. The AutoSeq contains steps 1 through 3 of type Report and steps 4 through 8 of type External Program. Each External Program step calls a specified Transaction Analyzer configuration set to print to file as a PDF. When I run the AutoSeg manually from the AutoSeqExec.exe GUI the full AutoSeq runs through and all reports are properly run and saved as individual PDF's. However, when the AutoSeq is triggered by the schedule class, it only runs the first 3 steps (the Report type) and never completes the other remaining steps (the External Program type). In the 3700d log I can see that as step 4 is called, Transaction Analyzer is started and then logged in:

Mon Oct 13 12:49:16 2014 | M-BOPC | Transaction Analyzer | 0 | Application Started |
Mon Oct 13 12:49:16 2014 | M-BOPC | Transaction Analyzer | 0 | -1 - Logged In |

However nothing ever shows after that. No errors, no "Application Shutdown", no "Step 4 of type X completed". Nothing.

Any ideas why the AutoSeq would function perfectly when called manually, but not when triggered by a Schedule Class?

I have other AutoSeq triggered by Schedule Classes that run External Programs that call batch files to perform various file renames, moves, and PDF merges, and they all function correctly, it is only the Transaction Analyzer that fails. It is also of note that the Schedule Class triggered calls to Transaction Analyzer worked in Micros ver 4.11 running XP Pro before we upgraded last Monday.

Thanks in advance!!

 

[DJensen999]

Some people have had luck changing the Autosequence service to Local Service from Local System in Windows to fix printing issues from Autosequence. I believe this is due to changes in how Windows assigns security to accounts by default.

 

[Wildbar]

We run Transaction Analyzer reports through autosequences as you are trying to do. DJensen999's fix is what we had to do to get it to work.

 

[cobbler9]

Thank you both, that did the trick!

I had experimented with that earlier under POS Configurator | System | Restaurant | Security but that did not seem to work. Just changing it in the POS Configurator, windows did not actually start the service under the local account even with a reboot (seemed that possibly the password did not transfer to the service setting correctly, or I repeatedly typed it incorrectly). I needed to go into the Windows services and reenter the password there, then success.