Just In Time Debugger

The Instillation has 3 servers
Two Microsoft Server 2003 R2 S/P 2
Microsoft Server 1003 S/P 2

I have 3 servers which have remote desktop users running an application that runs a Crystal Report.

The server without the R2  runs the report with not problems.
One of the servers was recently upgraded to R2 and the report ran on that server before the R2 upgrade

After the R2 Upgrade
When the report is run
JUST IN TIME DEBUGGER error occurs which of course tells you nothing and just closes the program.

The error appears to occur in a formula of the report where SELECT CASE is used.

Are they a way to turn off the JUST IN TIME DEBUGGER or ANY OTHER SUGGESTIONS WOULD BE APPRECIATED?





 
LVL 2
Phil ChapmanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

csoussanCommented:
To enable/disable Just-In-Time debugging

1)  On the Tools menu, click Options.

2)  In the Options dialog box, select the Debugging folder.

3)  In the Debugging folder, select the Just-In-Time page.

4)  In the Enable Just-In-Time debugging of these types of code box, select or
     clear the relevant program types: Managed, Native, or Script.

     To disable Just-In-Time debugging, once it has been enabled, you must be
     running with Administrator privileges. Enabling Just-In-Time debugging sets a
     registry key, and Administrator privileges are required to change that key.

5) Click OK.
0
Phil ChapmanAuthor Commented:
Are you referring to Microsoft Server Administrative Tools ?  If so which option?

Thanks
0
csoussanCommented:
The above enable/disable instructions apply to Microsoft Visual Studio 2003, 2005 and 2008/.NET Framework (http://msdn2.microsoft.com/en-us/library/5hs4b7a6.aspx)

Note: Make sure you click the checkbox in the lower left corner of the Options dialog box.

If you prefer, you can re-enable the Dr. Watson program to catch unhandled exceptions (http://support.microsoft.com/default.aspx/kb/923827) instead.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
edbedbCommented:
Seems to me that this suggestion in the first one by csoussan might do it.
"If you prefer, you can re-enable the Dr. Watson program to catch unhandled exceptions (http://support.microsoft.com/default.aspx/kb/923827) instead.  "
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.