• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 353
  • Last Modified:

New 2003 Server and pst's

I replaced an old DL Server running 2000 Server with a new DL385 with Windows  Server 2003 - since then, I have multiple users who cannot open their .pst's on the network share.  It's not consistent, sometimes they can open their .pst's and other times they can't. They receive messages anywhere from 'not enough server storage is available to process this request' (standard irpstack size error) to access is denied. File is in use and cannot be opened.  We run all XP desktops and the mail server is housed at an offsite 3rd party company, so there isn't an Exchange server in the mix.  The most common denominator is that everyone that is having the problem have large .pst files (anywhere from 1-7 gig).  It only seems to be with the .pst's but they receive the 'not enough server storage is available to process this request ' error even if they are trying to just move the .pst from the network to their local drive to eliminate the network.  I am waiting to hear back from one person to see if it is the 'over 2gig' size problem, to see if converting them to unicode text would help (some of these .pst's have been around for a long time and may have been created in previous versions of Outlook), but since it just started happening once 2003 server was put in, I'm thinking not?   This is a file server only, and have alot of people going to it.  It's starting to impact heavily and I'm looking for assistance.  I noted that the IRPStack Size isn't even in the registry, so I was going to try that, but trying to get a reboot on this particular server is not easy - so I'm trying to limit the changes I make and reboot as few times as necessary to fix it.  Also, what does the IRPStack actually do? Thoughts?  
1 Solution
I always make sure clients have under the 2 GB limit, and generally tell them to keep them under 1GB for speed.  Get them to do an archive.
Cinder62Author Commented:
Thanks, I did resolve the problem with a hot fix from MS and a few registry hacks, basically, adding IRPSack Size, changing nonpagedpool and paged pool to ffffffff.  Thanks  - By the way, these people will not reduce any of them unfortunately - I wonder how they can find anything!  Thanks.  Can this be closed?
Closed, 500 points refunded.
The Experts Exchange
Community Support Moderator of all Ages
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now