Cannot Create a Version with the Specified Name?

[EdwardBlair]

OK.  I'm stumped.   I've got a branch versioned feature service from which I'm trying to create a new version as a child of SDE.Default.   Here's are the GP tool parameters:

and here is the error

there is no other version of this name in this database.   I don't know if there is an issue with the name provided ('TestVersion') or something else.  

Any thoughts or suggestions would be much appreciated.

Thx,

Ed

[EdwardBlair]

On the off chance that there might be another "TestVersion" lurking somewhere unseen in my database, I tried again with a version name I sure does not exist.   Same result:

[DavidPike]

Possibly lack of create privileges on the database?

[EdwardBlair]

David -

Thanks much for the suggestion.   I've considered this as well and I thought I had my bases covered, but maybe not.   I'm using SQL*Server.  Here are the permissions granted to my editor user:

- Server Roles:

- The schema containing the UN data is named GISADMIN.   I've granted my editor user SELECT, INSERT, UPDATE and DELETE on this schema.  Out of desperation I granted the same to the SDE schema.

- Also the editor user has the Enterprise user type "Creator"

If I'm missing something I would greatly appreciate any pointers.

Thx,

Ed

[EdwardBlair]

For what it's worth, I also tried assigning the editor user the User Type "ArcGIS Advanced Editing", and got the same result.

[EdwardBlair]

Walked through the steps with ESRI Tech Support.  Still stumped.   Here's what we observed/tried:

• We have a Branch versioned service published to ArcGIS Enterprise 11.2 from Utility network data in an enterprise geodatabase.
• We encounter the mentioned error when we create new versions on the service.
• Confirmed from the ArcGIS enterprise portal that the user with which we are connected to the portal in ArcGIS Pro has administrators privileges, has Advanced editing user type extension.
• From the server manager we confirmed that the service has version management capabilities enabled.
• We published a new service from the same data and observed that we encounter the same error message.
• We created a new polygon feature class in the enterprise geodatabase and registered it as branch versioned.
• We published yet another branch versioned service from the new feature class created with the version management capabilities enabled however when creating the versions encountered the same error message.
• From the server manager we observed that in the server logs we do not get any additional error rather the same error is mentioned there as well.

Tech support is going to research further.   Will post a resolution when we get to one.

Ed

[EdwardBlair]

So... suspecting that the issue was rooted in SQL*Server permissions, I granted additional permissions to all users involved and systematically checked in ArcGIS Pro after each change to see if this allowed the process to complete.   None of the permissions changes made a difference.

Then, at the suggestion of Jeff Buturff, master of all Geodatabase knowledge, I started SQL*Profiler before opening ArcGIS Pro with the hope of capturing the offending call.   

For whatever reason, after starting SQL*Profiler and then starting ArcGIS Pro I was able to create a new version without error.  I suspect that starting the profiler somehow put the previous permissions changes into effect -- but that's just a guess.  At any rate, I can now create versions.

Ed