Trying to implement a workaround since PSM has known issues in Server 2019 environment where we have PresConnect workflow installed. We have a PSM dongle on another computer as it is not recognized on a Win2019 server. The new version of PSM 7.2.11 recognizes the dongle and also allows me to run command line parameters (automate printing mode) successfully without limited pages or watermark, meaning when I run PSM outside of PresConnect it produces output. For some reason, I can run the workflow in Debug mode successfully (it finds the dongle via -net command) and also runs the script (via -script command) to an output location with no limitted records NO WATERMARK, however the External program does not run or get called in service mode/when scheduled.
NOTE the same domain account is used in Debug and service mode and is the account used to run PresConnect as a service.
The batch file called at CMD = KPMRUNSCRIPT.bat
start /d "C:\Program Files (x86)\PrintShop Mail Suite 7\PrintShop Mail" PSMAIL.exe -net -script D:\KPM-\ExampleJobs\MDACC-TEST\KPMTESTSCRIPT2.txt
the script file called at PSM cli -script = KPMTESTSCRIPT2.txt
FileOpen D:\KPM-\ExampleJobs\MDACC-TEST\MDACC-WELCOME_SERIES.psmd
DatabaseOpen D:\KPM-\ExampleJobs\MDACC-TEST\59582_Print-test_10.txt
SetPrintTech PDF
FilePrintToFile D:\KPM-\ExampleJobs\MDACC-TEST\OUT\KPMTESTOUT.PDF
FileExit
The file capture is only used to trigger the External program not sure of any other way to execute this in service mode
Workflow tasks
Folder capture task to trigger the External Program…not sure if this can be done differently but it allows the trigger of next step
External program that calls cmd.exe (command prompt) and runs my KPMRUNSCRIPT.bat file (see attached)
Send to folder does nothing and can be removed.