Autodesk desktop connector FSLogix VDI crash

Wesley Ramon 36

Hi all,

i'm having a very specific problem and can't seem to find out how to resolve it.

i have a VDI Environment with windows 11 virtual machines and FSLogix running.

this is backed with vGPU's so we use autodesk products to draw our plan's.

we make use of Autodesk Desktop Connector v16.2 , with that we can sync our cloud files to our VDI Machine.

After installation and sign in to the app , we need to configure our workspace (choose what folders to sync)

after that configuration the app crashes. but it is a CDX Crash.

if i change my workspace to a folder that is not part of my FSLogix profiles , for example C:\DC , it works fine.

problem is since this is VDI , the machine gets destroyed after logoff and the autodesk data has to stay in the profile.

this is a clean machine , latest win11 version , up to date , and only the connector app installed.

when the error occurs , i can see the dump error report. i'll paste them below.

<RuntimeInformation version="1.0" XmlBasedBucketing="True" DeobfuscationRequired="True">

<Exception type="System.Reflection.TargetInvocationException">

<Message>Exception has been thrown by the target of an invocation.</Message>

<StackTrace>

<Method module="mscorlib" object="System.RuntimeMethodHandle" function="InvokeMethod(System.Object, System.Object[], System.Signature, System.Boolean)" offset="0x0"/>

<Method module="mscorlib" object="System.Reflection.RuntimeMethodInfo" function="UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])" offset="0x16"/>

<Method module="mscorlib" object="System.Delegate" function="DynamicInvokeImpl(System.Object[])" offset="0x24"/>

<Method module="WindowsBase" object="System.Windows.Threading.ExceptionWrapper" function="InternalRealCall(System.Delegate, System.Object, System.Int32)" offset="0x0"/>

<Method module="WindowsBase" object="System.Windows.Threading.ExceptionWrapper" function="TryCatchWhen(System.Object, System.Delegate, System.Object, System.Int32, System.Delegate)" offset="0x2"/>

<Method module="WindowsBase" object="System.Windows.Threading.DispatcherOperation" function="InvokeImpl()" offset="0x7A"/>

<Method module="WindowsBase" object="MS.Internal.CulturePreservingExecutionContext" function="CallbackWrapper(System.Object)" offset="0x22"/>

<Method module="mscorlib" object="System.Threading.ExecutionContext" function="RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, System.Boolean)" offset="0x79"/>

<Method module="mscorlib" object="System.Threading.ExecutionContext" function="Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, System.Boolean)" offset="0x9"/>

<Method module="mscorlib" object="System.Threading.ExecutionContext" function="Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)" offset="0x34"/>

<Method module="WindowsBase" object="MS.Internal.CulturePreservingExecutionContext" function="Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)" offset="0x34"/>

<Method module="WindowsBase" object="System.Windows.Threading.DispatcherOperation" function="Invoke()" offset="0x20"/>

<Method module="WindowsBase" object="System.Windows.Threading.Dispatcher" function="ProcessQueue()" offset="0xF6"/>

<Method module="WindowsBase" object="System.Windows.Threading.Dispatcher" function="WndProcHook(System.IntPtr, System.Int32, System.IntPtr, System.IntPtr, System.Boolean&)" offset="0x90"/>

<Method module="WindowsBase" object="MS.Win32.HwndWrapper" function="WndProc(System.IntPtr, System.Int32, System.IntPtr, System.IntPtr, System.Boolean&)" offset="0x30"/>

<Method module="WindowsBase" object="MS.Win32.HwndSubclass" function="DispatcherCallbackOperation(System.Object)" offset="0x36"/>

<Method module="WindowsBase" object="System.Windows.Threading.ExceptionWrapper" function="InternalRealCall(System.Delegate, System.Object, System.Int32)" offset="0x77"/>

<Method module="WindowsBase" object="System.Windows.Threading.ExceptionWrapper" function="TryCatchWhen(System.Object, System.Delegate, System.Object, System.Int32, System.Delegate)" offset="0x2"/>

<Method module="WindowsBase" object="System.Windows.Threading.Dispatcher" function="LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, System.Int32)" offset="0xBB"/>

<Method module="WindowsBase" object="MS.Win32.HwndSubclass" function="SubclassWndProc(System.IntPtr, System.Int32, System.IntPtr, System.IntPtr)" offset="0x130"/>

<Method module="WindowsBase" object="MS.Win32.UnsafeNativeMethods" function="DispatchMessage(System.Windows.Interop.MSG&)" offset="0x0"/>

<Method module="WindowsBase" object="System.Windows.Threading.Dispatcher" function="PushFrameImpl(System.Windows.Threading.DispatcherFrame)" offset="0x40"/>

<Method module="Comet.Common.Utilities" object="Comet.Common.Utilities.IO.FileSystemWatcherExWithDispatcher+<>c__DisplayClass34_0" function="<InitializeDispatcher>g__ChangeHandler|0(System.Object)" offset="0x1C"/>

<Method module="mscorlib" object="System.Threading.ExecutionContext" function="Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)" offset="0x34"/>

<Method module="mscorlib" object="System.Threading.ThreadHelper" function="ThreadStart(System.Object)" offset="0x32"/>

</StackTrace>

<InnerException type="System.ComponentModel.Win32Exception">

<Message>The parameter is incorrect</Message>

<StackTrace>

<Method module="CloudFileApi" object="CloudFileApi.FolderMonitor" function="Watcher_Error(System.Object, System.IO.ErrorEventArgs)" offset="0x28"/>

</StackTrace>

</InnerException>

</Exception>

</RuntimeInformation>

Daniels 15 Reputation points

2023-05-25T14:08:03.36+00:00

I have the exact same issue and no solution so far.
Wesley Ramon 36 Reputation points

2023-06-19T09:59:02.94+00:00

To give you all an update , After a ton of emailing with autodesk they finally admit there is a problem, but it's not "that important", DevOps will look into it in an upcoming update , although they can't say in what update the fix will be applied. there are several issues with the DC if compared with previous versions and they will be systematically handled one at a time. In other words, we are left with a broken DC and it will not be fixed any time soon by the looks of it.
Daniels 15 Reputation points

2023-06-19T12:44:52.81+00:00

Thanks for the update. Same here, I have been corressponding with Autodesk too but no solution so far. By right Autodesk should maintain DC 15 to work with 2024 products, at least until they ironed out DC 16 issues.
Valerie Cintolo 5 Reputation points

2023-06-29T18:43:27+00:00

Interesting that you got that response; we are in the middle of a Azure VDI proof of concept with similarly configured hosts (not multisession): Win 11, FSLogix, Autodesk 2024 with ADC v16.x, but we ran into the same problem. We tried changing the path to C:\DC but after restarting the host, we were also seeing a message that the ADC folders have to be cleared. Then it's just one error after another.
We opened an Autodesk Support case and after recommending the clean uninstall/reinstall, the rep replied with: "I have heard back from our development team, and currently, Desktop Connector is not supported in any virtual environment. Even if a specific virtual environment will work in one release, we do not guarantee that it will work in subsequent releases". So that was disappointing!
Wesley Ramon 36 Reputation points

2023-06-30T09:26:56.8033333+00:00

Strange that you still got errors after changing the path to C:\DC ... that is not a part of the FSLogix profile and in my case that resolved the problem, but it is not a solution since after logoff the machine gets destroyed and rebuild from template and they have to start syncing there projects again ...

Regards

5 answers

Daniels 15 Reputation points

2023-05-25T13:56:29.4866667+00:00

My office got a similar setup, Azure Virtual Desktop, Win11 multi-session with FSlogix. We are facing exactly the same issue that DC v16 (including the latest 16.2) always crash upon login to windows session. We never had this issue with the previous DC v.15 and have been using it over 2years+.

Unfortunately we can't keep be using DC v.15 moving forward because Autodesk 2024 products must use DC v16.

Hope can find the solution very soon as we need to deploy 2024 products for our users. I've been liaising with Autodesk support separately but yet to hear any solution.
Please sign in to rate this answer.

1 person found this answer helpful.
Wesley Ramon 36 Reputation points

2023-05-26T06:10:47.33+00:00

we have the exact same problem , we need to move on to 2024 products but need connector 16.2 for that , we would like to use Storage Sense too and want to move on to windows 11 ... worst case we will keep using windows 10 since there the issue is not present ... but that's not a solution ... i also have autodesk involved but they just classify it as a Windows Problem (what is true) and that's that. not helpful ... I'm actually glad I'm not the only one. only question is, who can help us ...

Daniels 15 Reputation points

2023-05-26T07:06:26.8+00:00

The issue is also present in Win 10 multi-session 22H2, with FSlogix. I suspect it is related to roaming profile FSlogix. Or DC 16 doesn't work with roaming profile environment. Did you try Win 10 with or without FSlogix profile?
When I tested both Win 10 & 11 without FSlogix and it works ok, no crash. But without FSlogix means it will be a persistent setup that doesn't fit into my use case. In my environment I need roaming profile (FSlogix) setup so user can have the same settings whenever login to any available VM in the pool.

Wesley Ramon 36 Reputation points

2023-05-26T07:23:48.7333333+00:00

i tested with windows 10 both with and without FSLogix and both worked , not sure what version windows 10 was at and i upgraded that machine in the meantime so can't tell anymore. i don't use Multisession ... what i can tell you is if you open up DC 16 the first time , and change the workspace location to somewhere outside FSLogix (for example create a folder C:\DC) and point it to that directory , that also works ... it's really an FSLogix issue where DC recognizes it's not a physical hard disk but a redirected location ...
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Alexandre Cossette 5 Reputation points

2023-10-06T11:24:27.39+00:00

Hi,

I'm running into the same problem but the error message is different.

I'm virtualized with multi-users Windows OS with FSLogix.

Desktop Connector v16

At each login, users are getting the message that C:\users%user%\DC\ACCDocs needs to be cleared

Workaround is to exclude that folder from the FSLogix redirections.xml file

That prevent that folder to be saved and it's always clean for next login. But there is a catch and I would like to Autodesk to fix that in order to be compatible with Virtual environments.

Every login, you need to reselect your projects to include into Docs. A bit anoying but it looks to be the best workaround until Autodesk fixes that issue.

I would like to have better fix then that so please, if you have another solution, share it here for all of us.
Please sign in to rate this answer.

1 person found this answer helpful.
Wesley Ramon 36 Reputation points

2023-10-06T11:59:38.43+00:00

yes but if you exclude this folder, after every login the projects are downloaded again ? if you do this with 300+ employees daily ...

Alexandre Cossette 5 Reputation points

2023-10-06T13:10:35.94+00:00

Hi @Wesley Ramon

I know but it's the only workaround I could find so far. Still searching for other options
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Limitless Technology 44,531 Reputation points

2023-05-25T12:43:59.8333333+00:00

Hello there,

It might take time to check the dump.

Is there anything in event viewer?

I would suggest you to use proc mon to identify if there is nothing on the event viewer.

Process Monitor is an advanced monitoring tool for Windows that shows real-time file

system, Registry and process/thread activity. You can get the tool from here

https://docs.microsoft.com/enus/sysinternals/downloads/procmon

System Monitor (Sysmon) is a Windows system service and device driver that, once installed on a system, remains resident across system reboots to monitor and log

system activity to the Windows event log.You can get the tool from here

https://docs.microsoft.com/enus/sysinternals/downloads/sysmon

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer--
Please sign in to rate this answer.
Wesley Ramon 36 Reputation points

2023-06-05T09:50:01.3433333+00:00

i tried both of them , but I'm not familiar with them and don't know what i should be looking for ...
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Keith Clarke 0 Reputation points

2023-06-23T15:29:24.0933333+00:00

I would suggest that you CURRENTLY have the DC running Elevated. This is a Prohibited Workflow adn will Cause Stackdumps.

You must Run the DC as a Standard User. whether that means scripting it to restart and request a double login because yes even in an SSO environment some ADSK software will require that now.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Guillaume Beauchamp 0 Reputation points

2024-10-23T15:08:26.2666667+00:00

Same issue with FSlogix, does someone have found a way to fix this?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Autodesk desktop connector FSLogix VDI crash

5 answers

Your answer