Re: Server crawls during backup

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




1) Re-enable your write cache. I can see that a lot of the errors you
get are related to write operations, that might solve the problem.
2) Check the File Replication event logs to see if NTFrs logged JOURNAL
WRAP errors and fix them according to the error explanation provided if
applicable. If that doesn't clear the Userenv 1030 errors, Microsoft has
a fix for it. Go to http://support.microsoft.com and enter Userenv 1030
in the KB search bar.


Pharismod Wrote:
Hey there,

I have an SBS 2003 server that runs ridiculously slowly during the
backup process. So slowly in fact that the console is all but unusable.
It seems that the server freezes almost solid at times and then several
errors/warnings are logged immediately afterwards.

The server is new and the domain was swung using the Swing Kit and
Exchange Forklift. Other than the problems during the backup it runs
like a dream.

Specs:
Tyan Tiger K8SSA
Single AMD Operton Processor
4 GB Reg'd ECC Ram
3 x 150 GB WD 10K Raptor Disks - Raid 5 - Write Cache Disabled
Adaptec 2410SA

The backup drives are external 320 GB external USB hard drives. I have
used the same type on multiple servers without incident.

Event Viewer starting from 11pm when the backup begins, warnings/errors
only:

11pm - backup begins

Event Type: Warning
Event Source: ESE
Event Category: Performance
Event ID: 508
Date: 11/3/2006
Time: 11:30:03 PM
User: N/A
Computer: BUDDY
Description:
Information Store (5040) First Storage Group: A request to write to the
file "E:\EXData\E00.log" at offset 5169152 (0x00000000004ee000) for 512
(0x00000200) bytes succeeded, but took an abnormally long time (121
seconds) to be serviced by the OS. This problem is likely due to faulty
hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.

For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Date: 11/3/2006
Time: 11:37:46 PM
User: N/A
Computer: BUDDY
Description:
Unexpected replication thread error 0x80004005 on database "First
Storage Group\Public Folder Store (BUDDY)".

FReplAgent


For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 508
Date: 11/3/2006
Time: 11:40:16 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\log\edb.log" at offset 5013504
(0x00000000004c8000) for 512 (0x00000200) bytes succeeded, but took an
abnormally long time (299 seconds) to be serviced by the OS. This
problem is likely due to faulty hardware. Please contact your hardware
vendor for further assistance diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 11/3/2006
Time: 11:42:32 PM
User: NT AUTHORITY\SYSTEM
Computer: BUDDY
Description:
Windows cannot access the file gpt.ini for GPO
CN={79ABAAD1-90E9-4760-8FC8-A26573C4EC3A},CN=Policies,CN=System,DC=horsejournals,DC=office.
The file must be present at the location
<\\horsejournals.office\SysVol\horsejournals.office\Policies\{79ABAAD1-90E9-4760-8FC8-A26573C4EC3A}\gpt.ini>.
(Configuration information could not be read from the domain
controller, either because the machine is unavailable, or access has
been denied. ). Group Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 11/3/2006
Time: 11:42:32 PM
User: NT AUTHORITY\SYSTEM
Computer: BUDDY
Description:
Windows cannot query for the list of Group Policy objects. Check the
event log for possible messages previously logged by the policy engine
that describes the reason for this.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 510
Date: 11/3/2006
Time: 11:50:09 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\log\edb.log" at offset 5046272
(0x00000000004d0000) for 512 (0x00000200) bytes succeeded, but took an
abnormally long time (256 seconds) to be serviced by the OS. In
addition, 0 other I/O requests to this file have also taken an
abnormally long time to be serviced since the last message regarding
this problem was posted 592 seconds ago. This problem is likely due to
faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 510
Date: 11/3/2006
Time: 11:53:41 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\log\edb.log" at offset 5062656
(0x00000000004d4000) for 512 (0x00000200) bytes succeeded, but took an
abnormally long time (158 seconds) to be serviced by the OS. In
addition, 0 other I/O requests to this file have also taken an
abnormally long time to be serviced since the last message regarding
this problem was posted 212 seconds ago. This problem is likely due to
faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 508
Date: 11/3/2006
Time: 11:55:00 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\sys\edb.chk" at offset 0 (0x0000000000000000) for
4096 (0x00001000) bytes succeeded, but took an abnormally long time (61
seconds) to be serviced by the OS. This problem is likely due to faulty
hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2392
Date: 11/3/2006
Time: 11:54:05 PM
User: N/A
Computer: BUDDY
Description:
Process WMIPRVSE.EXE -EMBEDDING (PID=5344). DSAccess failed to register
an Active Directory shutdown notification with the local server, error
0x55. To expedite the shutdown process, manually shut down Exchange
services before shutting down the server.

For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Warning
Event Source: ESE
Event Category: Performance
Event ID: 510
Date: 11/3/2006
Time: 11:57:51 PM
User: N/A
Computer: BUDDY
Description:
Information Store (5040) First Storage Group: A request to write to the
file "E:\EXData\E00.log" at offset 5234688 (0x00000000004fe000) for 512
(0x00000200) bytes succeeded, but took an abnormally long time (105
seconds) to be serviced by the OS. In addition, 0 other I/O requests to
this file have also taken an abnormally long time to be serviced since
the last message regarding this problem was posted 1667 seconds ago.
This problem is likely due to faulty hardware. Please contact your
hardware vendor for further assistance diagnosing the problem.

For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 11/4/2006
Time: 12:01:27 AM
User: N/A
Computer: BUDDY
Description:
Process MAD.EXE (PID=3980). All Domain Controller Servers in use are
not responding:
buddy.horsejournals.office


For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1031
Date: 11/4/2006
Time: 12:03:07 AM
User: N/A
Computer: BUDDY
Description:
One of the System Attendant's task is blocked.
Function: CMonitoringTask::Work

For more information, click
http://www.microsoft.com/contentredirect.asp.


Various combinations of these errors continue on all night long usually
in clumps, which indicates that the server is hanging up for several
seconds and then coming back to life.

Any suggestions? Seems likely that this is hardware related, but is the
hardware most likely bad or misconfigured? Would a disabled write cache
cause this? How serious is it if left alone?

Thanks,

Pharismod


--
rrafiringa
------------------------------------------------------------------------
rrafiringa's Profile: http://forums.techarena.in/member.php?userid=18734
View this thread: http://forums.techarena.in/showthread.php?t=619536

http://www.techarena.in

.



Relevant Pages

  • Re: openSUSE as small bussiness server
    ... hardware support for current systems. ... decade and they have hardware support. ... The other 8.2 server is old-ish Dell ca 2001. ... Most of my customers are small to medium size. ...
    (alt.os.linux.suse)
  • Re: Why upgrade to SBS2008
    ... Just to comment on a minor part of your post - IMO the winding down of SBS 2003 support is a valid consideration in your scenario. ... You're getting ready to put a major time investment into moving to new hardware, and in my opinion, you'll get more mileage out of the installation if you use the currently shipping version. ... I'm not rushing to upgrade my perfectly functioning SBS 2003 before my normal hardware refresh cycle, but if I were replacing hardware anyway, it would never occur to me to stand up the new server with an old platform version. ...
    (microsoft.public.windows.server.sbs)
  • Re: Openserver 5.07 and a medical practice
    ... hardware failure creates a crisis, as I figure most hardware is good ...  The OS on our server is OS 5.07. ... support for their product given Sco's ... an arbitrary virtualization server. ...
    (comp.unix.sco.misc)
  • Re: Migration from Windows Server 2000
    ... the potential losses in support and just plain 'stuffin ... to near 'as-is' condition and now having a copy in virtual hardware. ... finding 'OHHH, and now _this_ is referring to the old server, how do we fix ... The SBS2k3 install can be stopped after just the OS stage and enter ...
    (microsoft.public.windows.server.sbs)
  • Re: repeated failure of store - securty hack?
    ... You can always call Microsoft product support - Security and discuss the issues. ... I have a problem with a sbs 2003 server runnig fine since ... This problem is likely due to faulty hardware. ... Please contact your hardware vendor for further assistance diagnosing the problem. ...
    (microsoft.public.windows.server.sbs)