Esri Keycodes File

[Vickey Melling]

Loremipsum dolor sit amet, consectetur adipiscing elit. Suspendisse suscipit sapien ac sapien malesuada fringilla. Fusce venenatis, mauris id sagittis dapibus, mauris velit sollicitudin ante, a pulvinar leo orci vel erat. Nam mattis erat augue, at luctus ex dignissim et. Donec suscipit, dui at efficitur tristique, nulla nisi ornare lorem, vel dictum lectus eros nec felis.

When authorizing an enterprise geodatabase on an ArcGIS Server instance, a keycodes file is required to complete the authorization process. As the keycodes file is generated during the authorization process, in some instances, when access to an ArcGIS Server instance is unavailable, the authorization process cannot be completed. For example, when a different machine is used for the authorization, or when the server is unavailable.

Procedure Follow the steps below to complete the software authorization process, and generate a new keycodes file to authorize an enterprise geodatabase when an ArcGIS Server instance is unavailable.

So I want to create a new SDE GDB. The issue I am having is how to enter the path to my keycodes properly. I keep getting back the invalid file location error message. The keycode file is located on our gis server on the C drive. How do I represent the "C" in my file path in the tool so that it finds my keycode. Our IT people showed me once and I forgot.. I thought it was using $ or this %.

The Create Enterprise Geodatabase, Enable Enterprise Geodatabase, and Update Enterprise Geodatabase License tools require browsing to an ArcGIS Server authorization file called a keycodes file. On Windows, this is found in the following folder:

Cause This expected behavior is due to changes introduced to the ArcGIS Pro 2.5 Browse dialog. These changes prevent ArcGIS Pro from being able to browse to files without extensions.

When ArcGIS Server is authorized, the keycodes file is automatically created without a file extension, and therefore it is unable to be recognized by the Browse dialog. Adding the extension during the creation of the keycodes file is being considered for a future release.

The behavior was corrected at ArcGIS Pro 2.5.1. Updating ArcGIS Pro to 2.5.1 or a later release will resolve the issue.

Previously, the following workaround could be used at ArcGIS Pro 2.5:

Until the keycodes file is generated with a proper file extension, the following workarounds can be used:

I've already posted more or less the same question at esri's GeoNet Forum, but until now I have got any response. As my license will expire shortly, the is my second try to get some information before license-expiration.

Last year, I have struggled with the some problems with my enterprise geodatabase after my license expired.

My current licenses will expire after the 29th of September (so in 1,5 hours) but I have already a new license-file for the next year.For the license-update process, I would perform the following steps:Using the license-file and the ArcGIS Administrator I'll authorize my ArcGIS Server instance including the GeoEvent Processor.

To avoid problems with my enterprise geodatabase: Are there any additional steps, which I have to perform (like inject the license key directly in my database)?!

And what's about my GeoDatabase-Connection from my personal computer to the enterprise geodatabase? Do I have to establish a new connection using a "new generated" keycodes file?

Enterprise geodatabases are licensed through an ArcGIS Server authorization file. With an ArcGIS Enterprise (or ArcGIS Server basic) license, you can create or enable an enterprise geodatabases in ArcGIS Pro.

If your organization licenses ArcGIS Server for a set time period using a term license, the license is subject to expiration and must be updated manually on the machine hosting ArcGIS Server as well as the related enterprise geodatabase.

Your geodatabase administrator should update the enterprise geodatabase with a new ArcGIS Server authorization file to update the license information in the enterprise geodatabase before the existing license expires. This allows clients to continue working with the geodatabase without interruptions caused by expired licenses.

If the license of an enterprise geodatabase is left to expire, ArcGIS Pro users will see an error message when attempting to connect to the geodatabase. The error message instructs users to contact their geodatabase administrator.

In ArcGIS Enterprise, web layers referencing data in the enterprise geodatabase will become unresponsive and fail to render in web maps. Severe errors messages will also be seen in the ArcGIS Server Logs as shown below:

When the geodatabase administrator (SDE user) attempts to connect to an enterprise enterprise geodatabase with an expired license, they will be prompted to provide the path to the keycodes file as shown below.

While this approach also updates the license of the enterprise geodatabase, it can lead to interruptions and downtime for users and services. It is therefore recommended to update the ArcGIS Enterprise license prior to the expiration date.

A week later one of our ArcGIS Server installations started having issues with the map services. Basically the map services, though running, stopped displaying the features that were in them. Looking into the error logs, we found stuff like this:

For this particular ArcGIS Server installation, I decided to setup the Enterprise Geodatabase inside PostgreSQL, store GIS data in it, and use the data for the map services. When I was setting it up I used the Create Enterprise Geodatabase tool. One of the parameters for the tool required me to provide a path to the keycodes file that was created when I authorized ArcGIS Server. I wonder if it is PostgreSQL?

Aha! I guess PostgreSQL does not automatically get updated when I update the ArcGIS Server license. I am running ArcGIS Server 10.2, so the keycodes file (named keycodes) is located under C:\Program Files\ESRI\License10.2\sysgen. After entering that and pressing OK, I had access to the Enterprise Geodatabase again. I then restarted the map services that access the Enterprise Geodatabase and all was well again!

3a8082e126