topic Re: Why is ArcGIS Pro using old data in ArcGIS Pro Questions

Why is ArcGIS Pro using old data

WillPlatt — Mon, 30 Jul 2018 18:54:37 GMT

When I try to change the symbology for a polygon layer, ArcGIS Pro 2.2.0 is using old values that don't exist anymore and ignoring new values. In the attached screen show, when I add all the Values for the field called "Type" it is symbolizing values like "Overhead Fiber" and "Road" and the misspelled "Tranmsission". These values no longer exist in the data. Also, in the data there are values "Access" and "Commitment" that ArcGIS Pro does show as a value. It seems like ArcGIS Pro is using using some old cached version of the data. I have tried deleting all the cache files in C:\Users\XXXXX\AppData\Local\ESRI\Local Caches. That didn't work. I'm stuck. It works perfectly fine in ArcMap.

Thanks for any help you can give.

Re: Why is ArcGIS Pro using old data

MichaelVolz — Mon, 30 Jul 2018 19:06:05 GMT

What is the source for the problematic data?

Did you originally see these values that included the misspelled value in Pro and then made the change in the datasource but Pro is unable to show the edited values?

Re: Why is ArcGIS Pro using old data

WillPlatt — Mon, 30 Jul 2018 19:21:20 GMT

The source is a versioned polygon layer in a Microsoft SQL database. The version has been edited and reconciled and posted numerous times since that old data was there. It has probably been a year since I last saw those old values in ArcMap (my primary software).

I did originally see these values in ArcGIS Pro. I tested Pro a little bit about a year ago but stayed with ArcMap for my primary software doing all of my editing with it. I recently started testing Pro again since we recently upgraded our Microsoft SQL and ArcGis Servers.

Re: Why is ArcGIS Pro using old data

MichaelVolz — Mon, 30 Jul 2018 19:23:29 GMT

Are those values tied to domains?

Re: Why is ArcGIS Pro using old data

WillPlatt — Mon, 30 Jul 2018 19:25:22 GMT

No, they are not. It is just a Text field.

Re: Why is ArcGIS Pro using old data

MichaelVolz — Mon, 30 Jul 2018 19:28:47 GMT

Did you create the aprx from an mxd by using the import mxd process?

Or did you create the aprx from scratch? If so, are you using connection files that were created a year ago in your previous version of Pro that you were testing? If you were using old connection files, I would create new connection files in Pro 2.2.0 and then see if the old values still show up.

Re: Why is ArcGIS Pro using old data

WillPlatt — Mon, 30 Jul 2018 19:38:57 GMT

I just started a blank ArcGIS Pro document. I add the database and then add the layer. I am using the connections that I made to the new SQL database using ArcCatalog 10.2.1. That connection is located in this folder C:\Users\XXXX\AppData\Roaming\ESRI\Desktop10.2\ArcCatalog correct? The data is in a new database so the old connections that Pro had wouldn't work.

Thanks for the help, Michael, I really appreciate it.

Re: Why is ArcGIS Pro using old data

WillPlatt — Thu, 02 Aug 2018 13:52:40 GMT

OK, I figured it out! I reconciled and posted the version of the database, then deleted the version. When I tried to compress I got an error like "arcgis failed to compress the database error 08S01 microsoft sql server native client 11.0 tcp provider and existing connection was forcibly closed by the remote host". I looked online and this happened to people who had upgraded to a different version of SQL server like we had done. So the answer was to go into ArcToolbox>Data Management Tools>Geodatabase Administration>Rebuild Indexes. However, when I tried with the DBO account the re-indexing failed. I tried with another SQL account and it work. I then was able to compress the database. After the compression the data and symbology was fixed.

Hope this helps anyone else that runs into this problem.

Thanks

Re: Why is ArcGIS Pro using old data

MichaelVolz — Thu, 02 Aug 2018 14:01:40 GMT

One question on your troubleshooting discovery. Is the DBO account supposed to be able to rebuild indexes? If this account has those privileges, then you might want to bring this item to ESRI's attention.

Can you see if the DBO account can rebuild indexes in ArcMap, so you can show ESRI that this functionality works in ArcMap but not in Pro (You have to test to determine if in fact this is the case as I don't know if the DBO account is supposed to have those privileges)?

Re: Why is ArcGIS Pro using old data

WillPlatt — Thu, 02 Aug 2018 14:27:38 GMT

From what I understand about the SQL database, the DBO should be able to do anything to the database. It is a database level account. I am going to talk to my database admin and see why the DBO couldn't do it but a user level account could.

I rebuilt the indexes through ArcToolbox from ArcCatalog so I would assume I would be able to do it in ArcMap as long as I chose the correct connection.

I have not attempted any kind of database administration in Pro. I will look into how that is done and give it a try.

Thanks Michael

Re: Why is ArcGIS Pro using old data

JonathanFarmer_oldaccount — Thu, 02 Aug 2018 14:57:58 GMT

Hi Will,

Esri's best practices for geodatabase administration are to have the SDE user (or the user that your organization has dubbed the Geodatabase Administrator user) perform these tasks. This is assuming that your geodatabase is an SDE schema geodatabase. Is that the case here?

If you are working with a DBO schema geodatabase, then you can use a database user that is a member of the DBO schema to perform these tasks. That being said, a database user that is a member of the DBO schema, even in an SDE geodatabase, has the privileges to administer the geodatabase should you choose to do that.

Here is a look at Geodatabase owners in SQL Server and the Pros and Cons: A comparison of geodatabase owners in SQL Server—Help | ArcGIS Desktop

We will always recommend that you guys use the least privileges principle when working with the geodatabase. At the top is the Database Administrator user (the SA user or member of the sysadmin fixed server role in SQL Server). They can do everything but really should be limited to 1 or 2 people in your organization and not used for geodatabase administration tasks. Then there is the Geodatabase Administrator user (the SDE user) which handles all the admin tasks such as what you are doing here. Then Data Owner roles which can create and own new data. Then Data Editor roles which can edit existing data. The Data Viewer roles which can only view data.

Hope that helps a little. Let me know if I can clarify anything.

Jonathan