Announcement

Collapse
No announcement yet.

SBS2003 hickups/timeouts (NtFrs eventid: 7011)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SBS2003 hickups/timeouts (NtFrs eventid: 7011)

    Hello All,

    I have read a lot about the eventid 7011 in your system eventviewer and there are many cases to solve this problem. However I did not find my case and therefor I want to post this to his forum to help others and this forum is very active and I like the information on it.

    Configuration:
    Intel Xeon CPU 5120 @ 1.86 GHz
    4 GB RAM
    Dell Perc 5/I Integrated Raid Controller
    LSI Logic PCI-X Ultra320 Scsi host adapter
    Intel 631xESB/6321ESB Ultra ATA Storage Controller
    ATi ES1000
    Dell Perc 5/I Scsi Disk Device
    Dell Perc 5/I Scsi Disk Device
    Broadcom BCM5708C NetExtreme II GigE (NDIS VBD Client #3)
    Small Business Server 2003 SP2

    First day:
    Came in at work and the server was not responding to any network requests. People had troubles logging in. Looked at the server and found out that it is not crashed. Mouse and keyboard were still responsive on screen however the OS did not respond to it in a matter that you could use the server. Therefor I gave it a hard shutdown and booted it up again.
    When it was booted and back In Windows I noticed a lot of events id:7011 Source:NtFrs. I hoped that after boot it would be refreshed and nothing is needed.
    But after 2 hours it started to get hickups on the server, timeouts if you will. Which freeze the session up for 30-60 seconds and then work again. Till the point that it froze up more and longer.
    I did another reboot and shut down a lot of services when it was booted:
    -All Exchange services
    -Backup Symantec Exec Recovery services
    -VSS Writer
    -Sharepoint services
    -SQLAgents
    -Symantec SymSnap VSS Provider
    -SymSnapService
    -LiveUpdate
    -Automatic LiveUpdate Scheduler
    Once this was done the server worked perfectly normal!

    Then I start to execute some of the fixes I found on the internet:
    1. Change the registry entry of Servicespipes
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l
    You either edit 'ServicesPipeTimeout' or add a new, and then click DWORD Value.
    Set it to decimal and to a value of 60000

    2. Change the registry entry of LanmanServer:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\LanmanServer\Parameters
    Normally 'Autodisconnect' is set to f or 0xf. Highest value is 0xfffff. You can also disable it to -1.
    Command for it in commandline: net config server /autodisconnect:-1

    I haven't put sharepoint on cause I first want to update this service.
    hopefully I can have time to do this today and keep you posted.

    Make sure you always have a back-up before you reboot and test the new setting!

  • #2
    Re: SBS2003 hickups/timeouts (NtFrs eventid: 7011)

    Ok an update:

    I have updated the Sharepoint services today rebooted the server twice.
    Once you update to SP3 of Sharepoint Services 2.0 you need to run update again, because there is another update for this.

    I also know there is a 3.0 for it. I will test that later on.

    After the 2 updates I turned on the following services:
    MSSQL$SHAREPOINT
    SQLAGENT$SHAREPOINT
    SharePoint Timer Service

    I inmediately checked the eventvwr in the system log if the errors came back (7011).
    After running it for a few hours it is still running smoothly. So a Yay .

    I still have 2 services left to go before it is back in his original state:
    LiveUpdate (Symantec)
    Automatic LiveUpdate Scheduler (Symantec)

    I have did some digging and found out that the first one could be the cause of the trouble. Next week I am going to check whether i need both services and if so if there are updates for it or fixes.

    I will Keep you posted.



    I did some more finding and reading

    Comment


    • #3
      Re: SBS2003 hickups/timeouts (NtFrs eventid: 7011)

      run a checkdisk on your volumes first.
      Then, update the firmware on your RAID controllers.
      Then, use OpenManage to see if there are any errors on the physical disk.

      because to me, it sounds remarkably like a disk issue - either physical or at FS level

      sigpic


      Please do show your appreciation to those who assist you by leaving Rep Point

      Comment

      Working...
      X