I installed SP1 on 8 of our 2003 servers without incident but the 9th one
belched. After installing SP1 and rebooting no one (including the server
itself) was able access any of the shares on that drive and the event log
was spewing out tons of messages indicating that the "irpstacksize was too
small". What's up with that?

"Don Powell" <don@mresource.com> wrote...
Someone may have manually modified it on the server sometime in it's life
beforehand. Have you any documentation on the history of changes to the
server? Probably not.

To set the IRPStackSize back to the default (15 for XP/2003), perform the
following steps:
1. Start the registry editor
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es
\lanmanserver\parameters.
3. Double-click IRPStackSize (or if this registry setting doesn't exist,
create it of type DWORD and ensure the case is correct).
4. Change the base to decimal, set the value to 15 and click OK. If a
value is already present, add 3 to that number, and set it to the new
number.
5. Reboot the server

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

already tried that.

It's a relatively new server that had 2003 installed from scratch and has
had nothing but Microsoft Critical Updates installed since. The only
difference I can find between this server and the others is that it has a
Western Digital SATA RAID controller installed in addition to the Adaptec
RAID controller that they all use.


"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:eDetrvzcFHA.3504@TK2MSFTNGP12.phx.gbl...