Coexistence Exchange 2003 and Exchange 2007
Currently we are on final phase of implementing Exchange 2007. Only 1 Exchange 2003 (Back End) server left. Last week, we had create New Send Connector so that all outboud mail will thorugh Exchange Hub Transport not Exchange 2003. Testing run fine so we decide to shutdown temporary Exchange 2003 for confirmation. After 3 days, we reboots it back and we unable to start MSExchange IS, MS ExChange MTA. Look at Event viewer there are log found: Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 5000 Date: 3/16/2010 Time: 4:04:03 PM User: N/A Computer: MERCURY Description: Unable to initialize the Microsoft Exchange Information Store service. - Error 0x8004010f. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 1121 Date: 3/16/2010 Time: 4:04:03 PM User: N/A Computer: MERCURY Description: Error 0x8004010f connecting to the Microsoft Active Directory. For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: ErrorEvent Source: MSExchangeMTAEvent Category: Directory Access Event ID: 137Date: 3/16/2010Time: 4:03:28 PMUser: N/AComputer: MERCURYDescription:A fatal directory error occurred. Change to the maximum logging level for more details. [MTA MAIN BASE 1 12] (16) For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Error Event Source: MSExchangeMTA Event Category: Field Engineering Event ID: 9405 Date: 3/16/2010 Time: 4:03:28 PM User: N/A Computer: MERCURY Description: An unexpected error has occurred which may cause the MTA to terminate. Error: Init Routing API returned error -1073478776. [BASE MAIN BASE 1] (16) For more information, click http://www.microsoft.com/contentredirect.asp. I had been googling for whole day but haven't found the solution. I had try based on links:http://support.microsoft.com/kb/285116http://technet.microsoft.com/en-gb/library/bb266900(EXCHG.80).aspxhttp://support.microsoft.com/kb/305392On Exchange 2003, there is no more mailbox available, all mailbox had been transfered to Exchange 2007, same to public folder. We should like to start MSExchange services before running demotion.Please help
March 16th, 2010 11:35am

The event IDs are very generic ones. Run Exbpa and see what exactly that comes up with. Also incresed the diagnostics loggin on the exchange 2003 server on AD and MTA components and then try to start the services.Also try to shut down the E2k3 box, reboot the GC in the AD site and then reboot the E2K3 again and see if that makes any difference.Raj
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2010 11:45am

Step 1 Result from Exbpa: "Header","Severity","Title","Group Type","Group Name","Description","More Info Link" ": Active Directory Forest","Error","Unknown schema extension version","","Active Directory Forest","The Exchange schema extensions are from an unknown version. Schema version detected is 14622.","http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.2&id=01bd7110-617f-498b-b2d4-87eb55b199b3" ": Active Directory Sites","Error","'MaxPageSize' is set too high","","Active Directory Sites","The maximum LDAP page size for the default query policy is set too high and may cause performance problems. The default of 1000 is recommended. Current value: 50000.","http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.2&id=ef05b737-0a94-49ab-8deb-5acf91865531" "Routing Group: ContosoHQ","Error","Cannot connect to port 691 of the routing group master","Routing Group","ContosoHQ","Server MERCURY is a routing group master but a connection to port 691 cannot be established from the workstation where this tool is running.","http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.2&id=b79d83a3-76d0-4fae-8373-281a2479717a" "Server: MERCURY","Error","RegTrace is enabled","Server","MERCURY","RegTrace is currently enabled on server mercury.Contoso.com. This should be enabled only when troubleshooting problems.","http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.2&id=90b3eb47-ad77-4ae4-87b0-8d8ac5b575fb" Step 2 Diagnostic logging MS Exchange MTA : all categories set to Maxi Ms Exchange IS : MTA = Max IS/AD sync: Max Shutdown the Exchange 2003 and restart GCs After GCs restarted Reboot the Exchange 2003 Then try to restart MXExchange services, still failed, same event logged. Actually we have 5 GCs in AD Site with Exchange 2003, 3 of them running on Windows Server 2008 while the rest running on Windows Server 2003. I restarted the GCs (Win2k3) due to its appear in Exchange 2003's DSAccess tab Please advice
March 16th, 2010 1:30pm

run a DCDIAG and NETDIAG from the exchange and see the report.Looks like some issue with AD.Raj
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2010 2:06pm

I read an article saying that there was an issue if deleted default email policy due to Exchange 2003 using SMTP and X400 while Exchange 2007 only using SMTP to send an emails. Previously, there was an issue related to email policy in this coexistance enviroment. So, we decided to delete the default email policy and then recreate it using EMC(Exchange 2007). At that time, this problem not occur due we are not shutdown the Exchange 2003 server.I forgot the link of that article but could you provide me the instruction how to add back X400 address to recreated default email policy. This may help tp solve the problem.Thank
March 18th, 2010 4:09am

HiSure you are right, the issue maybe caused by the default Email Address Policy (EAP, a.k.a. recipient policy) has been modified or missed the X400 address type and the policy order was changed.You could solved it by 1. Added the X400 address type back to the default EAP. 2. Set the policy order of default EAP to 2147483647 (lowest).The detail procedures:1. Install Windows 2003 Support Tools from your Windows 2003 CD in case you haven't installed it. 2. Click Start->Run, type "adsiedit.msc" without quotes and then click OK. 3. Browse to the following location:CN=Default Policy,CN=Recipient Policies,CN=Headquarters,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=paclib,DC=com4. Right-click CN=Default Policy and then click Properties. 5. Locate the msExchPolicyOrder attribute and set the value to 2147483647.6. Locate the gatewayProxy attribute and add the following entry:X400:c=US;a= ;p=YOURHeadquarters;o=Exchange;7. Click OK. Regards!gavin
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2010 5:50am

Thank you Gavin-Zhang! That worked for me.
January 28th, 2011 3:00am

Have the same issue, the above is configured exactlly in my organization. Still cannot start the Information store 2147483647. any ideas ?
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2011 9:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics