Re: MTA and IS services will not start till the following day
- From: "Tom Felts" <tfelts@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Mar 2006 13:07:01 -0500
MOre than likely the exchange services are trying to start before the
Directory service is ready....set the exchange services to manual, and then
start them after the Dir Svcs start. Also, make sure your DC is a GC....see
the following for reasons why Exchange on a Domain controller is not the
best idea...
http://www.petri.co.il/problems_with_exchange_2003_installed_on_domain_controllers.htm
http://hellomate.typepad.com/exchange/2004/02/exchange_on_a_d.html
<NigelWKing@xxxxxxxxxxxxxx> wrote in message
news:1143633461.568120.65970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi I have a Win2000 Domain with Exchange2000. I am trying to repalce
the server with a New Win2003 R2 server with Exchange2003. at the
moment I have both severs running on the doamin, both are domain
controllers, the FSMO roles moved to the new Win2003 server. all the
data is still in the Exchange2000.
The problem I have is when I bootup the new Win2003 server the
Exchange2003 info store and MTA stack sevices will not start. If I
leave the server running over night, the services start up successfully
the next morning. When I shut down and restart the server, once again I
cannot start the services will not startup till the next morning.
Can anybody shed some light on what is going on here. Thank you for for
help in advance
Nigel
system events
29/03/2006 12:13:02 Service Control Manager 7035
The Microsoft Exchange MTA Stacks service was successfully sent a start
control.
29/03/2006 12:14:09 Service Control Manager 7036
The Microsoft Exchange MTA Stacks service entered the stopped state.
29/03/2006 12:14:13 Service Control Manager 7035
The Microsoft Exchange Information Store service was successfully sent
a start control.
29/03/2006 12:14:20 Service Control Manager 7036
The Microsoft Exchange Information Store service entered the stopped
state.
29/03/2006 12:14:20 Service Control Manager 7024
The Microsoft Exchange Information Store service terminated with
service-specific error 0 (0x0).
Application events
29/03/2006 12:08:44 MSExchangeSA 9153
"Microsoft Exchange System Attendant reported an error '0xc0072030'
when setting DS notification
29/03/2006 12:09:05 MSExchangeSA RFR Interface 9070
"The Directory Service Referral interface (RFRI) started successfully.
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 9409
"The Microsoft MTA registry parameter Max RPC Alloc Size is missing.
The default value will be used. [BASE MAIN BASE 1] (14)
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 2219
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)
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 2206
"The MTA database recovery operation is now checking queue: XAPIWRKQ,
the filename of this queue is: 01000020. [DB Server MAIN BASE 1 29]
(14)
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 2206
"The MTA database recovery operation is now checking queue: OOFINFOQ,
the filename of this queue is: 01000025. [DB Server MAIN BASE 1 29]
(14)
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 2206
"The MTA database recovery operation is now checking queue: REFDATQ,
the filename of this queue is: 01000026. [DB Server MAIN BASE 1 29]
(14)
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 2206
"The MTA database recovery operation is now checking queue: MTAWORKQ,
the filename of this queue is: 01000027. [DB Server MAIN BASE 1 29]
(14)
29/03/2006 12:09:05 MSExchangeMTA Field Engineering 2206
"The MTA database recovery operation is now checking queue:
/O=PORTAL/OU=FIRST ADMINISTRATIVE
GROUP/CN=CONFIGURATION/CN=CONNECTIONS/CN=SMTP
(EXCHANGE2K3)/CN={E9812E87-291A-49B4-A73C-2AA81B011935}, the filename
of this queue is: 01000029. [DB Server MAIN BASE 1 29] (14)
29/03/2006 12:09:06 MSExchangeMTA Field Engineering 2207
"The MTA database recovery operation has completed successfully.
Recovery details can be found in the file: C:\Program
Files\Exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. [DB Server MAIN
BASE 1 67] (14)
29/03/2006 12:09:42 LoadPerf
1001
Performance counters for the WmiApRpl (WmiApRpl) service were removed
successfully. The Record Data contains the new values of the system
Last Counter and Last Help registry entries.
29/03/2006 12:09:42 LoadPerf
1000
Performance counters for the WmiApRpl (WmiApRpl) service were loaded
successfully. The Record Data contains the new index values assigned to
this service.
29/03/2006 12:10:42 MSExchangeFBPublish 8213
"System Attendant Service failed to create session for virtual machine
EXCHANGE2K3. The error number is 0xc0072030.
29/03/2006 12:12:06 MSExchangeMTA Configuration 125
"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)
29/03/2006 12:12:06 MSExchangeMTA Resource 9406
"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)
29/03/2006 12:12:11 MSExchangeIS General 1121
"Error 0x80004005 connecting to the Microsoft Active Directory.
29/03/2006 12:12:11 MSExchangeIS General 5000
"Unable to initialize the Microsoft Exchange Information Store service.
- Error 0x80004005.
29/03/2006 12:12:12 MSExchangeMTA
9996
he description for Event ID ( 9996 ) in Source ( MSExchangeMTA ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: ExitProcess called in file:
f:\tisp2\mta\src\emsmta\sysglue\sbnilnt.c, line: 2784.
29/03/2006 12:12:16 MSExchangeMU General 1040
"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.
29/03/2006 12:12:17 SceCli Information 1704
Security policy in the Group policy objects has been applied
successfully.
29/03/2006 12:12:39 LoadPerf Information
1001
Performance counters for the WmiApRpl (WmiApRpl) service were removed
successfully. The Record Data contains the new values of the system
Last Counter and Last Help registry entries.
29/03/2006 12:12:40 LoadPerf Information 1000
Performance counters for the WmiApRpl (WmiApRpl) service were loaded
successfully. The Record Data contains the new index values assigned to
this service.
29/03/2006 12:13:02 MSExchangeMTA Field Engineering
"The Microsoft MTA registry parameter Max RPC Alloc Size is missing.
The default value will be used. [BASE MAIN BASE 1] (14)
.
- References:
- MTA and IS services will not start till the following day
- From: NigelWKing
- MTA and IS services will not start till the following day
- Prev by Date: IMS keeps shutting down ever 22min
- Next by Date: TWO outbound SMTP smarthosts?
- Previous by thread: MTA and IS services will not start till the following day
- Next by thread: activesync troubleshooting?
- Index(es):
Relevant Pages
|