So your E2k server still sees an IMS that doesn't exist. I seem to remember doing something similar in a test lab, but fortunately I did a simple reinstall. I'm not sure of the ramifications of deleting the connector using, say, ADSIEdit, so maybe a call to PSS is in order here to get the official word.
Neil -----Original Message----- From: Ryan Gorman [mailto:[EMAIL PROTECTED]] Posted At: 13 June 2002 17:25 Posted To: Sunbelt Exchange List Conversation: Deleting Legacy Connection / Event ID 929 Subject: RE: Deleting Legacy Connection / Event ID 929 Your assessment matches mine. During the migration Internet mail went to the IMS on the 5.5 server until most to the users were on the E2K server. We then changed the E2K virtual SMTP connector (to point outwards) and changed the firewall to direct incoming mail to the E2K server. The 5.5 server was re-installed from scratch - not an in-place upgrade. So the question remains - how do I remove references to a server and connector that no longer exist (without wrecking the working system) -----Original Message----- From: Neil Hobson [mailto:[EMAIL PROTECTED]] After a brief look, it looks like the E2k server is trying to reference an IMS on the 5.5 server, which leads me to the quesiton of how did you handle the Internet email during your migration? How did you reinstall the 5.5 server with E2k? Was it an upgrade? Neil -----Original Message----- From: Ryan Gorman [mailto:[EMAIL PROTECTED]] Environment: Windows 2000 Advanced Server SP2 and Exchange 2000 Enterprise Server SP2 I have an Exchange system that was migrated from Exchange 5.5 to Exchange 2000. The upgrade method was as follows 1. Upgrade NT4 domain to W2K AD 2. Install a temporary E2K server 3. Setup an Active Direcorty Connector (ADC) 4. Move the 5.5 mailboxes to the E2K server 5. Re-install the 5.5 server with E2K (keeping the same name) 6. Move the mailboxes back from the temporary E2K server to the new server. 7. Move all first server roles from the temporary server to the new server 8. Wait a week 9. Re-check first server roles then remove the temporary server. The server has settled in but fills the application event log with the following message. Event Type: Error Event Source: MSExchangeTransport Event Category: Routing Engine/Service Event ID: 929 Date: 22/05/2002 Time: 07:50:14 User: N/A Computer: RIDDLER Description: Failed in reading Connector's DS Info Process Id: 1224 Process location: x:\x\inetsrv\inetinfo.exe ConnectorDN: CN=Internet Mail Service (PENGUIN),CN=Connections,CN=BELFRY,CN=Routing Groups,CN=BELFRY,CN=Administrative Groups,CN=BATT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=com Hr:80040920 Attribute:[] ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm ************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. Any view or opinions presented are solely those of the author and do not necessarily represent those of Silversands, or any of its subsidiary companies. If you have received this email in error, please contact our Support Desk immediately on 01202-360360 or email [EMAIL PROTECTED] ************************************************* List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
