3ds Max 2027 "ADP Failed to start" in server mode when opted out #271
ZainAallii
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Effect
3ds Max 2027 launched in server mode (
3dsmaxbatch.exe/3dsmaxcmd.exe, as render nodes do) aborts during startup, before any scene work, and the render task fails. The 3ds Max log shows:This blocks all rendering on affected nodes.
Affected host configuration scripts (Deadline Cloud samples)
Any 3ds Max 2027 service-managed fleet provisioned with these scripts is affected (apply the opt-in consent workaround below):
Root cause
This happens when the launching user is opted out of the Autodesk Analytics Program (ADP). The opted-out path runs a "Starting network" step that cold-starts the Autodesk SSO server app
AdSSO.exe. That executable is not installed: the ADP SDK bundled with 3ds Max 2027 still expects the legacyAdSSO.exe, but the installed Autodesk Identity Manager shipsAdSSOServices.dll/AdskIdentityManager.exeand noAdSSO.exe. The SSO cold-start times out, ADP reports failure, and Max exits-12.The opted-in path (
ADP Initialize: Done) skips the "Starting network" / SSO step entirely, so it does not hit the missingAdSSO.exe.What it is not:
3dsmaxbatch.exelaunch and a trivial script.Render nodes hit this because they run in server mode and their service account defaults to opted out. Interactive artists using the normal 3ds Max GUI do not, because the GUI resolves consent (or they are opted in).
Workarounds
1. Use 3ds Max 2026 render nodes — not affected.
2. Record an ADP opt-in consent for the render user before launch, if you agree to it. Writing
%APPDATA%\Autodesk\ADPSDK\UserConsent\UnNamed.jsonwith alloptIn: trueanduserActionRequired: falsemakes ADP reachDoneand Max start:{ "preferences": [ {"consentId": "ADSK_PUD_CONTRACTUAL_NECESSITY_DESKTOP", "optIn": true}, {"consentId": "ADSK_PUD_OPTIMIZATION_IMPROVEMENT_DESKTOP", "optIn": true}, {"consentId": "ADSK_PUD_GO_TO_MARKET_DESKTOP", "optIn": true} ], "userActionRequired": false, "userId": "UnNamed" }On a service-managed fleet, apply this script to opt-in if agree at provision time from your host configuration script by writing the file into the Default user profile so every new profile (including the render service account) inherits it:
(Writing to the current user's
%APPDATA%at render time works too, but the Default-profile approach is one-time and covers every job.)3. Opting out does not work — the same file with
optIn: falsestill fails (OptedOut→ADP Failed to start), confirmed on both a render node and an interactive workstation. The crash is in the opted-out SSO cold-start itself, so a proper fix must come from Autodesk: make the opted-out server-mode path non-fatal (do not requireAdSSO.exe), or provide a way to fully disable ADP.All reactions