Cases and solutions where ArcGIS Server cannot be started and services cannot be accessed

Server cannot be started

Problem Description

        When the server reads the disk abnormally, a new service is published, and the service cannot be accessed at this time.

        After restarting the Server service, it was found that the Server could not be started. After restarting the server machine, this problem could not be solved, and it still could not be started, and the following information appeared in the Server log file. 

Problem Cause and Solution

        Checking multiple logs found that no other problems were found, so go to the Server installation directory and enter the directory

        C:\Program Files\GeoScene\Server\framework\etc下

        Find   the machine-config.xml   file , open it directly with a browser and find that it cannot be opened.

        After opening it with a text editor, it was found that the format of the file was messed up, which made it impossible to start.

        It can be started normally after being modified to a normal xml file. It is not possible to determine whether the format is normal. You can check the corresponding xml file on a normal Server machine.
 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Machine>
  <MachineName>WIN1022（机器名）</MachineName>
  <Platform>Windows Server 2012-amd64-6.2（操作系统）</Platform>
  <Ports>
    <JMXPort>4000</JMXPort>
    <OpenEJBPort>4001</OpenEJBPort>
    <NamingPort>4002</NamingPort>
    <DerbyPort>4003</DerbyPort>
    <HTTP>6080</HTTP>
  </Ports>
  <WebServerMaxHeapSize>-1</WebServerMaxHeapSize>
  <webServerSSLEnabled>false</webServerSSLEnabled>
  <webServerCertificateAlias/>
  <AppServerMaxHeapSize>256</AppServerMaxHeapSize>
  <SocMaxHeapSize>64</SocMaxHeapSize>
  <WebServerMaxHeapSize>-1</WebServerMaxHeapSize>
</Machine>

The service cannot be accessed after the server starts

Problem Description

        As mentioned above, the machine cannot start the server service because of  the disordered machine-config.xml  file. After modification, restart the server

        But at this time, it was found that although the service was restarted, the service could not be accessed, and a 500 error occurred. All service accesses are like this

solution

Check the arcgisjobregistry.json   file         under the Server directory E:\geosceneserver\config-store\serverdirs  

    The following is the json file under normal circumstances. If there is an error, just restart the service after modifying it according to the version

{"name":"arcgisjobregistry","physicalPath":"E:\\geosceneserver\\directories\\geoscenesystem\\arcgisjobregistry","directoryType":"JOBREGISTRY","cleanupMode":"NONE","maxFileAge":0,"description":"存储由 GIS 服务器内部使用的文件。","useLocalDir":"false","localDirectoryPath":"","virtualPath":"/rest/directories/arcgisjobregistry"}