Hi Sakti, basically this is a new Exchange 2K3 server in an existing 5.5 site. The 5.5 site contains only a single MSX 5.5 server with an Internet Mail Connector, Outlook Web Access front end server and thats really all. There are no other sites or servers in the organization.
The 2K3 MSX server is being setup in the site so mailboxes and public folders, etc.. can be moved from 5.5 to 2K3, and the 5.5 server eventually decomissioned. We have not yet put any mailboxes or IMC on the 2K3 server. Essentially we have checked the 5.5 directory for problems, checked the AD for problems, replicated stuff from 5.5 directory to Active Directory, installed Exchange 2K3 and have not been able to proceed from there due to issues with services on MSX 2K3 not starting up. We followed both the Wizard on the Exchange CD and also documentation from Microsoft regarding this type of procedure. IIS and etc all seem to start fine using the LocalSystem account on the server and as I recall the MSX virtual directories do show up in IIS. The server was setup just for this purpose with 9GB for the C: and about 36GB for the M:. The server does nothing else (except GC and other AD functions). So free space on the disk would not be an issue. Thanks again for your help with this issue. Regards, Luke > Luke, > > Can you tell us a bit more about your Exchange organisation? Is this a > new server you're building or an in-place upgrade? Is it supposed to be > talking to other Exchange servers? > > Are you seeing any messages queuing up, waiting to be routed? > > Is IIS working OK? I mean, do the services start, and do the Exchange > virtual directories show up? > > I think the final event you mentioned - 9406 - may be the key. Do you > have sufficient disk space? Perhaps you could try increasing the > pagefile size? Is the service running under the LocalSystem account? > > Sakti > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 5 May 2004 9:41 AM > To: Exchange Discussions > Subject: RE: Exchange 5.5 to 2k3 migration - MTA Stacks wont start > > > Hi, > thanks for your feedback on this issue. I had a look at the routing > group in Exchange Manager on the 2k3 server and both servers (5.5 and > 2k3) are in this group. With ADSIEdit, I used > http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;830828 as a > reference point for what to check and everything seemed to be in order > (note that the routing group was not deleted, but this seemed like a > good list of things to check anyway). > > So if the problem is not related to routing group membership (or at > least does not appear to be related to it) is there anything else you > can suggest? > > Thanks again for all your help. > Regards, > Luke Cassar > > > Luke, > >=20 > > I recall having a similar problem on 2000 years ago ... Chris seems to > > > have you on the right track, perhaps your server is not properly=20 > > configured as a Routing Group member? > >=20 > > Sakti > >=20 > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, 4 May 2004 12:10 PM > > To: Exchange Discussions > > Subject: RE: Exchange 5.5 to 2k3 migration - MTA Stacks wont start > >=20 > >=20 > > Hi Chris,=3D20 > >=20 > > Thanks for your help. Can you advise if it is not=20 > > msExchHomeRoutingGroup is not populated in the server proprieties. =20 > > What do we need to do to get it in the MTA? > >=20 > > Thanks in advance. > >=20 > > Luke > >=20 > >=20 > > -----Original Message----- > > From: Chris Scharff [mailto:[EMAIL PROTECTED] > > Sent: Sunday, 2 May 2004 2:18 AM > > To: Exchange Discussions > > Subject: RE: Exchange 5.5 to 2k3 migration - MTA Stacks wont start > >=20 > > OK, this is a WAG based on something I've recently seen with a=20 > > customer, but using ADSIEdit can you check and see if the=20 > > msExchHomeRoutingGroup attribute is populated for all of the servers?=20 > > (In ADSIEdit connect ot Configuration Naming context, services,=20 > > exchange , admin group, server <properties> I think...) > >=20 > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Posted At: Saturday, May 01, 2004 10:33 AM > > Posted To: swynk > > Conversation: Exchange 5.5 to 2k3 migration - MTA Stacks wont start > > Subject: Exchange 5.5 to 2k3 migration - MTA Stacks wont start > >=20 > > Ok, we ended up removing the exchange 2k3 install, fixing up the=20 > > domain owner issue by siezing the role holder for the Domain Naming=20 > > Operations master to a server that actually exists, re-ran all of the=20 > > ADC/AD tools to make sure everything was in order, and then=20 > > re-installed Exchange 2k3. > >=20 > > This time, all of the services would start as per normal EXCEPT for=20 > > the MTA stacks.. these will not start. I have already done some fairly > > > intensive looking about on the web (both knowledgebase AND google.com) > > > only to find that this issue is not particularly common. > >=20 > > Basically cranked up the MTA logging to full blast and started the=20 > > service, the following was logged: > >=20 > > Start Service > >=20 > > Event ID: 2219 - MTA running recovery on internal message database due > > > to MTA not shutting down cleanly > >=20 > > Event ID: 2206 - MTA database recovery option is now checking=20 > > queue:(queuename). > >=20 > > Event ID: 2167 - Bunch of notices about cleaning up the queues and=20 > > re-assigning things to them, informational only > >=20 > > Event ID: 2207 - MTA Recovery operation completed sucessfully. Points=20 > > to a log file, the named file contains no errors. > >=20 > > Event ID: 9405 - Unexpected error has occured which may cause MTA to=20 > > terminate. Error: Init Routing API returned error - 1073478776 > >=20 > > Event ID: 137 - Fatal directory error occured. > >=20 > > Event ID: 9406 - Not enough performance monitor memory to display the=20 > > MTA connections info. Stop attached performance monitors and restart=20 > > MTA > >=20 > > Service is stopped at this point. > >=20 > > Only found one other forum where a person had the same issue but it=20 > > was unresolved. Can anyone provide some clues as to what this might=20 > > indicate. We re-installed MSX cleanly into new directories and stuff,=20 > > so its not left over files (that I would know of anyway). > >=20 > > Cheers and thanks for all of your feedback with the recent questions=20 > > about MSX, Luke > >=20 > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Web Interface:=20 > > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=3D3Dexchange&text_m= > o > > de=3D3D=3D > > & > > lang=3D3Denglish > > To unsubscribe send a blank email to > > %%email.unsub%% > > Exchange List admin: [EMAIL PROTECTED] > > To unsubscribe via postal mail, please contact us at: Jupitermedia > Corp. > > Attn: Discussion List Management > > 475 Park Avenue South > > New York, NY 10016 > >=20 > > Please include the email address which you have been contacted with. > >=20 > >=20 > >=20 > >=20 > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Web Interface:=20 > > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=3D3Dexchange&text_m= > o > > de=3D3D=3D > > & > > lang=3D3Denglish > >=20 > > To unsubscribe send a blank email to > > %%email.unsub%% > > Exchange List admin: [EMAIL PROTECTED] > > To unsubscribe via postal mail, please contact us at: Jupitermedia=20 > > Corp. > > Attn: Discussion List Management > > 475 Park Avenue South > > New York, NY 10016 > >=20 > > Please include the email address which you have been contacted with. > >=20 > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Web Interface:=20 > > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=3D3Dexchange&text_m= > o > > de=3D3D=3D > > & > > lang=3D3Denglish > > To unsubscribe send a blank email to > > %%email.unsub%% > > Exchange List admin: [EMAIL PROTECTED] > > To unsubscribe via postal mail, please contact us at: Jupitermedia > Corp. > > Attn: Discussion List Management > > 475 Park Avenue South > > New York, NY 10016 > >=20 > > Please include the email address which you have been contacted with. > >=20 > > ********************************************************************** > > This message is intended for the addressee named and may contain=20 > > privileged information or confidential information or both. If you are > > > not the intended recipient please delete it and notify the sender. > > ********************************************************************** > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=3Dexchange&text_mode=3D= > & > lang=3Denglish > To unsubscribe send a blank email to > %%email.unsub%% > Exchange List admin: [EMAIL PROTECTED] > To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. > Attn: Discussion List Management > 475 Park Avenue South > New York, NY 10016 > > Please include the email address which you have been contacted with. > > ********************************************************************** > This message is intended for the addressee named and may contain > privileged information or confidential information or both. If you > are not the intended recipient please delete it and notify the sender. > ********************************************************************** _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
