Welcome to the troubleshooting guide for deployment issues when using ArcGIS GeoBIM on ArcGIS Enterprise. This article aims to offer guidance on errors that may occur due to missing or misconfigured Enterprise infrastructure, services, or deployment settings.
General deployment errors
Use the information below to troubleshoot the common errors experienced within ArcGIS GeoBIM for ArcGIS Enterprise configurations.
Note: After opening the web help links in the table below, use the version switcher to switch to the specific version of ArcGIS Enterprise you are using.
Error message | Description | Troubleshooting |
|---|
Unable to project geometry | Indicates that the Geometry processing may have failed due to Enterprise deployment issues. This can occur if the Geometry GP service is inactive or misconfigured. This error can also be encountered if Autodesk document contents are out of bounds for the spatial reference used. | Ensure the Geometry GP service is active and functional in your Enterprise deployment. Ensure your documents are compatible for the sync process. See georeferencing workflows. |
Job Failed: failed to create ArcGIS GeoBIM 3D Document Models service | Add Document Models tool fails because the Object Data Store (tile cache) is not active. | Install and configure the ArcGIS Data Store to enable 3D workflows. |
401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission to view this directory or page using the credentials that you supplied. | Indicates unsupported security model configuration with Enterprise deployment. | See supported security models |
requests.exceptions.SSLError: Please set verify_cert=False due to encountered SSL error: HTTPSConnectionPool(host='rqalnxpki03pt.esri.com', port=443): Max retries exceeded with url: /gis/sharing/rest/info?f=json (Caused by SSLError(SSLError(1, '[SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate | Indicates unsupported security model configuration with Enterprise deployment. | See supported security models |
The request has not been applied because it lacks valid authentication credentials for the target resource | Indicates unsupported security model configuration with Enterprise deployment. | See supported security models |
If you encountered an error that is not listed in the table above and you are unsure on next steps, please leave a comment under this article and we will respond with recommended actions as soon as possible.
Autodesk authentication errors
ArcGIS GeoBIM requires authentication with Autodesk to securely access your BIM project data.
If you encounter problems with the authentication process on ArcGIS Enterprise you should verify the setup of the configuration file is correct.
You can also check the logs in ArcGIS Server where the services are hosted to help you identify errors and provide context on how to address problems.
Error | Description | Troubleshooting |
|---|
Blank bim360-callback.html page | This error can be caused by: - An incorrect URL in the authurl GeoBIM helper service.
- Missing authurl in GeoBIM help service.
- Missing GeoBIMAuth service.
- Incorrect or missing callback URL in APS app.
| - After the GP service is published, update the ArcGIS Server configuration for GeoBIM to locate the service. The authurl must match the path to the GeoBIMAuth service.
- Publish the ArcGIS GeoBIMAuth GP service.
- The default callback URL (https://localhost:8080/) for the APS app needs to be replaced with your server information and Portal oauth callback URL. See create an APS app for GeoBIM.
|
Oops looks like something is not right. Please contact your administrator. 400 - Invalid redirect_uri | This indicates there is an incorrect callback URL in the APS app. | The default callback URL (https://localhost:8080/) for the APS app needs to be replaced with your server information and Portal oauth callback URL. See create an APS app for GeoBIM. |
Autodesk login modal persists in the GeoBIM UI after successfully logging in | This indicates either: - Missing or incorrect client ID/secret in the GeoBIMAuth config.dat file.
- Client ID is different in autodesk.json and GeoBIMAuth.
| - Open the GeoBIMAuth config.dat file with a text editor (running in administrator mode) and add your APS app client ID and secret.
- After installation is complete, enter the client ID (created after creating the APS app) to \apps\geobim\autodesk.json then restart the Portal for ArcGIS service.
|
The client_id specified does not have access to the api product | This indicates there is a missing or incorrect client ID in the autodesk.json file. | After installation is complete, enter the client ID (created after creating the APS app) to \apps\geobim\autodesk.json then restart the Portal for ArcGIS service. |
If you encountered an error that is not listed in the table above and you are unsure on next steps, please follow the steps outlined in the Issue not listed? section of the ArcGIS GeoBIM troubleshooting hub.
