topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Friday March 29, 2024, 12:07 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Anyone understand .Net error codes? (all gobbledigook to me)  (Read 5403 times)

Carol Haynes

  • Waffles for England (patent pending)
  • Global Moderator
  • Joined in 2005
  • *****
  • Posts: 8,066
    • View Profile
    • Donate to Member
Anyone understand .Net error codes? (all gobbledigook to me)
« on: December 19, 2007, 02:03 AM »
Got a number of these evens in my system log when I was trying to run Seagate's diagnostic tools (Seatools.exe) on my external USB drive. Each time the tools bombed out while starting up and never got to a point where I could actually do any tests (though the drive was recognised).

Error details:

Event Type:   Error
Event Source:   .NET Runtime 2.0 Error Reporting
Event Category:   None
Event ID:   5000
Date:      16/12/2007
Time:      16:35:53
User:      N/A
Computer:   LAIRDSWOOD
Description:
EventType clr20r3, P1 seatoolsforwindows.exe, P2 1.1.0.7, P3 461e8ed4, P4 mscorlib, P5 2.0.0.0, P6 461eee3d, P7 167c, P8 22, P9 system.invalidoperationexception, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft....om/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00   c.l.r.2.
0008: 30 00 72 00 33 00 2c 00   0.r.3.,.
0010: 20 00 73 00 65 00 61 00    .s.e.a.
0018: 74 00 6f 00 6f 00 6c 00   t.o.o.l.
0020: 73 00 66 00 6f 00 72 00   s.f.o.r.
0028: 77 00 69 00 6e 00 64 00   w.i.n.d.
0030: 6f 00 77 00 73 00 2e 00   o.w.s...
0038: 65 00 78 00 65 00 2c 00   e.x.e.,.
0040: 20 00 31 00 2e 00 31 00    .1...1.
0048: 2e 00 30 00 2e 00 37 00   ..0...7.
0050: 2c 00 20 00 34 00 36 00   ,. .4.6.
0058: 31 00 65 00 38 00 65 00   1.e.8.e.
0060: 64 00 34 00 2c 00 20 00   d.4.,. .
0068: 6d 00 73 00 63 00 6f 00   m.s.c.o.
0070: 72 00 6c 00 69 00 62 00   r.l.i.b.
0078: 2c 00 20 00 32 00 2e 00   ,. .2...
0080: 30 00 2e 00 30 00 2e 00   0...0...
0088: 30 00 2c 00 20 00 34 00   0.,. .4.
0090: 36 00 31 00 65 00 65 00   6.1.e.e.
0098: 65 00 33 00 64 00 2c 00   e.3.d.,.
00a0: 20 00 31 00 36 00 37 00    .1.6.7.
00a8: 63 00 2c 00 20 00 32 00   c.,. .2.
00b0: 32 00 2c 00 20 00 73 00   2.,. .s.
00b8: 79 00 73 00 74 00 65 00   y.s.t.e.
00c0: 6d 00 2e 00 69 00 6e 00   m...i.n.
00c8: 76 00 61 00 6c 00 69 00   v.a.l.i.
00d0: 64 00 6f 00 70 00 65 00   d.o.p.e.
00d8: 72 00 61 00 74 00 69 00   r.a.t.i.
00e0: 6f 00 6e 00 65 00 78 00   o.n.e.x.
00e8: 63 00 65 00 70 00 74 00   c.e.p.t.
00f0: 69 00 6f 00 6e 00 20 00   i.o.n. .
00f8: 4e 00 49 00 4c 00 0d 00   N.I.L...
0100: 0a 00                     ..     

Unfortunately MS offers no further assistance on this error code (what is the point of error codes if there isn't any documentation to help?)

justice

  • Supporting Member
  • Joined in 2006
  • **
  • Posts: 1,898
    • View Profile
    • Donate to Member
Re: Anyone understand .Net error codes? (all gobbledigook to me)
« Reply #1 on: December 19, 2007, 03:45 AM »
I found some results googling for http://EventType clr20r3
Seems to point to this solution
To fix your applications what you need to do is to look at your references (in solution explorer and in insertable objects) and make sure that you copy these dll's and dependancys onto the machine you want to install to and do a regsvr32 -i <dll>

Looking for http://system.invalidoperationexception I found a questionable fix from microsoft, but you might be able to get more out of that search.

Carol Haynes

  • Waffles for England (patent pending)
  • Global Moderator
  • Joined in 2005
  • *****
  • Posts: 8,066
    • View Profile
    • Donate to Member
Thanks for the heads up - but since I don't actually have any source code to play with I don't think it helps me to solve the problem. I have sent a support ticket to Seagate so maybe they can come up with a solution.

The problem I am having is ...

I have an external NTFS formatted Seagate USB2 drive. Infrequently I get an error in my system log saying that there is a disk error (apparently related to cabling issue - which seems strange as you would have thought with USB that the cable either works or it doesn't - maybe it is an internal cable in the drive box!)

I wanted to check the drive intergrity so I opened a console window and ran CHRKDSK /R on the drive which should do the usual check plus a low level check of all file data and free space data. It gets through the usual first three stages with no problem but when it gets to checking file data sticks at 0% until I close the console with TaskManager.

There doesn't actually appear to be any problems with the data on the disk but I can't figure out why CHKDSK hangs at that point - unless it is USB drive thing.

Anyway that is why I tried to use SEATOOLS to check the drive with the above problem.

Maybe I'll try SEATOOLS on another computer and move the external drive as the .NET problem described above seems to be likely to be a system specific problem - might be worth a try anyway.

Anyone got any ideas on the CHKDSK problem?

f0dder

  • Charter Honorary Member
  • Joined in 2005
  • ***
  • Posts: 9,153
  • [Well, THAT escalated quickly!]
    • View Profile
    • f0dder's place
    • Read more about this member.
    • Donate to Member
Re: Anyone understand .Net error codes? (all gobbledigook to me)
« Reply #3 on: December 19, 2007, 05:51 AM »
There doesn't actually appear to be any problems with the data on the disk but I can't figure out why CHKDSK hangs at that point - unless it is USB drive thing.

I've had that with a few drives, and I have no idea why... 4gig hatachi microdrive (CompactFlash form factor, but it's a small HDD and not flash) from my dead MuVo^2 MP3 player, and a really old 5400rpm Quantum drive. They would stall like forever at 0%, and then suddenly jump to 70% or so. Weirdness.

As for for the connection problem, I've found USB2 external enclosures (exclosures? :)) to be somewhat unreliable, losing connection for half a second every now and then if attached for several hours. Not bad enough to spin the drive down or (as far as I can tell) lose data, but definitely loses the connection enough that the autoplay thing kicks in.

But it might just be my exclosure that sucks :)
- carpe noctem