Geoprocessing services do not honor ArcGIS Server defined scratch workspace output locations if ArcGIS Server directories are referenced via a Universal Naming Convention (UNC) pathway.
上次发布: June 21, 2019ArcGIS GIS Server
漏洞 ID 编号
BUG-000122884
已提交
June 6, 2019
上次修改时间
June 5, 2024
适用范围
ArcGIS GIS Server
找到的版本
10.6.1
操作系统
Windows OS
操作系统版本
2016 64 Bit
状态
Known Limit
经开发团队审核,已确定此问题与不受 Esri 控制的软件的已知限制有关。 问题的“其他信息”部分可能包含进一步说明。
附加信息
For the behavior and execution of the geoprocessing service, the output PDF file is generated in the correct UNC path. In that regard, this is not a bug, but if printing off the path of the environmental variable itself, it shows otherwise. This is as designed.
When running a geoprocessing service with a path of "environmental path plus output name" as an output, the scratch workspace and folder actually points to the "arcgis server job directory/GUID/scratch" directory. GUID is generated dynamically when running a service with an output. This means the server would not know the path until the user runs it. This works for either the server job directory is set to default or UNC path.
In contrast, when printing off the environmental variable path only, it does not know where this dynamic path is since the real task with output is not run. So the behavior of environmental variable path acts more like the one on desktop, points to a static path as:
1. C:\arcgis\arcgisserver\directories\arcgissystem\arcgisinput\GPServiceName.GPServer\extracted\p20\serverscratch - if server job directory is set to default path.
2. C:\Users\\AppData\Local\Temp\ - If server job directory is set to UNC path
Although it is not consistent for the static path between the default and UNC path, it does not affect the correctness of the dynamic path of a geoprocessing service with output.