Enable Geodatabase and ArcCatalog Crashes

2443
8
Jump to solution
03-19-2014 11:35 AM
Highlighted
Regular Contributor
I am using ArcGIS 10.2.1 (Desktop and Server).

I created a new database in SQL Server 2008 R2. Then opened ArcCatalog and did "Add Database Connection". I am able to connect the database from within ArcCatalog. But, when I choose "Enable Geodatabase" ArcCatalog crashes, instantly closes. I also tried "Enable Enterprise Geodatabase" from within ArcToolbox, same result.

Any ideas on why I am not able to Enable Geodatabase?

Note that I already have enterprise Geodatabases successfully running on our Application Server Machine using SQL Server Express 2008 R2. Where I am having problems is with enabling the new enterprise
Geodatabase on our Test Server Machine.

ArcGIS for Server 10.2.1 is running on our Application Server with SQL Server Express 2008 R2. I want to create a new Enterprise Geodatabase on our Test Server (which does not have ArcGIS for Server or ArcGIS Desktop installed on it) on which is installed SQL Server 2008 R2.
Reply
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Regular Contributor
I figured out the answer, maybe. By right-clicking on the geodatabase - Geodatabase administration - Manage Users and Roles - I added myself as the dbo and sysadmin roles. Then I was able to enable enterprise Geodatabase.

The enterprise Geodatabase is now enabled. No more errors. It works.

View solution in original post

Reply
0 Kudos
8 Replies
Highlighted
Esri Esteemed Contributor
If you're getting crashes, you really ought to be talking with Tech Support.
The cause is likely due to database client configuration, so be sure to have
Native Client build information available when you call.

- V
Reply
0 Kudos
Highlighted
Regular Contributor
It no longer crashes. I was entering in the wrong instance, I misplaced a letter.

However, now I get this error message when I try to Enable Geodatabase.

I have full admin rights to the database and the schema name is dbo.
Reply
0 Kudos
Highlighted
Esri Esteemed Contributor
What does the setup log file contain?

- V
Reply
0 Kudos
Highlighted
MVP Regular Contributor
What does the referenced error log file contain?  Are you using the SDE user in your input connection file?  Make sure you have granted the correct privileges for the SDE user (I'm not sure if you are using SDE schema or DBO schema).  You might already have done that, but just in case you haven't, take a look at the Privileges to create or upgrade a geodatabase table from the link below:

http://resources.arcgis.com/en/help/main/10.2/index.html#//002q0000002s000000

To upgrade the geodatabase, the SDE user requires the following privileges:

  • CREATE FUNCTION

  • CREATE PROCEDURE

  • CREATE TABLE

  • CREATE VIEW


The SDE user must be added to the db_owner role in the database to upgrade.  Alternatively, the upgrade can be run by a user (other than sde) who is in the db_owner database role or sysadmin fixed server role.  The dbo user already has the required privileges to create a geodatabase inside a database.

EDIT: Looks like privileges might not be an issue since your screenshot says "User has required privileges for geodatabase setup".
Reply
0 Kudos
Highlighted
Regular Contributor
I am using the DBO Schema.

Here is a partial paste of the the sde_setup.log file says (the file is 7 pages long):

[Thu Aug 22 13:01:58 2013] DBMS stored procedures being created or updated...
[Thu Aug 22 13:01:59 2013] DBMS stored procedures created or updated...
[Thu Aug 22 13:02:00 2013]
Successfully installed ArcSde.
[Thu Aug 22 13:02:00 2013] Successfully created  GDB_Tables_Last_Modified table...
[Thu Aug 22 13:02:02 2013] Successfully created  GDB_Items table...
[Thu Aug 22 13:02:02 2013] Successfully created  GDB_ItemRelationships table...
[Thu Aug 22 13:02:03 2013] Successfully created  GDB_ItemTypes table...
[Thu Aug 22 13:02:03 2013] Successfully created  GDB_ItemRelationshipTypes table...
[Thu Aug 22 13:02:03 2013] Successfully created  GDB_ReplicaLog table...
[Sat Feb 15 10:46:12 2014] ArcSde is already at an acceptable release:10.1.0 
[Sat Feb 15 10:46:13 2014] DBMS stored procedures being created or updated...
[Sat Feb 15 10:46:15 2014] DBMS stored procedures created or updated...
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "A_PARTITION_RASTER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "A_PARTITION_ROWID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "A_PARTITION_SHAPE" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "A_PARTITION_STATEID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "A_PARTITION_USER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "A_PARTITION_XML" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "B_PARTITION_RASTER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "B_PARTITION_ROWID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "B_PARTITION_SHAPE" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "B_PARTITION_TO_DATE" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "B_PARTITION_USER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "B_PARTITION_XML" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "BND_PARTITION_COMPOSITE" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "BND_PARTITION_ID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "D_PARTITION_DELETED_AT" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:15 2014] WARNING: Config parameter "S_PARTITION_SP_FID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:46:17 2014] Upgrading instance to ArcSDE 10.2
[Sat Feb 15 10:46:17 2014] Old Release:    10.1.0 (101010)
[Sat Feb 15 10:46:17 2014] Upgrade Type:   instance
[Sat Feb 15 10:47:11 2014] ArcSde is already at an acceptable release:10.1.0 
[Sat Feb 15 10:47:11 2014] DBMS stored procedures being created or updated...
[Sat Feb 15 10:47:13 2014] DBMS stored procedures created or updated...
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "A_PARTITION_RASTER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "A_PARTITION_ROWID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "A_PARTITION_SHAPE" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "A_PARTITION_STATEID" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "A_PARTITION_USER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "A_PARTITION_XML" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "B_PARTITION_RASTER" not found in keyword "DEFAULTS".
  Inserting the default values.
[Sat Feb 15 10:47:13 2014] WARNING: Config parameter "B_PARTITION_ROWID" not found in keyword "DEFAULTS".
  Inserting the default values.
Reply
0 Kudos
Highlighted
Regular Contributor
I did the following test:

1) I already have ArcGIS for Server 10.2.1 and SQL Server Express 2008 R2 running on our Application Server Machine. On this same machine are 4 SQL Server Enterprise Geodatabases which are running no problems.

2) I created a 5th SQL Server Database (DBO Schema), then was able to successfully enable enterprise Geodatabase. No problems.

After this test, it appears that the problem is this:

1) The database I want to enable enterprise Geodatabase on resides on a different server machine, that does not have ArcGIS for Server installed on it. However, it does have SQL Server 2008 R2 (full version) running on it. But, with 10.2.1 this should not be an issue.

2) Unfortunately, this server machine is managed along with the SQL Server installed on it by our IT Dept. Whereas the Application Server Machine I mention above is managed by me in our GIS Group (Not in the IT dept, thank goodness). I have no idea what privileges our IT Dept provided me in the SQL Server Database other than what they told me this: "You are using DBO Schema with full editing privileges".

Do you think this problem of not being able to enable enterprise Geodatabase is an issue having to do privileges?
Reply
0 Kudos
Highlighted
Regular Contributor
I figured out the answer, maybe. By right-clicking on the geodatabase - Geodatabase administration - Manage Users and Roles - I added myself as the dbo and sysadmin roles. Then I was able to enable enterprise Geodatabase.

The enterprise Geodatabase is now enabled. No more errors. It works.

View solution in original post

Reply
0 Kudos
Highlighted
Occasional Contributor III
Hi,

your case is interesting.

in your logs...there are only "warning" messages regarding "DEFAULT" keyword defined in your dbtune. if possible can you fetch out the lines from the sde_setup.log  were it has the actual failure messages ?

and the snapshot you have provided does not indicate that you are facing a "privilege issue".

Thanks,
Reply
0 Kudos