ArcPro says "user is not data owner" but I know it is

1372
5
Jump to solution
01-27-2023 04:38 AM
BryanPrice
New Contributor III

 Hopefully you can point me in right direction. 
Environment: ArcPro 3.0.3 connecting to SQL 2019 enterprise geodatabase ver 11.0.0.3.0

I have had a user called stclairGIS that has been data owner for years. Example of a dataset in question here (but its happening throughout database) is listed in cataloge as  <STCLAIRGIS.MiscellaneousAnno100>  but when I go to manage, it says its not data owner (see attachment) im at a loss as to how to "reassert it as owner" if thats even a thing.

This is preventing me from upgrading annotations , calculating statistice, reindexing etc...

ExampleForDan.png

0 Kudos
1 Solution

Accepted Solutions
BryanPrice
New Contributor III

I FOUND IT !!!!  - I FOUND IT !!!! - I FOUND IT !!!!

In SSMS for that user Server Roles , I had processadmin checked. When I unchecked it, this resolved my problems.

Thanks a million for kick starting my brain!

View solution in original post

5 Replies
George_Thompson
Esri Frequent Contributor

Can you provide a screen shot of your connection properties?

When was the last time that this worked for you?

--- George T.
0 Kudos
BryanPrice
New Contributor III

Thanks for your time on this George, 

My automated nightly processes use this user's connection and so I can't say exactly how long, but we'll say a couple of weeks , I believe (?) it was around the time I upgraded the enterprise geodatabase "CurrentYr" to ver 11.0.0.3.0

0 Kudos
George_Thompson
Esri Frequent Contributor

Thanks for that information. That is weird behavior.

Does that user have "dbowner" role in SQL Server? Or did the permissions get changed during the upgrade?

Can you create a new feature class (empty) without any issues?

In the connection, can you put the username in ALL CAPS?

Random question: Are you using Pro Basic license?

Is the annotation versioned? (https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/upgrade-dataset.htm)

Thanks!

 

--- George T.
BryanPrice
New Contributor III

I FOUND IT !!!!  - I FOUND IT !!!! - I FOUND IT !!!!

In SSMS for that user Server Roles , I had processadmin checked. When I unchecked it, this resolved my problems.

Thanks a million for kick starting my brain!

George_Thompson
Esri Frequent Contributor

That could cause it. Glad you found out the issue.

--- George T.
0 Kudos