Posted: 4 Mar 2019 6:25 EST Last activity: 20 Jan 2020 12:51 EST
An error occured while setting up shared memory with the Pega Notification Manager Service in Pega CRSA
When I gave the Path as "CRM.exe(complete location)" and in the target path "calc.exe" applications and then changed the Start Method from Start to Start&Wait and clicked on Start Interrogation. I am getting error as "An error occured while setting up shared memory with the Pega Notification Manager Service", How to fix this ? so that I can interrogate the Target path application.
***Edited by Moderator Marissa to update platform capability tags****
All the services are running, As a part of default installation of CRSA, what ever suggested I had enabled them. As well as Please let me know what services that needs to be checked furthur in services.msc(Under Extended or Standard Tabs)?
Developing in Studio w/ 8 2021. Using StartAndWait option causes a Notification Manager service needs to be running message. However, the only reference I can find in the manual to Notification Manager service (NMS) is in the help page (http://help.openspan.com/80/) where is describes each StartMethod option, and simply states the NMS needs to be running to use StartAndWait. Beyond that, I find no reference to NMS. How does one initiate/start the NMS while coding in Studio?
Can you please provide an update on this. It is not possible for me to Start the "NMS Service" during coding or when I execute/run the automation/project. As well as, I need a detailed info on how this NMS works and useful in the project/automation & what are the uses of this NMS during project development or automation development.
If Path and Target path values are configured then it will not interrogate the path file path. In your case Path have CRM app and Tragetpath have calc which is not correct. Try with correct application path/targetpath values.
I would like to know why only the Notification Manager Service message is thrown when I went with this approach and want to know in what scenarios will this message will be thrown and the actual usage of this service and what will this service does ? and during this execution of a project/automation I haven't brought down any services in services.msc manually to trigger this notification manager service message.
I am able to overcome this following the usual process of coding/automation(Path and Target path: usual configuration) development.
I'm experiencing a similar issue..and get this message when the bot is running and tries to open an adapter (v2021) ...do you believe if i change the adapter property from 'StartandWait' to 'Start' we may avoid this error? Any help would be greatly appreciated!
'Unable to open private shared memory. Verify that 'Pega Notification Manager is running'
If changed from StartandWait to Start,the notification manager message maynot trigger(It didn't triggerd for me).However the exact reason why this message is getting triggered and how this is related to change done from Start to StartandWait approach is not know.