Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5123
  • Last Modified:

Excuse the cross post. "Access denied attempting to launch a DCOM Server" also affecting Ex2k3. I think it's a Win 2k3 server problem

Win2k3 server.  Fully up to date.  Exchange 2003 Enterprise version because of large store (23gig)

Hi all.

For no good reason that I can determine this installation that’s been running ok for months suddenly stopped.  The information store is stopped and wont start because the System Attendant wont start.  I have all Exchange logging to max and the event viewer - apps log shows these two entries:

Microsoft Exchange System Attendant failed to start Exchange server 'MAILServer2'. Error code '0xc0070005'.

and

Unexpected error Access is denied. Facility: Win32 ID no: c0070005 Microsoft Exchange System Attendant  occurred.

also logged is this message which is odd because it is reported even when message tracking is off:

Unable to create the message tracking directory 'd:\'. Error 0xc0070005.

Contributing factors may be disk space (300mb) but the store has run and stopped / started ok with much less.  I have new server lined up and ready to move all the users to the new larger server but this happened just before I could do it.  Other contributing factors may be that when I added the new store to the site it all went well except that public folders were not replicated. Log examination shows that was due to permissions.  Trouble shooting the Public folder problem I added the machine accounts to each other server and gave full control. That fixed the public folder replication problem but then this happened an hour later.

In the sysem log are a lot of these:

Access denied attempting to launch a DCOM Server. The server is:
{9DA0E103-86CE-11D1-8699-00C04FB98036}
The user is SYSTEM/NT AUTHORITY, SID=S-1-5-18.

MS content redirect suggests various causes but this one:  http://support.microsoft.com/default.aspx?scid=kb;en-us;290398&sd=ee is the closest as the Server instance it wants to create is ExOLEDb, if you read through the fix there is the problem that the DCOM object ExOLEDb does not exist, nor can I create it.


I see a pattern emerging of permission problems.  I've trawled the MSKB but there is no one difinitive article that supports these symptoms.  I've tried quite a few of the similar fixes but to no avail.


Very much appreciate any assistance.
0
looops
Asked:
looops
1 Solution
 
What90Commented:
The disk where the message tracking logs are stored is either out of space, or the permissions on the directory or share are not correct.  The share should be SERVERNAME.log.  The "exchange enterprise servers" group, which contains each of the "Exchange domain servers" groups, which in turn contain all the machine accounts for the exchange servers in the domain, should have access to the share and directory.

1.  Make sure the machine account of your exchange server is a member of "Exchange domain servers".  You may want to remove it and add it back.

2.  Make sure there is space available on the drive hosting the share.

3.  Check the share permessions as well as file and folder permissions.

4.  Make sure another application, especial AV software, is not putting a lock on the files.

Otherwise have a look at the solution someone who had the same problems solved it by:
http://forums.msexchange.org/ultimatebb.cgi?ubb=get_topic;f=4;t=001375
0
 
looopsAuthor Commented:
\o/

Fixed.  Tracking log could not write to \\server\share because I moved the tracking log to save space.  I made a new directory and shared it and pointed tracking log there and bingo, all works.

Many thanks for the kick up the reminder What90  500 well earned :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now