Hi All, We are experiencing an odd issue within our ArcGIS Enterprise environment (ver 10.9.1). We are encountering Error (ERROR 001369) during publishing. All steps for publishing (from desktop) take much longer than expected. These are few observations:
This site is an active-active ArcGIS server site that is federated with Portal. Our configuration is as follows:
We are trying to find where the bottleneck is coming from and if there are any tool/options that can help in identifying the issue by checking end to end communication and capturing time for each step.
Thanks in advance
JS
Has the network share been configured for any kind of redundancy? Often see similar issues when customers configure a DFS for a network share which contains the ArcGIS Server directories.
Please see: https://enterprise.arcgis.com/en/server/latest/install/windows/choosing-a-nas-device.htm#:~:text=dat....
I know this doesnt help but we have had a similiar issue for years.Specifically dealing with CSV's being published directly through the Portal front end. I would 90% of the time it fails with that same error code. We never really found a fix. We developed a work around instead where we publish through ArcGIS Pro.
We did work with esri on this for months. I want to say at least 6 months worth of troubelshooting and we could never find a root cause.
Hello @Sunnywaygis ,
It seems like somewhere there is a network bottlenecks as you expect. However, It would surely not be an easy thing to figure out.
It seems that ArcGIS Server has issues in accessing components on the same machines as in this scenario the statistics and logs would be stored individually on their own as opposed to config-store and directories being on shared directory. This could be causing a delay in response
I would suggest taking the following approach.
Cover all the bases
If you perform the above and it does help (make sure you the above first)
A bit more advanced ways
I would say that this would be a good starting point. Please be aware that there are just ways to narrow down the issue, either of these could/could not be a solution but this will help us in understand where the problem resides for sure.
Let's try this and let me know, how it goes and then we take it further.
Hope it helps!
-Archit