Scenario is:
At the company with this problem - the exchange server mobo went down, and was a week+ in being replaced. In the meanwhile, they installed E2k3 on a new machine - giving it the same name, and restored a backup of the data - they were not able to get this going. Not sure why, but I do have a horrible feeling that at some point they did a setup.exe /removeorg and a re-isntall
Today the repaired server is back online - I have sorted out the problem caused by a new machine taking its name in AD (using NETDOM.exe).
And it boots up just fine, and is replicating with the GCS and other DCs happily.
However, MTA and also the Inf. Store are not starting.
The errors given are as below - I am listing all the events that are thrown - from start to end for each service.
On the startup of the inf. store you get two errors in the application log. These are:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9538
Date: 15/06/2005
Time: 12:45:50
User: N/A
Computer: EXCHANGE
Description:
Error 0xc004038a calling StrInitialize in REAPI.DLL.
For more information, click Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 5000
Date: 15/06/2005
Time: 12:45:50
User: N/A
Computer: EXCHANGE
Description:
Unable to initialize the Microsoft Exchange Information Store service. - Error 0xc004038a.
For more information, click
On the startup of MTA stacks you get:
Event Type: Information
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9095
Date: 15/06/2005
Time: 12:41:18
User: N/A
Computer: EXCHANGE
Description:
The MAD Monitoring thread is initializing.
For more information, click
Event Type: Information
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9096
Date: 15/06/2005
Time: 12:41:18
User: N/A
Computer: EXCHANGE
Description:
The MAD Monitoring thread is initialized.
For more information, click Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9098
Date: 15/06/2005
Time: 12:41:30
User: N/A
Computer: EXCHANGE
Description:
The MAD Monitoring thread was unable to read its configuration from the DS, error '0xc004038a'.
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2219
Date: 15/06/2005
Time: 12:41:50
User: N/A
Computer: EXCHANGE
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)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2206
Date: 15/06/2005
Time: 12:41:50
User: N/A
Computer: EXCHANGE
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)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2206
Date: 15/06/2005
Time: 12:42:11
User: N/A
Computer: EXCHANGE
Description:
The MTA database recovery operation is now checking queue: /O=SLINGCO/OU=FIRST ADMINISTRATIVE GROUP/CN=CONFIGURATION/CN=CONNECTIONS/CN=SMTP (EXCHANGE)/CN={FB2F22CB-1180-4FEE-8267-3F7A87F126AA}, the filename of this queue is: 0100002B. [DB Server MAIN BASE 1 29] (14)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2207
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
Description:
The MTA database recovery operation has completed successfully. Recovery details can be found in the file: D:\Program Files\Exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. [DB Server MAIN BASE 1 67] (14)
For more information, click Event Type: Error
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 9405
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
Description:
An unexpected error has occurred which may cause the MTA to terminate. Error: Init Routing API returned error -1073478774. [BASE MAIN BASE 1] (16)
For more information, click Event Type: Error
Event Source: MSExchangeMTA
Event Category: Directory Access
Event ID: 137
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
Description:
A fatal directory error occurred. Change to the maximum logging level for more details. [MTA MAIN BASE 1 12] (16)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Resource
Event ID: 9406
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
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)
For more information, click
Any help gratefully recieved.
Hollingside Technologies, Making Technology work for you.
(No, I am not scary at all! See
At the company with this problem - the exchange server mobo went down, and was a week+ in being replaced. In the meanwhile, they installed E2k3 on a new machine - giving it the same name, and restored a backup of the data - they were not able to get this going. Not sure why, but I do have a horrible feeling that at some point they did a setup.exe /removeorg and a re-isntall
Today the repaired server is back online - I have sorted out the problem caused by a new machine taking its name in AD (using NETDOM.exe).
And it boots up just fine, and is replicating with the GCS and other DCs happily.
However, MTA and also the Inf. Store are not starting.
The errors given are as below - I am listing all the events that are thrown - from start to end for each service.
On the startup of the inf. store you get two errors in the application log. These are:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9538
Date: 15/06/2005
Time: 12:45:50
User: N/A
Computer: EXCHANGE
Description:
Error 0xc004038a calling StrInitialize in REAPI.DLL.
For more information, click Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 5000
Date: 15/06/2005
Time: 12:45:50
User: N/A
Computer: EXCHANGE
Description:
Unable to initialize the Microsoft Exchange Information Store service. - Error 0xc004038a.
For more information, click
On the startup of MTA stacks you get:
Event Type: Information
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9095
Date: 15/06/2005
Time: 12:41:18
User: N/A
Computer: EXCHANGE
Description:
The MAD Monitoring thread is initializing.
For more information, click
Event Type: Information
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9096
Date: 15/06/2005
Time: 12:41:18
User: N/A
Computer: EXCHANGE
Description:
The MAD Monitoring thread is initialized.
For more information, click Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9098
Date: 15/06/2005
Time: 12:41:30
User: N/A
Computer: EXCHANGE
Description:
The MAD Monitoring thread was unable to read its configuration from the DS, error '0xc004038a'.
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2219
Date: 15/06/2005
Time: 12:41:50
User: N/A
Computer: EXCHANGE
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)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2206
Date: 15/06/2005
Time: 12:41:50
User: N/A
Computer: EXCHANGE
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)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2206
Date: 15/06/2005
Time: 12:42:11
User: N/A
Computer: EXCHANGE
Description:
The MTA database recovery operation is now checking queue: /O=SLINGCO/OU=FIRST ADMINISTRATIVE GROUP/CN=CONFIGURATION/CN=CONNECTIONS/CN=SMTP (EXCHANGE)/CN={FB2F22CB-1180-4FEE-8267-3F7A87F126AA}, the filename of this queue is: 0100002B. [DB Server MAIN BASE 1 29] (14)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 2207
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
Description:
The MTA database recovery operation has completed successfully. Recovery details can be found in the file: D:\Program Files\Exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. [DB Server MAIN BASE 1 67] (14)
For more information, click Event Type: Error
Event Source: MSExchangeMTA
Event Category: Field Engineering
Event ID: 9405
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
Description:
An unexpected error has occurred which may cause the MTA to terminate. Error: Init Routing API returned error -1073478774. [BASE MAIN BASE 1] (16)
For more information, click Event Type: Error
Event Source: MSExchangeMTA
Event Category: Directory Access
Event ID: 137
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
Description:
A fatal directory error occurred. Change to the maximum logging level for more details. [MTA MAIN BASE 1 12] (16)
For more information, click Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Resource
Event ID: 9406
Date: 15/06/2005
Time: 12:43:27
User: N/A
Computer: EXCHANGE
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)
For more information, click
Any help gratefully recieved.
Hollingside Technologies, Making Technology work for you.
(No, I am not scary at all! See