How to trace the error if Visual Studio Just-In-Time Debugger non-stopped to prompt for OWSTIMER.EXE RRS feed

  • Question

  • Greetings, I have a SharePoint Devlopment Server that multiple teams shared, now we have no idea if Visual Studio Just-In-Time Debugger non-stopped to prompt for OWSTIMER.EXE...

    Could you please advise how to trace if we assumed the error should be triggered by some custom SharePoint timer job (not sure, may be caused by SharePoint but we need the proof. e.g. How to check the related job name / Program name if Sharepoint timer job crashed)? Thanks a lot. 

    (Don't know who done it and don't we have source code or not. Very worry if one day we have the same error on Produciton Site and some critial job cannot be done.)

    Message as follows:

    --------------------------------------- Visual Studio just-In-Time Debugger --------------------------------------- An unchandled exception System.Security.Cryptography.CrypraghicException occurced in OWSTIMER.EXE Possible Debuggers: - Visual Studio 2010 - Visual Studio 2013 [ ] Set the current selected debugger as the default [ ] Manully choose the debugging engines Do you want to debug using the selected debugger?

    [Yes] [No] // When I click [Yes], message shown: "Unable to attach the crashing process. The process had been terminated"

    .NET Beginner 3.5

    Wednesday, March 1, 2017 9:16 AM