Imaging - Silent network deployment hangs at completion, Inventor 2022, AutoCAD 2023, others

[dfulle14]

In past years, we had no problem doing silent network deployments during computer imaging. Starting with Inventor, Revit, and Navisworks 2022, and now AutoCAD 2023, the deployment hangs at completion, the log simply repeating this line (this is AutoCAD 2023, the other apps have the exact same issue) every 30 seconds: 

2023-06-15T15:17:04.012 [DDA: 2196, single] [Installer INFO] [ Autodesk::DDA::SdkAgent::Listen::<lambda_8f7c2cafda285d6f3324fbe86a24bae4>::operator () ] [IPC] ChannelWin::Listen: WaitForSingleObject timeout. error_code: 997, pipe_name: \\.\pipe\adsk_dda_sdk

The install completed, I can run AutoCAD without problems. The installer just never returns an exit code, as it's waiting for some response from somewhere that never comes. The same command line can be used for testing a manual install, it's only during a deployment that it hangs.

It's not an issue with SYSTEM account and access, it has no problem doing the install. It's not an issue with Internet Options and Sites/Security Zones, the server and it's UNC paths are properly configured (which we added earlier in the process as the silent install was hanging waiting for confirmation that we trust the network location). 

When we were working with Autodesk Support last year, they wouldn't say more than there was a process waiting. Couldn't or refused to let us know which process, or what it was waiting for. So, basically zero help.

There are some very kludgy workarounds, that require maintaining some Autodesk installs in one manner and others in the standard/typical manner. What I'd like is for there to be an actual solution that allows all of the applications to install silently during network imaging, which is what they did for several years.

[henkstubbe]

Are you doing an offline installation, or does it download files from the internet? If it is downloading the odis installer from the internet, it is taking the newest version, 1.40.0.24, which seems b0rked. I had a similar problem, going back to a previous version fixed this issue.
I deploy the odis installer first, then deploy something like acad like this:

"C:\Program Files\Autodesk\AdODIS\V1\Installer.exe" --install_mode install --ui_mode basic --offline_mode --manifest "%ScriptPath%\files\setup.xml" --install_source "%ScriptPath%\files\"

%ScriptPath% is something my deployment software uses as a placeholder for the location of the files.

[Simon_Weel]

I've seen that too - install has finished but the installer lingers on forever. I just kill it and as the applications run fine, I guess it's probably an ODIS 'feature' 😞 

[ed57gmc]

Something like this where the installer is failing, I would definitely open a support ticket so they can be aware of the issue.

[henkstubbe]

I've opened a topic here about the borked installer here, but they don't seem to care. Of course this didn't come as a surprise to me.

[ed57gmc]

Depending on your subscription level, they have up to 48 hrs to respond. I don't expect them to have a fix either. But it needs to be reported so that they can fix it.

[Simon_Weel]

There are numerous problems with ODIS and I think Autodesk is well aware of that. If you make a service request, you'll be answered by a first-line responder, suggesting to post it as 'idea'. So, yeah.....

[dfulle14]

It's an offline install, build the deployment through the Custom Install section of the Account Portal, run the little exe it generates to download all the files to the network deployment location specified. Then run the command line install provided in the batch file that gets created (with --offline_mode flag). I don't use the --manifest or --Install_Source flags, though. Is --manifest just because you're not using the default location / Collection.xml value?

It is using installer version 1.40.0.24. What's odd is that this year the Inventor 2023 install works (2022 is where the original problem occurred), but AutoCAD 2023 doesn't (using the same installer version 1.04.0.24), while AutoCAD 2022 did. Revit 2023 hangs like Revit 2022 did last year, I haven't had a chance to test the rest yet.

Navisworks 2022 and Revit 2022 would complete and exit if I mapped a drive to the network folder rather than use the UNC path (which isn't optimal, but such is life). Inventor 2022 wouldn't even handle a mapped drive, I had to move the entire install source to the deployment server and then use %dp0 (the equivalent to your &ScriptPath%), which I found from a thread here last year.

Is there a way to force using a different version of the ODIS installer?

It doesn't seem unreasonable to expect a consistent install method across all the applications, since we had that pre-ODIS and it worked, and now they've taken it away without any real indication they care to fix it. Or in last year's case, actively worked against me fixing it by refusing to tell me which process specifically was hanging (I figured I could check for it running after the install completed or had been running ~30+ minutes I could just script killing it and faking an exit code).

[dfulle14]

Yeah, I did that last year and not only didn't get a solution, but even though they agreed a process was blocked/hanging they refused to tell me which process so I couldn't even investigate that deeper. Worse still, the workaround I put together was something they told me wouldn't work when I asked about it.

I get that they need to know how many customers are impacted by a bug to determine what gets attention, but it's hard to muster the motivation to deal with the back and forth on that when the customer consensus is "Even submitting support tickets doesn't get the same helpful info as posting on forums".

[PetrStudnicka8111]

Hi there,

did anyone manage to solve this, please?

I face identical issue with offline installer of 2025 versions generated from https://manage.autodesk.com/ and downloaded to our deployment share. 

Problematic lines:

YYYY-MM-DDTHH:MM:SS.SSS [DDA: 3756, single] [Installer INFO] [ Autodesk::DDA::BaseHandler::{ctor}::<lambda_20a742db0dddb05b9a2b39e951593bef>::operator () ] [IPC] UI ChannelWin::Listen: WaitForSingleObject timeout. error_code: 997, pipe_name: \\.\pipe\adsk_dda_sdk

Found in this log:

%LOCALAPPDATA%\Autodesk\ODIS\DDA.log

Installer version:

2.7.0.34

It makes no difference if I install 4 products at once or one at a time. It doesn't matter if I install without UI or with UI. Re-generating and re-downloading didn't help either. It's completely random and a another attempt usually results in a correct installation. Hundreds of our computers affected.

Thank you.

Regards,

Petr

[dfulle14]

I never got a consistently successful solution, unfortunately. Which applications are problematic (it's been different ones for me each year) and what deployment method are you using, I can offer some suggestions depending on that?

This year's problem child for me has been Revit 2024. If it gets stuck, it's usually around 35%, 65%, or 97%. I've taken to running the installer in basic UI mode so I can watch it. When it gets stuck, if I click "Cancel" and then wait a few seconds before clicking "Continue" it usually gets it back on track. If you watch the Task Manager during this, it jumps right into downloading the next component to install. It's very clearly an issue where one component installer finishes but doesn't successfully report it so the parent install just waits. Fake-Cancelling forces it to do a status check, and sees that it's ready to install the next component. There is no consistency in which component is the last one before the hang. It's infuriating.

[Simon_Weel]

Yes - sort of. I run a second script that checks for any file activity. For example, if there's a folder 'Revit 2025'. If the installer runs for 5 minutes without any file activity, it kills the installer, wait 30 seconds and then starts the installation again. And repeats this until the installer actually starts installing.

This is no 'solution' - the installer should act upon pipe-issues and not wait indefinitely....