View the LRS hierarchy from the Location Referencing tab in the Contents pane or from the geodatabase node in the Catalog pane. If the LRS needs an upgrade, the (Upgrade) text appears next to it in the LRS hierarchy. Run the Modify LRS tool to upgrade the LRS. The operation can take several minutes. Find the version of the LRS Dataset to verify that the LRS has been upgraded.

The system requirements for Pipeline Referencing include the system requirements for ArcGIS Server; however, Pipeline Referencing is only supported on Windows Server platforms (not Linux or UNIX).

The memory (RAM), disk space, and processor power need to be adjusted based on the data volumes being worked with. In addition, the number of machines in the enterprise implementation need to be scaled to handle the number of concurrent requests being requested from the deployment.

When working with linear referencing data in Pipeline Referencing, it is recommended that you at least double the minimum RAM requirements specified by ArcGIS Server. This allows for some of the memory requirements needed by the ArcGIS event feature layer if you are publishing external event tables in your map services.

Learn more about ArcGIS Server system requirements

Yes. The Location Referencing toolbox automatically deploys with ArcGIS Server with most of the tools found in ArcGIS Pro. Refer to the list of tools that deploy with ArcGIS Server. You can also continue to publish geoprocessing tools as a geoprocessing service through ArcGIS Pro.

No, the Location Referencing Server license allows publishing services that use the Version Management and Linear Referencing capabilities.

Not directly. Event Editor was developed to edit the event data modeled in the geodatabase registered with Pipeline Referencing. The only way external event tables that are not modeled in the geodatabase can be edited with Event Editor is to create equivalent event feature classes in the geodatabase and register them with Pipeline Referencing. Event data could then be edited, but a process would need to be developed to move edited data from those event feature classes into the external event tables to provide the updates to the external system. You could also use the RelocateEvent REST operation to send updates to external events at regular intervals if creating copies in the geodatabase isn’t an option.

RCE supports the following browsers:

• Firefox
• Google Chrome

The Event ID, LocError, and ST_length fields are not editable.

Event Editor can't determine the single version name to display if you have at least one of the layers in a map service that was not versioned or if you have layers from multiple versions in a map service.

Ensure that all Pipeline Referencing and ArcGIS Server licenses haven’t expired.

There could be a number of causes. Confirm all of the following:

• The user has access to the web map.
• The map service with the Linear Referencing capability is running on ArcGIS Server.
• Pipeline Referencing is installed on all machines in the ArcGIS Server cluster hosting the map services with the Linear Referencing capability.
• The Event Editor config.json file is properly formatted (compare it in a file compare tool with the original version to ensure that the JSON syntax isn't corrupt).
• The web map configuration in the config.json file points to the correct web map.

Ensure that z-values is enabled on the redline feature class and that map services with the Linear Referencing capability also have the Feature Access capability enabled.