Regular SBS crashes

Discussion in 'Windows Small Business Server' started by Chris ONeill, Apr 5, 2006.

  1. Chris ONeill

    Chris ONeill Guest

    SBS 03 Premium, Dual Zeon, 4GB. 60 Users.

    Hi,

    Any help with this problem would be very much appreciated.

    Our sbs has been crashing regularly on us since we set it up back in
    October. It will usually run fine for 14 to 21 days, then, usually in the
    morning, it becomes impossible to log on (just get ‘processing logon’
    message) either from a client machine or at the server itself.

    Upto a week before it flakes out we get nightly ‘Alocated Memory Alets ‘ to
    let us know that the available memory has gone below the threshold. Yet when
    I check the process memory usage, the top 3 seem normal; Store.exe sits at
    around 635MB, and sqlservr.exe has two instances around 176MB and 124 MB.
    These do not seem to change much over time.

    For each crash, all of the memory alerts happen at almost exactly the same
    time each night. However the time is different for each crash. For example,
    the first time, we were getting alerts at 4:43:37 PM, the second time,
    6:33:50 PM and most recently, the times coincided with the backup reaching
    the exchange public folders.

    FYI our backup is the sbs’s only daily sheduled task and starts at 8pm each
    night

    Usually, the logs server event logs reveal that the firewall and RRAS
    services have stopped. This would explain not being able to log on.

    The last time we had a ‘crash’ there was nothing in the logs at all to give
    a clue as to what had happened. Some users had already been logged in the
    morning on before the server stops crashed. Internet and e-mail
    (outlook/exchange) seemed to work as normal for them, but they are unable to
    browse the shared file system.

    Can anyone help point me in the direction that I sould be looking?
     
    Chris ONeill, Apr 5, 2006
    #1
    1. Advertisements

  2. Chris ONeill

    Joe Guest

    RAM is usually the best guess. Failing drives normally produce errors,
    RAM doesn't. Reseating the RAM and all the large motherboard connectors
    is worth doing as a first step.
     
    Joe, Apr 5, 2006
    #2
    1. Advertisements

  3. Is the total virtual memory on the server set to a value at least 1.5
    times the physical memory (4GB physical -> 6GB virtual)? (This may be a
    single page file or divided up among several partitions, depending on
    your specific disk configuration.)

    -- Owen Williams
     
    Owen Williams, Apr 5, 2006
    #3
  4. Chris ONeill

    Andy Roth Guest

    Hi Chris,
    This may not be the cause of your issue but I thought it was worth
    mentioning. Do you have any HP printer drivers/software installed on the
    server? Older versions of some HP port resolver software had a memory leak
    problem. My server was giving me memory alerts like that and then would
    occasionally crash and restart. Once I disabled the offending HP software
    those problems went away.
     
    Andy Roth, Apr 5, 2006
    #4
  5. Chris ONeill

    NickC Guest

    Chris,

    First place to start is to check the memory; run Memtest86, full tests, for
    at least 48hrs. Any problems wuill be obvious. Really not worth looking
    elsewhere until you know the memory is clean. If it is ok how about then
    installing Win2003 workstation to a seperate partition.

    Nick
     
    NickC, Apr 5, 2006
    #5
  6. Chris ONeill

    Chris ONeill Guest

    Yes. Virtual memory is set to 6GB

     
    Chris ONeill, Apr 6, 2006
    #6
  7. Chris ONeill

    Chris ONeill Guest

    No printers installed on server

     
    Chris ONeill, Apr 6, 2006
    #7
  8. Chris ONeill

    Chris ONeill Guest

    Hi Nick,

    Thanks for replying. Forgive my ignorane, what is Win2003 workstation? I'm
    not sure what you intend me to try.

    Chris.
     
    Chris ONeill, Apr 6, 2006
    #8
  9. It would not hurt to run the RAM tests the others are recommending, but
    I suspect that will not reveal any problems. If some of the RAM was
    really flaky, the failures would be random.

    Since it is always taking at least 14 days from a reboot, it sounds to
    me like one or more of the processes running has a memory leak
    somewhere.

    You've been really tolerant - perhaps too tolerant - of failures like
    this happening for 6 months. Are you a Microsoft Partner (any level)?
    If so, you should be eligible for a free CSS "business down" call for
    this problem.

    -- Owen Williams
     
    Owen Williams, Apr 6, 2006
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.