JIT Debugging needs to be installed

G

Guest

Hi,

I have Windows XP Pro, SP2, IE7.

I recently installed a HP Deskjet 5610 All-In-One printer. I have tried to
resolved this problem with Hewlett Packard but the solutions they gave me
didn't help.

The basic problem is that Windows doesn't recognize several programs that
were installed with the printer. Approximately 1/2 the time I reboot, I
receive a message that I need to insert the HP program disk in my CD ROM
drive so that TrayApp and DocumentViewer can be installed. These programs
have been installed at least 10 times.

The message that I receive is very long but the end of it says:

"To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog."


I'm surmising that if I enable JIT debugging, I'll no longer have the
TrayApp and DocumentViewer problems, but I don't know how to do what needs to
be done, what is mentioned in the message.

Would someone lead me by the hand?

Denise
 
G

Guest

Hi jmatt,

Thanks for responding and heading me in the right direction. It seems that
many people are experiencing the same problem.

Since I have no idea how to write or re-write script, I followed 2 methods
to get a Debugger working. First I tried to get JIT Debugger working. I
went into Tools -> Internet Options -> Advanced Tab -> uncheck "Disable
Script Debugging." However, I kept getting messages on most of the pages
that I opened that asked me if I wanted to debug a script. I needed to click
on "Yes" a number of times for each page that caused me to receive the
message and most of them ended with "permission denied." I would prefer to
use JIT Debugger but some settings need to be changed so that I no longer
receive these messages but I don't know where the settings are located or how
to change them.

I also just found a Microsoft url http://support.microsoft.com/kb/923827 for
Dr. Watson. In case the link doesn't work, it says

"Method 1: Re-enable the Dr. Watson program to catch unhandled exceptions
You can re-enable the Dr. Watson program to catch unhandled exceptions.
After you do this, the Visual Studio JIT debugger will no longer catch
unhandled exceptions. To do this, follow these steps:1. Click Start, click
Run, type cmd, and then click OK.
2. Type the following command, and then press ENTER:
drwtsn32 -i "

I followed the instructions and it gave me the message that Dr. Watson was
now my default debugger. I can't tell you yet how well it's working or not
working, but I'll be back tomorrow and let you know.

Denise
 
J

jmatt

I followed the instructions and it gave me the message that Dr. Watson was
now my default debugger. I can't tell you yet how well it's working or not
working, but I'll be back tomorrow and let you know.
Click to expand...

Hi Denise, thanks for that, it's going to be very interesting to see
if that is the fix.

John.
 
G

Guest

Hi jmatt,

I haven't received the JIT Debugging message again, but I haven't rebooted
my computer much within the last few days. I didn't always receive the
message when I rebooted so the fact that it hasn't cropped up again doesn't
mean much.

I'm having a new problem with the JIT debugging. For many pages that I open
I receive a message that says that a page needs to be debugged and it asks me
if I want to debug it. I click yes to several requests and at the end, it
tells me that it failed or that I don't have the permission to do it.

I use Dial-A-Fix so I "Repaired Permission" but it didn't help.

Any thoughts?

Denise
 
J

jmatt

I'm having a new problem with the JIT debugging. For many pages that I open
I receive a message that says that a page needs to be debugged.
Click to expand...

If you are using IE then do the following.
http://www.tweaksforgeeks.com/IEDebug.html
Tools > Internet Options > Advanced > Browsing.
Make sure there is checkmarks against > Disable Script Debugging
(Internet Explorer) & Disable Script Debugging (Other)
Remove the checkmark, if applicable against > Display a notification
about every script error.
Now hit OK.
 
G

Guest

Hi again jmatt :)

I checked and those three boxes aren't checked.

Also, when I rebooted about an hour ago, I received the "unhandled
exception" message again and my pc froze. I put the HP disk in my CD ROM
Drive and hit the reset button on my tower and when my pc booted up, it
installed TrayApp and DocumentViewer again. I know it's a HP problem but I'm
hoping that changing Windows settings will fix the problem because HP hasn't
been able to. JIT and Dr. Watson are more of an annoyance now because they
don't debug the problem but constantly ask me if I want to debug an
exception. Clicking the "Yes" button about 5 or 6 times leads me to the end
which tells me that either it hasn't/couldn't be debugged or I don't have the
permission to do it. I'm the admin of my pc.

If you can think of anything else, I'm ready to listen, and I appreciate the
help you've given me so far . . . thanks :)

Denise
 
J

jmatt

If you can think of anything else, I'm ready to listen, and I appreciate the
help you've given me so far . . . thanks :)
Click to expand...

You may be able to get more info from the Event viewer Denise.
HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308427
Or,
Start > Run, copy & paste > eventvwr.msc /s & press Enter.
Scroll down to the last time your computer crashed and it should tell
you what device/driver caused the problem?

Also, minidumps.
Control Panel --> System --> Advanced --> Startup and Recovery -->
Settings ---> Write debugging
information --> Complete memory dump
Minidumps are located in c/windows/minidumps
How to solve Windows system crashes in minutes
http://www.networkworld.com/news/2005/041105-windows-crash.html
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://forums.majorgeeks.com/showthread.php?t=35246
This primer will show you how to solve problems quickly. Using a tool
that costs nothing, you can solve approximately 50% of Windows server
and workstation crashes in a few minutes. The tool is WinDbg, the free
Windows debugger.
You've probably never used the debugger, don't have it and don't want
it. After all, it's a developer's tool, not an administrator's, right?
Yes, but what you need to know is remarkably easy to learn, and even a
rudimentary familiarity with the debugger could enhance your skills
and your resume.
Still hesitant? Think about this: After rebooting a crashed machine,
we've brought up the debugger, opened a memory dump file, given the
debugger a single command, and learned not only that the cause was a
driver, but also the driver's name - all in less than a minute.
Granted, the debugger was installed and configured, we knew what
commands to use and what to look for.

Another thought.
If you want to be 100% sure it's a HP problem, uninstall it.
 
G

Guest

Hi jmatt,

Today at 5:30:18 PM, I received a Warning, Source MSilnstaller, Category
None, Event ID 1001. The description says: "Detection of product
'{172975EB0946504861-95B5-C7BB6D3DE62A}'. feature 'DocViewerExe' failed
during request for component '{916C2D9A-BB97-4065-9F32-153578753C3A}'.

I clicked on the link that was included in the message:

Details
Event ID: 1001
Source: MsiInstaller

We're sorry
There is no additional information about this issue in the Error and Event
Log Messages or Knowledge Base databases at this time. You can use the links
in the Support area to determine whether any additional information might be
available elsewhere.

Denise
 
G

Guest

Also, in the System Event Viewer, at 5:32:58 PM today, I received a Warning.
It says:

"Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 2/3/2007
Time: 5:32:58 PM
User: N/A
Computer: OWNER-6DVD83PEX
Description:
The Routing and Remote Access service terminated with service-specific error
340 (0x154).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

At the url, it says:

Details
Product: Windows Operating System
Event ID: 7024
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED_SPECIFIC
Message: The %1 service terminated with service-specific error %2.

Explanation
The specified service stopped unexpectedly with the error indicated in the
message. Windows does not recognize the service's error code.

User Action
To display the service-specific error code in the Service_Exit_Code field,
at the command line, type sc query service name. The information displayed
might help you troubleshoot why the error occurred. (WHEN I TYPED CMD AND SC
QUERY, A VERY LONG LIST APPEARED THAT I COULDN'T COPY AND PASTE. IF YOU
THINK THE INFO IS IMPORTANT IN PIN-POINTING THE PROBLEM WITH MY PC, I CAN
TYPE IT UP LINE FOR LINE.)

Version: 5.2
Symbolic Name: EVENT_SERVICE_EXIT_FAILED_SPECIFIC
Message: The %1 service terminated with service-specific error %2.

Explanation
The specified service stopped unexpectedly with the error indicated in the
message. Windows does not recognize the service's error code.

User Action
To display the service-specific error code in the Service_Exit_Code field,
at the command line, type sc query service name. The information displayed
might help you troubleshoot why the error occurred.

Related Knowledge Base articles
You can find additional information on this topic in the following
Microsoft Knowledge Base articles:
• You cannot start the Routing and Remote Access service on a Windows 2000
Server-based computer or on a Windows Server 2003-based computer
Describes an issue where you cannot start the Routing and Remote Access
service. Event ID 7024 and event ID 20152 are logged in the system event log.
This issue may occur if the IAS database is damaged.
• Error 2270 Is Described as "Computer Name Could Not Be Added as a Message
Alias" for Messenger Service
During the startup process, you may see the following error message: At
least one service or driver failed during system startup. Use Event Viewer to
examine the event log for details. Event Viewer shows Service Control Manager
event ID 7024,...
• You may receive error code -1073737712 when you try to start the
Distributed Transaction Coordinator service in Windows XP or in Windows
Server 2003
Discusses a problem where the Distributed Transaction Coordinator service
does not start and you receive a "-1073737712" error code. This article
describes two methods to resolve this problem.
• The Computer Browser service does not start and event ID 7024 is logged
when you restart your Windows XP Service Pack 2-based computer
Explains why event ID 7024 is logged and the Computer Browser service may
not start. Explains how to configure Microsoft Firewall for file and printer
sharing so that the Computer Browser service can start.
• Some services may not start when you upgrade a computer to Windows XP
Service Pack 2 or to Windows Server 2003 Service Pack 1
Describes the problem where some services may not start when you upgrade a
computer to Windows XP Service Pack 2 (SP2) or to Windows Server 2003 Service
Pack 1 (SP1). A resolution is provided. "

Denise
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

JIT Debugging 1
JIT Debugging 0
Just In Time Debugging in Windows Config File 1
SEATOOLS will not run. Can't test drive? 0
JIT Debugging 1
Do you guys HELP with .NET Problems?? 3
The Server Response was 5.5.1 Authentication Required 0
JIT Debugging 0

Top