Listed below are issues you may encounter when working with OSM Vector Basemaps content as well as recommended solutions.
If your hosted tile layer service did not publish successfully, an issue may have occurred during the upload of the vector tile package (.vtpk) file to your portal. The size of the .vtpk file on disk and the size of the uploaded file on your portal must match.
The size of the OSM_Vector_Basemap_DA72_Install.vtpk file is 33,311 MB and the OSM_Vector_Basemap_GCS_DA72_Install.vtpk file is 33,116 MB.
You can check the size of the uploaded vector tile package (supporting the service) on the item details page. The following screen capture shows the OSM_Vector_Basemap_DA72_Install vector tile package details:
If the size does not match, review the log via the server manager to see if there are any errors.
In some cases, the ArcGIS Pro Share Package geoprocessing tool may have produced a Success message, but when you check the size of the .vtpk file from the item details page, it does not match. Here are some things that you can try to resolve this issue:
- Upload the .vtpk file again. First, delete the OSM_Vector_Basemap_DA72_Install.vtpk or OSM_Vector_Basemap_GCS_DA72_Install.vtpk file from your portal. Next, upload the OSM_Vector_Basemap_DA72_Install.vtpk or OSM_Vector_Basemap_GCS_DA72_Install.vtpk file again using the ArcGIS Pro Share Package geoprocessing tool.
- Verify with your portal administrator that there is at least 68 GB of disk space per .vtpk file available on your portal. Make sure there is space on <ArcGIS portal install drive>\arcgis\arcgisportal where the content items are stored.
- Verify that you are using a supported version of ArcGIS Pro. See the system requirements for details.
Contact Esri Technical Support if you still cannot successfully upload the .vtpk file.
Note:
The following answers reflect troubleshooting of the WMA vector tile package and service. To troubleshoot the GCS vector tile package and service, you need to take the GCS naming into consideration.
Work with your systems administrator to check the ArcGIS Server Manager logs.
If there is an error due to a geoprocessing service (PublishingTools) timing out or crashing, you may have skipped a system requirements step. Confirm that you changed the value of The maximum time a client can use a service to 21,600 seconds.
Once you have updated the geoprocessing service maximum time, do the following:
- On your server, delete the OSM_Vector_Basemap_v2 or OSM_Vector_Basemap_GCS_v2 hosted tile layer.
- On the ArcGIS Server machine, delete the job in
the <ArcGIS_Server_Install_Path>\arcgis\arcgisserver\directories\arcgisjobs\system\publishingtools_gpserver\<Job_ID> folder.
Note:
You can find the job ID in the log file.
- Restart the server.
- Verify that you have at least 68 GB of available space per .vtpk file on ArcGIS Server.
- In your portal, publish the OSM_Vector_Basemap_v2 or OSM_Vector_Basemap_GCS_v2 tile layer again.
If the Creating Service progress bar continues to load after two hours, the browser connection to the portal may have failed.
Sign out of the portal and sign in again to see if the thumbnail has changed to the Data Appliance 7.2 icon, because the browser connection does not affect the creation of the service.
If the thumbnail changes to the Data Appliance 7.2 icon, confirm that the map displays as expected.