nimsession error 10055

[amar kondraju]

Dear all,

We are getting this error in hub log and we are unable to open IM console and admin console when we get this error. 

hub: nimSession - failed to connect session to HUBIP:48001, error code 10055




Regards
Amar

[amar kondraju]

Hi all,

Please let me know if there is any hotfix for this error / how to resolve this ?  Need suggestions on priority!!!


Regards
Amar

[Gene Howard]

This is not enough information to help.
Set your loglevel to 3 and log size to 35000 in the hub.cfg and restart to get more information. 

If you are running  hub and controller  9.20 update to the latest hotfix  on the hotfix site that might help.

For the community to help more we will need more information such as os type and version as well as probe versions and any recent changes.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[amar kondraju]

Hi Gene ,

We have 9.0.2 UIM in our production and our hub version is s 9.0.2.

UIM is sitting on Windows server 2012.


Regards
Amar

[Franklin Ravi D'souza]

Can try

1)
Upgrade to below from UIM hotfix index if running lower versions on Primary
hub_7.97HF6
robot_update 7.97HF9

2) Ensure Nimsoft folder excluded from AV scanning

3)If OS is Win 2012R2 check the dynamic port range for outbound communications is increased 

netsh int ipv4 show dynamicportrange tcp

https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-tcpip-port-exhaust

[amar kondraju]

Dear Ravi ,

Thanks for your insights but need some clarity on points 2 & 3.

Point 2) We have ​Anti virus running on server and shall I go ahead and exclude AV scanning on nimsoft folder Ravi - recommended in this case right? please confirm..

Point 3) I have run the command in the UIM server . Please explain a bit further what exactly needs to be done using this link ?

netsh int ipv4 show dynamicportrange tcp   ---- output states start port is 49152.


Regards
Amar

[Franklin Ravi D'souza]

Yes please check below KB for the recommendation
1)
Antivirus scanning of UIM components

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=137152

2)


The default port range starts at 49152 and goes to 65535 or 16K ports. This can be changed by a Windows configuration option to start at port 1025, thereby allowing 64510 ports before exhaustion. 
 
There are 2 recommended changes to help resolve this problem: 

a. Change the ephemeral port range:
netsh int ipv4 set dynamicport tcp start=1025 num=64510
netsh int ipv4 set dynamicport udp start=1025 num=64510
netsh int ipv6 set dynamicport tcp start=1025 num=64510
netsh int ipv6 set dynamicport udp start=1025 num=64510

b. Change TcpTimedWaitDelay to 30 seconds in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters

Might need to reboot the server after changes
Please check with your windows admin for additional info on this point since this is related to OS settings

[amar kondraju]

Hi Ravi ,

Thanks lot Ravi for clearcut justifications . I will try them and will update . Thanks a lot sir.

Regards
Amar

[amar kondraju]

Hi Ravi,

I have followed steps 1 and 3 but step is not yet done. After 2 weeks again we have got this error : hub: nimSession - failed to connect session to HUBIP:48001, error code 10055. If I follow step 2 will there be any chance of remediating this error Ravi - please suggest.


1)
Upgrade to below from UIM hotfix index if running lower versions on Primary
hub_7.97HF6
robot_update 7.97HF9

2) Ensure Nimsoft folder excluded from AV scanning

3)If OS is Win 2012R2 check the dynamic port range for outbound communications is increased

netsh int ipv4 show dynamicportrange tcp



Regards
Amar

[Luc Christiaens]

Amar,
Why do you open a new entry if you have still another one for the same problem where we are waiting on your answers?
(https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?GroupId=1315&MessageKey=85f9d7d9-f358-4392-8991-df7d1f8c8a30)

[amar kondraju]

Hi Luc,

No worries. Please consider this one. Kindly answer the above queries that I have posted .

Reagards
Amar

[amar kondraju]

Hi Ravi,

I have followed steps 1 and 3 but step is not yet done. After 2 weeks again we have got this error : hub: nimSession - failed to connect session to HUBIP:48001, error code 10055. If I follow step 2 will there be any chance of remediating this error Ravi - please suggest.


1)
Upgrade to below from UIM hotfix index if running lower versions on Primary
hub_7.97HF6
robot_update 7.97HF9

2) Ensure Nimsoft folder excluded from AV scanning

3)If OS is Win 2012R2 check the dynamic port range for outbound communications is increased

netsh int ipv4 show dynamicportrange tcp



Regards
Amar

[Franklin Ravi D'souza]

Hi Amar,

As mentioned in KB  this is recommended so you can try with this

KB: Antivirus scanning of UIM components

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=137152

[amar kondraju]

Hi Ravi,

Thanks for the quick replies. I will try that step too and update .

Regards
AMar

[Garin Walsh]

It's worth your time to look into https://www.google.com/search?q=error+code+10055&rlz=1C1GCEU_enUS892US892&oq=error+code+10055&aqs=chrome..69i57j0l7.1343j0j8&sourceid=chrome&ie=UTF-8

Next time this happens, run "netstat -a -n > ports.txt" then look to see how many entries are in the file. 

It is also in your best interest to open a case with support.

One common place this can occur is if there is a firewall between the this hub and a system that's connecting to this hub which is terminating long running connections. SonicWall for instance will terminate the down stream side of hte connection but there's a number of defective versions of that product where they won't terminate the upstream side. As a result the client side keeps creating new connections but the server side is never notified to close th estale connections. Just a thought.

[David Michel]

Yes, most likely 10055 is a winsock error the OS is passing back to the application. 

Here is the MS doc page on it:
https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2

WSAENOBUFS 10055
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

------------------------------
Support Engineer
Broadcom
------------------------------

[amar kondraju]

Hi David,

For this 10055 - winsock error , kindly let us know what else we need to do . Other than these below steps anything else will resolve this problem? Please suggest.

As Ravi has suggested we have done with steps 1 and 3 but for step 2 we are following with our CISO/Infosec team to approve this exclusion of nimsoft folder .

1)
Upgrade to below from UIM hotfix index if running lower versions on Primary
hub_7.97HF6
robot_update 7.97HF9

2) Ensure Nimsoft folder excluded from AV scanning

3)If OS is Win 2012R2 check the dynamic port range for outbound communications is increased

netsh int ipv4 show dynamicportrange tcp

https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-tcpip-port-exhaust