Re^6: Win32 - Memory can not be "read"

in reply to Re^5: Win32 - Memory can not be "read"
in thread Win32 - Memory can not be "read"

We initially thought it correlated to some Windows security patching. We had the I.T. department re-image the machines back to where they were several months ago, and the problem persists.

Other than that nothing changed on the machines that we're aware of

Network switches were upgraded around the time I saw a dramatic increase in the frequency of this problem

Other than that, nothing that we know of

Comment on Re^6: Win32 - Memory can not be "read"

Replies are listed 'Best First'.
Re^7: Win32 - Memory can not be "read" by GrandFather (Saint) on Oct 04, 2006 at 23:37 UTC
Network timeouts or high error rates accessing files maybe? Sorta consistent with Find::File being involved at least. DWIM is Perl's answer to Gödel	[reply]

In Section Seekers of Perl Wisdom