| Numéro d’ID de bogue |
BUG-000122884 |
| Envoi | June 6, 2019 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS GIS Server |
| Version trouvée | 10.6.1 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 2016 64 Bit |
| Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
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.
Étapes pour reproduire
ID de bogue: BUG-000122884
Logiciel: