Troubles when importing Exchange 2003 accounts

[gallycyborg]

Hello

I am studying the possibility of migrating a Exchange server towards a Zimbra server. The installation occurred very well, but when I try to import the accounts since Exchange (2003), the assistant of migration makes go up 1 warning by element of calendar to be imported (the importation of the emails and the address books occurs on the other hand well), then crash without message at the time of the last screen. The log lets appear those errors :

04-04-2007 12:35:27 [5972]: (MI): Adding Appoinment d(Mon, 2 Apr 2007 15:27:54 -0000) fid(010)
04-04-2007 12:35:28 [5972]: Exception Address: 0x44237a
04-04-2007 12:35:36 [5972]: CORE: Generated core dump: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\ZCSMigWiz-4.5.3_GA_731\ZimbraCore_04042007_123528.dmp
04-04-2007 12:35:36 [5972]: Unable to process message d(Mon, 2 Apr 2007 15:27:54 -0000) Folder Name - Calendar
04-04-2007 12:35:36 [5972]: (MI): The MAPI message was logged to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\ZCSMigWiz-4.5.3_GA_731\000000007f3c7ec9f5449541836d572db480c e140

I find indeed files “msg” containing information of calendar in the repertory of the log, one by element of calendar, accompanied by a file “dump” from 45 to 50 Mo by element (ZimbraCore_04042007_123528.dmp for example)
I specify that I checked the problems of CDOEX, the rights of access to the base,…, all that one finds in this wiki page speaking about an appreciably equivalent problem, exception and CORE DUMP in less: http://wiki.zimbra.com/index.php?tit...ooting#CDO EX
I also announce that the problem arises on 2 environments different servers, since I met it on a Windows 2000 server, and that there always exists in spite of a migration towards Windows 2003 server, and with exactly the same address of exception (tried if the COEX would not have been compatible, never knows one with cro$oft )

Here is, if somebody could guide me, that would arrange me, and prevent that we cancel the migration towards Zimbra (the calendars are fundamental)

Thank you in advance

[sam]

Open a case with support@zimbra.com and send us the logs + core file. We'll get you a patched version right away.

[gallycyborg]

I found a way to make migration working, funny way in fact :
During the migration process, by looking at the task manager, I realise that outlook was launched, but not visible on screen (It was installed to create the MAPI profile required by MigWiz). So I try to uninstall it, and then, miracle, the migration fully worked

So, for other people in the same case than me, install Outlook to create the MAPI profile, but uninstall it immediatly after, this **** "program" make MigWiz crashing

[manish]

Originally Posted by gallycyborg

I found a way to make migration working, funny way in fact :
During the migration process, by looking at the task manager, I realise that outlook was launched, but not visible on screen (It was installed to create the MAPI profile required by MigWiz). So I try to uninstall it, and then, miracle, the migration fully worked

So, for other people in the same case than me, install Outlook to create the MAPI profile, but uninstall it immediatly after, this **** "program" make MigWiz crashing

To create MAPI profile installing Outlook on the same machine having MS Exchange is not required. Follow the steps given in the following Microsoft support article to create MAPI profiles on the Exchange machine:
http://support.microsoft.com/kb/306962

Also, installing Outlook on Exchange is not recommended. http://support.microsoft.com/kb/266418

[manish]

To create MAPI profile installing Outlook on the same machine having MS Exchange is not required. Follow the steps given in the following Microsoft support article to create MAPI profiles on the Exchange machine:
http://support.microsoft.com/kb/306962

Also, installing Outlook on Exchange is not recommended. http://support.microsoft.com/kb/266418

[Uday]

Originally Posted by gallycyborg

I found a way to make migration working, funny way in fact :
During the migration process, by looking at the task manager, I realise that outlook was launched, but not visible on screen (It was installed to create the MAPI profile required by MigWiz). So I try to uninstall it, and then, miracle, the migration fully worked

So, for other people in the same case than me, install Outlook to create the MAPI profile, but uninstall it immediatly after, this **** "program" make MigWiz crashing

You need not install Outlook to create MAPI profile.
http://support.microsoft.com/kb/306962

Also you can create the MAPI profile while selecting one for migration with "New" button on "Choose Profile" Dialog box.

One more thing, Outlook and Exchange on the same machine is an unsupported combination. Microsoft warns that this should not be the configuration.

http://support.microsoft.com/kb/266418

[Uday]

Originally Posted by gallycyborg

I found a way to make migration working, funny way in fact :
During the migration process, by looking at the task manager, I realise that outlook was launched, but not visible on screen (It was installed to create the MAPI profile required by MigWiz). So I try to uninstall it, and then, miracle, the migration fully worked

So, for other people in the same case than me, install Outlook to create the MAPI profile, but uninstall it immediatly after, this **** "program" make MigWiz crashing

You need not install Outlook to create MAPI profile.
http://support.microsoft.com/kb/306962

You can create the MAPI profile while selecting the one for migration with "New" button on "Choose Profile" Dialog box.

Outlook and Exchange on the same machine is an unsupported combination. Microsoft warns that this should not be the configuration.

http://support.microsoft.com/kb/266418

[Uday]

You need not install Outlook to create MAPI profile.
http://support.microsoft.com/kb/306962

You can create the MAPI profile while selecting the one for migration with "New" button on "Choose Profile" Dialog box.

Outlook and Exchange on the same machine is an unsupported combination. Microsoft warns that this should not be the configuration.

http://support.microsoft.com/kb/266418

[manish]

You need not install Outlook to create MAPI profile.
http://support.microsoft.com/kb/306962

You can create the MAPI profile while selecting the one for migration with "New" button on "Choose Profile" Dialog box.

Outlook and Exchange on the same machine is an unsupported combination. Microsoft warns that this should not be the configuration.

http://support.microsoft.com/kb/266418

[gallycyborg]

Thanks for your answer, but I've got few other troubles :

When I try to launch MigWiz from another computer, I've got two kinds of errors : MigWiz ask that it's unable to create new MAPI profile, or, on a newly installed under Win2K computer, with all patchs applied, Outlook 2003 installed and patched, no antivirus, no firewall, any other program installed, when I want to validate the second screen of the MigWiz (the one where you enter the hostname, admin port, Username & password of the Zimbra server), I obtain a popup asking "unexpecting error". The log of MigWiz is nearly empty (only the first line with the version), there is non errors on the Zindozs event viewer : what can I do

For information, I obtain the same error on the production server, which is in fact an Exchange 5.5 running under Windows 2000 server (my society is unable to find back the CD of Exchange 5.5, so I had to made my test with an MSDN version of Exchange 2003, sorry for the difference )

Thanks you in advance for your help,
Simon

PS : the other solution for creating profiles you gave me made me a little bit paranoiac : running those kind of system script on a Windows server on production for years... I'm afraid in advance of what this "server" can do after those kind of manipulation

Originally Posted by manish

You need not install Outlook to create MAPI profile.
http://support.microsoft.com/kb/306962

You can create the MAPI profile while selecting the one for migration with "New" button on "Choose Profile" Dialog box.

Outlook and Exchange on the same machine is an unsupported combination. Microsoft warns that this should not be the configuration.

http://support.microsoft.com/kb/266418