Hi team, we are frequently getting the below Exception Message because of which we need to Re-install the local SOSS.Please suggest the solution for

"Message":"Unable to register AppId 12345 corresponding to AppName \"\/LM\/W3SVC\/2\/ROOT\/Services\" with StateServer: Unable to open a handle to the local StateServer service","StackTrace":" at Soss.Client.CallbackManager.RegisterAppId(UInt32 appId)\u000d\u000a at Soss.Client.StateServerKey.EnsureAppIdRegisteredForEventCallbacks(UInt32 appId)\u000d\u000a at Soss.Client.StateServerKey.AppNameToId(String appName, Boolean registerForEvents)\u000d\u000a at Soss.Client.StateServerKey.get_DefaultAppId()\u000d\u000a at Caching.CacheProviderFactory.GetCacheProvider()\u000d\u000a Caching.CacheManager.CreateInstance(String area)\u000d\u000a


The important text in that error is Unable to open a handle to the local StateServer service. There is no need to regularly reinstall the SOSS components. This error indicates that your client application was unable to communicate with any of the SOSS servers. This can be caused by multiple issues:
  • The local service isn't running,
  • The local service is running, but no hosts are actively joined to the store,
  • You have a remote client configuration that is not yet configured to communicate with any SOSS hosts, or all of the SOSS hosts are unavailable (see 1 and 2),
  • There is a firewall blocking communication between your client and server communication. Please ensure the svr_port (default: 720) and mgt_port (default: 721) on each SOSS host are open to receive TCP connections from your client, as well as the int_port (default: 722) between SOSS hosts.
Please verify that the SOSS service is running your your SOSS host, the service is an active state (i.e., "joined" to the store), and there is no firewall or routing misconfiguration blocking network communication between your client and the SOSS service.
I am also facing the similar issue from past two days in our environment. We have verified all the mentioned options in this thread , but we did not find any issues . Any other suggestions to dig further


Staff member
If this exception occurs out of nowhere then it's typically the result of a networking change in your environment.

On your client machines, open the soss_client_params.txt file and review the IP addresses in the remote gateway (rem_gw) entries listed there. For each IP address, use PowerShell's Test-NetConnection cmdlet to check connectivity to the server port (typically 721) on your ScaleOut hosts. For example:

Test-NetConnection xxx.xxx.xxx.xxx -Port 721
...where the IP is the address of a cache server. The "TcpTestSucceeded" result in the output will tell you if client machines can connect to the server port. If there's a failure then you'll want to check your networking and firewall setup and resolve any connectivity issues you find.