ERROR: “ArcGIS Server Site is currently being configured by another administrative operation. Please try again later.”
I got the error shown in the screenshot below
What might be the issue here?
Thank you
Best
Jamal
I agree with you Daniel.
We'd experienced this issue before. We changed the Arcgis server directory to NAS & we kept facing down services until we changed the directory back to the local machine.
Best,
Alaa
More than likely, whomever administers or configured your NAS has OpsLocks enabled. Disable OpsLock and your issues will likely be gone.
I prefer using SAN for the superior performance of a NAS.
I had posed similar earlier in the thread. Isilon is a NAS appliance.
Thanks for your input Michael.
We'll try this.
Hi
Way to disable ops
To Disable SMB2 and OPLOCK (Network Locking Errors) – Infusion Business Software
It is recommended to leave the configuration of a NAS appliance to a 'network' / IS / IT specialist. Not for a GIS 'anyone' to tinker with unless it is the GIS groups dedicated appliance and must be managed by them for whatever reason. NAS typically is shared with more than just the GIS group and is more of an organization IS backbone appliance.
Its great to 'know about it' but not recommended you act on it.
Scale-Out NAS for Unstructured & Big Data | Dell EMC Belgium
Users experiencing this issue should also consider logging cases with the NAS/SAN vendors. The essential issue here is that the device can't keep up with with the high IO between ArcGIS Server and the remote config-store.
Hi Randall,
In my case, I had, and it was brutal. Was multiple weeks of conference calls and deep diving and I was in a position with no luxury of time due to high business demands and limited resourcing. EMC (the vendor for Isilon), eventually figured out how to get the NAS running without AGS issues, however, I had created a clustered environment mirroring the setup but used EMCs vMAX disks (SAN) and the performance was 10 fold different. EMC failed to determine why the performance 'sucked' with the NAS in its configuration. I had to pull the plug when we had reached week four and several 'specialists' from the vendor and the possible weeks/months more internal process for Isilon changes (because it was used as a 'network' drive for many business groups) I went out of my way to resubmit an architectural change and introducing a single point of failure with the SAN setup. Far better than tinkering with that NAS let me tell you.