Re: Repost on Startup Errors

From: Jason Kontkanen (trash_at_ipdas.com)
Date: 03/24/05


Date: Thu, 24 Mar 2005 14:32:00 -0500

Thanks, I appreciate the pointer a lot. This took care of one part. Now
the Information Store and MTA Stacks aren't starting. I apologize for being
a pain, but this is my first Exchange 2003 install. Now, the first error I
get is:
Event ID: 9153
User: N/A
Computer: server
Description:
Microsoft Exchange System Attendant reported an error '0xc0072030' when
setting DS notification.

I go to "more information", but that doesn't provide any help. It mentions
Exchange 5.5, which we are still running, but it says this happens where the
old 5.5 server was improperly removed. The server is still running. We're
single-server, only one exchange server, so I'm doing the 2003 install while
we still have a working mail server. The previous exchange 2003 install on
this server went bad, so it was reinstalled. Would that also cause the
problem?

Also, the following errors and warnings then come up, I'm guessing possibly
because of the above error:
Event ID: 2219
Description:
The MTA is running recovery on the internal message database because the MTA
was not shut down cleanly. This operation may take some time. Status
updates will be written to the Windows 2000 Event Log. [DB Server MAIN BASE
1 0] (14)
Event ID: 2206
Description:
The MTA database recovery operation is now checking queue: XAPIWRKQ, the
filename of this queue is: 01000020. [DB Server MAIN BASE 1 29] (14)
(this one repeats for a couple queues)
Event ID: 125
Description:
A fatal error occurred reading a value from the directory. No MTA name was
found. Contact Microsoft Technical Support. [MTA MAIN BASE 1 12] (16)
Event ID: 9406
Description:
There is not enough Performance Monitor memory to display the MTA
Connections information. Stop attached Performance Monitors and re-start
the MTA. [BASE MAIN BASE 1] (14)
Event ID: 1121
Description:
Error 0x8004010f connecting to the Microsoft Active Directory.
Event ID: 5000
Description:
Unable to initialize the Microsoft Exchange Information Store service. -
Error 0x8004010f.
Event ID: 1040
Description:
Metabase Update failed replication 5 times with error 80070490 (Element not
found.). Please change the diagnostic logging level of MSExchangeMU to
'minimum' or greater to find the source of the problem.
Description:
The MAD Monitoring thread was unable to read its configuration from the DS,
error '0xc004038a'.

Again, sorry for being a pain here
Thanks for any more pointers.

"Tom Felts" <tfelts@mckennalong.com> wrote in message
news:OaK$GnjLFHA.3420@tk2msftngp13.phx.gbl...
> You can use this KB article to troubleshoot the DSAccess errors....
>
> http://support.microsoft.com/kb/316300/EN-US/
>
>
> "Jason Kontkanen" <trash@ipdas.com> wrote in message
> news:Of2bAcjLFHA.576@TK2MSFTNGP15.phx.gbl...
>>I already posted this, but there was no response. Again, the environment
>>is:
>> Operating in a Windows 2000 domain
>> The Exchange Server is Windows 2003 running Exchange 2003.
>>
>> I get the following errors when Exchange starts:
>>
>> Process INETINFO.EXE Topology Discovery failed, error 0x80040a02.
>>
>> Metabase Update failed to read the Configuration namespace property from
>> the domain controller. Error code is 80040a01.
>>
>> Unexpected error Access denied. Facility: LDAP Provider ID no: 80070005
>> Microsoft Exchange System Attendant occurred.
>>
>> Microsoft Exchange System Attendant failed to start Exchange server
>> 'SERVER'. Error code '0x80070005'.
>> Process MAD.EXE (PID=1724). Topology Discovery failed, error 0x80040a02.
>>
>> Process MAD.EXE (PID=1724). All Domain Controller Servers in use are not
>> responding:
>> domaincontroller.office.domain.com
>>
>> I searched for all these, and there was no help. Can anyone give me some
>> pointers here? I'd rather not stick to an older (but working) version of
>> Exchange.
>>
>>
>
>



Relevant Pages

  • Re: Error c1041724 SBS 2000
    ... Exchange Domain Server: Full ... I have tried to disable McAfee antivirus and then restart information store ... service and tried to mount database. ... Attemting to start the Microsoft Exchange Information Store "First Storage ...
    (microsoft.public.windows.server.sbs)
  • Re: big problem after applying critial updates remotely
    ... Can you go into services and manually start any stopped Exchange service? ... > My policy was to apply critical updates to my test setup ... > The Microsoft Exchange Server computer is not available. ... > Microsoft Exchange Server Information Store ...
    (microsoft.public.windows.server.sbs)
  • Re: Repost on Startup Errors
    ... but this is my first Exchange 2003 install. ... old 5.5 server was improperly removed. ... The MTA is running recovery on the internal message database because the MTA ... Unable to initialize the Microsoft Exchange Information Store service. ...
    (microsoft.public.exchange.setup)
  • Re: Repost on Startup Errors
    ... but this is my first Exchange 2003 install. ... old 5.5 server was improperly removed. ... The MTA is running recovery on the internal message database because the MTA ... Unable to initialize the Microsoft Exchange Information Store service. ...
    (microsoft.public.exchange.admin)
  • Re: Transaction Log Growth in Exchange Server 2003
    ... that had been looping for months...finally discovered that by manually ... one Exchange 2003 Server on ... I moved old mailboxes into a different information store on another ...
    (microsoft.public.exchange.admin)

Loading