Problems when pinging

[Jerry Spence1]

I am doing:

My.Computer.Network.Ping("192.168.0.1", 2000)

I often (but not always) get the following error:

System.Net.NetworkInformation.PingException: An exception occurred during a
Ping request. ---> System.AccessViolationException: Attempted to read or
write protected memory. This is often an indication that other memory is
corrupt.

I see several references to this on Google and also a claimed fix from
Microsoft, but this fix didn't work. I get the following:

"The upgrade patch cannot be installed by the windows installer service
because the program to be upgraded may be missing, or the upgrade patch may
update a different version of the program."
The refence for this fix is here: http://support.microsoft.com/kb/923028

I am running .NET 2.0 and VB2005, which is exactly what is required by the
fix.

If I download .NET 3.5, how do I tell my VB application to use this instead
of 2.0? I can't find a reference to the version of .NET in the IDE.

-Jerry

 

[Michel Posseth [MCP]]

Hello Jerry,

There is ofcourse also the posibility that your memory banks are not in such
a good state as you might believe ( hardware flaw )
so i would say test it also on another computer first and / or run memtest
386 to be sure http://support.dunaweb.hu/UTIL/memtest386/?C=M;O=A

If I download .NET 3.5, how do I tell my VB application to use this
instead
of 2.0? I can't find a reference to the version of .NET in the IDE.

AFAIK : you can only do this with VS.net 2008 there you have the option to
use the 2.0 or 3.5 framework ( advanced compile options )

 

[Jerry Spence1]

Thanks Michel. I sould have mentioned that this happens on a number of
production PCs as well, and I was going to ask also if this patch should be
applied to all the target PC's or just the one the code is developed on. The
Microsoft artcle doesn't make this clear.

So on VB2005, does it automatically use the latest version of .NET it finds
installed? If I put 3.5 on the target PC, does it automatically use this, or
will it always use the same version as I compiled on?

-Jerry

 

[Bill McCarthy]

Hi Jerry,

First of, the KB article you referred to, is included in .NET 2.0 SP1. So
if you have 2.0 SP1 you don't need the hotfix. That's probably why it isn't
installing for you.

As to 3.5, well 3.5 is 2.0 SP1 really, and then added features such as LINQ
libraries, WPF, WCF, Cardspace and Workflow libraries. The runtime is still
the CLR version 2, and the 2.0 SP1 libraries are the same. So installing
3.5 will not change anything for a 2.0 SP1 application at all.

 

[Jerry Spence1]

Thanks Bill. I've upgraded to SP1 but unfortunately the problem still
exists. I guess this is a Microsoft Bug. Do Microsoft read this news group?

-Jerry

 

[Bill McCarthy]

It appears they do, but that may only be for MSDN subscribers ?? What I
would suggest is you report it as a bug, in the new bug feedback forum:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=2008&SiteID=1
Although it doesn't look like anyone responds at all in there yet

In the meantime, I'd suggest wrapping your Ping calling into a separate
function with a Try Catch block around the Ping call, and perhaps a loop for
a number of retries. Sorry can't be of more help.