With the changes in how new enterprise ArcSDE geodatabases are created in ArcGIS 10.1, I wanted to share a few tips on how to authorize your geodatabase when it is created, when it is upgraded, and when your license has expired.
Before version 10.1, the Post Installation Wizard allowed you to authorize enterprise geodatabases with an authorization file or by using the ECP registration number from the Customer Care Portal. If the registration number was used, the Post Installation Wizard had an option to register online, which validated the registration number with your customer information and populated the necessary system tables. At the 10.1 release, the Create Enterprise Geodatabase and Enable Enterprise Geodatabase tools require the .ecp file or the keycodes file for authorization.
Creating New Geodatabases
At ArcGIS 10.1, two new tools have been added to the Geodatabase Administration toolbox: Create Enterprise Geodatabase and Enable Enterprise Geodatabase. The Create Enterprise Geodatabase tool performs the geodatabase administrator creation, geodatabase creation, and authorization functions previously performed through the ArcSDE for SQL Server, Oracle, and PostgreSQL Post Installation wizards on Windows.
TIP: Within the Customer Care Portal you have access to the ECP registration number, but this format of the license information is not a valid input for the Create Enterprise Geodatabase tool. If you are an ArcSDE administrator and have been using ArcSDE for several releases you may be wondering where to get the correct file format for these new tools at 10.1. You’ll need to authorize ArcGIS Server first and use the keycodes file, or obtain a physical .ecp authorization file.
The Create Enterprise Geodatabase and Enable Enterprise Geodatabase tools’ Help documentation gives a summary of what is needed for the authorization file and the path that can be used to locate the keycodes file.
Examples of valid input for the Authorization File field in this tool include the keycodes file within the ArcGIS for Server Enterprise directory and the physical .ecp authorization file.
NOTE: You must have authorized ArcGIS Server to create the keycodes file ahead of time!
Upgrading Existing Geodatabases
If there is a valid license in the geodatabase when upgrading (Upgrade Geodatabase tool), you will not be prompted for this information. If the license has expired, you will be prompted to navigate to a valid license to update the database tables.
Expired Enterprise Geodatabase License
In the case of an expired geodatabase license, the geodatabase administrator is prompted with an Update ArcGIS Server License dialog box when making a database connection.
This tool guides you through updating the ArcSDE enterprise geodatabase license if it has expired. This populates the database server_config table with the updated license information.
Previous Tools from the Customer Care Site
The ArcSDE and ArcIMS Authorization Form on the Esri Customer Care site can still be used to convert your registration numbers to physical .ecp files if this is preferred; however, the keycodes file can be used interchangeably with the .ecp file.
Helpful Links
ArcGIS 10.1 for Server Enterprise Quick Start Guide (Including ArcGIS 10.1 Spatial Data Server and ArcSDE 10.1) > See the Authorize ArcSDE section
Melissa J. – Geodata Support Analyst
Hi Melissa,
We are running the Create Enterprise Geodatabase Tool and have navigated to the Authorisation file but receive the following error:
“Invalid license file provided. Please provide an ArcGIS for Server enterprise keycodes file.”
The Authorization file we navigated to matches the file location suggested in the tool help and is:
\\server name\Program Files\ESRI\License 10.1\sysgen\keycodes.ecp
Thanks in advance,
Chris
Chris – I would recommend you log a Support Services incident if you haven’t already. The issue could be the License file you are using and a Support analyst will be able to help you determine this. Please visit our support site http://support.esri.com and contact support.
NOTE: The KEYCODES file should not have an .ecp file extension. The only way you would have a file with the .ecp file extension if if you used the ‘ArcSDE and ArcIMS Authorization Form’ listed in the article above using the ECP# from the Customer Care Portal.
Hi Melissa,
What if you don’t have ArcGIS Server? According to the help on the Enable Enterprise Geodatabase tool, “You must have ArcGIS for Desktop (Standard or Advanced), ArcGIS Engine Runtime, or ArcGIS for Server Standard or Advanced installed” – which says to me that you don’t need Server to connect to an enterprise geodatabase. If you do not have ArcGIS Server, what should you put for the Authorization File?
Thanks,
Mel
Mel – I believe what the help is trying to say is that you have to be using one of the higher level Desktop licenses for the Enable Enterprise Geodatabase tools to work.You would also have to have an Enterprise license level for ArcGIS for Server Enterprise in order to authorize an enterprise ArcSDE geodatabase for use.
If you don’t have ArcGIS for Server Enterprise then you may be able to check with your Account manager in regards to if you have a Workgroup license or you may be able to take advantage of ArcSDE Personal. Determining which one you have a license for can be done through your account manager. These type of ArcSDE geodatabases are both installed with media that can be downloaded on the Customer Care Portal and do not use the create or enable enterprise geodatabase tools.
If you still have questions I would recommend contacting Esri Support Services at 888-377-4575 and they can certainly help with clearing up the differences.
10.1 – Types of geodatabases
http://resources.arcgis.com/en/help/main/10.1/index.html#//003n00000007000000
I had a similar problem when renewing the license in the geodatabase. I tried to access the geodatabase from ArcCatalog and was prompted to point out the license file. The problem was that the old license number that had expired was still in the file together with the new license numbers. When i removed the old information everything worked.