Re: SA hungs on starting

Tech-Archive recommends: Speed Up your PC by fixing your registry

i think we found it. it turns out to be the schema master is down since link
to the server is down.

regards


"sherwin de claro" <sherwin.de.claro@xxxxxxxxx> wrote in message
news:%23A7sbB25GHA.3732@xxxxxxxxxxxxxxxxxxxxxxx
another info from server not running Exchange SA
-------------------------------

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Corporate\SELENE
Starting test: Connectivity
......................... SELENE passed test Connectivity

Doing primary tests

Testing server: Corporate\SELENE
Starting test: Replications
[Replications Check,SELENE] No replication recently attempted:
From PONTUS to SELENE
Naming Context: CN=Schema,CN=Configuration,DC=newpagcor,DC=com
The last attempt occurred at 2006-10-04 04:57.01 (about 5
hours
ago)
.
REPLICATION LATENCY WARNING
SELENE: A full synchronization is in progress
from PONTUS to SELENE
Replication of new changes along this path will be delayed.
The full sync is 0.00% complete.
[Replications Check,SELENE] A recent replication attempt failed:
From HYPNOS to SELENE
Naming Context: CN=Schema,CN=Configuration,DC=newpagcor,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-10-04 09:31.16.
The last success occurred at 2006-10-03 15:53.54.
16 failures have occurred since the last success.
The source HYPNOS is responding now.
[Replications Check,SELENE] A recent replication attempt failed:
From MEDEA to SELENE
Naming Context: CN=Schema,CN=Configuration,DC=newpagcor,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-10-04 09:31.58.
The last success occurred at 2006-10-04 08:49.09.
1 failures have occurred since the last success.
The source MEDEA is responding now.
[Replications Check,SELENE] A recent replication attempt failed:
From HESTIA to SELENE
Naming Context: CN=Schema,CN=Configuration,DC=newpagcor,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-10-04 10:36.11.
The last success occurred at (never).
1 failures have occurred since the last success.
[HESTIA] DsBind() failed with error 1722,
The RPC server is unavailable..
The source remains down. Please check the machine.
REPLICATION LATENCY WARNING
SELENE: A full synchronization is in progress
from HESTIA to SELENE
Replication of new changes along this path will be delayed.
[HESTIA] LDAP connection failed with error 58,
The specified server cannot perform the requested operation..
[Replications Check,SELENE] No replication recently attempted:
From PONTUS to SELENE
Naming Context: CN=Configuration,DC=newpagcor,DC=com
The last attempt occurred at 2006-10-04 04:44.26 (about 6
hours
ago)
.
REPLICATION LATENCY WARNING
SELENE: A full synchronization is in progress
from PONTUS to SELENE
Replication of new changes along this path will be delayed.
The full sync is 0.00% complete.
[Replications Check,SELENE] A recent replication attempt failed:
From HYPNOS to SELENE
Naming Context: CN=Configuration,DC=newpagcor,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2006-10-04 09:27.02.
The last success occurred at 2006-10-03 16:18.03.
20 failures have occurred since the last success.
The replication RPC call executed for too long at the server
and
was cancelled.
Check load and resouce usage on HYPNOS.
[Replications Check,SELENE] A recent replication attempt failed:
From HESTIA to SELENE
Naming Context: CN=Configuration,DC=newpagcor,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-10-04 10:35.51.
The last success occurred at (never).
1 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION LATENCY WARNING
SELENE: A full synchronization is in progress
from HESTIA to SELENE
Replication of new changes along this path will be delayed.
[Replications Check,SELENE] A recent replication attempt failed:
From HYPNOS to SELENE
Naming Context: DC=newpagcor,DC=com
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2006-10-04 10:24.49.
The last success occurred at 2006-10-03 16:21.20.
36 failures have occurred since the last success.
The replication RPC call executed for too long at the server
and
was cancelled.
Check load and resouce usage on HYPNOS.
[Replications Check,SELENE] A recent replication attempt failed:
From HESTIA to SELENE
Naming Context: DC=newpagcor,DC=com
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2006-10-04 10:35.34.
The last success occurred at (never).
1 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION LATENCY WARNING
SELENE: A full synchronization is in progress
from HESTIA to SELENE
Replication of new changes along this path will be delayed.
REPLICATION LATENCY WARNING
SELENE: A long-running replication operation is in progress
The job has been executing for 12 minutes and 30 seconds.
Replication of new changes along this path will be delayed.
Error: Higher priority replications are being blocked
Enqueued 2006-10-04 10:35.09 at priority 70
Op: SYNC FROM SOURCE
NC DC=newpagcor,DC=com
DSADN CN=NTDS
Settings,CN=HYPNOS,CN=Servers,CN=Corporate,CN=Sites,CN
=Configuration,DC=newpagcor,DC=com
DSA transport addr
375fda01-d715-4b55-a443-90d22e08c8b6._msdcs.newpa
gcor.com
......................... SELENE passed test Replications
Starting test: NCSecDesc
......................... SELENE passed test NCSecDesc
Starting test: NetLogons
......................... SELENE passed test NetLogons
Starting test: Advertising
......................... SELENE passed test Advertising
Starting test: KnowsOfRoleHolders
Warning: HESTIA is the Schema Owner, but is not responding to DS
RPC Bi
nd.
Warning: HESTIA is the Schema Owner, but is not responding to
LDAP
Bind
.
Warning: HESTIA is the Domain Owner, but is not responding to DS
RPC Bi
nd.
Warning: HESTIA is the Domain Owner, but is not responding to
LDAP
Bind
.
......................... SELENE failed test KnowsOfRoleHolders
Starting test: RidManager
......................... SELENE passed test RidManager
Starting test: MachineAccount
......................... SELENE passed test MachineAccount
Starting test: Services
......................... SELENE passed test Services
Starting test: ObjectsReplicated
......................... SELENE passed test ObjectsReplicated
Starting test: frssysvol
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SELENE passed test frssysvol
Starting test: kccevent
An Information Event occured. EventID: 0x4000051C
Time Generated: 10/04/2006 10:39:59
(Event String could not be retrieved)
An Information Event occured. EventID: 0x4000051C
Time Generated: 10/04/2006 10:39:59
(Event String could not be retrieved)
......................... SELENE failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x80001770
Time Generated: 10/04/2006 10:34:55
Event String: The System log file is full.
An Error Event occured. EventID: 0x80001770
Time Generated: 10/04/2006 10:35:39
Event String: The Application log file is full.
......................... SELENE failed test systemlog

Running enterprise tests on : newpagcor.com
Starting test: Intersite
......................... newpagcor.com passed test Intersite
Starting test: FsmoCheck
......................... newpagcor.com passed test FsmoCheck
-------------------------------

"Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@xxxxxxxxxx> wrote in message
news:Oguiefx5GHA.3404@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

Sounds as if you have AD problems.- SA won't start without a running
active
directory. Run dcdiag on the server (part of the system tools) and see
what
it tells you.

Leif

"sherwin de claro" <sherwin.de.claro@xxxxxxxxx> wrote in message
news:OwP3itv5GHA.3808@xxxxxxxxxxxxxxxxxxxxxxx
Our exchange server services stops. and the SA services stays
"starting"
for
a very long time. event logs that might help posted below:


-----DNS Event log--------------------------------------
Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 4013
Date: 10/3/2006
Time: 10:07:28 PM
User: N/A
Computer: MORPHEUS
Description:
The DNS server was unable to open the Active Directory. This DNS
server
is
configured to use directory service information and can not operate
without
access to the directory. The DNS server will wait for the directory
to
start. If the DNS server is started but the appropriate event has not
been
logged, then the DNS server is still waiting for the directory to
start.
Data:
0000: f5 25 00 00 õ%..



-----Application Event log--------------------------------------
Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1002
Date: 10/3/2006
Time: 10:14:44 PM
User: N/A
Computer: MORPHEUS
Description:
Metabase Update agent failed to start. Error code is 80040a01.

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


Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9004
Date: 10/3/2006
Time: 10:14:44 PM
User: N/A
Computer: MORPHEUS
Description:
The Metabase Update service failed to start, error '80040a01'.

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


Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 10/3/2006
Time: 10:14:44 PM
User: N/A
Computer: MORPHEUS
Description:
Unexpected error An unknown error has occurred. ID no: 80040a01
Microsoft
Exchange System Attendant occurred.

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


Event Type: Information
Event Source: MSExchangeSA
Event Category: General
Event ID: 1004
Date: 10/3/2006
Time: 10:14:44 PM
User: N/A
Computer: MORPHEUS
Description:
Microsoft Exchange System Attendant failed to start.

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


Event Type: Information
Event Source: MSExchangeDSAccess
Event Category: General
Event ID: 2078
Date: 10/3/2006
Time: 10:14:44 PM
User: N/A
Computer: MORPHEUS
Description:
Process MAD.EXE (PID=1844). DSAccess is shutting down.

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


Event Type: Warning
Event Source: POP3SVC
Event Category: General
Event ID: 1036
Date: 10/3/2006
Time: 10:14:45 PM
User: N/A
Computer: MORPHEUS
Description:
An error occurred while starting the Microsoft Exchange POP3 Service:
server
instance number 1 failed to start with error 0x80040a01.

For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 6e 01 51 00 n.Q.


Event Type: Information
Event Source: POP3SVC
Event Category: General
Event ID: 1033
Date: 10/3/2006
Time: 10:14:45 PM
User: N/A
Computer: MORPHEUS
Description:
Microsoft Exchange POP3 Service (Build 6.0.6249.0) has started.

For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 9b 02 49 00 ?.I.


Event Type: Warning
Event Source: IMAP4SVC
Event Category: General
Event ID: 1036
Date: 10/3/2006
Time: 10:15:45 PM
User: N/A
Computer: MORPHEUS
Description:
An error occurred while starting the Microsoft Exchange IMAP4 Service:
server instance number 1 failed to start with error 0x80040a01.

For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 78 01 2d 00 x.-.


Event Type: Information
Event Source: IMAP4SVC
Event Category: General
Event ID: 1033
Date: 10/3/2006
Time: 10:15:45 PM
User: N/A
Computer: MORPHEUS
Description:
Microsoft Exchange IMAP4 Service (Build 6.0.6249.0) has started.

For more information, click
http://www.microsoft.com/contentredirect.asp.
Data:
0000: aa 02 30 00 ª.0.


Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 61
Date: 10/3/2006
Time: 10:16:46 PM
User: N/A
Computer: MORPHEUS
Description:
WMI ADAP was unable to process the RemoteAccess performance library
due
to
a
time violation in the open function











.

Relevant Pages

  • AD 2000, FSMO, and Exchange 2000.. I broke it..
    ... server in a small office of about 10 users. ... I try a manual replication I see the following errors ... Event Source: NETLOGON ... Source DSA Address: ...
    (microsoft.public.win2000.active_directory)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • My Active Directory is barely active...heh
    ... Windows 2000 Server - George ... Windows 2003 Server - Newman ... manually readded them and then got eventlogs stating replication had ... Event Source: System Error ...
    (microsoft.public.windows.server.active_directory)