RE: Exchange Services do not start after reboot, but starts manually afterwards (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Information Stores



Message


DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 5:06:20 PM)

 
Well I manually at added DC2 then DC1, same issue, so i removed DC1 and left DC2 as the only Gc available, now rebooting...

Heres something : doesnt services use the GC that are specified in the registry?

I was noticing since the inetinfo.exe log sayin it will use GC specififed in the registry., and through out googling, i noticed some pages came up with ppl changing the GC to look for in the reg.




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 5:28:44 PM)

well bad news..specified GC is the 2nd DC and same problem..

i will post the logs here, maybe it might help..

Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2115
Date:  09/07/2007
Time:  16:41:11
User:  N/A
Computer: SERVER
Description:
Process STORE.EXE (PID=3944). DSAccess needs to close a connection to the Domain Controller servername.domain due to error 0x80040952.
____________________________________-

Event Type: Information
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2070
Date:  09/07/2007
Time:  16:41:11
User:  N/A
Computer: SERVER
Description:
Process MAD.EXE (PID=4228).  DSAccess lost contact with domain controller servername.domain  Error was 80040951 ().  DSAccess will attempt to reconnect with this domain controller when it is reachable.


___________________________________________________________

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2110
Date:  09/07/2007
Time:  16:41:11
User:  N/A
Computer: SERVER
Description:
Process STORE.EXE (PID=3944). Could not bind to DS server servername.domain, error 34 at port 389.

______________________________________________


_Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date:  09/07/2007
Time:  16:41:11
User:  N/A
Computer: SERVER
Description:
LDAP Bind was unsuccessful on directory servername.domain for distinguished name ''. Directory returned error:[0x34] Unavailable.   

_________________

These are errors after i did the manual switch for exch to look for DC2 only.

I must admit, i am see more critical looking errors this time. For example the codes 80040951 was not there before, it was 80040952  when i was monitoring before. I thikn 52 means local error, i will now check and see what 51 means.

Should i put back to auto find GCs?

Note its only the GCi  manually forced to DC2 the other server setting under directory access are auto still...

Same issue occurs for  the WMI AND INETINFO processes




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (9.Jul.2007 5:40:14 PM)

Judging from the logs, its seems the errors is with 389 - LDAP, and since the GC is 3289 it might be the issue of the GC? i am thinking of manually putting the DC manually  as the 2nd DC , question is what about the configuration DC ? what is that about anyhow?





a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (10.Jul.2007 5:39:14 AM)

Hiya David, ok, place the Exchange server back into Auto Discover.
Have you run dcdiag at all - if so can you post the results? thanks

Cheers

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (10.Jul.2007 10:32:03 AM)

ok it was let on all directory access settings to manuall use DC2. so now that i am reading your post, i am switchin back to auto discover and it seems to be discovering the DC2 first, not the DC1 as it originally was doing. Would the exch box require some time frame to update its settings perhaps? juding from this behaviour with DC2 being found first??? I cannoto restart the server right right now, to check if the exch services start on its on with this difference in discovery behaviour.

what i will do is give u the dcdiag results, I am guessing you want the dcdiag when its set to use the dc1?

and yes i have run dcdiag before , no fails, I will  post it.




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (10.Jul.2007 10:44:07 AM)

verbose :

Domain Controller Diagnosis
Performing initial setup:
  * Verifying that the local machine server, is a DC.
  * Connecting to directory service on server server.
  * Collecting site info.
  * Identifying all servers.
  * Identifying all NC cross-refs.
  * Found 2 DC(s). Testing 1 of them.
  Done gathering initial info.
Doing initial required tests
  Testing server: Default-First-Site-Name\server
     Starting test: Connectivity
        * Active Directory LDAP Services Check
        * Active Directory RPC Services Check
        ......................... server passed test Connectivity
Doing primary tests
  Testing server: Default-First-Site-Name\server
     Starting test: Replications
        * Replications Check
        * Replication Latency Check
           DC=ForestDnsZones,DC=domainname,DC=abc,DC=ab
              Latency information for 3 entries in the vector were ignored.
                 3 were retired Invocations.  0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc.  0 had no
latency information (Win2K DC).
           DC=DomainDnsZones,DC=domainname,DC=abc,DC=ab
              Latency information for 3 entries in the vector were ignored.
                 3 were retired Invocations.  0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc.  0 had no
latency information (Win2K DC).
           CN=Schema,CN=Configuration,DC=domainname,DC=abc,DC=ab
              Latency information for ab entries in the vector were ignored.
                 ab were retired Invocations.  0 were either: read-only replica
s and are not verifiably latent, or dc's no longer replicating this nc.  0 had n
o latency information (Win2K DC).
           CN=Configuration,DC=domainname,DC=abc,DC=ab
              Latency information for ab entries in the vector were ignored.
                 ab were retired Invocations.  0 were either: read-only replica
s and are not verifiably latent, or dc's no longer replicating this nc.  0 had n
o latency information (Win2K DC).
           DC=domainname,DC=abc,DC=ab
              Latency information for 13 entries in the vector were ignored.
                 13 were retired Invocations.  0 were either: read-only replica
s and are not verifiably latent, or dc's no longer replicating this nc.  0 had n
o latency information (Win2K DC).
        * Replication Site Latency Check
        ......................... server passed test Replications
     Test omiabed by user request: Topology
     Test omiabed by user request: CutoffServers
     Starting test: NCSecDesc
        * Security Permissions check for all NC's on DC server.
        * Security Permissions Check for
          DC=ForestDnsZones,DC=domainname,DC=abc,DC=ab
           (NDNC,Version 2)
        * Security Permissions Check for
          DC=DomainDnsZones,DC=domainname,DC=abc,DC=ab
           (NDNC,Version 2)
        * Security Permissions Check for
          CN=Schema,CN=Configuration,DC=domainname,DC=abc,DC=ab
           (Schema,Version 2)
        * Security Permissions Check for
          CN=Configuration,DC=domainname,DC=abc,DC=ab
           (Configuration,Version 2)
        * Security Permissions Check for
          DC=domainname,DC=abc,DC=ab
           (Domain,Version 2)
        ......................... server passed test NCSecDesc
     Starting test: NetLogons
        * Network Logons Privileges Check
        Verified share \\server\netlogon
        Verified share \\server\sysvol
        ......................... server passed test NetLogons
     Starting test: Advertising
        The DC server is advertising itself as a DC and having a DS.
        The DC server is advertising as an LDAP server
        The DC server is advertising as having a writeable directory
        The DC server is advertising as a Key Distribution Center
        The DC server is advertising as a time server
        The DS server is advertising as a GC.
        ......................... server passed test Advertising
     Starting test: KnowsOfRoleHolders
        Role Schema Owner = CN=NTDS Seabings,CN=server,CN=Servers,CN=Defau
lt-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=abc,DC=ab
        Role Domain Owner = CN=NTDS Seabings,CN=server,CN=Servers,CN=Defau
lt-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=abc,DC=ab
        Role PDC Owner = CN=NTDS Seabings,CN=server,CN=Servers,CN=Default-
First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=abc,DC=ab
        Role Rid Owner = CN=NTDS Seabings,CN=server,CN=Servers,CN=Default-
First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=abc,DC=ab
        Role Infrastructure Update Owner = CN=NTDS Seabings,CN=server,CN=S
ervers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=abc,DC
=ab
        ......................... server passed test KnowsOfRoleHolders
     Starting test: RidManager
        * Available RID Pool for the Domain is 8302 to 1073741823
        * server.domainname.abc.ab is the RID Master
        * DsBind with RID Master was successful
        * rIDAllocationPool is 7802 to 8301
        * rIDPreviousAllocationPool is 7802 to 8301
        * rIDNextRID: 7802
        ......................... server passed test RidManager
     Starting test: MachineAccount
        Checking machine account for DC server on DC server.
        * SPN found :LDAP/server.domainname.abc.ab/domainname.abc.ab
        * SPN found :LDAP/server.domainname.abc.ab
        * SPN found :LDAP/server
        * SPN found :LDAP/server.domainname.abc.ab/domainname
        * SPN found :LDAP/fd6e3b7b-46d4-411f-a8db-8cd4065b1c29._msdcs.domainname.o
rg.ab
        * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/fd6e3b7b-46d4-411f-a8
db-8cd4065b1c29/domainname.abc.ab
        * SPN found :HOST/server.domainname.abc.ab/domainname.abc.ab
        * SPN found :HOST/server.domainname.abc.ab
        * SPN found :HOST/server
        * SPN found :HOST/server.domainname.abc.ab/domainname
        * SPN found :GC/server.domainname.abc.ab/domainname.abc.ab
        ......................... server passed test MachineAccount
     Starting test: Services
        * Checking Service: Dnscache
        * Checking Service: NtFrs
        * Checking Service: IsmServ
        * Checking Service: kdc
        * Checking Service: SamSs
        * Checking Service: LanmanServer
        * Checking Service: LanmanWorkstation
        * Checking Service: RpcSs
        * Checking Service: w32time
        * Checking Service: NETLOGON
        ......................... server passed test Services
     Test omiabed by user request: OutboundSecureChannels
     Starting test: ObjectsReplicated
        server is in domain DC=domainname,DC=abc,DC=ab
        Checking for CN=server,OU=Domain Controllers,DC=domainname,DC=abc,DC=
ab in domain DC=domainname,DC=abc,DC=ab on 1 servers
           Object is up-to-date on all servers.
        Checking for CN=NTDS Seabings,CN=server,CN=Servers,CN=Default-Firs
t-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=abc,DC=ab in domain CN=Confi
guration,DC=domainname,DC=abc,DC=ab on 1 servers
           Object is up-to-date on all servers.
        ......................... server passed test ObjectsReplicated
     Starting test: frssysvol
        * The File Replication Service SYSVOL ready test
        File Replication Service's SYSVOL is ready
        ......................... server passed test frssysvol
     Starting test: frsevent
        * The File Replication Service Event log test
        ......................... server passed test frsevent
     Starting test: kccevent
        * The KCC Event log test
        Found no KCC errors in Directory Service Event log in the last 15 minut
es.
        ......................... server passed test kccevent
     Starting test: systemlog
        * The System Event log test
        Found no errors in System Event log in the last 60 minutes.
        ......................... server passed test systemlog
     Test omiabed by user request: VerifyReplicas
     Starting test: VerifyReferences
        The system object reference (serverReference)
        CN=server,OU=Domain Controllers,DC=domainname,DC=abc,DC=ab and
        backlink on
        CN=server,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Config
uration,DC=domainname,DC=abc,DC=ab
        are correct.
        The system object reference (frsComputerReferenceBL)
        CN=server,CN=Domain System Volume (SYSVOL share),CN=File Replicati
on Service,CN=System,DC=domainname,DC=abc,DC=ab
        and backlink on
        CN=server,OU=Domain Controllers,DC=domainname,DC=abc,DC=ab are
        correct.
        The system object reference (serverReferenceBL)
        CN=server,CN=Domain System Volume (SYSVOL share),CN=File Replicati
on Service,CN=System,DC=domainname,DC=abc,DC=ab
        and backlink on
        CN=NTDS Seabings,CN=server,CN=Servers,CN=Default-First-Site-Name,C
N=Sites,CN=Configuration,DC=domainname,DC=abc,DC=ab
        are correct.
        ......................... server passed test VerifyReferences
     Test omiabed by user request: VerifyEnterpriseReferences
     Test omiabed by user request: CheckSecurityError
  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 : domainname
     Starting test: CrossRefValidation
        ......................... domainname passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... domainname passed test CheckSDRefDom
  Running enterprise tests on : domainname.abc.ab
     Starting test: Intersite
        Skipping site Default-First-Site-Name, this site is outside the scope
        provided by the command line arguments provided.
        ......................... domainname.abc.ab passed test Intersite
     Starting test: FsmoCheck
        GC Name: \\server.domainname.abc.ab
        Locator Flags: 0xe00003fd
        PDC Name: \\server.domainname.abc.ab
        Locator Flags: 0xe00003fd
        Time Server Name: \\server.domainname.abc.ab
        Locator Flags: 0xe00003fd
        Preferred Time Server Name: \\server.domainname.abc.ab
        Locator Flags: 0xe00003fd
        KDC Name: \\server.domainname.abc.ab
        Locator Flags: 0xe00003fd
        ......................... domainname.abc.ab passed test FsmoCheck
     Test omiabed by user request: DNS
     Test omiabed by user request: DNS




a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (10.Jul.2007 3:20:47 PM)

Hiya David, the following is taken from http://technet.microsoft.com/en-us/library/aa996247.aspx#DSAccessTopologyDiscovery

What helps explain what happens when Exchange automatically discovers the domain controller topology;

The following sequential list outlines the discovery process and indicates differences between initial discovery and rediscovery:

The system attendant process (Mad.exe) instantiates and initializes DSAccess.dll during startup.
From the local domain, DSAccess opens an LDAP connection to a randomly chosen domain controller. This server is referred to as the bootstrap server.
DSAccess reads the local registry to determine if the topology is hard coded. If the topology is hard coded, the discovery process stops. If no hard coding is detected, DSAccess continues the discovery process.
DSAccess queries the bootstrap server to identify local domain controllers and global catalog servers. DSAccess then determines server suitability and assigns server roles.
DSAccess queries the bootstrap server to determine if one or more secondary sites are connected to the local site. If secondary sites exist, DSAccess sorts the siteLink objects for each site from lowest cost to highest cost. DSAccess places the lowest cost sites in a secondary topology list.
DSAccess queries the bootstrap server to identify the domain controllers and global catalog servers that are located in the secondary topology sites.
DSAccess identifies the full topology and compiles a list of working domain controllers, and a list of working global catalog servers.
By default, DSAccess initialization during startup must finish within one minute. Otherwise, DSAccess stops. One minute is usually long enough for DSAccess to initialize. If initialization takes longer than one minute, this might indicate a problem with the network or topology configuration. Although you can extend the time-out parameter by setting a registry key, you should first determine why initialization takes longer than expected. To configure the time-out, use the registry setting shown in the following table.

Can we try one more thing, set all of your Exchange services to manual startup, then reboot the Exchange server (and DC) when the server has booted up - wait about 5 minutes, then manually start the Exchange services - then check the logs.

What I need to now is do these messages appear?
Cheers

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (10.Jul.2007 5:10:07 PM)

ok i am going to try that out now, I only set to manual , IS, SYS ATTEN, AND MTA




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (10.Jul.2007 5:31:30 PM)

I am gettin the errors still as usual for the other services as shown below, I did mention that to you before did I? 

Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2115
Date:  7/10/2007
Time:  5:13:53 PM
User:  N/A
Computer: SERVER
Description:
Process WMIPRVSE.EXE -EMBEDDING (PID=2960). DSAccess needs to close a connection to the Domain Controller 127.0.0.1 due to error 0x80040952.


Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2115
Date:  7/10/2007
Time:  5:14:27 PM
User:  N/A
Computer: SERVER
Description:
Process INETINFO.EXE (PID=504). DSAccess needs to close a connection to the Domain Controller 127.0.0.1 due to error 0x80040952.


After I manually starting the exch services there are no errors.
Should I put manual startup for the IIS and WMI services, reboot , check logs and then manually start?




a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 3:41:01 AM)

Yes please mate.

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 12:22:59 PM)

ok here is the thing, I found the IIS service to manual the inetinfo.exe

but looking for
 
Process WMIPRVSE.EXE -EMBEDDING (PID=2960). Topology Discovery failed, error 0x80040952.
 
all i can fins is the adapter service WMIAPRVSE.EXE,  whic is already on manual.
 
so how can put the WMIPRVSE.EXE to manual?




a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 12:37:57 PM)

Hiya, I think that it runs as a process from the winmgmt service (Windows Management Instrumentation) - which can be set to manual as well.

Just to make sure that we are still on the same track all we are trying to prove here is that there is not a problem with the Exchange server per 'se just that you get the messages because it is waiting for its own directory service to start which generates the error messages that you see - I am pretty much sure that is the case already.

Cheers

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 1:48:21 PM)

ok , that by default is manual. yea i am pretty sure its not the exchange server, from the fact it starts without errors when i manually start it. But thinking ahead, can it just be the timing of discovery is the problem? From the technet article, its either a non-suitable GC is hard coded in my registry and hence makes it want to search for one, or contacting the hardcoded GC takes to long.

So what might be the next step , increasing the delay? which is not really finding out the real problem not so?




a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 2:06:43 PM)

Hiya David, this goes back to the point that I raised in the first post,

Exchange is not designed nor recommended on a Domain Controller for the very reason that we are seeing here, the issues with the services and event log entries are related to the processes that are run during the directory start up on the Exchange server and the Exchange services trying to start at the same time - as the processes will use the nearest domain controller (which is itself) this will happen.

I am not sure what else to suggest chap, I will have a look around on the web for you, there is an article here which explains a bit about Exchange on a DC and deals with slow shutdowns, which can also be related to boot ups http://hellomate.typepad.com/exchange/2004/02/exchange_on_a_d.html

Thanks

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 2:44:39 PM)

ya, but Andy, if we pushed up the DC 2 to a GC and DC and confg DC, what is the problem then? doesnt the exchange server setting for directory access override all? or does hard code takes priority and then that?

aand would it be a very safe assumption that is the problem?




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (11.Jul.2007 4:35:10 PM)

http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1206639,00.html




a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (12.Jul.2007 4:23:04 AM)

Ok, from what I understand a hardcoded value will override - some further information here http://technet.microsoft.com/en-us/library/aa998692.aspx, but, forgive me I am a little at a loss with what the problem is a the moment - we know what was causing the event log errors and know that it is part of what can be described as a hazard of running Exchange on a DC - do you now wish to try and get rid of them, if so I have an idea.

Thanks mate,

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (12.Jul.2007 10:20:57 AM)

well what are you suggesting to try?

Thing is the exchange server was loading up fine before i installed windows service pack 1. Do you I should try uninstalling the service pack 1 and see how it operates?





a.grogan -> RE: Exchange Services do not start after reboot, but starts manually afterwards (12.Jul.2007 2:52:37 PM)

Hiya David, well there are two options;

1. Rather than continue to mess around in the registry and with Domain Controller settings I could give you a script that runs about 30 seconds after the Exchange server boots and starts all of the services for you (this gives the directory time to load and will not place anything nasty in your Event Log).

2. You could un-install the service pack, which only you can decide on, personally I find removing Service Packs a little bit risky.

Let me know,

A




DavidTT -> RE: Exchange Services do not start after reboot, but starts manually afterwards (12.Jul.2007 8:46:54 PM)

hmm a script. before we go to that, what do you think of the delay increase in the registry that makes exchange wait longer than the registered 1 minute? It was something you posted earlier on, but does it dictate how long for the exch services to boot up?

I think one of the reg edits is to check to see if there are a certain # of GC's available before checking the local GC. But is this edit reversible? I am guessing so.

So i want to make sure its just that the directory services loading and not ready for exch to start. And if that is the case then i would prefer it use the other GC and just a script to force all services to start. Although that might be a better bet , in the case if DC 2 goes down. I guess i am still looking to see if it will work with the DC2 to satisify my mind that it is DC1 still loading definately causing it.

So anyhow, in other words the directory access override does not count for much because it is on a DC?




Page: <<   < prev  1 [2] 3   next >   >>