ArcGIS Server has several processes that communicate among themselves. Therefore, the machine's IP address for the machine must be correct for those components to work. There are two ways to address this issue:

• Remove the entry in the hosts file for the machine.
• If the entry is needed for some other purpose required by your organization, update the IP address. To make these changes, superuser access is required. To obtain the current IP address, run the ifconfig command. Then, open /etc/hosts in a text editor and either delete or modify the line.

ArcGIS Server is a data-intensive server product, and many of its data formats consist of hundreds of thousands of files. In heavily used systems, thousands or tens of thousands of files may be in use at any given time. If there are insufficient file handles and processes, requests may start failing randomly, leading to system downtime. The actual number of file handles and processes needed varies based on the data and the number of instances (threads/processes) running. Setting a file handle limit of 65,535 and a process limit of 25,059 will allow you to ensure that the system remains running.

There are soft and hard limits for file handles and processes on Linux. To determine the hard limits, use the ulimit -Hn -Hu (or limit -h descriptors if you're using csh) command. To determine the soft limits, use the ulimit -Sn -Su (or limit descriptors if you're using csh) command.

To increase the soft and hard limits, you'll need to edit the /etc/security/limits.conf file with superuser access. For example, you can add four lines in the file as follows:

<ArcGIS Server installation user> soft nofile 65535

<ArcGIS Server installation user> hard nofile 65535

<ArcGIS Server installation user> soft nproc 25059

<ArcGIS Server installation user> hard nproc 25059

After making this change, you'll need to log out and log back in with the particular user for the new values to take effect. To verify that the limits have been modified appropriately, use the ulimit -Hn -Hu and ulimit -Sn -Su commands as described above.

When you uninstall ArcGIS Server, some folders and files are left on disk. These are left for your convenience if you reinstall or upgrade the product. If you don't plan on reinstalling, you can delete these files.

You might notice persisting files located at <ArcGIS Server installation directory>/arcgis/server/usr that include the following:

• server directories
• config-store
• log files

Leaving these folders preserves map caches, your installation configuration, and other server resources that you might want to keep if you reinstall. Server directories that you created and registered on your own are also not affected by uninstalling.

If you receive a message about your license being expired, contact Esri Customer Service to obtain a new license and reauthorize ArcGIS Server using the ArcGIS Software Authorization Wizard.

If you are in a highly secure environment, you should restrict file permissions to the configuration store, and disable the primary site administrator account. Performing these two tasks ensures that the primary site administrator account password reset script will have no effect on the security of your site.

To learn more, see Best practices for configuring a secure environment.

If you have multiple machines participating in your ArcGIS Server site, the site requires the network to function.

If you have a one-machine deployment—that is, one machine participating in an ArcGIS Server site—ArcGIS Server will operate correctly when disconnected from the network as long as all the data referenced by your GIS services are stored locally on that machine. Additionally, if the machine is part of a domain and you have disconnected the computer from the domain, you must specify a local account as the ArcGIS Server account.

If your server administrator has configured the Web Adaptor to block administrative access to the server, you will not be able to connect to the server in ArcGIS Desktop through the Web Adaptor URL using an administrative or publisher connection. Alternatively, you can connect directly to the GIS server in ArcGIS Desktop by using the URL format https://gisserver.domain.com:6443/arcgis. For more information, see Connect to ArcGIS Server from ArcGIS Desktop.

Yes. ArcGIS Server will automatically detect a machine name change and reconfigure your site to use the new name. After you use your operating system's tools to rename the machine, you may see the following message in the server logs:

ArcGIS Server has detected that the server machine [old machine name] has been changed to [new machine name]. ArcGIS Server will be updated automatically to use the new host name.

Depending on your site deployment, you may need to perform some additional steps to ensure that your site is configured properly to use the new machine name:

• If you've enabled HTTPS for your site and your certificate was using the previous machine name, you'll need to generate a new certificate and configure your site to use it. For full instructions, see Enable HTTPS on ArcGIS Server.
• If you've configured ArcGIS Web Adaptor to use your previous machine name, you'll need to configure it with a new URL that uses the updated machine name. For full instructions, see Configure ArcGIS Web Adaptor after installation.

The files generated by ArcGIS Server at run time are only accessible by the account running ArcGIS Server. To change the access permissions of the files generated at run time (for example, server logs), you'll need to set the user file mode creation mask (umask) in the init_user_param.sh script. To edit this script, navigate to the <ArcGIS Server installation directory>/arcgis/server/usr directory.

• By default, umask is set to 077, which means that no other users can read or write data to the runtime files. This is sufficient for most private ArcGIS Server systems.
• If umask is set to 022, it allows only the account running ArcGIS Server to read and write data. However, anyone on the system can read the data.
• Setting umask to 002 is a good option when the account running ArcGIS Server shares data with other users in the same group. Keep in mind that members of the group in which the account running ArcGIS Server belongs to can also create and modify data files. Those outside of the group are not allowed to create and modify data files.
• Setting umask to 007 completely excludes users who are not group members of the account running ArcGIS Server.

You'll need to restart ArcGIS Server immediately after modifying access permissions for your changes to take effect. Keep in mind that once you modify the umask setting to a value other than 077, you have altered the access permissions of all the files created by ArcGIS Server at run time.

After disabling HTTP-based communication, you will be unable to access local help documentation from the installed shortcuts since they are configured to use HTTP in their URLs. As a workaround, you can manually modify the shortcuts to use HTTPS. Keep in mind that this only applies to local help resources, not content hosted on the web by Esri.

The Hardware Configuration resource in the ArcGIS Server Administrator Directory displays hardware information for the specified machine in your ArcGIS Server site, giving the specifications of the CPU and operating system, amount of system memory, and number of physical and logical processors. It updates the information when it detects any changes to the configuration of your machine, as well as each time the machine is restarted.

These errors can appear if the database client software or libraries are not found on the server machine. Each machine in your ArcGIS Server site must have the 64-bit version of the database client software installed to allow ArcGIS Server to access the database. You must install these clients before you can register your database with ArcGIS Server. See Database clients for more information.

Once you have installed the client software, restart ArcGIS Server.

By default, ArcGIS Web Adaptor checks the site for new or unavailable machines every minute. If you've waited over one minute since a machine was added, removed, or disabled, and the Web Adaptor still doesn't recognize the changes, it could be because you changed the properties of the user who originally registered the Web Adaptor with the site.

For example, if the account used to register ArcGIS Web Adaptor with the site was disabled, the password changed, or the role type was demoted to a role that does not have administrative privileges, the Web Adaptor will be unable to check the status of your site for new or unavailable machines. To fix this issue, you'll need to reconfigure the Web Adaptor. For full instructions, see Configure ArcGIS Web Adaptor after installation.

The plain text server configuration files that were used in ArcGIS Server 10.0 and earlier versions are no longer part of the server architecture beginning at version 10.1. You may find similar looking files in the configuration store, but these files are not intended to be manually edited, and you may severely disrupt your server's stability if you choose to directly modify them. Instead, you should use ArcGIS Server Manager to adjust your server properties. ArcGIS Server also exposes the ArcGIS REST API, which you can use to safely script changes to your server configuration. See Log in to Manager and An overview of scripting ArcGIS Server administration to get started.

The default location for the temp directory is <ArcGIS Server installation directory>/arcgis/server/temp. To specify a different temp directory, you will need to set the SERVER_TEMP_DIR variable in the init_user_param.sh script. To edit this script, browse to the <ArcGIS Server installation directory>/arcgis/server/usr directory. Remove the # sign in front of the SERVER_TEMP_DIR environment variable, and specify the location of a new temp directory. The location you specify must be accessible by the account that was used to install ArcGIS Server.

# -----------------------------------------------------------------------
# Modify this section to change the temp directory
#
# The default location for the temp directory is at
# <ArcGIS Server installation directory>/arcgis/server/temp.
# The specified directory needs to be accessible by the account
# that was used to install ArcGIS Server.
# -----------------------------------------------------------------------
#SERVER_TEMP_DIR=<Location_to_temp_directory>

For your settings to take effect in the init_user_param.sh script, you'll need to restart ArcGIS Server. To restart, run the startserver.sh script on each machine in the site.

You should not configure the Web Adaptor to work with both. A separate Web Adaptor should be configured to work solely with ArcGIS Server or Portal for ArcGIS.

If you encounter a failure when creating or joining an ArcGIS Server site, you can troubleshoot the issue by addressing the error messages reported in the create site or join site summary panel. Additionally, a log of the event is recorded on disk, located at <ArcGIS Server installation directory>/arcgis/server/usr/logs/<machine name>/server. The messages in the log can provide additional insight into what caused the issue. To view the log, browse to the logs directory and open the log in a text editor.

To log in to Manager, you must provide a user name and password that has been granted administrator or publisher privileges to the ArcGIS Server site. User names and passwords are case sensitive. You must provide the proper case to log in to Manager. Talk with your server administrator to find out which user name and password you should use. If you are the administrator, provide the user name and password that you specified when creating the site. For more information, see Logging in to Manager.

To have access to the best possible user experience, it is recommended that you use ArcGIS Server Manager in the latest versions of either a Firefox, Chrome, or Internet Explorer.

The ability to retrieve your Bing Maps key using Manager was removed beginning at 10.1. You should visit the My Esri website or contact your Esri customer service representative to find out about your key.

By design, ArcGIS Server Manager only shows you the file system of the local machine when browsing for a service definition file (.sd).

Since ArcGIS Server Manager is a web application, sign in to Manager on the machine containing the service definition file and publish.

At 10.6.1, a suite of resources and operations allow server administrators to locate, monitor, and intervene in asynchronous jobs being run by a geoprocessing service. Each of these are available by accessing the service's page in the ArcGIS Server Administrator Directory (URL format https://server:port/arcgis/admin/services/[<folder>]/<serviceName.serviceType>).

From the Jobs page, you can query for jobs that meet specific conditions, purge the queue of all jobs with a current status of NEW, SUBMITTED, or WAITING, and view statistics about the current jobs for the service.

From the page of a specific job, you can cancel the job if it currently carries a status of SUBMITTED or EXECUTING (keeping the job information in the system), or delete the job regardless of current status, which will remove all trace of it from the service and cancel the job if applicable.

GIS resources that you attempt to publish to ArcGIS Server are put through a rigorous analysis process to make sure they are ready to be exposed on the web. Since you'll need to analyze your GIS resources before publishing, ArcGIS Desktop is the primary tool that you use to publish services to ArcGIS Server.

However, if you are in a cloud or highly secure environment, you can create service definition files that can be published to ArcGIS Server using Manager. Service definition files offer you a way to take a snapshot of your GIS resources and data and publish them to ArcGIS Server as services at a later time. Any GIS resource can be analyzed and encapsulated as a service definition file. Once the service definition file is created, you can browse to it in Manager and publish it as a service.

The ArcGIS Server installation comes with a variety of preconfigured services that help you do common tasks such as the following:

• Caching maps and image services (CachingTools, ReportingTools)
• Publishing services (PublishingTools)
• Printing web maps (PrintingTools)
• Performing geometric calculations (Geometry)
• Previewing the functionality of ArcGIS Server (SampleWorldCities)
• Synchronizing data between clients and ArcGIS Server (SyncTools)

Essential services, such as CachingTools, PublishingTools, and ReportingTools are started by default and cannot be deleted. Stopping these services would be detrimental to the performance and functionality of ArcGIS Server.

Nonessential services, such as Geometry and PrintingTools are stopped by default. If you need to use these services, you can explicitly start them in Manager or ArcMap. The SampleWorldCities map service is started by default and can be deleted at any time.

Keep in mind that server resources are consumed only when a service is started and requested to perform a task. For more information, see the preconfigured services section of What's included with ArcGIS Server.

If your web app references a service from a remote server (a different server from the one where your web app is hosted), the server hosting your web app needs to have permission from the remote server to access the service. Often, the server hosting your web app is the one installed with ArcGIS Web Adaptor, and the server hosting your services is a GIS server. If these two servers reside on different domains, the web browser plug-in running the web app is not allowed to access the service for security reasons. To access services across web domains, a client access policy file must be present in the root directory of the web server hosting the service.

If your server administrator has enabled security on your ArcGIS Server site, this file may need to be modified to include the domain of the server hosting your web app. For more information, see Restricting cross-domain requests to ArcGIS Server.

When any changes are made to the GIS resource referenced by a service, you'll need to overwrite the service so clients see changes to your GIS resource and its source data.

For instructions on how to overwrite your service, see Overwriting a service in ArcMap or Overwrite a web layer (in the ArcGIS Pro help).

ArcGIS Server only supports TrueType fonts and OpenType fonts. For fonts to be used successfully within a GIS service, the font must either reside on the server or the font must be embedded within the GIS resource. For example, most fonts can be embedded into a map document, but occasionally you may come across a situation in which a layer uses a font that is not embeddable. When you publish, a warning (20025) will display in ArcGIS Desktop indicating that the layer uses fonts that are not embeddable and are not on the server.

To address this issue, you'll need to install the fonts directly on ArcGIS Server. To so do, copy the fonts you want to use and place them in the <ArcGIS Server installation directory>/arcgis/server/fonts directory. Make sure the account running ArcGIS Server has read permission on the font files. For the changes to take effect, you'll need to restart ArcGIS Server.

Service definitions that contain source GIS datasets can take a long time to publish because the data must be transferred to the server. However, it is a known limitation that service definitions over 2 GB in size cannot be published when running Manager in the Internet Explorer or Firefox web browsers. Service definitions over 2 GB can be published when you run Manager in Google Chrome.

If you're unsure whether your service definition is over 2 GB, examine its properties immediately after you create it. If you didn't change the default staging location, the service definition will be in C:\Users\<user name>\AppData\Local\ESRI\Desktop<version number>\StagingFolder (on Windows machines).

If your ArcMap session is running in Layout View, the option to share the map as a service is unavailable. Switching to Data View will allow you to publish the map as a service. See Displaying maps in data view and layout view.

If the data referenced by your GIS resource resides in a Windows file share, you may encounter the following error in ArcGIS Desktop when publishing:

Packaging succeeded, but publishing failed. ERROR 001369: Failed to create the service.

This failure may result from opportunistic locking, or oplocks, which is a Windows file-locking feature. When oplocks are enabled for your designated file share, the Windows machine is allowed to cache files locally. Usually, this is the machine that is being used to publish the service. If a second machine needs access to the data, it must receive an oplocks break from the Windows machine before the file is synchronized back to the second machine. Usually, this is the machine that the service is being published to. If a break is received by the Windows machine during publishing, the subsequent data synchronization may cause publishing to fail.

Other common issues related to opportunistic locking:

• A machine or machines in your multi-machine site enables locks on the config-store and directories, preventing other machines from accessing them.
• Publishing failures due to the reasons described above
• Issues accessing registered data in shared locations
• Issues accessing cached tiles stored in locations with oplocks

To work around these issues, you'll need to disable oplocks for each file share you have configured.

For more information about oplocks, see Opportunistic Locks in the Microsoft documentation.

If the data referenced by your GIS resource resides in a Samba directory, you may encounter the following error in ArcGIS Desktop when publishing:

Packaging succeeded, but publishing failed. ERROR 001369: Failed to create the service.

This failure may result from opportunistic locking, or oplocks, which is a Windows file-locking feature. When oplocks are enabled in a Samba directory, the Windows machine is allowed to cache files locally. Usually, this is the machine that is being used to publish the service. If a second machine needs access to the data, it must receive an oplocks break from the Windows machine before the file is synchronized back to the second machine. Usually, this is the machine that the service is being published to. If a break is received by the Windows machine during publishing, the subsequent data synchronization may cause publishing to fail.

To work around this issue, you'll need to disable oplocks for each Samba directory you have configured. To do so, follow these steps:

1. On the machine hosting Samba, open smb.conf.
2. For each directory configured to be accessible through Samba, add the following properties:

   [folder]
        ...
        oplocks = false
        level2 oplocks = false
        ...

3. Save smb.conf.
4. Run the command testparm to verify that the properties appear in the Samba configuration file.
5. Restart Samba (SMB) and NetBIOS (NMB) services.

For more information about oplocks, see File and Record Locking in the Samba configuration documentation.

Using ArcGIS Server, you can publish Web Coverage Services (WCS), Web Feature Services (WFS), Web Map Services (WMS), Web Map Tile Services (WMTS), and Web Processing Services (WPS). Additionally, you can configure map services to return Keyhole Markup Language (KML) if requested.

Learn more about OGC support in ArcGIS Server

To understand how to configure the correct permissions required for database and geodatabase data, see Make your data accessible to ArcGIS Server.

The amount of time needed to create your map cache depends on the scale levels you have chosen, the amount of server resources you have dedicated to generating the cache, and the settings you have chosen (tile format, storage format, and so on). These factors are discussed in detail in Plan a map cache.

If you update an area of a map cache, users of ArcMap and ArcGIS Pro who have already visited that area and extent must clear their local image caches before they can see the updates. As a server administrator, you need to alert your users when updated data is available so that they know to clear their caches. Consult the help system for your client application for instructions on how to clear the local cache.

The error message is for error code 001862: Publishing of geoprocessing services is restricted to administrators only. Beginning at 10.4, only administrators can publish geoprocessing services and deploy service extensions (SOEs or SOIs). This restriction can be changed by an administrator. See Change geoprocessing service and service extension publishing privileges for details.

If the tile cache data store is configured to use SSLv3 encryption, but the machines in the hosting server do not have SSLv3 enabled, this message will be returned when a user publishes a scene layer from ArcGIS Pro or the ArcGIS Enterprise portal.

To resolve this, you can either enable SSLv3 on all the machines in the hosting ArcGIS Server site or, if your security practices to not allow for this, have the ArcGIS Data Store administrator disable encryption on the tile cache data store. See ArcGIS Data Store command utility reference in the ArcGIS Data Store help or the Portal for ArcGIS Administrator Guide for information on disabling SSLv3 encryption on the tile cache data store.

If you decide to enable SSLv3 on the hosting server machines, consult your Linux operating system documentation for instructions on how to do that.