Autodesk desktop connector FSLogix VDI crash

Wesley Ramon 36 Reputation points
2023-05-24T08:58:16.81+00:00

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="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="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>

FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
475 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,941 questions
{count} votes

4 answers

Sort by: Most helpful
  1. 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.

    1 person found this answer helpful.

  2. 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 clearedUser's image

    Workaround is to exclude that folder from the FSLogix redirections.xml fileUser's image

    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.User's image

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

    1 person found this answer helpful.

  3. Limitless Technology 44,096 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--


  4. 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.

    0 comments No comments