Three Errors on Server 2003 SB Any idea?
- From: Jim <Jim@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Mar 2006 10:39:24 -0800
These are the three errors I'm getting and I have follow all the
recommendations For Microsoft links with no luck in correcting the issues.
Any help would be greatly appreciated. I am running 2003 Sb with Exchange
2003.
Microsoft Software Shadow Copy Provider
Total auto-started services not running: 1
In normal conditions, these services should be running. For details, it is
recommended that you review errors in the Event log related to the service.
Critical Alerts
Critical Errors in Application Log
Source Event ID Last Occurrence Total Occurrences
MSExchangeSA 9334 3/20/2006 2:01 AM 1
OALGen encountered error 8004010f while initializing the offline address
list generation process. No offline address lists have been generated. Please
check the event log for more information. - Default Global Address List For
more information, click http://www.microsoft.com/contentredirect.asp.
Source Event ID Last Occurrence Total Occurrences
MSExchangeSA 9344 3/20/2006 2:01 AM 1
OALGen could not find the address list with the Active Directory object GUID
of '/guid=2FAC79CC15D45444B0CD02EDBDCD6A1A' in the list of available address
lists. Please check the offline address list configuration object. - Default
Global Address List For more information, click
http://www.microsoft.com/contentredirect.asp.
Critical Errors in File Replication Service Log
Source Event ID Last Occurrence Total Occurrences
NtFrs 13552 3/19/2006 8:04 PM 1
The File Replication Service is unable to add this computer to the following
replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" This could be caused by a
number of problems such as: -- an invalid root path, -- a missing directory,
-- a missing disk volume, -- a file system on the volume that does not
support NTFS 5.0 The information below may help to resolve the problem:
Computer DNS name is "Adminmgr-002.austinmps.local" Replica set member name
is "ADMINMGR-002" Replica set root path is "c:\windows\sysvol\domain" Replica
staging directory path is "c:\windows\sysvol\staging\domain" Replica working
directory path is "c:\windows\ntfrs\jet" Windows error status code is FRS
error status code is FrsErrorMismatchedJournalId Other event log messages may
also help determine the problem. Correct the problem and the service will
attempt to restart replication automatically at a later time.
Source Event ID Last Occurrence Total Occurrences
NtFrs 13555 3/19/2006 8:04 PM 1
The File Replication Service is in an error state. Files will not replicate
to or from one or all of the replica sets on this computer until the
following recovery steps are performed: Recovery Steps: [1] The error state
may clear itself if you stop and restart the FRS service. This can be done by
performing the following in a command window: net stop ntfrs net start ntfrs
If this fails to clear up the problem then proceed as follows. [2] For Active
Directory Domain Controllers that DO NOT host any DFS alternates or other
replica sets with replication enabled: If there is at least one other Domain
Controller in this domain then restore the "system state" of this DC from
backup (using ntbackup or other backup-restore utility) and make it
non-authoritative. If there are NO other Domain Controllers in this domain
then restore the "system state" of this DC from backup (using ntbackup or
other backup-restore utility) and choose the Advanced option which marks the
sysvols as primary. If there are other Domain Controllers in this domain but
ALL of them have this event log message then restore one of them as primary
(data files from primary will replicate everywhere) and the others as
non-authoritative. [3] For Active Directory Domain Controllers that host DFS
alternates or other replica sets with replication enabled: (3-a) If the Dfs
alternates on this DC do not have any other replication partners then copy
the data under that Dfs share to a safe location. (3-b) If this server is the
only Active Directory Domain Controller for this domain then, before going to
(3-c), make sure this server does not have any inbound or outbound
connections to other servers that were formerly Domain Controllers for this
domain but are now off the net (and will never be coming back online) or have
been fresh installed without being demoted. To delete connections use the
Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the "system state" of this DC from backup (using ntbackup or
other backup-restore utility) and make it non-authoritative. (3-d) Copy the
data from step (3-a) above to the original location after the sysvol share is
published. [4] For other Windows servers: (4-a) If any of the DFS alternates
or other replica sets hosted by this server do not have any other replication
partners then copy the data under its share or replica tree root to a safe
location. (4-b) net stop ntfrs (4-c) rd /s /q c:\windows\ntfrs\jet (4-d) net
start ntfrs (4-e) Copy the data from step (4-a) above to the original
location after the service has initialized (5 minutes is a safe waiting
time). Note: If this error message is in the eventlog of all the members of a
particular replica set then perform steps (4-a) and (4-e) above on only one
of the members.
.
- Follow-Ups:
- RE: Three Errors on Server 2003 SB Any idea?
- From: "Brandy Nee [MSFT]"
- RE: Three Errors on Server 2003 SB Any idea?
- Prev by Date: Re: CEICW and Remote Web Workplace
- Next by Date: Re: MSSQL$SBSMonitoring Database size (SBS2003)
- Previous by thread: Errors during SBS 2003 SP1 Installation
- Next by thread: RE: Three Errors on Server 2003 SB Any idea?
- Index(es):
Relevant Pages
|
