Listed here are issues you may encounter when setting up or using ArcGIS Data Store. The links take you to possible solutions to each issue.
ArcGIS Data Store configuration
- I receive the message Could not connect to server on machine. ArcGIS Data Store or GIS Server on that machine may not be running or the machine is not reachable at this time.
- I receive the message Could not configure data store machine. ArcGIS Data Store and ArcGIS Server must be the same release version.
- I receive the message There is already a standby configured in the data store ('<primary data store machine name>'). A data store cannot have more than one standby machine.
- I receive the message Unable to create directory.
- When configuring a relational data store, I receive the message Failed to start relational data store database.
ArcGIS Data Store upgrade
General
- I receive the message Error: AGSDATASTORE variable is not set when I run an ArcGIS Data Store utility.
- The directory that contains my backups is consuming a lot of storage space.
- I receive the error message Could not connect to server on machine '<fully qualified machine name>'. ArcGIS Data Store or GIS Server on that machine may not be running or the machine is not reachable at this time.
- When running the deletebackup utility, I receive the error message: Attempt to delete backup 'backup_oneFS' is not allowed. You can only delete a manual backup that is not required for a future restore.
- When validating a spatiotemporal big data store in the ArcGIS Server Administrator Directory, I receive the message Server Machine returned an error. None of the configured nodes are available.
- I receive the message Failed to create the service: Underlying DBMS error [ERROR: cannot execute CREATE TABLE in a read-only transaction...] when I publish hosted feature layers to my portal, and I see the message Available disk space for the relational data store is less than 1024 MB. The relational data store will be placed in READONLY mode. Once you increase the amount of disk space on the drive, you can place the relational data store back in READWRITE mode. in the ArcGIS Data Store log file.
ArcGIS Data Store configuration
I receive the message There is already a standby configured in the data store ('<primary data store machine name>'). A data store cannot have more than one standby machine.
Only two machines are allowed to participate in a relational or tile cache data store: one primary and one standby machine. If you want to add a new standby machine, you must first remove the existing standby machine.
Possible reasons you would see this message include the following:
- The content directory you specified is already in use.
If you specify an existing directory, the directory cannot contain any files.
- You don't have privileges to create a directory in the specified location. Confirm that you have sufficient privileges.
- You specified a directory on a remote machine. The ArcGIS Data Store content directory cannot be stored on a machine that is remote from the ArcGIS Data Store installation.
When configuring a relational data store, I receive the message Failed to start relational data store database.
This message indicates the PostgreSQL database needed for the relational data store could not be created. There are many reasons for this; however, the most common is that the Data Store Configuration wizard or configuredatastore utility could not connect to PostgreSQL to create the database. Either the ArcGIS Data Store account does not have sufficient permissions on the ArcGIS Data Store content directory, or the PostgreSQL service (Windows) or process (Linux) could not start due to security settings on the machine. Confirm that PostgreSQL is running. If it is not, check if domain policies, firewall settings, or antivirus software settings prevented it from starting. If the PostgreSQL is running, confirm that the ArcGIS Data Store account has full control (read, write, and execute permissions) on the content directory.
ArcGIS Data Store upgrade
If my ArcGIS Data Store fails or I discover that, after testing my upgraded deployment, I have to revert to the previous software version, how do I restore my data stores to the previous ArcGIS Data Store version?
How you restore your data stores to a previous ArcGIS Data Store version varies slightly depending on the software version and the type of data store.
- Uninstall ArcGIS Data Store from every machine.
- Install the ArcGIS Data Store version to which you want to revert onto all machines. Do not proceed with configuration.
- Restore each type of data store.
- To revert to ArcGIS Data Store 10.5 or a later release, restore each data store using the restoredatastore utility and the backup file you created before upgrading.
- To revert to a 10.4.1 or earlier release tile cache data store, use the importmanagedb utility and the export file you created before upgrading to replace your tile cache data.
- To revert a spatiotemporal big data store to 10.4 or 10.4.1, follow these steps:
- Stop the ArcGIS Data Store service on every machine.
- Replace the content directory on each machine with the backup copies you created of the directories before upgrading. The default location of the ArcGIS Data Store content directory is /home/<username>/arcgis/datastore/usr/arcgisdatastore.
- Open the arcgis-data-store-config file in a text editor, remove the comment mark (#) from dir.data, and be sure dir.data is set to the location of your content directory. The arcgis-data-store-config file is located in the etc directory of the ArcGIS Data Store installation directory. By default, that location is /home/<username>/arcgis/datastore.
- Save and close the arcgis-data-store-config file.
- Restart the ArcGIS Data Store service.
General
I receive the message Error: AGSDATASTORE variable is not set when I run an ArcGIS Data Store utility.
The ArcGIS Data Store setup executable and Data Store Configuration wizard set the AGSDATASTORE variable to the directory where it installs ArcGIS Data Store. If you run the configuredatastore utility from the same command prompt in which you ran the setup executable, that command prompt session predates the existence of the variable and, therefore, will not recognize that the variable is set. Similarly, if you opened a command prompt before running the Data Store Configuration wizard, then tried to run any utility in the command prompt, you will receive this message because the command prompt session predates the existence of the variable. To solve this problem, open a new command prompt and run the utility.
The size of each data store backup varies depending on the amount and size of your data, how frequently ArcGIS Data Store creates backups, and how long you retain backup files.
For relational data stores, you can schedule how frequently backups are created and how long they are retained. If you use the default backup frequency and retention schedule, a backup directory will contain five full backups and 31 days of incremental backup files. If you find the backup directory uses a large amount of storage, either increase the disk space on the machine or alter the ArcGIS Data Store backup frequency and retention schedules.
If you configure a backup location for tile cache and spatiotemporal big data stores, you can also schedule how frequently backups are created. However, you are responsible for cleaning up tile cache and spatiotemporal big data store backup files when they are no longer needed.
I receive the error message Could not connect to server on machine '<fully qualified machine name>'. ArcGIS Data Store or GIS Server on that machine may not be running or the machine is not reachable at this time.
You could receive this message under a variety of circumstances but, in all cases, an attempt to connect to either the ArcGIS Data Store or its registered GIS Server site failed. Be sure both are available for connections. Also be sure the client from which you are trying to connect has network connectivity.
When validating a spatiotemporal big data store in the ArcGIS Server Administrator Directory, I receive the message Server Machine returned an error. None of the configured nodes are available.
You will see this message if you configured the spatiotemporal big data store with an ArcGIS Server site, used the remove function in the ArcGIS Server Administrator Directory to remove the machine from the site, and subsequently tried to register the same spatiotemporal big data store with the same or a different ArcGIS Server site.
The remove function is used for removing standby tile cache or relational data stores and should not be used to unregister a spatiotemporal big data store. Use the unregisterdatastore utility to unregister the spatiotemporal big data store from the ArcGIS Server site with which it was originally registered. This will cleanly unregister the spatiotemporal big data store from the site, and you can proceed with registering with the GIS Server used as the portal's hosting server.
I receive the message Failed to create the service: Underlying DBMS error [ERROR: cannot execute CREATE TABLE in a read-only transaction...] when I publish hosted feature layers to my portal, and I see the message Available disk space for the relational data store is less than 1024 MB. The relational data store will be placed in READONLY mode. Once you increase the amount of disk space on the drive, you can place the relational data store back in READWRITE mode. in the ArcGIS Data Store log file.
To prevent the loss of data, the primary relational data store is placed in read-only mode when the disk space of the machine on which it is running drops below a specific size. By default, that size is 1024 MB, but you may have changed this to a different size using the changedbproperties utility.
Once the primary relational data store machine is in read-only mode, you cannot publish hosted feature layers to the portal with which the relational data store is used. To take the relational data store out of read-only mode, add disk space to the primary data store machine, run the changedatastoremode utility to set the relational data store back to read-write mode, and run the updatebackupschedule utility to re-establish automatic backups for the relational data store.