Pega Notification Manager goes to Stopped state from Running state
We are encountering an issue with Pega Notification Manager where some of our Pega Robot Runtime users who are on Virtual Machines frequently get an error whenever they try to launch applications. The error states that it "Could not get reference to Pega.Interop.Services.IDriverEventService".
We've tried opening Task Manager to check the Status of the services(Pega Updater Service and Pega Notification Manager. We are aware that Pega Updater Service kickstarts Pega Notification Manager) before launching Pega Robot Runtime. Once, we ensured that both the services are 'Running', we try to launch applications using Bot.
However, we've noticed that when the Bot is trying to open a IBM PCOM Mainframe session, the Pega Notification Manager goes from "Running" to "Stopped".
Has anyone else experienced this issue? Has anyone else solved it?
Pegasystems Inc.
US
I have not personally seen this, but this does sound like something that support may have encountered. I would suggest opening a support case and recording the case number in the post.
Tech Mahindra
IN
@VivekK39 I am also encountering the same issue since I installed 19.1.70 version .I am also not able to launch IBM P_Comm and my Pega notification manager start up type is "Automatic". Did we get any resolution for this ticket?
CWT
PH
Pegasystems Inc.
IN
The reported behavior was a known issue and got fixed in 19.1.46. If you have observed this issue in 19.1.70 or later, I suggest you open a support request and tag the same here.
Regards,