Scheduled Tasks c0000005 error

[Dave Mandy]

Hi All

I have written a C# console based program. The first line of code simply
writes to the event log and this works 99% of the time, whether being run
manually or kicked off by Windows Scheduled Tasks. However, the other 1% of
the time Windows Tasks will return the following error (from the SchedLgU.txt
log file)

Started 20/03/2006 08:20:01
"ServerInfoServ ice.job" (ServerInfoServ ice.exe)
Finished 20/03/2006 08:20:03
Result: The task completed with an exit code of (c0000005).

Does anybody know what this error means / if there is a public chart of the
error codes?

Thanks

[Vadym Stetsyak]

Hello, Dave!

DM> I have written a C# console based program. The first line of code
DM> simply writes to the event log and this works 99% of the time, whether
DM> being run manually or kicked off by Windows Scheduled Tasks. However,
DM> the other 1% of the time Windows Tasks will return the following error
DM> (from the SchedLgU.txt log file)

DM> Started 20/03/2006 08:20:01
DM> "ServerInfoServ ice.job" (ServerInfoServ ice.exe)
DM> Finished 20/03/2006 08:20:03
DM> Result: The task completed with an exit code of (c0000005).

DM> Does anybody know what this error means / if there is a public chart of
DM> the error codes?

c0000005 usually means access violation, memory read or write error, this may happen if you pass null pointers or null references.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Jason Hales]

I've seen similar problems when a screen saver kicks at the same time
as the scheduled task.

[Brian Gideon]

I don't think an access violation is possible in managed code. I
suspect the fault is coming from unmanaged code. The Dr. Watson log
may provide more information.

Vadym Stetsyak wrote:

Hello, Dave!

DM> I have written a C# console based program. The first line of code
DM> simply writes to the event log and this works 99% of the time, whether
DM> being run manually or kicked off by Windows Scheduled Tasks. However,
DM> the other 1% of the time Windows Tasks will return the following error
DM> (from the SchedLgU.txt log file)

DM> Started 20/03/2006 08:20:01
DM> "ServerInfoServ ice.job" (ServerInfoServ ice.exe)
DM> Finished 20/03/2006 08:20:03
DM> Result: The task completed with an exit code of (c0000005).

DM> Does anybody know what this error means / if there is a public chart of
DM> the error codes?

c0000005 usually means access violation, memory read or write error, this may happen if you pass null pointers or null references.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Vadym Stetsyak]

Hello, Brian!

Yes, you're right, AVs do not happen in managed world, only "Object reference not set...".
And if you pass nulls to the unmanaged world via P/Invoke or interop you may obtain AV.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

[Dave Mandy]

The Dr Watson log yielded the following:

function: CoInitializeCor
791cfe80 5e pop esi
791cfe81 7408 jz CoInitializeCor +0xb6eb (791d9f8b)
791cfe83 a1cccb3d79
ds:793dcbcc=000 00000
mov eax,[CorCreateMiniDu mp+0x7f709
(793dcbcc)]
791cfe88 ff4048 inc dword ptr [eax+0x48]
ds:00819ee6=??? ?????
791cfe8b a1cccb3d79
ds:793dcbcc=000 00000
mov eax,[CorCreateMiniDu mp+0x7f709
(793dcbcc)]
791cfe90 ff4074 inc dword ptr [eax+0x74]
ds:00819ee6=??? ?????
791cfe93 e86341feff call Ordinal71+0x3ff b (791b3ffb)
791cfe98 5d pop ebp
791cfe99 c20400 ret 0x4
791cfe9c a1cccb3d79
ds:793dcbcc=000 00000
mov eax,[CorCreateMiniDu mp+0x7f709
(793dcbcc)]
FAULT ->791cfea1 397850 cmp [eax+0x50],edi
ds:00819ee6=??? ?????
791cfea4 53 push ebx
791cfea5 8b1d10121b79
ds:791b1210=7c5 73a71
mov ebx,[Ordinal71+0x121 0 (791b1210)]
791cfeab 56 push esi
791cfeac 0f856e6f0700 jne DllGetClassObje ctInternal+0x10 0cd
(79246e20)
791cfeb2 68b0010000 push 0x1b0
791cfeb7 e88af5ffff call CoInitializeCor +0xba6 (791cf446)
791cfebc 59 pop ecx
791cfebd 8945f0 mov [ebp+0xf0],eax
ss:0094994a=??? ?????
791cfec0 3bc7 cmp eax,edi
791cfec2 897dfc mov [ebp+0xfc],edi
ss:0094994a=??? ?????
791cfec5 0f8496000000 je CoInitializeCor +0x16c1 (791cff61)

A bit of a google reveals a few others have experienced similar issues, but
without resolution posted:

http://dotnet247.com/247reference/msgs/37/187561.aspx
http://www.thescripts.com/forum/thre...7068-1-10.html

Most ideas are geared around the code, but I am pretty sure that isn't the
issue here, as the first line isn't being called, it is bombing out on start
up.

Thanks for the responses from all the gurus thus far, any more thoughts?

"Brian Gideon" wrote:

I don't think an access violation is possible in managed code. I
suspect the fault is coming from unmanaged code. The Dr. Watson log
may provide more information.

[Brian Gideon]

Dave,

Strange. The fault appears to be in CLR initialization code or
something.

Brian

[antonio.costa]

I've a problem bellow in the scheduled tasks:

Result: The task completed with an exit code of (c0000005)
---
Posted via DotNetSlackers. com