|
POST
|
Hi Joe, Yep, you and I worked together on that topology case. And, we recommend disconnecting all users and blocking new connections for a scripted rec, post, and compress process. So if it works that way, it would be the way we'd recommend to do it anyway. That being said, you should still be able to reconcile a version with users connected to the geodatabase but ideally they aren't using that same version you are trying to reconcile. I see the case you mentioned. It looks like that analyst has responded asking for a trace. Send them another round of intercepts that match up with the trace. This way, if they look at your intercept and see something interesting that happens at a certain time, they can look to the trace and see what is happening at that same time from the DB side. This is the way I'd ask you to do it. Jonathan
... View more
10-15-2018
08:07 AM
|
1
|
5
|
4570
|
|
POST
|
Hi Joe, The best way to find out what is happening here is to setup and run an SDE Intercept to look and see where the hanging in occurring. How To: Set up an SDEINTERCEPT log file on a client machine for ArcGIS Desktop and ArcGIS Server What you'll need to do once this is setup is run a reconcile of this problem version and compare it to a reconcile of a version that works fine. What you are looking for is the command that is occurring while or just before the hang occurs. This may be able to help you identify what the software is trying to do when it hangs. Tech Support can assist with this as well if you'd like to create a new case with them. I'd also check the following: Does the Reconcile Versions GP tool provide different results? Are there any problem edits in this particular version? Bad geometry or bad attributes? It may not be easy to find but we've seen this hanging behavior in these situations. If you delete this problem child version and create a new one for this user, do you get the same issue? Let me know if you have any questions. Jonathan
... View more
10-15-2018
07:23 AM
|
1
|
7
|
4570
|
|
POST
|
Ikbel, It sounds like you installed a stand-alone instance of SQL Server Express 2017 rather than going through the Setup a Database Server process in our documentation, is that right? I also want to make sure you are using ArcGIS 10.5.x or 10.6.x as those are the only 2 versions we support SQL Server Express 2017 on. Are you using one of those ArcGIS versions? Even with an instance of SQL Server Express installed, you need to run through the Database Server setup wizard to enable geodatabase storage on that instance. So you'll want to use the documentation I sent over before to do this. Under the heading "Start the Setup Wizard", you'll see this: "If you already have an instance of SQL Server Express installed that you want to use as a database server, uncheck the Microsoft SQL Server Express Edition option in the Installation Options dialog box and skip to Enable geodatabase storage; otherwise, proceed with SQL Server Express installation" So you'll want to skip the installation part and move to the enable geodatabase storage part. You won't be able to create a new SQL database using ArcGIS if you haven't gone through the workflow outlined in the documentation I sent over. Jonathan
... View more
10-03-2018
08:28 AM
|
1
|
0
|
1512
|
|
POST
|
Hi Ikbel, Are you attempting to setup a Desktop Database Server in ArcGIS? Are you going through the steps shown in the documentation below? If so, what step in the process are you seeing this error? Set up a database server—Database Server (Desktop) installation guide | ArcGIS Desktop What version of ArcCatalog are you working with (10.6.1, 10.5.1, etc) and what is your license level for ArcGIS Desktop (Basic, Standard, or Advanced)? Thanks, Jonathan
... View more
10-03-2018
07:12 AM
|
1
|
2
|
1512
|
|
POST
|
Hi Jay, Thanks for the response. It is certainly odd behavior. Both of those titles, while a little long, should work. Even if the title were an issue, it should have failed for your co-worker. I also don't see anything obvious in the x or y columns that would make ArcGIS think it is a mixed data type field (at least from the screen shot provided). The only other thing I can think of is that maybe you were not including row 1 as headers and they were being treated as values in the column itself? Would match up with the mixed data type issue that Tim mentioned. This may be one of those things we can't give a definite answer to without a reproducible case. Jonathan
... View more
10-02-2018
02:03 PM
|
1
|
3
|
2211
|
|
POST
|
Hi Jay, I'm not sure why you were seeing that behavior. You mentioned your co-worker renamed the file (presumably in file explorer since they did not do a save-as), what was the original name vs. the new name? Were there any spaces or special characters in the file name? Jonathan
... View more
10-02-2018
11:14 AM
|
0
|
0
|
2211
|
|
POST
|
Matthew, Thanks for this information. Given that we see some different behavior in ArcMap 10.3 vs. ArcGIS Pro and also because we appear to have some records in the database which may or may not be orphaned, I think we need to get a case created with Tech Support to troubleshoot further. Is this something you'd be open to doing? Jonathan
... View more
09-25-2018
08:05 AM
|
0
|
0
|
2615
|
|
POST
|
Hi Dongxing, You'll need to create a new case with Tech Support and then we can assist. Jonathan
... View more
09-20-2018
04:27 PM
|
0
|
1
|
8703
|
|
POST
|
Hi Dongxing, If you can't open the attribute table at all, then your issue should be separate from this bug. This is something that Tech Support should look into further for you. It could be something on our side or it may be something specific with your install. But they can help troubleshoot that with you. Jonathan
... View more
09-20-2018
03:45 PM
|
1
|
3
|
8703
|
|
POST
|
Josh, This issue has come up again here in Support and we are updating this bug a bit. But I want to confirm a couple of things with you because you've tested this on the latest Pro release. If you use the ez connect string with OS authentication, do you see the hang? What about if you use the ez connect string with database authentication? Is the hang present? Lastly, if you use database authentication with the ez connect string and chose to not save the username and password, do you see the hang? Thanks for testing this. I just want to make sure what we see here matches what you are seeing so we can update this bug as needed. Jonathan
... View more
09-20-2018
10:01 AM
|
0
|
1
|
3649
|
|
POST
|
Hi Matt, Just to confirm, the ProcessID for those 2 table locks does not exist in the process_information table? Does the ENGDUSTCONTROL feature class still exist in the database? This lock does not show up in the Geodatabase Administration dialog in ArcMap? We certainly don't want to go deleting everything from the locks table as some of those are valid locks. Actually, we never want to delete anything from the database but it does sound like you may have a couple of orphans here. My recommendation would be to take a full backup of this database and restore it into another SQL instance. This way no other users are connected or will connect and there are no services or replicas hitting this geodatabase. You can then make sure that no locks or connections exist in the Geodatabase Administration dialog in ArcMap and also that the SDE_Process_Information table is empty. Once that is done, if the 2 locks for ENGDUSTCONTROL are still present, you can remove them from the SDE_Locks table in the database. Then get back into ArcMap and test to see if the errors are still present. But you may very well be running into that bug I mentioned and this isn't an issue of orphaned locks. If that is the case, this workflow above won't help. Also feel free to open a case with Support as we can work with you more closely and take a database backup in house to go through these workflows before we ask you to do them yourself to make sure they work on our end. Something to consider. Jonathan
... View more
09-18-2018
12:59 PM
|
0
|
2
|
2615
|
|
POST
|
Hi Matt, We have a bug logged for this issue and it is going to be addressed. I don't have a version that it will be fixed at yet though. We have seen this error in Desktop as well so it's not specific to Pro. Take a look in the SDE_table_locks, SDE_layer_locks, SDE_object_locks, SDE_state_locks and SDE_process_information tables and see what is there. There may be an orphaned entry hanging things up. But do not modify anything in those tables without a full backup of your database. BUG-000110574: The error, “Column value is null” is encountered whi.. Jonathan
... View more
09-14-2018
07:53 AM
|
0
|
5
|
2615
|
|
POST
|
Hi Scott, First, I'm not a security expert here. But I did want to point you in the direction of our ArcGIS Trust Center in case you hadn't seen that site already. Specifically, there is a page on privacy: Privacy—ArcGIS Trust Center | ArcGIS But hopefully someone on our security team can chime in here and speak in more specifics on what we do and don't collect when using ArcGIS Pro. Jonathan
... View more
09-10-2018
01:59 PM
|
2
|
0
|
2548
|
|
POST
|
Hi Jeff, Unfortunately, Microsoft does not allow transformations through their ST functions like we do for Oracle and PostgreSQL DBMS's. The only workaround that is going to work here is to use 2 spatial columns in the table in SQL Server. While we do not support multiple spatial columns when working with tables or views in ArcGIS, Microsoft does. So you could add a second spatial column in the WKID that you need and then create a view or query layer using only one of those columns for use in ArcGIS. Outside of this though, I can't think of another way around it. Jonathan
... View more
09-06-2018
09:15 AM
|
1
|
0
|
4477
|
|
POST
|
Hi Forest, We do not have a script or tool to create these logfile tables unfortunately. If you do not want your users to have to select over 100 features themselves, you'll have to make connections to the database under their logins and do it. I do also want to note since you mentioned a new 10.2 geodatabase, support for 10.2.x ends in July 2019. Something to think about as you move forward. This also means that support for SDE command line is ending at that time as well since the 10.2.2 geodatabase was the last release to support it. Esri Support 10.6 (10.6.1) Let me know if you have any questions for me! Jonathan
... View more
09-05-2018
07:52 AM
|
1
|
0
|
3791
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-10-2018 07:40 AM | |
| 1 | 10-03-2018 08:28 AM | |
| 1 | 04-12-2018 01:47 PM | |
| 1 | 01-24-2019 07:35 AM | |
| 1 | 01-03-2019 07:56 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:24 AM
|