Error loading versions

10-07-2013 03:43 PM
New Contributor II

I have just upgraded to 10.1 and orginally I had editing rights to the an SDE connection (which has not been upgraded) but now when I select the version manager, nothing happens. ?  Also, when i select the change version I get the following error: "Error loading versions. [An item with the same key has already been added.]

Are these errors the result of an incompatability between 10.1 and 10.0 with regards to database connections? Is there some other reason that would cause this?

0 Kudos
2 Replies
Occasional Contributor III
can you please clarify ......what is your ArcGIS Desktop version you are using and what is the version of your geodatabase ?

Remark: if you are using ArcGIS 10.1 Desktop create a fresh new connection (don't use the previously stored 10.0 connection).
0 Kudos
New Contributor II
I was upgraded from 10.0 to 10.1.

The error message that I was having, was related to a need for a service pack. Specifically, I have a (.) in my user name. This may have been the cause of the error.

Here is what I found on the following site:
04/25/13 �?? Issues when SQL Server user names contain special characters such as a dot (.) or a hyphen (-).(Patch Available)

Product(s) Affected:

ArcGIS for Desktop, ArcGIS Engine, ArcGIS for Server


10.1 SP1

Bug ID's:

NIM082739 - Failure to create a new layer or table, access an existing one, or add it into ArcMap if the SQL Server user name includes a dot (.), hyphen (-) or any other character that requires delimiting.

NIM082947 - Cannot modify or delete a version created by a user with a dot (.) in the user name.

NIM083805 - ArcGIS Desktop is unable to connect to the geodatabase version if the username of the owner of that version contains a dot (.).

NIM088882 - SQL Server only: An error is encountered when creating a child or grandchild version when the version owner has a dot (.) in their name.

NIM089772 - If the connected user's name contains a dot (.), copy-paste of a feature class can fail with a 'Column Index Already Exists' error.

Knowledge Base Article:



Released 04/25/13