Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Core 2018.2 Port Exhaustion Issue - Server restarts required

Core 2018.2 Port Exhaustion Issue - Server restarts required

Updated 07/08/2018


You may come across an issue where you are having to restart services or even perform a full reboot of the server frequently to bring back your system to a stable state since upgrading the Orion modules to the latest platform (Core 2018.2) - Products such as NPM 12.3, SAM 6.6.1, NCM 7.8


The main symptom is port exhaustion, which may be concerning, especially if you have performed our recommended  Tweaking Windows Server Performance as outlined here.


You may also see services or processes consume 100% CPU even though you have checked the recommended specifications are in place as outlined in the Orion multi-module guidelines here.


Related Errors found within SolarWinds logs such as Information Service V3 / Job Engine V2 / Core Business Layer / Windows Event Log - SolarWinds.NET


[STP DatabaseProcessing Thread #1711] ERROR SolarWinds.InformationService.Contract2.InfoServiceProxy - An error occured opening a connection to the orion communication service.

System.InsufficientMemoryException: Insufficient winsock resources available to complete socket connection initiation. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)

   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

   --- End of inner exception stack trace ---


System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.) ---> System.ComponentModel.Win32Exception (0x80004005)



  • Modules running Core 2018.2
  • Windows Server 2012, 2012 R2 And 2016





  • This issue has been resolved in SolarWinds Orion Platform 2018.2 Hotfix 4
  • Please Note, If you were advised and changed the SolarWinds Information Service advanced setting to use "Buffered" prior to installing Orion Platform 2018.2 Hotfix 3 You can use the advanced setting to "Streamed" again.
  • This setting has a performance improvement over the alternative "Buffered" Transfer Mode.

Please change the SWIS transfer mode by performing the following steps:

  1. Log in to Orion Web Console using an account with administrative privileges.
  2. In the address field of the web browser, enter the following:
    http:// (your host name)/Orion/Admin/AdvancedConfiguration/Global.aspx
  3. Press Enter.
  4. Find "SolarWinds.Orion.InformationServiceClient" and change TransferMode to "Streamed"
  5. To apply changes please restart Orion services on all SolarWinds Servers.



Last modified