Information store

[GrimR]

Every time my server reboots the IS does not start, anyone know how to fix it?

 

[Tricky100]

the service set to start automatically?

 

[GrimR]

Yes, and cant see any IS error only The ones below. I have 2 AD servers both acting as GC servers.

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8365
Date: 21/01/2008
Time: 8:43:59 AM
User: N/A

Description:
Could not read the Security Descriptor from the Exchange Server object with guid=461BCCEF9EC35545A38FEEA199C55E17. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: MSExchangeSA
Event Category: NSPI Proxy
Event ID: 9057
Date: 21/01/2008
Time: 8:44:01 AM
User: N/A

Description:
NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service. New clients will be refused until a Global Catalog is available. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

[xmsre]

Wher is the GC? Is it reachable? Have you tried rebooting the GC?

 

[58sniper]

I see this a lot on servers that don't have enough RAM. The server essentially times out because it's overwhelmed.

Pat Richard
Microsoft Exchange MVP

 

[GrimR]

At the time I'm not sure if the GC's where able to be contacted as I had just turned all servers back on. I believe this is why the Microsoft Exchange System Attendant failed to start [this time].
But this has happened before where the IS failed to start even with the GC's up and running.

x64 Dell 2900 Server has 8GB RAM. RAID 1 and 5, Originally 1 terabyte HDD space, but it only runs exch2007.