Link to home
Create AccountLog in
Avatar of Bruce_S_C
Bruce_S_CFlag for United States of America

asked on

Exchange 2007 Information store not starting after new install to migrate from Exchange 2003

I have the following errors in my application logs, any ideas?


Event Type:      Error
Event Source:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2104
Date:            3/7/2008
Time:            11:56:35 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1308). None of the domain controllers in the domain are responding. This event can occur if the domain controllers in local or all domains become unreachable because of network problems. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health.

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:      1053
Date:            3/7/2008
Time:            11:56:36 AM
User:            NT AUTHORITY\SYSTEM
Computer:      EX1
Description:
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). 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:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2120
Date:            3/7/2008
Time:            11:56:47 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1308). Error ERROR_TIMEOUT (0x800705b4) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain domin.domain.com
 The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.domin.com
. The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:
172.22.1.2
172.22.1.1

. Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.
 For information about correcting this problem,  type in the command line:
hh tcpip.chm::/sag_DNS_tro_dcLocator_messageB.htm

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






Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1005
Date:            3/7/2008
Time:            11:56:49 AM
User:            N/A
Computer:      EX1
Description:
Unexpected error No authority could be contacted for authentication. ID no: 80090311 Microsoft Exchange System Attendant  occurred.

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




Event Type:      Information
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1004
Date:            3/7/2008
Time:            11:56:49 AM
User:            N/A
Computer:      EX1
Description:
Microsoft Exchange System Attendant failed to start.

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






Event Type:      Warning
Event Source:      MSExchange ADAccess
Event Category:      General
Event ID:      2601
Date:            3/7/2008
Time:            11:57:21 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1308). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=80040a01.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

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





Event Type:      Error
Event Source:      MSExchange ADAccess
Event Category:      General
Event ID:      2501
Date:            3/7/2008
Time:            11:57:21 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1308). The site monitor API was unable to verify the site name for this Exchange computer - Call=HrSearch Error code=80040a01. Make sure that Exchange server is correctly registered on the DNS server.

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




Event Type:      Warning
Event Source:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2116
Date:            3/7/2008
Time:            11:57:48 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1308). The domain controller dc3.domain.domain.com is running Windows 5.0 (2195) (Unknown Service Pack). Exchange Active Directory Provider requires that domain controllers are running Windows Server 2003 Service Pack 1 or later versions of Windows.

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







Event Type:      Information
Event Source:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2081
Date:            3/7/2008
Time:            11:57:48 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1308). Exchange Active Directory Provider will use the servers from the following list:
Domain Controllers:
dc1.domain.domain.com
dc2.domain.domain.com
 
Global Catalogs:
dc1.domain.domain.com
dc2.domain.domain.com
 
The Configuration Domain Controller is set to dc2.domain.domain.com.  

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





Event Type:      Information
Event Source:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2080
Date:            3/7/2008
Time:            11:57:48 AM
User:            N/A
Computer:      EX1
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1308). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
dc1.domain.domain.com      CDG 1 7 7 1 0 1 1 7 1
dc2.domain.domain.com      CDG 1 7 7 1 0 1 1 7 1
 Out-of-site:
dc3.domain.domain.com      CD- 1 6 6 0 0 1 1 6 0
 

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





Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      1121
Date:            3/7/2008
Time:            11:57:49 AM
User:            N/A
Computer:      EX1
Description:
Error 0x96f connecting to the Microsoft Active Directory.

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





Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      5000
Date:            3/7/2008
Time:            11:57:49 AM
User:            N/A
Computer:      EX1
Description:
Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f.

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









Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

All of those errors mean the same thing.

The server cannot connect to the domain controller.

Ensure that the DNS is configured correctly, only domain controllers should be listed.

Does the store start manually? If it does then the problem may be with the NIC or switch.

Simon.
Avatar of Bruce_S_C

ASKER

As far as i can see DNS is fine, what do you mean by "only domain controllers should be listed"?    The store and system attendant start manually.

What should i do to test from here?
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account

Hi,
Can you ping your domain controlers using the full FQDN
example: server1.local.contoso.com
Ping by full FQDN works, nsloopup is fine and even did a netdiag.


What should i be testing or looking at if it could be a spanning tree issue or any other possible issues
Do your primary and secondary dns are internal or do you have any external dns configured?
You have to look outside the server. Spanning tree has various names depending on the switch manufacturer.
Do make sure that you have the latest drivers for the NIC.

I don't think this is related to DNS at all, as the services start eventually. I think this has something to do with the initial speed or communication of the network.

Simon.
The other day a client.
Asked help to resolve some exchange server 2003 issues.
One of the problems that he was having was that information store didn´t start up, and when we clicked in the system manger a error appears saying that he could not contact any domain controller.

After verifying active directory I notice that the client configured in the alternate DNS a public dns server.
When I removed that dns server and let only the internal working everything started working thats why I asked that first question?
I found a separate issue that may be the cause of this


Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5719
Date:            3/10/2008
Time:            11:12:28 AM
User:            N/A
Computer:      EX1
Description:
This computer was not able to set up a secure session with a domain controller in domain <domain> due to the following:
There are currently no logon servers available to service the logon request.  
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    



Event Type:      Error
Event Source:      Kerberos
Event Category:      None
Event ID:      7
Date:            3/10/2008
Time:            11:12:34 AM
User:            N/A
Computer:      EX1
Description:
The kerberos subsystem encountered a PAC verification failure.  This indicates that the PAC from the client EX1$ in realm <domain>.COM had a PAC which failed to verify or was modified.  Contact your system administrator.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    

That would cause the problem. The server would fail to communicate with the domain if the secure channel cannot be created. Fixing it though isn't something I am sure of. It may mean the server has to be taken off the domain and put back in again, which if not done with care can damage Exchange.

Simon.
I gracefully removed exchange, reinstalled the OS and back to the netlogon error.
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
The problem was that spanningtree was enabled on the switch.
Spanning tree again... until TCP Chimney that was the most common reason for services not starting for me.

Simon.