Latest Contributions by RickGeittmann

Ouch if you are running MS SQL 2014 or later it is barely able to run on that. Check perfmonitor and see what is available for free memory - select overview - I am going to guess you are at 88 - 92% on memory committed. Check the Arc Server / SQL logs for errors like appdomain unloading - that is a good indication you are short on memory resources. On rebuilding the indexes check the box to Include System Tables then hit the select all and UNCHECK Rebuild Delta Tables Only run that and see what happens I am thinking in your case it is more a question of SQL croaking due to memory resources. ... View more

How much memory do you have on your SQL machine?? MS SQL 2014 and later are memory hogs. ... View more

Hey gang, OK so still had real slow performance from the databases so as someone else mentioned earlier in the thread I went through this past Friday (11/10/2017) evening and ran the Rebuild Indexes tool against the main database that was giving us fits and customers reported this morning this were running fast and no problems. Toolboxes\System Toolboxes\Data Management Tools.tbx\Geodatabase Administration\Rebuild Indexes Took a few minutes to run but folks are very happy with the result - try it - might help. ... View more

Michael, Arc Server manager is installed by default below is how you would access it from the local machine [localhost] or remotely via http if you have it enable for management over the network http:// [server IP or name or localhost]:6080/arcgis/manager/  You would need to know the management account created to login with http://server.arcgis.com/en/server/latest/install/windows/log-in-to-manager.htm From there you would be able to look at the logs for arc server for MS SQL you would need SSMS installed and either do remote administration or install on the server its self and remote in and then bring up SSMS locally on that machine. ... View more

Margaret - yes I forgot to mention to clear out all add ins and third party installs related to the desktop software - had that issue on one machine with some add ins running we had to clear those add ins out and things started working just fine. I still am of the mind set there is as yet some undiscovered bug on the server side causing issues but have not located anything in any logs to point at. ... View more

Mark, Did you upgrade to SDE databases through Arc Catalog to the later version? I have also determined there may perhaps be an issue due to the changes in the coding of SQL 2014 and later engines. Check you logs on Arc Server and on SQL and see if you are getting any errors of an AppDomain unloading due to memory pressure issue - I am currently working through that issue on our systems. ... View more

Tina - well written and helps alot as I think many of us assume the support technicians know what button we clicked to get where and that oft times is more detrimental to getting help / assistance. I definitely have this bookmarked and in my system documentation notes for future reference. ... View more

Kenny - 2 of our folks just got back from the NWGIS in Boise and sat in the learning labs and experienced the same frustration of simply wanting to do "something" that is simple in Arc Map but in Pro they were pulling their hair out to figure things out - hence we are not going to switch over to the last dying day probably. ... View more

Michael, My root issue was the slooooooow connection and response to the client in edit sessions etc. The result was me doing the uninstall routine on the work stations and using the ODBC driver - see earlier in the thread. As for SQL open the connect to your DB instance and then open a NEW QUERY window type in SELCET @@version Highlight it and then select the EXECUTE button you should get a response back similar to the one below Microsoft SQL Server 2014 (SP2-CU6) (KB4019094) - 12.0.5553.0 (X64)   Jun 28 2017 16:26:18   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) I reinstalled the client machines - then installed the patches for v10.5.1 THEN went to each machine and used the windows uninstall programs to remove the SQL client connection driver then simply ran the installer for the ODBC driver which you can get in the My ESRI portal where you download your software installs from. ... View more

Molly, We are running 11 but I have some systems that are running the normal 64bit client driver and connect just fine - seems to be a hit and miss. But every install where we did a upgrade in place for concurrent seats of desktop I had to go back rip it out clean things up and do a "clean" install - the stand alone installs have worked just fine. Had 2 DB's that refused to be upgraded so had to dump them to a FGDB kill the DB in SQL and rebuild them from scratch and bring the data back in. Good catch on the fact they had renamed a DB - that is a tough one to figure out. ... View more

Also check the issue of the client connection driver loaded on your local machine http://desktop.arcgis.com/en/arcmap/latest/manage-data/databases/database-requirements-sqlserver.htm We had to switch over and use the ODBC connector driver to get things sorted out - running a Frankenstein until we collapse the hard server into our Hyper-V. Have 2008R2 OS on the server, MS SQL 2014 and v10.5.1 Desktop. Also don't forget 64bit client needs the 64 bit driver for DB connection. ... View more

OK so same here went from v10.3.1 to 10.5.1 and did the install over the top of the v10.3.1. What worked for us was to uninstall everything desktop related via the add remove programs. Next did a search and destroy on any and all folders that referenced ESRI on the local machine to include each and every profile. Also unloaded any other ESRI software such as Explorer / Arc Earth Then we ran a registry cleaner to clear any and all references to pointers in the registry. Still had issues - ripped out the SQL client driver and installed the ODBC driver that suits your version of OS 64 / 32 bit and database engine. That has seemed to fix the problems for us - most notable was the "clean" install. Here is where I removed ESRI / ArcGIS references: C:\Program Files\Common Files\ArcGIS C:\ Program Files(x86)\ArcGIS C:\Program Files\Common Files(x86)\ArcGIS C:\Python27 C:\Users\ I did find a few directories with just the name ESRI - killed those also Oh if you see anything in the FlexNet directories leave that alone !! Hope this helps someone ... View more

Adam, Any service will create a lock on data - so by having services running they are going to lock the schema to anything they are connected to. Locks in workgroup or enterprise geodatabases Users must own a dataset to make changes to its schema and have the appropriate privileges granted to them to edit other user's data. Schema locks, both shared and exclusive, are applied to individual datasets and related tables. For example: If you acquire a lock on a feature class within a feature dataset, the lock applies to the entire feature dataset and its contents. Locks also apply to both sides of a relationship class. For example, if two stand-alone feature classes are related via a relationship class and you acquire an exclusive or shared lock on one of them, the lock also applies to the other. Here is some further information on schema locking (rules) - it is older but still gives some good information. In short any connection is going to result in a lock. http://edndoc.esri.com/arcobjects/9.2/NET_Server_Doc/manager/geodatabase/creating_a_geodatabase/schema_locking.htm Hopefully this gives you a bit more info that will help. ... View more

Travis did you have to federate your arc server with portal? I am running in the Azure Cloud 2 server deployment with portal for ArcGIS installed instead of the AGOL route ... View more