This is a problem that affects a lot of you and the simptoms are that after
you load a document containing client side script in Internet Explorer, you
don't see "Script" in the Type column in the Debug | Processes dialog for IE
and hence you cannot debug any client side script in IE. This happens most
likely because of some configuration issues in DCOM. Here are some of the
solutions we identified so far:
1. You don't have script debugging enabled on your machine. In Internet
Explorer go to Tools | Internet Options | Advanced and uncheck the Disable
Script debugging box.
2. You have at least one of the following registry keys:
HKLM\Software\Microsoft\Ole\DefaultAccessPermissions
HKLM\Software\Microsoft\Ole\LegacyAuthenticationLevel
HKLM\Software\Microsoft\Ole\LegacyImpersonationLevel
just delete them. They were probably added on your machine by installing an
older software (I'm curious which one) and are not useful.
Then, reset mdm by running the following commands from a cmd prompt:
net stop mdm
net start mdm
And finally, close and re-open IE with your page.
Now, you should be able to see Script in the Processes dialog as the Type
for IE. Just attach to IE in Script mode, open your document from the Debug
| Windows | Running Documents window, set breakpoints and you should be able
to debug.
Please let me know if none of these fix your problem by sending me the
contents of the HKLM\Software\Microsoft\Ole registry key.
You can find more information about script debugging at:
http://www.gotdotnet.com/team/csharp/learn/whitepapers/How%20to%20debug%20sc
ript%20in%20Visual%20Studio%20.Net.doc
Hope this helps,
Monica
<drive>:\Documents and Settings\All Users\Application Data\Microsoft\Machine
Debug Manager\mdm.ini
Gregg
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Zvi Danovich" <z...@cmt.co.il> wrote in message
news:OFvfQk7oCHA.2564@TK2MSFTNGP10...
> Hello, Monica,
> I saw many messages on this issue, because I have the same problem too. As
> many others, I can successfully debug server scripts, but cannot do it for
> client ones.
> I have performed on my computer all what you recommend in the message that
I
> am replying for now, and in addition I have checked the pdm.dll loading as
> you requested in your letter to <bor...@yahoo.com>.
>
> The results you can see in the Word file attached: pdm.dll is used by the
IE
> process PID 2964 that runs the script, but "Type" is empty (and "Debugger"
> column has "Microsoft Development Environment" !).
>
> How can we continue at this point ?
>
> Thank you for advance,
>
> Zvi
>
> "Monica Rosculet [MS]" <mko...@online.microsoft.com> wrote in message
> news:#s7P70YnCHA.1816@TK2MSFTNGP11...
Hope for your success,
Zvi
"Visual C# Team" <csh...@microsoft.com> wrote in message
news:#I2V0uMpCHA.2384@TK2MSFTNGP09...
Thanks,
Monica Rosculet
--
This posting is provided "AS IS" with no warranties, and confers no rights
"Zvi Danovich" <z...@cmt.co.il> wrote in message
news:uxkSTxPpCHA.2412@TK2MSFTNGP12...
1. See, please, the attached Word file attached to my message to you on Dec
14: it has the requested screen (i.e contents of
'HKLM\Software\Microsoft\Ole' key).
2. It seems to me, that I did reboot. To be on the 'safe side', I'll do it
once more. But, you wrote previously about restart of 'mdm' only ...
Best regards,
"Visual C# Team" <csh...@microsoft.com> wrote in message
news:#4oXRaupCHA.2600@TK2MSFTNGP10...