Latest Contributions by Clint_Glover

I am currently running three environments (development, acceptance, production) of ArcGIS Enterprise 10.6.1 on Windows 2012 servers (Portal and Server are federated) and I am experiencing an issue (only on the acceptance environment) where all of our web services within ArcGIS Server are shown with a status of "Stopping".  In the ArcGIS Server logs, two big error codes appear after each attempt to restart the ArcGIS Server windows service.  The error codes are 6550 (failed to start the server machine) and 7365 (error while starting AppServer).  I began my troubleshooting by restarting the ArcGIS Server windows service.  After that didn't fix the issue, I rebooted the entire server (didn't fix the issue).  After that, I went through and checked multiple things including verifying that the windows account running ArcGIS Server has the correct folder permissions set, verifying that I have a valid licenses to run ArcGIS Server, verifying that the acceptance environment is configured the same as the development and production environments, and verifying that the acceptance environment has the same ArcGIS Enterprise patches installed as the other environments.  I will note that this behavior occurred after some recent windows patches were installed on that server.  When comparing the timestamp of the errors appearing in the ArcGIS Server logs to the timestamp of the installation of the windows patches on the acceptance server, they are very similar (same day).  This leads me to believe that the recent windows patches had some affect on ArcGIS Server.  The odd thing is that the same windows patches were installed on the development and production environments with no issues arising after installation.  I contacted ESRI support and all they can tell me to do is to attempt to uninstall the windows patches to see if it corrects the issues or uninstall/reinstall ArcGIS Server in that environment.  I would rather not have to uninstall/reinstall ArcGIS Server due to possible issues that might arise from our federation with Portal.  This is the first time I have ever experienced this behavior in any version of ArcGIS Enterprise.  Does anyone have any other suggestions for things I can try?  ... View more

I am currently responsible for updating layer data sources within mxds after an Oracle password change takes place.  To do this I have put together a Python script that goes through a folder (designated by the user), finds all of the .mxd files, and one by one reads in the layers of each mxd (arcpy.mapping.ListLayers), checks the workspacePath of each layer to determine which Oracle account is used for the layer, and then uses the replaceDataSource method to set it to the updated sde connection file.  After it finishes, it saves the mxd and then goes on to the next mxd file.   I've recently discovered that when running the Python script, the data source information of some of the layers will occasionally be assigned to a temporary sde connection file that is being generated by some part of the ESRI software.  This assignment is being done BEFORE my Python checks the workspacePath and attempts to use the replaceDataSource method.  The temporary sde files are being generated in the following location on my local machine: C:\Users\John Doe\AppData\Local\Temp.  Within the Temp folder, a folder titled "arc66D2" was generated, which contained the temporary sde file that was named 131dcb16a392ebc818a09874d51fce89.sde.  When I looked at the connection properties of this temp sde file (from ArcCatalog), it contained the old connection information from one of the layers within a mxd I ran my Python script on.  This behavior has happened on multiple occasions, each of which involves a different temporary sde file that were generated. I have also discovered that this behavior occurs some times when I open ArcCatalog, right click on a mxd file, and select the "Set Data Source(s)..." option, which allows you to manually update the data source information for an mxd.  The tricky part is that there doesn't appear to be any pattern with this occurrence.  Has anyone ever had this same issue and/or know why this is occurring and how to prevent it?  From my tests, this has occurred when working with mxds on my local machine as well as mxds located on various servers. After a password change, I have to run this Python script on thousands of mxds that have been created over the past 5 to 10 years by our end users to fix the data source information of all the layers, and when this temporary sde file is thrown in there "randomly", I can't trust my script to work 100% of the time and it causes additional work for me.   For reference, I am using ArcMap/ArcCatalog 10.6.1 and Oracle 12c.  In the past, our Oracle account passwords have never changed, thus this wasn't a problem.  Recently, my organization started forcing us to update our Oracle passwords every 90 days, so this is becoming a huge ordeal for our GIS group to support and manage. ... View more

Currently within my organization, password rules have been put in place that requires us to update our Oracle passwords every 90 days.  Due to these rules, I am in the process of creating a python script for both ArcMap mxds and ArcGIS Pro projects.  We currently have our SDE connection files in a shared directory to make this process easier.  When a password change is required, we update the Oracle password and then update the password for the associated SDE connection file in the shared directory.  Our intentions are to reuse the SDE connection files after a password changes, so our python scripts essentially should just reset each layer's connection info back to itself, which would then contain the updated password for the associated SDE file. The ArcMap python script has been created and works correctly using the .replaceDataSource function.  When I began working on the ArcGIS Pro python script, I ran into issues using the updateConnectionProperties function for layers within a map in a ArcGIS Pro project that used SDE connection files in our shared directory.  I attempted to set the new SDE connection file for each layer back to itself (which works with the replaceDataSource function for ArcMap), due to the SDE connection file staying the same, with only the password being updated.  I have also attempted to reset each layer's connection properties to a completely new SDE file, but that doesn't appear to work either.  None of ESRI's examples show using updateConnectionProperties to go from one SDE connection to another SDE connection file.  Does anyone know if this is possible or if there is an alternate route I can take to complete this task?  For reference, I am using the latest version of ArcGIS Pro (2.3.3) and our SDE connection files are pointed to an Oracle database (12c). ... View more

I currently have several database connections that are used in various MXDs that are used to publish my map and feature services.  I recently had to change the passwords for all of those database connections, and thus there is a need to update all of the layers in the MXDs with the updated data source information.  In this situation, once the layers in the MXDs are updated, will the web services need to be republished or simply just restarted?  I feel like the services would need to be republished for the changes to be reflected, but I've never done this before so I just wanted to make sure I was doing it correctly.  For reference, I am currently using ArcGIS Server 10.5.1 and my database connections are Oracle. ... View more