Re: Local Delivery is not sending to one recipient in Exchange Ser
- From: Carolyn <Carolyn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Apr 2006 06:14:03 -0700
These are my errors in DNS Server Event Viewer:
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4007
Date: 4/19/2006
Time: 2:57:56 PM
User: N/A
Computer: SERVER-J
Description:
The DNS server was unable to open zone rickkochoil in the Active Directory
from the application directory partition DomainDnsZones.rickkochoil. This DNS
server is configured to obtain and use information from the directory for
this zone and is unable to load the zone without it. Check that the Active
Directory is functioning properly and reload the zone. The event data is the
error code.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 ....
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4007
Date: 4/19/2006
Time: 2:57:56 PM
User: N/A
Computer: SERVER-J
Description:
The DNS server was unable to open zone _msdcs.rickkochoil in the Active
Directory from the application directory partition
ForestDnsZones.rickkochoil. This DNS server is configured to obtain and use
information from the directory for this zone and is unable to load the zone
without it. Check that the Active Directory is functioning properly and
reload the zone. The event data is the error code.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 00 00 ....
Errors in File Replication Service:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 4/19/2006
Time: 3:49:00 PM
User: N/A
Computer: SERVER-J
Description:
The File Replication Service has detected that the replica set "DOMAIN
SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to
read from the NTFS USN journal is not found. This can occur because of one
of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can
truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long
time.
[5] File Replication Service could not keep up with the rate of Disk IO
activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1
will cause the following recovery steps to be taken to automatically recover
from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be
deleted from the replica set. If you do not want to wait 5 minutes, then run
"net stop ntfrs" followed by "net start ntfrs" to restart the File
Replication Service.
[2] At the poll following the deletion this computer will be re-added to
the replica set. The re-addition will trigger a full tree sync for the
replica set.
WARNING: During the recovery process data in the replica tree may be
unavailable. You should reset the registry parameter described above to 0 to
prevent automatic recovery from making the data unexpectedly unavailable if
this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value
function under the Edit Menu item. Type the value name exactly as shown above.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
dcdiag gives me these results:
C:\Program Files\Support Tools>dcdiag
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER-J
Starting test: Connectivity
......................... SERVER-J passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER-J
Starting test: Replications
......................... SERVER-J passed test Replications
Starting test: NCSecDesc
......................... SERVER-J passed test NCSecDesc
Starting test: NetLogons
......................... SERVER-J passed test NetLogons
Starting test: Advertising
......................... SERVER-J passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER-J passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER-J passed test RidManager
Starting test: MachineAccount
......................... SERVER-J passed test MachineAccount
Starting test: Services
......................... SERVER-J passed test Services
Starting test: ObjectsReplicated
......................... SERVER-J passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER-J passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... SERVER-J failed test frsevent
Starting test: kccevent
......................... SERVER-J passed test kccevent
Starting test: systemlog
......................... SERVER-J passed test systemlog
Starting test: VerifyReferences
......................... SERVER-J passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : rickkochoil
Starting test: CrossRefValidation
......................... rickkochoil passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... rickkochoil passed test CheckSDRefDom
Running enterprise tests on : rickkochoil.com
Starting test: Intersite
......................... rickkochoil.com passed test Intersite
Starting test: FsmoCheck
......................... rickkochoil.com passed test FsmoCheck
Any help would be much appreciated! I know when I'm in over my head!
--
Carolyn
"Carolyn" wrote:
I think I have a bigger problem. When I restarted the server, it came up.
with an event code 4015. I think my problems started when I attempted to
install system restore on the windows server 2003. I am going to revert to a
backup and then see where we are at. Thanks for all your help. I'll post
more when I get the backup restored.
--
Carolyn
"Ben Hoffman [MVP Exchange]" wrote:
Hi Carolyn,
Have you tried forcing the connection?
This could be a corrupt mailbox, you might need to backup this mailbox into
PST using either ExMerge the Exchange Migration Wizard or Outlook delete the
mailbox, then re-create finally import the email back in.
If you are able to, you might want to schedule a reboot, to see if this
fixes the stuck messages.
Regards
--
Ben Hoffman
MVP Exchange
http://www.exchangeis.com
"Carolyn" <Carolyn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:739CA042-104F-472C-A2A6-FAEE5BFF4403@xxxxxxxxxxxxxxxx
I have one person that is not able to receive emails. I checked and they
are
all in the Administrative Group Queue "Local Delivery". I don't see any
errors and everyone else is receiving their emails. Any help would be
greatly appreciated.
Exchange Server 2003 version 6.5
--
Carolyn
- References:
- Re: Local Delivery is not sending to one recipient in Exchange Server
- From: Ben Hoffman [MVP Exchange]
- Re: Local Delivery is not sending to one recipient in Exchange Server
- Prev by Date: Re: SSL Issue - [WP]
- Next by Date: Re: strange hanging problems with exchange
- Previous by thread: Re: Local Delivery is not sending to one recipient in Exchange Server
- Next by thread: Re: Webaccess + Resources
- Index(es):
Relevant Pages
|
