Exchange not functioning after installing

[ArmedAndClueless]

I installed Exchange 2003 on a lab server a few days ago. It is is running Server 2003 Enterprise Ed. However, Exchange is pretty screwed up, and I don't know how to get it online. I get errors from LDAP in the system log, that look like such:

2/14/2006 6:47:44 AM LSASRV Warning SPNEGO (Negotiator) 40960 N/A SHATTERED1 "The Security System detected an authentication error for the server LDAP/Localhost. The failure code from authentication protocol Kerberos was ""There are currently no logon servers available to service the logon request.
(0xc000005e)""."

The application log is full of surprises, too. This one relateds to ExchangeDSAccess

2/13/2006 9:56:27 PM MSExchangeDSAccess Error Topology 2114 N/A SHATTERED1 "Process INETINFO.EXE (PID=516). Topology Discovery failed, error 0x80040952.

When I installed exchange, I got a ton of warnings like this:

2/13/2006 6:33:00 PM WinMgmt Warning None 5603 SHATTERED\Administrator SHATTERED1 A provider, ExchangeServerProvider, has been registered in the WMI namespace, root\MicrosoftExchangeV2, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.

Take that into account with beautiful warning:

2/13/2006 6:27:06 PM WinMgmt Warning None 47 N/A SHATTERED1 WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\mssindex\Performance\Library, error code: 0x80041009


I hope that was enough information to get this post somwhere. Can anyone make heads or tails of this?

 

[david817]

Have you done forest and domain prep first? Dave

 

[58sniper]

Could be a DNS issue. The server you're installing this on MUST be looking at the AD DNS and NOTHING ELSE. Verify that.
Event ID 40960:

http://eventid.net/display.asp?eventid=40960&eventno=787&source=LsaSrv&phase=1

Event ID 2114:

http://eventid.net/display.asp?eventid=2114&eventno=2458&source=MSExchangeDSAccess&phase=1

Event ID 5603:

http://eventid.net/display.asp?eventid=5603&source=

Event ID 47:

http://eventid.net/display.asp?eventid=47&eventno=665&source=WinMgmt&phase=1

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[Zelandakh]

Can Exchange see a DC and a GC?
Did you run forestprep and domainprep?
Have you got a DNS running?

 

[ArmedAndClueless]

That's the weird thing. I followed the Deployment instructions to the letter. I wound up throwing up my hands and reformatting, and installing some extra .Net things, then trying it again. That did the trick, in a fashion. I can connect to OWA, and a test email from the admin to itself worked. Hoever, during the install process I still got a ton of messages from WinMgmt, as noted earlier. Does anyknow know how that will effect my box?

And insofar as DNS, this is the DC, global catalog, operations manager, etc. etc. It has every role needed for a main AD server, and DNS is installed and was configured by the AD installer, so I kind of doubt it is the issue, unless I need to enter some manual entries.

 

[58sniper]

Just because the installer installed DNS doesn't mean it can't be the culprit. If you're getting that many errors, I'd be reloading the box. No reason to get those. But I still think it's a DNS issue.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)