none
Remote debugger crashes when trying to debug locally

    Question

  • My team has all started having an odd issue with Visual Studio all at once. It occurs with different versions (2015, 2017) on different machines, but the problems started for all of us at once. We are unable to debug locally.

    Here are the errors details:

    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: msvsmon.exe
      Application Version: 15.0.26228.0
      Application Timestamp: 58b565ab
      Fault Module Name: dgapi64.dll
      Fault Module Version: 7.3.0.1021
      Fault Module Timestamp: 58937c18
      Exception Code: c0000005
      Exception Offset: 000000000018f699
      OS Version: 6.1.7601.2.1.0.256.4
      Locale ID: 1033
      Additional Information 1: 760d
      Additional Information 2: 760d72250deffbe71745df9cedf89d34
      Additional Information 3: 1e5a
      Additional Information 4: 1e5a482fdaa69ee459afdf9cc4cf1786

    One person is able to debug when set to 32 bit, but no one else can. The odd thing is that actual remote debugging works (Manually starting msvsmon on the local machine and the specifying your own machine name and port in the project properties.) The problem started for us on March 10th, 2017. The first time we run the project, the remote debugger crashes, resulting the exception info above. Subsequent runs just get an error message stating that msvsmon is not running on the remote machine. 

    Any idea what could cause this?

    Tuesday, March 14, 2017 10:49 PM

Answers

  • Hi Keith Emanuel,

    >>Fault Module Name: dgapi64.dll.

    Is it related one third party software like the Digital Guardian or others?

    If it worked well before or certain member could debug it normally, I suggest you compare the Windows Environment, maybe yours installed certain third party tools/software or others.

    Please also visit the Event viewer to get more detailed messages there.

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, March 16, 2017 10:32 AM
    Moderator

All replies

  • Hi Keith Emanuel,

    >>Fault Module Name: dgapi64.dll.

    Is it related one third party software like the Digital Guardian or others?

    If it worked well before or certain member could debug it normally, I suggest you compare the Windows Environment, maybe yours installed certain third party tools/software or others.

    Please also visit the Event viewer to get more detailed messages there.

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, March 16, 2017 10:32 AM
    Moderator
  • It looks like it is related to Digital Guardian. Apparently it just recently started being installed. I have a ticket open with them now. Waiting on their response now. Thanks!
    Thursday, March 16, 2017 8:22 PM
  • Hi Keith Emanuel,

    You are welcome.

    If this issue has been resolved, please make helpful replies as the answers, so it would help other community members, and I could help you close this case.

    Have a nice day,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 17, 2017 4:25 AM
    Moderator