| Numéro d’ID de bogue |
BUG-000107203 |
| Envoi | August 8, 2017 |
| Dernière modification | July 15, 2025 |
| S’applique à | ArcGIS GeoEvent Server |
| Version trouvée | 10.5.1 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 2012 R2 |
| Statut | Fixed
Le bogue a été corrigé. Pour plus d’informations, reportez-vous aux sections Version de correction et Informations supplémentaires, le cas échéant.
|
Solution de contournement
Note: If users like to do a backup of the GeoEvent configuration prior to doing this workaround, users can do so by logging into GeoEvent Manager > Click Site > Go to the Configuration Store tab > Export Configuration > Export Configuration > Export.Do this workaround while GeoEvent is running:1) Navigate to the Network Fleet jar file available here:<a href="file:C:/Program" target="_blank">C:\Program</a> Files\ArcGIS\Server\GeoEvent\deployNote that if GeoEvent is installed somewhere else than the C drive, users need to modify this file path to point to their installed location.2) Move this jar file to a different location on the computer so that this jar file is removed from the Deploy folder entirely.Note: If this is done successfully, users can see the Network Fleet input connector go red in the monitor available in GeoEvent Manager3) Go into the Windows Services program and stop the GeoEvent service4) Navigate to the data folder available here:<a href="file:C:/Program" target="_blank">C:\Program</a> Files\ArcGIS\Server\GeoEvent\data5) Delete everything from this folder6) Start the GeoEvent Windows service. When users do this, the data folder should repopulate with the proper files.7) Navigate back to this folder:<a href="file:C:/Program" target="_blank">C:\Program</a> Files\ArcGIS\Server\GeoEvent\deploy8) Drag the Network Fleet jar file back into the deploy folder above.9) The Network Fleet input connector must be working again now.
Étapes pour reproduire
ID de bogue: BUG-000107203
Logiciel: