Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange (SBS) Event ID 1005 MSexchSA 1

Status
Not open for further replies.

MarkRobinson

Programmer
Feb 18, 2000
112
US
Event log says
Event ID: 1005
Source MSExchangeSA
Type: Error
Category: Monitoring

Unexpected Error <<0xc00400000 - The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange SErver is down for maintenance. Microsoft Exchange SErver Information Store no: 8004011d-0526-00000000>> occured.

Server takes about 20 mins to start up, including when I start/stop services.
MS Exchange Administrator takes 10 mins to start up.

Removed the Internet E-Mail service... not even using POP3 and SMTP.

Have done the ISINTEG checks and others. Database seems fine Normally I would reinstall exchange but SBS won't let me.
Knowledgebase is no help.

Only event log error Previous to this is is an LDAP Error 10049. &quot;Make sure port 636 is not in use&quot;. It''s not. [sig][/sig]
 
This is common with Exchange 5.5, SP3 on a Win2K server when the MDBDATA folder is encrypted. See MS &quot;Q&quot; article Q233400. [sig][/sig]
 
Thanks... I've looked at the article... It DOES have the text of the message from the event log...
But I haven't done anything around encryption. The article doesn't indicate what to do about the problem. ANy Ideas.

ALso... how did you find this... I did a search for event 1005 and came up with nothing.

- Mark [sig][/sig]
 
I just searched for 1005 on the July 00 TechNet CD.

This message seems to occur any time the Information Store doesn't start within a predetermined time. I have seen it before when we had to &quot;pull the plug&quot; on an Exchange server, rather than doing a normal shutdown. So I would start looking at why it is taking so long for the Information Store to start. Look at the usual suspects: memory (both physical and virtual), disk fragmentation, CPU utilization, etc. Do you have multiple active NICs in this machine? Based on the response of Exchange Administrator, it sounds like you've got a resource bottleneck somewhere. Exchange Administrator should come up within a minute or so, unless you are connecting to a bunch of remote Exchange servers. [sig][/sig]
 
Sounds like some possibilities there.
Yes, I have 2 NICS, one connects to the hub and the other to a device called a WEBRAMP that is a router and a device that combines the bandwidth of several modems.
Plenty of memory,
I'll defrag (but it's a new installation... I doubt it).
No other exchange servers [sig][/sig]
 
The first thing I would do is to disable whichever of the 2 NICs is not absolutely essential for functionality. We have seen cases where the addition of a second functional NIC would, in and of itself, use up to 90% of the available CPU cycles. [sig][/sig]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top