"test stand has detected that your script debugging"

[rhowes]

Hi everyone. I am setting up a new installation of Test stand and writing my first sequence with an existing sequence of legacy code.

When I run the sequence and stop on the call to the DLL, and then step into the dll and I get this error:

test stand has detected that your script debugging settings might cause visual studio to hang when attaching to the teststand process to perform this step into operation.

To fix this problem, open internet explorer, select tools>>Internet options>> Advanced, check Browsing>>Disabl script debugging, click okay, and restart your sequence execution.

The message is vague and it is indermanent as to whether I should "enable" or "disable" Script debugging so I tried both. Test stand then crashes again and I get the same error.

Do I need to reboot after each crash? I'll try that next. Any ideas on how to make this error go away?

Thank you for your help.

Richard

[rhowes]

"indeterminant" and...

 What the heck is a mermaid doing by my profile information? Is National Instruments really that childish to their customers?

[James_Grey · Accepted solution]

Hmm, I clicked on your profile and could not find a mermaid.

[rhowes]

The more I think about your response, the less impressed I am. How very UN-helpful that was to answer the least important question in the topic. Want to take a shot at the other questions?

[dug9000]

1) What version of TestStand are you using?

2) What version of Visual Studio are you using?

3) The instructions say to "check" the "Disable script debugging" setting correct? I'm pretty sure by "check" the message means to check the checkbox next to that setting. When I open IE I see two settings related to this "Disable script debugging (Internet Explorer)" and "Disable script debugging (Other)". They should both be checked.

4) I'm not sure if you need to close IE and/or reboot after changing this setting, but it can't hurt, so you might as well give it a try.

Hope this helps,

-Doug

[rhowes]

Hi Dug9000,

Thank you for your assistance.

1) What version of TestStand are you using? TestStand 2010 SP1 Version 4.5.1.134

2) What version of Visual Studio are you using?

Visual Studio Version 10.0.30319 RTMRel

.Net 4.0.30319 RTMRel

3) The instructions say to "check" the "Disable script debugging" setting correct? I'm pretty sure by "check" the message means to check the checkbox next to that setting. When I open IE I see two settings related to this "Disable script debugging (Internet Explorer)" and "Disable script debugging (Other)". They should both be checked.

4) I'm not sure if you need to close IE and/or reboot after changing this setting, but it can't hurt, so you might as well give it a try.

I tested this while both checked and unchecked. more later... I'm going to test something else.

[dug9000]

TestStand is looking at the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main

It is looking at the string value called "Disable Script Debugger"

If such a key and value exist then the value must be set to "yes" or stepinto will give you the error you are seeing.

Hope this helps,

-Doug

[Al.B]

Hi,

Also, could you clarify exactly what you are seeing when you say that TestStand is crashing?  Are you getting a "Sequence Editor has encountered an error and needs to close" error, or does TestStand just close?  Any details on this point would be very helpful - you should not be seeing a crash in this case, so we'd like to investigate why this is occurring.

[rhowes]

Not sure if it is related but the dll would hang due to a code-completion bug. I fixed that. If I run the sequence alone it runs fine, but in an existing Test stand workspace project that was provided to me I get that warning message when Disable Script Debugging is checked (AND the same if unchecked.) And the Registry shows that Disable Script debugging is YES, which accurately reflects the IE options setting.

So now I know that the problem appears to be the Test Stand Workspace provided to me, and I'm off to debug that!

Thank you and I'll keep you posted.

[dug9000]

Is it upper case "YES"? The comparison on the teststand side is currently case-sensitive, though maybe it shouldn't be, and is expecting all lowercase yes.

Also, what version of IE are you using?

-Doug