Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeraldaUse another job step.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeralda

Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeraldaUse another job step.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeraldasql

Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeralda
Use another job step.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeralda

Job Fails on Linked Server [solution]

I've got a job running on a SQL2005 box (server07) that modifies data on a SQL2000 box (server05). The databases on the 2005 were imported from an older box running SQL2000. The step that is failing is:

update server05.xtender.sysop.ae_rf4
set field3 = sname
from server05.xtender.sysop.ae_rf4 x inner join allscholarships..studentsindb_table s
on x.field1 = s.ssn
where x.field3 is null or len(field3) = 0

The history shows this for the failed step:

Message
Executed as user: Domain\Administrator. Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)Unable to open Step output file. The step failed.

Domain\Administrator is a sysadmin on both boxes. This job had been running some time ago, but the SQL2000 box (under a different dba) has somehow changed. Now I need to get the thing running again.

Hi,

The error said its untrusted connection ... have you tried re mapping accounts using sp_addlinkedsrvlogin!!!?

refer this thread http://www.webservertalk.com/archive137-2006-4-1477449.html

Hemantgiri S. Goswami

|||That discussion is the only thing that pops up when I google "Error 15274", I've read the very original and he hasn't gotten an answer yet.

The best I can tell is that the SQL Agent is supplying the security credentials to the linked server and I'm not able to specify which security context for the job to use.

In the Job Step Properties pages, under each step's General page in the middle of the window is a dropdown - Run As. There is nothing in the dropdown list and no way to enter a value. On the Advanced page of each step is a Run As User with a select user button, I've entered every conceivable value on this Advanced page with no success.
|||Check services - which account is used for startup of the SQL agent. System account is no good - only local resources are available. Use "This account" with administrative rights on the Windows & SQL server.|||Make sure Domain\Administrator has got required privilges on SQL Server (incl. SQLAgent) in order to complete the job process.|||Also check the linked server setup - security. Check "Be made using the login's current security context".|||

a very weird issue. Was able to resolve it using a new NT Account with Admin rights. Just created it at both servers, then added to both SQL Servers with rights I needed. And also set this account to be used for SQL Agent service.

Oh, also have used the imporsonate setting for linked servers mapping (at both sides)

and just leave "run as user" blank for step settings

|||check the connectivity of your linked server using sp_testlinkedserver

Job Fails on Linked Server

I've got a job running on a SQL2005 box (server07) that modifies data on a SQL2000 box (server05). The databases on the 2005 were imported from an older box running SQL2000. The step that is failing is:

update server05.xtender.sysop.ae_rf4
set field3 = sname
from server05.xtender.sysop.ae_rf4 x inner join allscholarships..studentsindb_table s
on x.field1 = s.ssn
where x.field3 is null or len(field3) = 0

The history shows this for the failed step:

Message
Executed as user: Domain\Administrator. Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)Unable to open Step output file. The step failed.

Domain\Administrator is a sysadmin on both boxes. This job had been running some time ago, but the SQL2000 box (under a different dba) has somehow changed. Now I need to get the thing running again.

Hi,

The error said its untrusted connection ... have you tried re mapping accounts using sp_addlinkedsrvlogin!!!?

refer this thread http://www.webservertalk.com/archive137-2006-4-1477449.html

Hemantgiri S. Goswami

|||That discussion is the only thing that pops up when I google "Error 15274", I've read the very original and he hasn't gotten an answer yet.

The best I can tell is that the SQL Agent is supplying the security credentials to the linked server and I'm not able to specify which security context for the job to use.

In the Job Step Properties pages, under each step's General page in the middle of the window is a dropdown - Run As. There is nothing in the dropdown list and no way to enter a value. On the Advanced page of each step is a Run As User with a select user button, I've entered every conceivable value on this Advanced page with no success.
|||Check services - which account is used for startup of the SQL agent. System account is no good - only local resources are available. Use "This account" with administrative rights on the Windows & SQL server.|||Make sure Domain\Administrator has got required privilges on SQL Server (incl. SQLAgent) in order to complete the job process.|||Also check the linked server setup - security. Check "Be made using the login's current security context".|||

a very weird issue. Was able to resolve it using a new NT Account with Admin rights. Just created it at both servers, then added to both SQL Servers with rights I needed. And also set this account to be used for SQL Agent service.

Oh, also have used the imporsonate setting for linked servers mapping (at both sides)

and just leave "run as user" blank for step settings

|||check the connectivity of your linked server using sp_testlinkedserver

Job Fails on Linked Server

I've got a job running on a SQL2005 box (server07) that modifies data on a SQL2000 box (server05). The databases on the 2005 were imported from an older box running SQL2000. The step that is failing is:

update server05.xtender.sysop.ae_rf4
set field3 = sname
from server05.xtender.sysop.ae_rf4 x inner join allscholarships..studentsindb_table s
on x.field1 = s.ssn
where x.field3 is null or len(field3) = 0

The history shows this for the failed step:

Message
Executed as user: Domain\Administrator. Access to the remote server is denied because the current security context is not trusted. [SQLSTATE 42000] (Error 15274)Unable to open Step output file. The step failed.

Domain\Administrator is a sysadmin on both boxes. This job had been running some time ago, but the SQL2000 box (under a different dba) has somehow changed. Now I need to get the thing running again.

Hi,

The error said its untrusted connection ... have you tried re mapping accounts using sp_addlinkedsrvlogin!!!?

refer this thread http://www.webservertalk.com/archive137-2006-4-1477449.html

Hemantgiri S. Goswami

|||That discussion is the only thing that pops up when I google "Error 15274", I've read the very original and he hasn't gotten an answer yet.

The best I can tell is that the SQL Agent is supplying the security credentials to the linked server and I'm not able to specify which security context for the job to use.

In the Job Step Properties pages, under each step's General page in the middle of the window is a dropdown - Run As. There is nothing in the dropdown list and no way to enter a value. On the Advanced page of each step is a Run As User with a select user button, I've entered every conceivable value on this Advanced page with no success.|||Check services - which account is used for startup of the SQL agent. System account is no good - only local resources are available. Use "This account" with administrative rights on the Windows & SQL server.|||Make sure Domain\Administrator has got required privilges on SQL Server (incl. SQLAgent) in order to complete the job process.|||Also check the linked server setup - security. Check "Be made using the login's current security context".|||

a very weird issue. Was able to resolve it using a new NT Account with Admin rights. Just created it at both servers, then added to both SQL Servers with rights I needed. And also set this account to be used for SQL Agent service.

Oh, also have used the imporsonate setting for linked servers mapping (at both sides)

and just leave "run as user" blank for step settings

|||check the connectivity of your linked server using sp_testlinkedserver

JIT Debug HELP

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at HP.CUE.Video.PlaybackControl.UpdateProgressBar()
at HP.CUE.Video.PlaybackControl._ProgressTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.Callback(IntPtr hWnd, Int32 msg, IntPtr idEvent, IntPtr dwTime)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
-
hpqimzone
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///C:/Program%20Files/HP/Digital%20Imaging/bin/hpqimzone.exe
-
hpqiface
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqiface/4.0.0.0__a53cf5803f4c3827/hpqiface.dll
-
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
-
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
-
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
-
hpqcc2
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqcc2/3.0.0.0__a53cf5803f4c3827/hpqcc2.dll
-
hpqutils
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqutils/4.0.0.0__a53cf5803f4c3827/hpqutils.dll
-
hpqfmrsc
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqfmrsc/4.0.0.0__a53cf5803f4c3827/hpqfmrsc.dll
-
hpqtray
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqtray/4.0.0.0__a53cf5803f4c3827/hpqtray.dll
-
hpqovskn
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqovskn/3.0.0.0__a53cf5803f4c3827/hpqovskn.dll
-
hpqimvlt
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqimvlt/3.0.0.0__a53cf5803f4c3827/hpqimvlt.dll
-
hpqimgrc
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqimgrc/4.0.0.0__a53cf5803f4c3827/hpqimgrc.dll
-
hpqntrop
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqntrop/4.0.0.0__a53cf5803f4c3827/hpqntrop.dll
-
Interop.hpqcxm08
Assembly Version: 3.0.0.0
Win32 Version: 53.0.13.000
CodeBase: file:///c:/windows/assembly/gac/interop.hpqcxm08/3.0.0.0__a53cf5803f4c3827/interop.hpqcxm08.dll
-
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
-
LEAD
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead/13.0.0.113__9cf889f53ea9b907/lead.dll
-
LEAD.Wrapper
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.wrapper/13.0.0.113__9cf889f53ea9b907/lead.wrapper.dll
-
LEAD.Windows.Forms
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.windows.forms/13.0.0.113__9cf889f53ea9b907/lead.windows.forms.dll
-
LEAD.Drawing
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.drawing/13.0.0.113__9cf889f53ea9b907/lead.drawing.dll
-
interop.hpqimgr
Assembly Version: 3.0.0.0
Win32 Version: 53.0.13.000
CodeBase: file:///c:/windows/assembly/gac/interop.hpqimgr/3.0.0.0__a53cf5803f4c3827/interop.hpqimgr.dll
-
hpqthumb
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqthumb/3.0.0.0__a53cf5803f4c3827/hpqthumb.dll
-
hpqasset
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqasset/4.0.0.0__a53cf5803f4c3827/hpqasset.dll
-
hpqmirsc
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///C:/Program%20Files/HP/Digital%20Imaging/bin/hpqmirsc.DLL
-
hpqedit
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqedit/3.0.0.0__a53cf5803f4c3827/hpqedit.dll
-
hpqvideo
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqvideo/3.0.0.0__a53cf5803f4c3827/hpqvideo.dll
-
LEAD.Windows.Forms.DrawingContainer
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.windows.forms.drawingcontainer/13.0.0.113__9cf889f53ea9b907/lead.windows.forms.drawingcontainer.dll
-
hpqmdmr
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqmdmr/4.0.0.0__a53cf5803f4c3827/hpqmdmr.dll
-
LEAD.Drawing.Imaging.ImageProcessing
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.drawing.imaging.imageprocessing/13.0.0.113__9cf889f53ea9b907/lead.drawing.imaging.imageprocessing.dll
-
hpqimlib
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqimlib/3.0.0.0__a53cf5803f4c3827/hpqimlib.dll
-
hpqglutl
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqglutl/4.0.0.0__a53cf5803f4c3827/hpqglutl.dll
-
Interop.hpqvideo
Assembly Version: 3.0.0.0
Win32 Version: 53.0.13.000
CodeBase: file:///c:/windows/assembly/gac/interop.hpqvideo/3.0.0.0__a53cf5803f4c3827/interop.hpqvideo.dll
-

************** JIT Debugging **************
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.

Hello Marc, I was just wondering what this ( Jit Debug Popup) means when it pops up onto your desktop. It happened to me today, and I want to know if there's anything to fix. If you could email me at goertzmatt@.hotmail.com I would greatly appreaciate it!!!!|||

Matt,

The cause of the JIT Debug I had was cause by my HP All in One Printer.

Since no one answered my problem I made a backup of all my files and rebuild my hard drive, formated like brand new. Reinstalled all my software and restore my files.

My PC is like brand new without problem. Hope this leads you to an idea of what is your next step.

Marc

JIT Debug HELP

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at HP.CUE.Video.PlaybackControl.UpdateProgressBar()
at HP.CUE.Video.PlaybackControl._ProgressTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.Callback(IntPtr hWnd, Int32 msg, IntPtr idEvent, IntPtr dwTime)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
-
hpqimzone
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///C:/Program%20Files/HP/Digital%20Imaging/bin/hpqimzone.exe
-
hpqiface
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqiface/4.0.0.0__a53cf5803f4c3827/hpqiface.dll
-
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
-
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
-
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
-
hpqcc2
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqcc2/3.0.0.0__a53cf5803f4c3827/hpqcc2.dll
-
hpqutils
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqutils/4.0.0.0__a53cf5803f4c3827/hpqutils.dll
-
hpqfmrsc
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqfmrsc/4.0.0.0__a53cf5803f4c3827/hpqfmrsc.dll
-
hpqtray
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqtray/4.0.0.0__a53cf5803f4c3827/hpqtray.dll
-
hpqovskn
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqovskn/3.0.0.0__a53cf5803f4c3827/hpqovskn.dll
-
hpqimvlt
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqimvlt/3.0.0.0__a53cf5803f4c3827/hpqimvlt.dll
-
hpqimgrc
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqimgrc/4.0.0.0__a53cf5803f4c3827/hpqimgrc.dll
-
hpqntrop
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqntrop/4.0.0.0__a53cf5803f4c3827/hpqntrop.dll
-
Interop.hpqcxm08
Assembly Version: 3.0.0.0
Win32 Version: 53.0.13.000
CodeBase: file:///c:/windows/assembly/gac/interop.hpqcxm08/3.0.0.0__a53cf5803f4c3827/interop.hpqcxm08.dll
-
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
-
LEAD
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead/13.0.0.113__9cf889f53ea9b907/lead.dll
-
LEAD.Wrapper
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.wrapper/13.0.0.113__9cf889f53ea9b907/lead.wrapper.dll
-
LEAD.Windows.Forms
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.windows.forms/13.0.0.113__9cf889f53ea9b907/lead.windows.forms.dll
-
LEAD.Drawing
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.drawing/13.0.0.113__9cf889f53ea9b907/lead.drawing.dll
-
interop.hpqimgr
Assembly Version: 3.0.0.0
Win32 Version: 53.0.13.000
CodeBase: file:///c:/windows/assembly/gac/interop.hpqimgr/3.0.0.0__a53cf5803f4c3827/interop.hpqimgr.dll
-
hpqthumb
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqthumb/3.0.0.0__a53cf5803f4c3827/hpqthumb.dll
-
hpqasset
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqasset/4.0.0.0__a53cf5803f4c3827/hpqasset.dll
-
hpqmirsc
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///C:/Program%20Files/HP/Digital%20Imaging/bin/hpqmirsc.DLL
-
hpqedit
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqedit/3.0.0.0__a53cf5803f4c3827/hpqedit.dll
-
hpqvideo
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqvideo/3.0.0.0__a53cf5803f4c3827/hpqvideo.dll
-
LEAD.Windows.Forms.DrawingContainer
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.windows.forms.drawingcontainer/13.0.0.113__9cf889f53ea9b907/lead.windows.forms.drawingcontainer.dll
-
hpqmdmr
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqmdmr/4.0.0.0__a53cf5803f4c3827/hpqmdmr.dll
-
LEAD.Drawing.Imaging.ImageProcessing
Assembly Version: 13.0.0.113
Win32 Version: 13.0.0.113
CodeBase: file:///c:/windows/assembly/gac/lead.drawing.imaging.imageprocessing/13.0.0.113__9cf889f53ea9b907/lead.drawing.imaging.imageprocessing.dll
-
hpqimlib
Assembly Version: 3.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqimlib/3.0.0.0__a53cf5803f4c3827/hpqimlib.dll
-
hpqglutl
Assembly Version: 4.0.0.0
Win32 Version: 053.000.013.000
CodeBase: file:///c:/windows/assembly/gac/hpqglutl/4.0.0.0__a53cf5803f4c3827/hpqglutl.dll
-
Interop.hpqvideo
Assembly Version: 3.0.0.0
Win32 Version: 53.0.13.000
CodeBase: file:///c:/windows/assembly/gac/interop.hpqvideo/3.0.0.0__a53cf5803f4c3827/interop.hpqvideo.dll
-

************** JIT Debugging **************
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.

Hello Marc, I was just wondering what this ( Jit Debug Popup) means when it pops up onto your desktop. It happened to me today, and I want to know if there's anything to fix. If you could email me at goertzmatt@.hotmail.com I would greatly appreaciate it!!!!|||

Matt,

The cause of the JIT Debug I had was cause by my HP All in One Printer.

Since no one answered my problem I made a backup of all my files and rebuild my hard drive, formated like brand new. Reinstalled all my software and restore my files.

My PC is like brand new without problem. Hope this leads you to an idea of what is your next step.

Marc