Environment: ca uim 9.0.2, mssql 2012 as db.
Ca uim primary hub controller is getting down intermittently and not able to reconnect automatically until we restart the robot watcher service.
This is causing huge production outages.
We can see below errors in windows event logs during the issue.
Error 1: TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.
Error 2: This computer was not able to set up a secure session with a domain controller in domain #### due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
Error 3: A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use.
We dont have any clue whether server is having issue or nimsoft is causing issue in the server due to lack of ports.
While trying to login to IM in primary hub, it is throwing an error saying not able to communicate with controller( screenshot attached).
Please find support cases details raised 01350414, 01316843.
Thanks for patience to read this long description.
make sure you are running robot 7.97Hf3 or newer
CnIa24uJ@ftp.ca.com/UIM_Probe_Hotfixes/robot_update-7.97HF3.zip" rel="nofollow" target="_blank">ftp://UIMuser:CnIa24uJ@ftp.ca.com/UIM_Probe_Hotfixes/robot_update-7.97HF3.zip
if that does not help resolve the issue open a case with support there is a new hub version for a handles problem that can be delivered from dev.
we had a similar issue and the workaround to get it back to work is the same we did (restart the robot watcher) we got an ems and hub probe hf and with those two updates it has worked.
Hi Gene_Howard / Mxcuellar, We applied 7.97 HF3 on 17th May. We are waiting if it works...Thanks..
The controller is down again today at 12.36pm.
For something like this, after the most common causes have been tried, the list of variables to consider becomes too great for this forum and need to rely on the support case you have open.