just-in-time (JIT) debugging

**Plater** · Aug 10 '07, 01:59 PM

Fix the error.
It looks pretty simple.
You're attempting to use an index that doesn't have valid data at it. You can probably do a check for null in your code to stop that.
Or use try/ctach blocks

**LadyU** · Oct 19 '07, 08:21 PM

Hello I am having the same problem and I have no idea how to fix it please any help would be great.I am at a lost right now Thanks for any help

**Plater** · Oct 19 '07, 08:30 PM

System.IndexOut OfRangeExceptio n: There is no row at position 0.

This should not be a brain bender here. Your object does not contain the data you thought it does.
Check to make sure it's not null and that count of items in the collection is enough to match the index you want to use.

**LadyU** · Oct 19 '07, 08:36 PM

Originally posted by Plater

This should not be a brain bender here. Your object does not contain the data you thought it does.
Check to make sure it's not null and that count of items in the collection is enough to match the index you want to use.

ok i am sorry but you lost me,I am new to this stuff and it is the first time i had this problem and i am tired it keeps popping up when i reboot thanks

**Plater** · Oct 19 '07, 08:39 PM

Originally posted by LadyU

ok i am sorry but you lost me,I am new to this stuff and it is the first time i had this problem and i am tired it keeps popping up when i reboot thanks

So this happening on your computer for code that you DID not write?

**LadyU** · Oct 19 '07, 08:44 PM

Originally posted by Plater

So this happening on your computer for code that you DID not write?

you got it,i don't even know how to do codes

**Plater** · Oct 19 '07, 08:50 PM

Originally posted by LadyU

you got it,i don't even know how to do codes

hehe apparently neither does someone who made some software that is trying to run when you boot your computer.

I would guess you either have some spyware of some sort, or old software trying to talk to a device (like a printer maybe?) that is no longer connected.

I would suggest running SPYBOT on your computer and removing any malware you may have running.

If you can figure out the NAME of the program that is doing it, you will have much better luck correcting the problem.

**mikeyeli** · Oct 19 '07, 08:52 PM

Originally posted by LadyU

you got it,i don't even know how to do codes

This issue is not your fault, and cant be fixed by users, contact the person in charge of developing the application, or someone that has the source and can change it

**LadyU** · Oct 19 '07, 08:54 PM

kk will try that when i reboot my comp i will write down what it is and pray i can fix it cuz it is a real pain

**LadyU** · Oct 19 '07, 09:08 PM

Originally posted by mikeyeli

This issue is not your fault, and cant be fixed by users, contact the person in charge of developing the application, or someone that has the source and can change it

How do I know who that would be,here is what it says when it pops up See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileN otFoundExceptio n: File not found.
at Microsoft.Visua lBasic.Interact ion.Shell(Strin g Pathname, AppWinStyle Style, Boolean Wait, Int32 Timeout)
at EULALauncher.NE T.Form1.Launch_ EULA()
at EULALauncher.NE T.Form1.Form1_L oad(Object sender, EventArgs e)
at System.Windows. Forms.Form.OnLo ad(EventArgs e)
at System.Windows. Forms.Form.OnCr eateControl()
at System.Windows. Forms.Control.C reateControl(Bo olean fIgnoreVisible)
at System.Windows. Forms.Control.C reateControl()
at System.Windows. Forms.Control.W mShowWindow(Mes sage& m)
at System.Windows. Forms.Control.W ndProc(Message& m)
at System.Windows. Forms.Scrollabl eControl.WndPro c(Message& m)
at System.Windows. Forms.Container Control.WndProc (Message& m)
at System.Windows. Forms.Form.WmSh owWindow(Messag e& m)
at System.Windows. Forms.Form.WndP roc(Message& m)
at System.Windows. Forms.ControlNa tiveWindow.OnMe ssage(Message& m)
at System.Windows. Forms.ControlNa tiveWindow.WndP roc(Message& m)
at System.Windows. Forms.NativeWin dow.Callback(In tPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
EULALauncher.NE T
Assembly Version: 1.0.2461.17552
Win32 Version: 1.0.2461.17552
CodeBase: file:///C:/dell/E-Center/EULALauncher.ex e
----------------------------------------
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__b77 a5c561934e089/system.windows. forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77 a5c561934e089/system.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__b03 f5f7f11d50a3a/system.drawing. dll
----------------------------------------
Microsoft.Visua lBasic
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.6001.4
CodeBase: file:///c:/windows/assembly/gac/microsoft.visua lbasic/7.0.5000.0__b03 f5f7f11d50a3a/microsoft.visua lbasic.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:

<configuratio n>
<system.windows .forms jitDebugging="t rue" />
</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.

how may I fix it ,this started not that long ago thanks

**Plater** · Oct 19 '07, 09:11 PM

Looks like it's DELL trying to show it's "welcome new user" screen, but cannot find the file(s) it needs to show you.

The process appears to be:
C:/dell/E-Center/EULALauncher.ex e

So check your startup directory (it should be in your start menu->programs->startup) and remove it from there. It might not be there, but if you are lucky it will be. Its harder to talk someone through the removal if it's kept elsewhere.

**LadyU** · Oct 19 '07, 09:16 PM

Originally posted by Plater

Looks like it's DELL trying to show it's "welcome new user" screen, but cannot find the file(s) it needs to show you.

The process appears to be:
C:/dell/E-Center/EULALauncher.ex e

So check your startup directory (it should be in your start menu->programs->startup) and remove it from there. It might not be there, but if you are lucky it will be. Its harder to talk someone through the removal if it's kept elsewhere.

well it looks like i will have to do some looking for it lol not where it should be thanks for the help i will keep trying to get rid of it

just-in-time (JIT) debugging

just-in-time (JIT) debugging

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment