Restarting Exchange

I did restart the server, no luck
Event logs are difficult to interpret... I'll check again.
OWA does not function.
I'm plugged up inside the corporate network, and no luck.

How are they difficult to interpret?  I don't understand that.

The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

The Exchange system manager says under tool>status>{servername} First Administrative Maintenance Group, In maintenance mode.

I assume that this is the problem, so where should i start next?

Thanks,
jpertchik

Please post a screen shot of the Exchange System Manager with the error.

herre is the requested error message

System manager Screen shot

Here is the screen tht says Exchnge is in maintenence mode

does this help?

> The Exchange system manager says under tool>status>{servername} First Administrative Maintenance Group, In maintenance mode.
Please post a screen shot of this.

That's not a problem - see:
http://hellomate.typepad.com/exchange/2004/03/exchange_in_mai.html

Were those the ONLY event log errors you found in both the Application and System logs?  Any warning messages?  How large is your information store?

it would not mount.

the smallest partition we have has 232GB remaining on it.

i don't know how large my store is or where it is. i inherited this network from the other guy and i have almost no experience with exchange

OK...you need to delve into the event log to tell us more.

Post those logs and we'll tell you what to do next.

Information Store (12160) First Storage Group: The database engine is rejecting update operations due to low free disk space on the log disk.

How much do you know about Exchange?  Suggest you get yourself on a crash course in Exchange.

The following problem occurred with the Jet database -1032:  Jet database read or write operations failed. If the computer  or database has just been upgraded, then this message can be  safely ignored. If this message appears frequently, either there  is not enough disk space to complete the operation or the database  or backup database may be corrupt.  To correct this problem,  either free additional space on your hard disk or restore the  database. After you restore the database, ensure that conflict  detection is enabled in DHCP server properties. For information  about restoring the database, see Help and Support Center.  Additional Debug Information: JetBackup.

This one is a system error. note that it refers to not enough disk space.

Please see this picture.

If your employer is going to place you in charge of this and NOT provide training SOON, you need to hire a consultant.  

this is from application errors

The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

For more information, click http://www.microsoft.com/contentredirect.asp.

Error initializing session for virtual machine ATI00830. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running.

For more information, click http://www.microsoft.com/contentredirect.asp.

Error Log disk full starting Storage Group /DC=com/DC=adaptivetechinc/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=ATI/CN=Administrative Groups/CN=First Administrative Group/CN=Servers/CN=ATI00830/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

For more information, click http://www.microsoft.com/contentredirect.asp.

looks like my error log disk is full. where is the default location of this?

it think this is the one:

Information Store (12160) First Storage Group: An attempt to write to the file "C:\Data\Exchange\mdbdata\res2.log" at offset 1048576 (0x0000000000100000) for 1048576 (0x00100000) bytes failed after 0 seconds with system error 112 (0x00000070): "There is not enough space on the disk. ".  The write operation will fail with error -1808 (0xfffff8f0).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

For more information, click http://www.microsoft.com/contentredirect.asp.

Right click the properties of the First Storage Group (though it should be pretty obvious - if you look in My Computer, which disk is out of space?)

To clean off space on the C: drive, please see:

http://www.lwcomputing.com/tips/static/bootdrivesize.asp

In addition, the Exchange files need to be moved to another drive (see the link above).

Just looking at your previous post...I'm guessing your log drive is C:\Data\Exchange\mdbdata.

Start there and see my last post.

we have a guy who handles this, but he is going into a diffferent area of the biz and has left it to me. the problem is although he has guided me through much stuff, he is currently not reqachable

i had to go to the bathroom.. i'm now moving some big directories to another drive. i'll try mounting again

if moving the files solves the problem temporarily, .on monday, i'll move the exchange db using your method

go into your logs drive and move the oldest log files (they should begin edb?????.log) to another drive.  Exchange will then restart but I cannot emphasise this enough - TAKE A COMPLETE EXCHANGE BACKUP AS YOUR SYSTEM IS AT RISK

That doesn't seem wise - won't your staff be in on Monday?  Moving the folders will disrupt the users.  Move it today and your disruption is minimal.