.NET application crashes upon startup in VDI with Windows Server 2018 r2 RRS feed

  • Question

  • Hello,

    We have a custom app written in Visual Studio 2015 that we wanted to install on a VDI running Windows Server 2008 r2.  The application crashes immediately upon startup.  Here is the error code:

    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: SmartCardRemovalReminder.exe
      Problem Signature 02:
      Problem Signature 03: 5bbcf80b
      Problem Signature 04: SmartCardRemovalReminder
      Problem Signature 05:
      Problem Signature 06: 5bbcf80b
      Problem Signature 07: 45
      Problem Signature 08: 40
      Problem Signature 09: System.ArgumentException
      OS Version: 6.1.7601.
      Locale ID: 1033
      Additional Information 1: 0a9e
      Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
      Additional Information 3: 0a9e
      Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

    We would really appreciate an suggestions or feedback you can give us on how to resolve this issue.  Thank you!

    Thursday, October 25, 2018 7:06 PM

All replies

  • Hello,

    1. What code is executing at startup of the application.
    2. Are you interfacing with hardware?
    3. Have you tried using try/catch statements that log to a log file when exception is raised?
    4. The only clue in the stack is System.ArgumentException which most likely points to the issue
    5. Also consider permissions/policies for the server.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.
    VB Forums - moderator
    profile for Karen Payne on Stack Exchange, a network of free, community-driven Q&A sites

    Thursday, October 25, 2018 10:30 PM
  • Given the argument exception it sounds like you're looking for a path or something that doesn't exist on that machine. Drop the PDB files associated with the binary you are deploying onto that machine and run it again. When it crashes the WER dialog you'll get has an option for technical information. That option will take you to the files WER generates which includes a crash dump. Given the PDBs, the binaries and the crash dump file you can load it up into VS and get the crash information.

    Alternatively if you're using logging or something then your log files should be catching the exception. Often the call stack is part of the WER report itself so I assume that the above information is only a portion of the data you're seeing in the event log. But for your app maybe you aren't getting anything else.

    Michael Taylor

    Friday, October 26, 2018 9:58 PM