[THIN] Re: Memory Issues

  • From: "Mike Semon" <msemon@xxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Mon, 22 Nov 2004 12:52:34 -0600

MessageCheck Group Policies also.

http://support.microsoft.com/?kbid=312164

-Mike
  -----Original Message-----
  From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Stratton, Doug MSER:EX
  Sent: Monday, November 22, 2004 12:39 PM
  To: 'thin@xxxxxxxxxxxxx'
  Subject: [THIN] Re: Memory Issues


  Already using this and it is great but not what is causing this particular
problem.
  Thanks
    -----Original Message-----
    From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Jeff Malczewski
    Sent: Mon, November 22, 2004 10:29 AM
    To: 'thin@xxxxxxxxxxxxx'
    Subject: [THIN] Re: Memory Issues


    http://www.microsoft.com/downloads/details.aspx?FamilyID=1b286e6d-8912-4
e18-b570-42470e2f3582&displaylang=en


    (watch for link wrapping)


      -----Original Message-----
      From: Stratton, Doug MSER:EX [mailto:Doug.M.Stratton@xxxxxxxxxxxxxxx]
      Sent: Monday, November 22, 2004 1:01 PM
      To: 'thin@xxxxxxxxxxxxx'
      Subject: [THIN] Memory Issues


      We have a small farm (6 W2k SP4, MF Xpe)

      We have had to bump up the Registry size over the years.  We are now
at 150Mb.
      We have one server which is serving up the roaming profiles (via a
share with AD pointing to the server\share).

      We have started to run into this error message:
      Event Type:     Error
      Event Source:   Userenv
      Event Category: None
      Event ID:       1000
      Date:           2004-11-22
      Time:           9:03:59 AM
      User:           NT AUTHORITY\SYSTEM
      Computer:       SAFFRON
      Description:
      Windows cannot log you on because the profile cannot be loaded.
Contact your network administrator.

      DETAIL - Insufficient system resources exist to complete the requested
service.

      At first I thought it was we were running out of registry space or
page pool space.  This could still be.  I have not found much on this
specific error.

      But I am starting to wonder if it is something else.

      Today when I came in (Monday morning after a Sunday morning reboot).
We were have this error.  In the end I had to log off a few disconnected
sessions on the roaming profile server and the problem went away.  I was
getting the error on all the servers when people logged on.

      I also restarted the spooler service as it had 256 K Page Pool.
(thought that was kind of high).

      I was not getting anything (that I can find) saying out of page pool
or increase registry size.  When I got around to comparing the memory
resources available on the other servers to the problem server it seemed
that the problem server was much better off then the others.  So I can't
figure out what was causing the problem.

      I have come across a couple of articles saying if you get "not enough
server storage" it could be IRPstackSize (pretty old messages)  but I am not
getting event id's 2011....

      The other person who supports this farm (the expert-away on holidays)
says that part of our problem the registry hives are getting to big and we
should clean up.

      SO here are my question (assuming you got this far in the message):
        If it is not page pool/registry size what could it be?
           How can I track it down?

        If it is page pool/registry size issues what can I do?

      Thanks for your help.



      Doug Stratton
      Operations Engineering
      Workstations Services Branch
      CITS, Solutions BC, Province of BC
      4000 Seymour Place, Victoria  B.C.
      Telephone: (250) 356-6678
      Email: Doug.M.Stratton@xxxxxxxxxxxxxxx





    ----------------------------------
    This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the system
manager. This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail.

Other related posts: