I don't know if this again some computer specific issue, but after installing ArcGIS for Desktop 10.6 + 64 bit background geoprocessing, and subsequently the install of the OSM Editor for 64 bit, background geoprocessing fails for the OSM File Loader (Load Only) tool.
I see the process starting up, but almost immediately finishing with the green mark of "success", but nothing is actually loaded into the target geodatabase.
If I disable background geoprocessing, the tool works as expected, and does create the Feature Classes with all the data. It just fails with background geoprocessing.
I fully uninstalled and reinstalled the 64 bit background geoprocessing component, and the OSM Editor as well, making sure I reinstalled the OSM Editor after installing the 64 bit background geoprocessing component, however all to no avail.
I did notice one other small anomaly, that the HTML Help page being opened after the OSM Editor install, still listed ArcGIS 10.5 instead of 10.6. However, I guess this is just an oversight to update the HTML page for the new 10.6 install...
@ThomasEmge
I don't know if this again some computer specific issue, but after installing ArcGIS for Desktop 10.6 + 64 bit background geoprocessing, and subsequently the install of the OSM Editor for 64 bit, background geoprocessing fails for the OSM File Loader (Load Only) tool.
I see the process starting up, but almost immediately finishing with the green mark of "success", but nothing is actually loaded into the target geodatabase.
If I disable background geoprocessing, the tool works as expected, and does create the Feature Classes with all the data. It just fails with background geoprocessing.
I fully uninstalled and reinstalled the 64 bit background geoprocessing component, and the OSM Editor as well, making sure I reinstalled the OSM Editor after installing the 64 bit background geoprocessing component, however all to no avail.
I did notice one other small anomaly, that the HTML Help page being opened after the OSM Editor install, still listed ArcGIS 10.5 instead of 10.6. However, I guess this is just an oversight to update the HTML page for the new 10.6 install...