This article documents a problem and work around New York and AgileAssets uncovered as we worked through the LRS Gateway testing between Roads and Highways 10.7.1 and AgileAssets 7.6.2 (both running on Windows 2019)
Please note: This issue only applies if you are using the Esri File Geodatabase API running on Windows Server (as opposed to Unix) to read the file geodatabase produced by the Roads and Highways (RH) ExportNetwork service. The Export Network GP Tool output is a file geodatabase. Applications that need to be aware of LRS network changes interface with the LRS in Roads and Highways through the RH Export Network service. At NYSDOT, our interfacing application is the AgileAssets enterprise asset management (EAM) system running on Windows Server 2019. Testing by NYS ITS and AgileAssets revealed that the File Geodatabase API could not reliably read the file geodatabase produced by the RH Export Network REST service. The problem was intermittent but otherwise persistent. As a result, the LRS Gateway sync would regularly fail. An upgrade
