IIS 5 & IIS 6
Intermittent shared file resource read errors from Windows 2003 (IIS6...
Last post Nov 07, 2008 04:03 PM by JStones
Nov 05, 2008 08:27 AM|JStones|LINK
A few weeks back, a colleague sent something similar to the following to the Microsoft technical support, and although we've collected and forwarded on a bunch of performance monitor stats etc since then, we're currently no closer to a solution, so I hoping/wondering
whether somebody here might be able to shed some light on the issue:
Nov 05, 2008 08:38 PM|steve schofield|LINK
There is a tag I have on some UNC posts / articles. I would verify the machines are identical, metabase properties, NIC binding orders, duplex speed on the switch (assuming it's a switched network). Are all servers on the same network? What is the error
you get when the file isn't available? Have you enabled monitoring and auditing to see if you can be alerted when the issue occurs. Sounds like you are on the right track. It's always fun to find a needle in a haystack.
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget
Nov 07, 2008 04:03 PM|JStones|LINK
Thanks for the reply, Steve.
I had a look at the UNC stuff on your blog - Was there something specific you were referring to?
I've not had chance to ask the "systems guy" that looks after the servers etc about whether the stuff you mentioned has been verified - I'm currently using up this year's holiday entitlement! :)
I'm not quite sure what you mean by are all the servers on the same network, but they're all in the same physical location (IBM BladeCenter) and connected by a gigabit switched network.
The virtual directory where the files are located sits under an ASP application, and a custom error handler for http status 500 records any errors under there. What gets recorded is not of much use though, as the error code/description in the ASP error
object is blank. The errors are stored in a database and email notifications are sent, so it's easy to see when they happen.
I'm not sure what stuff is being logged at the minute, as the "systems guy" has been doing a fair bit of logging etc to pass the information on to the Microsoft technical support. Is there something specific that you had in mind that may help in identifying
the cause of the error?