.net Runtime 2.0 Error Reporting Event ID 1000

[BrianLocke]

ARGHH have put quite a bit of work into AGX and here lately has been crashing worse than ever on multiple machines/ Win 7 Pro 64, WinXP SP3 X86 and WINXP Sp3 X86 Tablet (2005)
it used to crash once in a blue moon now seems to do crash when opening up Explorer or doing too many steps in AGX why is it doing this! all the machines seem to be getting the .NET Runtime Error Reporting Event 1000 or some variances of the that 1008, seems to happen while users are using IE the Most, thought that bugs and crashes were getting less and less with the 1500 builds but I must say that the 1700 build has been extremely frustrating why can't you be stable AGX

on Build 1700

Faulting application e3.exe, version 2.0.0.1700, stamp 4df14603, faulting module ntdll.dll, version 5.1.2600.6055, stamp 4d00f27d, debug? 0, fault address 0x00010cce.

0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
0008: 69 00 63 00 61 00 74 00   i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
0020: 75 00 72 00 65 00 20 00   u.r.e. .
0028: 20 00 65 00 33 00 2e 00    .e.3...
0030: 65 00 78 00 65 00 20 00   e.x.e. .
0038: 32 00 2e 00 30 00 2e 00   2...0...
0040: 30 00 2e 00 31 00 37 00   0...1.7.
0048: 30 00 30 00 20 00 34 00   0.0. .4.
0050: 64 00 66 00 31 00 34 00   d.f.1.4.
0058: 36 00 30 00 33 00 20 00   6.0.3. .
0060: 69 00 6e 00 20 00 6e 00   i.n. .n.
0068: 74 00 64 00 6c 00 6c 00   t.d.l.l.
0070: 2e 00 64 00 6c 00 6c 00   ..d.l.l.
0078: 20 00 35 00 2e 00 31 00    .5...1.
0080: 2e 00 32 00 36 00 30 00   ..2.6.0.
0088: 30 00 2e 00 36 00 30 00   0...6.0.
0090: 35 00 35 00 20 00 34 00   5.5. .4.
0098: 64 00 30 00 30 00 66 00   d.0.0.f.
00a0: 32 00 37 00 64 00 20 00   2.7.d. .
00a8: 66 00 44 00 65 00 62 00   f.D.e.b.
00b0: 75 00 67 00 20 00 30 00   u.g. .0.
00b8: 20 00 61 00 74 00 20 00    .a.t. .
00c0: 6f 00 66 00 66 00 73 00   o.f.f.s.
00c8: 65 00 74 00 20 00 30 00   e.t. .0.
00d0: 30 00 30 00 31 00 30 00   0.0.1.0.
00d8: 63 00 63 00 65 00 0d 00   c.c.e...
00e0: 0a 00                     ..     

Similar error accross all platforms, have tried to install a HOTFIX and will not install on any machines/ and not sure if the HOTFIX was intended for this specific error!  When is the 1900 build coming out>?? Hopefully we can expect it become farely stable@

[BrianLocke]

ARGHHH still having this issue, doing some background work it seems that it has something to do with authentication, alot fo the data is being pulled off of a SQL server 2008 SDE 9.3, we run backups that push across the state once a day sometimes these take a really long time to run, It seems that when these are running the AGX throws this error quite a bit, still doing some research and I will get back to you if I get a fix

[EdanCain]

Brain,
do you have .NET 2.0 SP2 installed?
Couple of things here. Looks like perhaps authentication is getting dropped, or that the service connection cannot be established.

Are you being prompted for a username/password when attempting to connect?
http://support.microsoft.com/kb/913384

I don't think that 1008 is really an issue its most likely just a passenger issue with causes due to the first.

We should be doing a better job of handling it. Its a hard bug to find or repro so thanks for the post.

Edan

[BrianLocke]

Thanks so much for the reply Edan, it does not prompt for a UN/PWD all of it is windows auth, yeah its seems to be pretty intermittent and we do have SP2 for .net 2.0 installed, going to start using a GDB and see if it has something to maybe do with the SDE Server ??

[BrianLocke]

.... Still no luck, I am getting ready to move everything over to a GDB.... Very frustrating, even the debugger seems to crash when I try to grab these reoccuring errors, they also seem to happen at anytime, even while not streaming and just idling ... not sure where to go from here to be honest....

have updated the 1750 build and the SDK, .NET 2.0 is at SP2 and have even updated our SDE to 10 and the DB to SQL Server 2008 R2 SP1 have applied all updates.... this error only seems to happen when there is SDE data present... I think.... I will know for certain after moving things off the SDE and into a GDB

anyone else experiencing similar errors?