Unable to access standalone Server manager/Rest end.

[ArshiyaNisa]

Hi,
We have a standalone server which is not federated to Portal. The server was working fine till yesterday night and today when we are trying to open the server manager/ rest end points the server is not accessible. We had a scheduled Windows update done on the server.

Today when we are trying to access server manager/rest end points, we are getting the error as-

We have checked logs. It says RMI Registry is not running on port '1099'. And most errors relate to java.rmi. 

Below is some part of the log we have checked.

<Msg time="2026-04-16T14:26:33,791" type="SEVERE" code="6550" source="Admin" process="8104" thread="1" methodName="" machine="Domain_name.com" user="" elapsed="0.0" requestID="">Failed to start the server machine 'Domain_name.com'. java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [META-INF/services/javax.xml.parsers.DocumentBuilderFactory]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.</Msg>

<Msg time="2026-04-16T17:35:06,819" type="DEBUG" code="9999" source="Server" process="9260" thread="29" methodName="" machine="Domain_name.com" user="" elapsed="" requestID="">Failed to create class.</Msg>
<Msg time="2026-04-16T17:35:06,819" type="DEBUG" code="9999" source="Server" process="9260" thread="29" methodName="" machine="Domain_name.com" user="" elapsed="" requestID="">java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: 
  java.net.SocketException: Connection reset
  at java.rmi/sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
  at java.rmi/sun.rmi.server.UnicastRef.invoke(Unknown Source)
  at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Unknown Source)
  at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(Unknown Source)
  at jdk.proxy2/jdk.proxy2.$Proxy46.createService(Unknown Source)
  at com.esri.arcgis.discovery.admin.rediscovery.service.ArcSOCGISService.start(ArcSOCGISService.java:425)
  at com.esri.arcgis.discovery.admin.rediscovery.service.ArcSOCGPService.start(ArcSOCGPService.java:213)
  at com.esri.arcgis.discovery.admin.rediscovery.service.ReDiscoveryService$c.initReDiscoveryServiceThread(ReDiscoveryService$c.java:555)
  at com.esri.arcgis.discovery.admin.rediscovery.service.ReDiscoveryService$c.run$PANW(ReDiscoveryService$c.java:508)
  at com.esri.arcgis.discovery.admin.rediscovery.service.ReDiscoveryService$c.run(ReDiscoveryService$c.java)
Caused by: java.net.SocketException: Connection reset
  at java.base/sun.nio.ch.NioSocketImpl.implRead(Unknown Source)
  at java.base/sun.nio.ch.NioSocketImpl.read(Unknown Source)
  at java.base/sun.nio.ch.NioSocketImpl$1.read(Unknown Source)
  at java.base/java.net.Socket$SocketInputStream.read(Unknown Source)
  at java.base/java.io.BufferedInputStream.fill(Unknown Source)
  at java.base/java.io.BufferedInputStream.read(Unknown Source)
  at java.base/java.io.DataInputStream.readUnsignedByte(Unknown Source)
  at java.base/java.io.DataInputStream.readByte(Unknown Source)
  ... 10 more
</Msg>

We have also observed that every single time we start the ArcGIS Server in services.msc the ArcSOC.exe appears and disappears (gets killed) immediately on task manager. 

Question:

1.  What might be the root cause, does windows update trigger this?
2. Can we repair the ArcGIS Server in Programs and Features, will it be any help?

   Can anyone help us with this. 
   
   Thank you!

[George_Thompson]

I would contact technical support and work with them on this.

Were there any other updates pushed to the machine like: anti-virus / reporting / other security tools?

[ArshiyaNisa]

Hi George, Thank you for your response.

No other updates were done on the machine apart from Windows update. We will contact technical support and check it.

[ArshiyaNisa · Accepted solution]

We've created a support ticket and based on the recommendations provided, we reviewed the server configuration and identified missing SSL certificate alias values in the following files:

• config-store\machines<machine_name><machine_name>.json
  The WebServerCertificateAlias property was set to an empty string (""). Additionally, HTTPS was not properly configured in the ports section, preventing correct HTTPS binding.
• C:\Program Files\ArcGIS\Server\framework\runtime\tomcat\conf\server.xml
  The certificateKeyAlias attribute within the <Certificate> element was set to an empty string (""). This prevented Tomcat from identifying the appropriate certificate in the keystore located at:
  C:\Program Files\ArcGIS\Server\framework\etc\certificates\arcgis.keystore
  Fix Applied:
  Using the keytool utility available at:
  C:\Program Files\ArcGIS\Server\framework\runtime\jre\bin\keytool.exe
  We listed the keystore entries, identified the correct certificate alias, and updated the configuration files accordingly:
• Updated WebServerCertificateAlias in <machine_name>.json
• Updated certificateKeyAlias in server.xml
• Modified "webServerSSLEnabled": true in <machine_name>.json
• Added "HTTPS": 6443 in ports in <machine_name>.json
  Resolution:
  After applying the changes and restarting the ArcGIS Server service, the system resumed normal operation. All endpoints — Server Manager, REST Admin, and REST Services — are now accessible and functioning as expected.