Inventor API error "ordinal 345 could not be found in Dt.dll"

[t.karipidis]

Hello, 

I have a software that, among others, creates pack'n'go for each specified order. Till version 2023, it was working fine (it still does on that version). On Inventor 2024 and now also 2025, when it's trying to pack'n'go the generated 3D, it gives me the error:

"The ordinal 345 could not be found in the dynamic link library C:\Program Files\Autodesk\Inventor 2025\Bin\Dt.dll".

Searching about it, I found that this error is similar for other software too, and there is also an unresolved subject for Navisworks in the forum. Also, I have checked any possible solution out there and still nothing.

It's crucial for our process that this gets resolved.

[bradeneuropeArthur]

This file still is in the C:\Program Files\Autodesk\Inventor 2025\Bin\Dt.dll folder, correct?

[t.karipidis]

Hello Arthur, 

Indeed, the DLL is there.

[Volant7800a]

This error is also occurring in "new PackAndGoComponent()" for Inventor Professional 2024 in our environment.

We have registered support request 22668785 and confirmed that the error also occurs on the Autodesk side.
They then escalated the issue to the development team as INVGEN-79836.
This is a major issue for us as well, so we would appreciate your immediate response.

[Volant7800a]

We received a response from Autodesk Support and took the following steps, which enabled the software to work normally without errors. 

----
After further investigation by the development team, we were informed that Pack And Go can be used from custom applications by specifying Comctrl32.dll version 6 to be used using the manifest when building the custom application. 

This is because a change has been made in Inventor 2024 and later to use a higher version of comctrl32.dll internally, and if you want to use the Pack And Go function from a custom application, you will need to set it in the manifest file at the time of build. 

We have confirmed that the situation has improved in our environment. We apologize for the inconvenience, but could you please check the following steps? 

If there is no manifest file in the project of the target application (exe), add the manifest using steps 1 to 3. 

If there is already a manifest file, please perform items 4 and after.

1. Open the project file of the target application (exe) in Visual Studio.

2. Right-click in Solution Explorer and select "Add" - "New Item" .

3. Select the application manifest file in the displayed dialog and click Add.

4. Open the manifest file and uncomment the following commented out settings. Also, if the following commented out items are not present, add the following <dependency>～ </dependency> settings under the <assembly> tag:   <!--

   <dependency>

     <dependentAssembly>

       <assemblyIdentity type="win32" name="Microsoft.Windows. Common-Controls"  version="6.0.0.0" processorArchitecture="*" publicKeyToken=" 6595b64144ccf1df" language="*" />

     </dependentAssembly>

   </dependency>

-->

5. Build and run the application.

----

Thank you for your cooperation.