Share
Report
790Running SL 2015 CU1, SQL 2014 in a Terminal Services Environment, 2012 R2.
Created an Active Directory "Service Account" and log it into the console session of the SL Terminal Server, the account has a SL User ID, and runs Process Manager, Communicator to Mail and Application Server.
Process Manager "crashes" periodically, and have to log into the console session and address it, essentially, close it, acknowledge all of the error messages that pop up, then relaunch it and start it again. All not really a big deal. However, sometimes the fact that it has "crashed" is not noticed right away, and this causes issues with inventory allocations, receipts, issues, etc. not being reflected in a timely manner.
Years ago, I had heard "chatter" about the Process Manager being run as a service in Windows. I figured I could set the service up in such a way as to have it restart automatically if it crashes. I would also "hide" the process manager menu item in SL so the users didn't run a second instance of it. So I hit Google, and actually had quite a few returns. Unfortunately, all of the returns pointed to pages that were no longer available...404 error.
I asked my partner, and they had no info, I asked an ISV and they had no info, so I figured I would ask here...anyone know how to run Process Manager as a Service?
Thanks in advance,
Chris
All responses (
Answers (
