none
failing services on WHS

    Вопрос

  • Im having lots of crashes on my WHS

    Windows Home server transport service, volume shadow service,  and windows home server computer backup server consistantly crash (about twice a day)

     

     

    Event Category: (100)
    Event ID: 1004
    Date:  5/05/2007
    Time:  12:45:12 PM
    User:  N/A
    Computer: server

    Description:
    Reporting queued error: faulting application TransportService.exe, version 6.0.1371.0, faulting module TransportService.exe, version 6.0.1371.0, fault address 0x00038df5.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74   Applicat
    0008: 69 6f 6e 20 46 61 69 6c   ion Fail
    0010: 75 72 65 20 20 54 72 61   ure  Tra
    0018: 6e 73 70 6f 72 74 53 65   nsportSe
    0020: 72 76 69 63 65 2e 65 78   rvice.ex
    0028: 65 20 36 2e 30 2e 31 33   e 6.0.13
    0030: 37 31 2e 30 20 69 6e 20   71.0 in
    0038: 54 72 61 6e 73 70 6f 72   Transpor
    0040: 74 53 65 72 76 69 63 65   tService
    0048: 2e 65 78 65 20 36 2e 30   .exe 6.0
    0050: 2e 31 33 37 31 2e 30 20   .1371.0
    0058: 61 74 20 6f 66 66 73 65   at offse
    0060: 74 20 30 30 30 33 38 64   t 00038d
    0068: 66 35                     f5     

    -----------

    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1001
    Date:  5/05/2007
    Time:  12:53:27 PM
    User:  N/A
    Computer: server

    Description:
    Fault bucket 407989115.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 42 75 63 6b 65 74 3a 20   Bucket:
    0008: 34 30 37 39 38 39 31 31   40798911
    0010: 35 0d 0a                  5..    

    5 мая 2007 г. 3:14

Ответы

  • Stability issues are often caused by faulty drivers or issues with memory/other hardware.

    I would recommend to get the most up to date drivers for your hardware, perform a reinstallation of server, patch up Windows Home Server inclusive Power Pack 1 and after that add the client PCs again.

    Best greetings from Germany

    Olaf

     

    2 сентября 2008 г. 7:52
    Модератор

Все ответы

  •  

    I just ran into these issues, anyone know how to solve it?
    2 сентября 2008 г. 7:22
  • Stability issues are often caused by faulty drivers or issues with memory/other hardware.

    I would recommend to get the most up to date drivers for your hardware, perform a reinstallation of server, patch up Windows Home Server inclusive Power Pack 1 and after that add the client PCs again.

    Best greetings from Germany

    Olaf

     

    2 сентября 2008 г. 7:52
    Модератор
  • I have seen this recommendation before.  Is this the best we can do?  Reinstall the OS?  If so than this software was a waste of money.  I fail to see why I should expect different results by re-installing the OS.  This was a fresh install and the only thing added to it was anti-virus software. 

     

    The AV software was added a long time ago so I am certain that this is not the cause, unless WHS PP1 has an issue with Etrust AV.

     

    2 сентября 2008 г. 13:51
  • The only AV products that have been released for WHS that I know of are avast! and McAfee. (And I'm not certain that McAfee is available for sale; I can't seem to find a version for WHS on their web site. It may be HP-only right now.) Other AV products, not being WHS aware, may register false positives from normal WHS activity.

    As for reinstallation/server recovery, if something is wrong with the WHS components, as a practical matter is may take less (perhaps significantly less) time, and entail less risk, to reinstall rather than try to figure out what specifically is wrong and fix it.
    2 сентября 2008 г. 14:35
    Модератор
  • And, other folks have had problems with that AV, I do not know if these could be compounded by WHS, but it is possible.
    http://forums.whirlpool.net.au/forum-replies-archive.cfm/505417.html ,

    Ben
    2 сентября 2008 г. 18:40
  • In most cases I have seen services fail in Server/SBS 2003 usually because of the following:

     

    - What I call "rough" usage of the system, eg. people punching the reset button instead of performing proper shutdown; or the lack of a high quality large UPS to maintain the system during brownouts and blackouts (I have an APC 1000W UPS on my WHS).  Hard shutdowns like this quickly lead to corrupted registry entries or files.  Servers are less forgiving for this than workstations.

    - What I classify as, "unsafe" software.  I never install anything on a server that I don't completely trust for stability with that OS, and AV software is not one of those I trust on servers.  I'll 'live' with Symantec EndPoint or MS ForeFront but I won't install them unless absolutely necessary.  AV should never normally be installed on a file server, only on Internet mail servers if required.  For WHS, I would not recommend installing an AV product in an attempt to provide a "blanket" approach to antivirus for all of the connected client systems.  Many of the current trojans are coming through the browser to infect the client system, so putting AV on WHS will no nothing to protect from this.

    - Hardware/driver issues.  Too many people try to use inexpensive hardware to run a server, and for 24:7 up-time you need high-quality components.  Also because the higher-quality components usually include better drivers or ones natively supported by the OS.

     

    I would recommend logging on locally and checking the Event Viewer to see if there are any other events logged that may give an indication why these services are failing.  Slow, unresponsive or failing drivers are often logged.

    If that all looks fine, then I would uninstall any third-party software that you are unsure of its compatibility and stability with WHS.  Note that some software, like Norton AV, leave behind files and running services that must often be manually stopped and removed.

    If the issue still happens after this, I would run a System File Check over it.  See this MSKB.  You want to run SFC with the /scannow option (eg. 'sfc /scannow' at a command prompt window).  With WHS make sure that none of the client systems are connecting and using WHS while running SFC.  Depending on your WHS setup, you will most likely be prompted for the Installation CD so that SFC can retrieve files for the cache.  Some OEM installs may already have the cache on the boot drive so you won't be prompted.  To get around having to insert the DVD every time you run SFC, insert the WHS DVD and locate the I386 folder (it may be in the disc at SVR_2003\I386), copy the entire I386 folder to the C: drive (ie. so it is at C:\I386), then in Windows Explorer locate regedit.exe in the Windows folder and run it, locate the registry key HKEY_LOCAL_MACHINE.SOFTWARE/Microsoft/Windows/Setup and change the SourcePath key from X:\SVR_2003 or whatever it is on your system to C:\I386.  Finally, note that SFC will still complain usually at least two dozen times about not locating a file it requires in the cache, simply click on "Cancel" and it will ask if you wish to skip this file, click on "Yes", and it will continue to scan.  Some time in the future I will attempt to determine what other WHS-specific files it is looking for so that the scan can complete without issues, but it will still validate thousands of the OS files.  When the scan is complete (the dialog just disappears) reboot the system.

    I have not seen any registry repair tools that I trust for Server 2003, so if the registry is borked a reinstall is required.

     

    If none of these ideas help, then as mentioned, a re-installation will probably be quicker than further troubleshooting.

     

    I am considering adding a new area to my web site for "Advanced WHS", that will cover a lot of the technical information and issues when using WHS and more specifically this Server 2003 version.

     

    David

    2 сентября 2008 г. 20:10