GeoBIM Integration Issue with Autodesk BIM360 & ACC

[기석김]

We have implemented ArcGIS Developer and installed Enterprise 11.3 and GeoBIM.

To integrate Autodesk BIM360 and ACC with GeoBIM, we have referred to the following documentation:

• Setting up ArcGIS GeoBIM
• Managing Access to Autodesk Docs

  We have correctly entered the callback URL and properly configured the Autodesk.json file. However, we are still unable to establish a connection. We are unsure of the cause of this issue.

  We would appreciate any guidance or support you can provide to help us resolve this problem.

  

  Could this issue be caused by differences in the configuration methods for Autodesk BIM360 and ACC?

[ACheuvront]

Hi @기석김 

That error message happens when the callback url specified in the Autodesk Platform Services (APS) application is not set correctly. This is covered in step 4 of Create an Autodesk Platform Services application for ArcGIS GeoBIM.

The webadaptorhost.domain.com/webadaptorname from the example callback url needs to match your GeoBIM url.

Example callback url:

https://webadaptorhost.domain.com/webadaptorname/apps/geobim/widgets/keystone/accounts-explorer/dist...

If this doesn't resolve your problem, I would recommend contacting Technical Support. We may need additional information that can't be shared here.

[기석김]

Thank you for your response.

We have entered the GeoBIM callback URL in the Autodesk Platform Services (APS) settings as shown on the screen, and since there are no error messages, we believe it has been configured correctly.

[기석김]

Subject:  GeoBIM Error in ArcGIS Enterprise 11.3

I installed ArcGIS GeoBIM, but I ran into several issues that I haven't been able to resolve.

1. I have identified an issue in GeoBIM. : BUG-000171822 for Portal for ArcGIS

2. Client ID Configuration Issue

After installing GeoBIM and configuring the autodesk.json file with the correct Client ID, the GeoBIM URL still displays a completely different Client ID.
Despite multiple reinstallation attempts and system reboots, the Client ID does not update or reflect the configured value.

3. Missing Configuration Files
The following folder and file are missing after installation: \GeoBIM.GPServer\extracted\cd\geobim\config.dat

4. Request for Patch/Update Information
Could you please provide information regarding the timeline for any upcoming patches or updates?
We hope for a swift resolution to these issues so that we can proceed with our project. 

The purpose of acquiring GeoBIM was to integrate BIM and GIS for testing and potential expansion.
However, due to these issues, we are currently unable to utilize the software as intended. 

Thank you.

[ACheuvront]

@Hi @기석김 

The bug you identified is based on a different result for the callback page and we are still trying to determine the source of the problem with that bug. We haven't been able to rule out a configuration problem with the customer on that.

The client ID seen in the url can only be used if the client ID in the autodesk.json file is blank. It is necessary to restart the "Portal for ArcGIS" Windows service after the autodesk.json file is updated. It should not require a full reboot of the machine.

Typically the autodesk.json file requires elevated privileges to update. If it was edited without elevated privileges, the changes may not have been saved. Can you verify the client ID was updated and restart the "Portal for ArcGIS" service just to be sure?

It has come to our attention that our documentation is not clear that the installation and post-installation configuration are both necessary. We are working to make this clearer. The missing config.dat files are part of the post-install configuration as described on the Install the ArcGIS Enterprise geoprocessing services page. If the geoprocessing services have not been published, that would need to be completed for ArcGIS GeoBIM to function correctly.

If the publishing of the services and restarting the Portal for ArcGIS service don't get you to an operational state, please contact me directly and we can set up a web meeting for additional troubleshooting.

We have also identified a new bug for recently created APS applications. If your APS application was created after December 9, 2024, please contact me directly and I can get that resolved.

[기석김]

Thank you for your response.

After encountering persistent errors despite following the administrator's instructions to generate a JSON file, I conducted multiple trial-and-error tests to identify the root cause.

Although I copied and pasted the correct URL, the issue persisted. Eventually, I discovered that the error originated from an encoding issue in the Callback URL input field in Autodesk APS. Specifically, I found that copying and pasting a URL that included https:// resulted in an encoding error.

To resolve this, I manually entered the URL without the https:// prefix. Upon doing so, I was able to successfully authenticate with Autodesk Construction Cloud (ACC).

I hope this information helps others who might encounter the same issue.

Additionally, I kindly request that the missing installation file bug be addressed as soon as possible.
Thank you for your prompt attention to this matter.

[ACheuvront]

@기석김 

Thank you for notifying us of the problem (and solution)! We have never seen this happen with the callback URL in the APS application. I'm not sure why it is happening to you. I will add this to our bug list and see if we can find a way to address the encoding error.

[ACheuvront]

@기석김 

A couple additional questions:

1. Is your ArcGIS Enterprise deployment configured with https?
2. When did you create your Autodesk Platforms Services application to get the APS client id?

[기석김]

@ACheuvront 

Thank you for your response and for your question.

1. Our organization has deployed and is operating the ArcGIS Enterprise portal based on https://g****.**

2. We completed a second installation of Autodesk Construction Cloud and conducted a cross-verification with an Autodesk partner on February 20, 2025.

3. On February 26, 2025, we reviewed encoding errors and connection issues with Esri Korea's partner.
Additionally, we identified an issue on February 17, 2025, where a folder was not created in the GeoBIM installation path.
Due to this bug or error, we have been unable to proceed with BIM integration tasks or conduct testing.