Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Exchange 2007 Server Information Store not mounting on reboot

Posted on 2009-02-16
7
Medium Priority
?
4,074 Views
Last Modified: 2012-05-06
We have a new Exchange 2007 server setup that we just migrated from SBS 2003. I'm getting some weird errors after just rebooting the server though : looks like it won't let the Information Store mount upon bootup, I have to manually start this service as well as MS System Attendant.
Here are the following error messages I get in the event log after a reboot : yes all of them in a row. A manually start of the services MSSA and the Information Store gets everything working fine, this only happens after a reboot.


Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1460). 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.

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1460). Exchange Active Directory Provider found SRV records for domain controllers in domain lle.local.
 The query was for the SRV record for _ldap._tcp.dc._msdcs.lle.local
 The following domain controllers were identified by the query:
llesrv00.lle.local
llesrv01.lle.local

Unexpected error No authority could be contacted for authentication. ID no: 80090311 Microsoft Exchange System Attendant  occurred.

Microsoft Exchange System Attendant failed to start.

Process utilCmdletWrapper.exe (EMS) (PID=2896). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.

Process MSEXCHANGEADTOPOLOGY (PID=1460). 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.

Error 0x96f connecting to the Microsoft Active Directory.

Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f.
0
Comment
Question by:danielevans83
  • 4
  • 3
7 Comments
 
LVL 65

Expert Comment

by:Mestha
ID: 23652637
The errors all mean the same thing.
The server is unable to contact the domain controller/s.

Are you pointing DNS at the domain controllers only?
Is Exchange installed on a domain controller?

If you run the Best Practises too from the toolbox, does that flag anything?

-M
0
 

Author Comment

by:danielevans83
ID: 23652669
Best Practices doesn't flag anything related to this. Exchange is not installed on a DC, we have two other Server 2003 boxes set up as DC's.
When you asked am I pointing DNS at the DC's only what did you mean? Both of the DC's are listed as NameServers in DNS yes.
Could it be because my external DNS for the Exchange (mail.xxx.com) is different than it's internal name (xxxsrv03.xxx.local) ? I do have one certificate mismatch error because of that.
0
 
LVL 65

Expert Comment

by:Mestha
ID: 23653333
Certificate mismatch wouldn't be the cause of the problem.
What I referred to for DNS was that the DNS servers on the network configuration are pointing to the domain controllers only.

-M
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 

Author Comment

by:danielevans83
ID: 23665456
That didn't help explain it any better. What settings are you talking about?
0
 
LVL 65

Accepted Solution

by:
Mestha earned 2000 total points
ID: 23666202
On your network card configuration, under TCP/IP you have to specific DNS servers. They should be domain controllers ONLY. No external DNS should be anywhere in the network configuration of the server.

-M
0
 

Author Comment

by:danielevans83
ID: 23666373
Oh I see. There were no external DNS IP's in the network card's TCP/IP settings. In fact only one of our DNS servers was configured and our WINS server wasn't listed either. I added both of those. Could this be happening if only one DNS server was listed? If so I find the one error odd that lists both DC's as unavailable.
The following domain controllers were identified by the query:
llesrv00.lle.local
llesrv01.lle.local
 
I'm not sure if it's relevant but the network card is configured with two IPs. We had to do this to resolve a certificate issue Outlook 2007 was prompting for internally. This was due to our internal DNS name for Exchange being different from the external one we purchased a cert for.
0
 

Author Comment

by:danielevans83
ID: 23666471
Wow okay, it looks like adding the secondary internal DNS and WINS server fixed the reboot problems. Sweet, thanks for pointing me there.
 
Can I have a moderator please X out my internal DNS names? Probably shouldn't have posted them.
Thanks for the help guys! Lookin' good!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
There can be many situations demanding the conversion of Outlook OST files to PST format and as such, there is no shortage of automated tools to perform this conversion. However, what makes Stellar OST to PST converter stand above the rest? Let us e…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses
Course of the Month20 days, 17 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question