Exchange Server Forums

Help: Ex5.5 -> Ex2k3 migration - Setup fails

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Migration >> Help: Ex5.5 -> Ex2k3 migration - Setup fails

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Help: Ex5.5 -> Ex2k3 migration - Setup fails - 6.Sep.2004 3:44:00 PM

zaffodb

Posts: 15
Joined: 27.Aug.2004
From: Greece
Status: offline

Hi all,

In our organization (say foo.bar.com) we have a recently upgraded our single NT4 domain (FOO) to Active Directory
running on Windows Server 2003 Enterprise Edition with two domain controllers (server names: DC-1, DC-2).

We also have Ex 5.5 on an NT4/SP6 server (MAIL) which was originally a member of the old NT4 domain but currently a member of the AD domain.
We wish to migrate the data to a new Exchange Server 2003 (Enterprise Edition) to be installed on a new server (ES-1), also running on Windows Server 2003 Enterprise Edition.
(NOTE: this is an interim server, since we wll finally use a cluster to host the production environment.)

We have (finally) succeded in using the ExDeploy tool to configure the New Exchange 2003 Server with Co-Existence with Exchange 5.5 up to the point of the actual Exchange Server 2003 setup.
This means that we successfully accomplished the following steps:
[Phase 1]
- Installed necessary services
- Run DSScopeScan / OrgNameCheck
- Installed Support Tools
- Run DCDiag, NetDiag and review the log files for errors
[Phase 2]
- Run ForestPrep and DomainPrep - designated an existing user (esadmin) for becoming Exchange Full Administrator in the new Exchange Server
- Run OrgPrepCheck and review the log files for errors
- Installed ADC, created Recipient and Public Folder CAs
- Proceeded with replication, which was completed (shown in Event Viewer, after turning on Minimal logging)
[Phase 3]
- Run SetupPrep and review the log files for errors

Last, we tried to run the ExDeploy tool again for running the Exchange Setup program, after having logged on as FOO\esadmin (Permissions have been set).
Unfortunately, the setup program fails when trying to connect to the Exchange 5.5 server after requesting its' name (MAIL).
The error message is:
"
Setup encountered an error while attempting to bind to the Exchange server MAIL: 0x8007052E (1326): Logon failure: unknown user name or bad password.
"

NOTES:

- "esadmin" is a new account created in the AD domain. It has NO associated mailbox in Exchange 5.5. It is a member of the following Domain groups:
Enterprise Admins
Schema Admins
Domain Admins (=> member of the Local Administrators group on every server)
although some of them should not be necessary, according to docs.

- "esadmin" cannot use the Exchange Administrator to administer/view data on Ex5.5 after a local logon, although it is a member of the Domain Admins group which has explicitly been given the same permissions as the Exchange Service account (FOO\ExchangeServer) at the Org/Site/Config levels:
-------------------------------------------------
Level / Role / Applied Rights (if non-standard)
-------------------------------------------------
Org / Custom / Add Child, Modify User Attributes, Modify Admin Attributes, Delete, Replication, Modify Permissions
Site / Service Account Admin / (standard)
Config / Service Account Admin / (standard)
-------------------------------------------------
The error (at connection time) is:
"
Network problems are preventing connection to the Microsoft Exchange server computer. Mapi was unable to load the information service emsabp.dll. Be sure the service is installed and configured.
"
In fact, the only account which succeeds in running the Exchange 5.5 Administrator program is FOO\ExchangeServer.
This account has become (during ForestPrep / DomainPrep?) a member of the "Exchange Domain Servers" and "Exchange Services" groups.

- Status of Exchange-related Services on MAIL:
-------------------------------------------------
Service Name/Status/Startup (A=Auto, M=Manual)
-------------------------------------------------
MS Exchange Connector for Lotus cc:Mail / - / M
MS Exchange Directory / Started / A
MS Exchange Directory Synchronization / - / M MS Exchange Event Service / Started / A
MS Exchange Information Store / Started / A
MS Exchange Internet Mail Service /Started / A
MS Exchange Message Transfer Agent / Started / A
MS Exchange System Attendant / Started / A
MS Mail Connector Interchange / - / M
MS Schedule+ Free/Busy Connector / - / M

- NO firewall or IPSec entries are applied to any of the servers mentioned above.

Any ideas?

TIA

-------------------------
Manos Anastasiadis
Systems Engineer