Hi Dojo,
When in presence of errors on SLProtocol.exe, DataMiner promptly flags these to admins & users:
what's the best type of capture // memory dump that can help in troubleshooting the root cause behind these hanging calls? Is it worth setting up some automation / correlation so that the related data collected automatically every time this type of RTE is listed in alarm console?
Thanks
Hi Alberto,
I am facing a similar issue for one of my customers. In my case, I found out the issue to be a driver problem. The way I found out was by executing Pending Calls via the SLNetClientTest tool.
If you grab the elementID from the Edit page of the element presenting the RTE, and you run the Pending Calls on the DMA hosting that element, you will probably be able to find which group or QAction is causing the protocol to get stuck.
With this information, you can later have a look at the driver and see what information is being retrieved by that group, and use this to guide a driver investigation afterwards.
You can find more related information and relevant troubleshooting steps in the following page
Kind regards