Home Dashboard Directory Help
Search

JIT Debugger by charles prabhu


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 420915
Opened: 3/5/2009 3:38:43 AM
Access Restriction: Public
2
Workaround(s)
view
3
User(s) can reproduce this bug

Description

i have used Microsoft script debugger for a while and i have uninstalled the script debugger
after that i wasn't able to debug the script files Using IE?

what will be the possible solution to make debug my script files.

"Unable to attach to the crashing process. An error occurred that usually indicates a corrupt installation (code 0x80040155). If the problem persists, repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel."

thanks in advance
Details
Sign in to post a comment.
Posted by Ivan-fjf on 6/18/2012 at 7:00 PM
Unable to attach to the crashing process. An error occurred that usually indicates a corrupt installation (code 0x80040155).

solution:
1、Copy msdbg2.dll , pdm.dll(c:\program files\common files\microsoft shared\vs7debug\) to c:\windows\system32
2、excute "regsvr32.exe c:\windows\system32\msdbg2.dll" in commond line.
Posted by BBirajdar on 9/2/2010 at 7:09 AM
I am facing the same issue.

I installed VS 2008
Then installed the Microsoft Script debugger. Used it for a while and then uninstalled.
Now, when I try to debug javascript through VS 2008, it gived me this error

Also I tried to enable script debugging for JIT from VS Tools> Debugging> Just-in-time.> Script

Then I get this error message.

I tried complete reinstalling of VS 2008. But no use
Posted by charles prabhu on 3/30/2009 at 11:21 PM
when i installed visual studio 2008 over 2005.the bug was automatically resolved,
i am not sure what cause the bug:)...
Posted by Microsoft on 3/30/2009 at 4:54 PM
Hello,

Since we have not heard back from you regarding whether you attempted a repair from the control panel that failed to resolve this problem, we are going to have to close the bug. If at any point in the future you have a chance to respond, please re-activate the bug.

Best Regards,
Andrew Hall
Visual Studio Debugger
Posted by Microsoft on 3/17/2009 at 6:18 PM
Hello,

Did you try repairing your Visual Studio installation from the Control Panel "Add/Remove Programs"?

Best Regards,
Andrew Hall
Visual Studio Debugger
Posted by Microsoft on 3/5/2009 at 11:26 PM
Thanks for your feedback. We are escalating this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.
Posted by Ivan-fjf on 6/18/2012 at 6:59 PM
1、Copy msdbg2.dll , pdm.dll(c:\program files\common files\microsoft shared\vs7debug\) to c:\windows\system32
2、excute "regsvr32.exe c:\windows\system32\msdbg2.dll" in commond line.
Posted by 皮皮1986 on 6/7/2010 at 6:06 PM
Please check the 'Distributed Transaction Coordinator' and 'WMI Performance Adapter' Service. If which are closed, please start, because will use its when the .Net framework is installing.