System.AccessViolationException [.NET BUG] - RunUO

noobie · 02-20-2007, 05:20 AM

I am not really sure this is the right place but I have seen lots people getting this error lately.

Here is the detailed information about bug: (.NET 2.0 is refered as Whidbey in the page)
Mahjayar's WebLog.

p.s NOD32 isnt the only cause. Also NetLimiter,PandaAntivirus are confirmed to cause such a problem.

Here is KB article and fix from MS: (however, you can only get the fix by contacting MS services - it is free)
FIX: Error message when you run a .NET Framework 2.0 Remoting application: "Unhandled Exception: System.AccessViolationException"

btw, the bug only exist in .NET 2.0 and by upgrading your framework to 3.0, it might go away.

02-20-2007, 05:20 AM	#1 (permalink)
noobie Forum Expert Join Date: Jul 2005 Location: Istanbul/Turkey Age: 27 Posts: 425	System.AccessViolationException [.NET BUG] I am not really sure this is the right place but I have seen lots people getting this error lately. Here is the detailed information about bug: (.NET 2.0 is refered as Whidbey in the page) Mahjayar's WebLog. p.s NOD32 isnt the only cause. Also NetLimiter,PandaAntivirus are confirmed to cause such a problem. Here is KB article and fix from MS: (however, you can only get the fix by contacting MS services - it is free) FIX: Error message when you run a .NET Framework 2.0 Remoting application: "Unhandled Exception: System.AccessViolationException" btw, the bug only exist in .NET 2.0 and by upgrading your framework to 3.0, it might go away. __________________ "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)