Pretty much the same issue as this thread discussed: thread693-1739035
Changed logon user from Local System to Local Service, still no luck.
Log shows the task was completed successfully, but no disk file created.
Turned on folder auditing, didn't find failure events either...
If running by clicking a button in AutoSequence, then it works (disk file created).
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Autosequence 30003 step 1 of type X has begun. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Transaction Analyzer - Menu Item - analyzer.exe /C2 |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Creating the analyzer.exe /C2 process |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | This autoSequence is running from UWS seq: 0 using connection [1] |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | This autoSequence is running on the server with UWS seq: 1 |
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Autosequence 30004 step 1 of type X has begun. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Transaction Analyzer - Payment - analyzer.exe /C1 |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Creating the analyzer.exe /C1 process |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Step completed. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Autosequence 30003 step 1 of type X has completed in 0 seconds. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | -------------------------------------------- |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Step completed. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Autosequence 30004 step 1 of type X has completed in 0 seconds. |
Changed logon user from Local System to Local Service, still no luck.
Log shows the task was completed successfully, but no disk file created.
Turned on folder auditing, didn't find failure events either...
If running by clicking a button in AutoSequence, then it works (disk file created).
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Autosequence 30003 step 1 of type X has begun. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Transaction Analyzer - Menu Item - analyzer.exe /C2 |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Creating the analyzer.exe /C2 process |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | This autoSequence is running from UWS seq: 0 using connection [1] |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | This autoSequence is running on the server with UWS seq: 1 |
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Autosequence 30004 step 1 of type X has begun. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | AutoSeqServer | 0 | Transaction Analyzer - Payment - analyzer.exe /C1 |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Creating the analyzer.exe /C1 process |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Step completed. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Autosequence 30003 step 1 of type X has completed in 0 seconds. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | -------------------------------------------- |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Step completed. |
Sun Apr 24 00:20:01 2022 | MICROSPOS | Autosequence.dll | 0 | Autosequence 30004 step 1 of type X has completed in 0 seconds. |