Question
Accenture
AU
Last activity: 13 Jul 2020 11:34 EDT
Web.MessagingHost.exe blocks adaptor working
Hi,
I am facing this issue recently with Proprietary information hidden version, I am starting UWA while runtime launches. Initially, there would be one instance of ‘OpenSpan.Translators.Web.MessagingHost.exe’ as part of UWA starts.
Users are working without any issue if one instance of Messaging Host running. Apparently, there would be another instance of ‘OpenSpan.Translators.Web.MessagingHost.exe’ running. I’m not sure, how the other instance opened.
If two instances are running, it blocks the adaptors working (like iexplore.exe and Siebel.exe).
Currently, I’m handling this situation by restarting the Chrome.exe and launching the application again.
Since restarting the chrome is not the best option since user might opened other application by manually as part of their process. This restart, it closes all the chrome application and user might lose the data.
Is there any other work around to handle this situation?
Pegasystems Inc.
US
I do not believe that WebMessagingHost blocks IE as I have used both UWA and a web adapter in projects many times.There should only be one instance of that running. I think your key is finding out how the other one starts.
Pegasystems Inc.
US
I don't see any fixes specific to web messaging host since 2039, although I am sure there have been some. As that version, is a year old, it might be worth it to test with the latest version. If you cannot move to 19.1, then the latest version of 8.0 SP1 would be worth it as well. I wonder if something is getting stuck with the current process which is causing it to stay around. That app should close when Chrome is closed.
Accenture
AU
Thanks tsasnett.
Is there a way to identify the thread/processes to kill that alone instead of closing all chrome ?.
As recommended, I'll try to upgrade my version and test these behaviours in new version.
Pegasystems Inc.
US
Web.Messaging.Host is running whenever Chrome is running (it is started by the extension). There's no single Chrome process that starts it other than the first one.