Features | Product Literature | System Requirements | Technical Support
MigratePro Support: Known Issues
The latest version of MigratePro is 1.0.4. All problems and issues reported for prior versions have been resolved and corrected.Software Pursuits makes every effort to resolve any issues with MigratePro as quickly as possible. Because we know that fixes can not always be instantaneous, we always keep our users informed of any known problems or issues with MigratePro that we are working to fix for our next release. For additional information on our release policy click here.
We send an e-mail notification to users when a critical error is found or when a significant version change is released. (You gave us your e-mail address when you downloaded MigratePro. If you suspect that we do not have your current email address, please contact our support staff.) We will not release your address to other companies. Please see our Privacy policy.
Below is our current list of known issues for all versions of MigratePro. Unless otherwise indicated, the problems listed for each earlier version were fixed in the later versions. Patches are generally not provided for prior versions, but upgrading to the latest version is even easier than applying a patch.
You can determine your MigratePro version by accessing Help, About when running any of the MigratePro programs.
|
Back to prior page
Known Issues in All Versions
This section has known issues that cross versions, such as conflicts with other software products or system requirements.
Required Microsoft Components
MigratePro requires MDAC 2.8, Jet SP8, .NET Framework 2.0, and Windows Installer 3.0 or newer versions of each. The installer will check to see if your system meets these requirements. If it does not it will offer to install them for you.
Zip Magic
If you are using ZipMagic to handle your zip files and are allowing ZipMagic to display zip files as folders, MigratePro will be unable to copy those files. If you turn off ZipFolders then the files will copy as expected.
In order to display the zip files as folders, ZipMagic must somehow intercept the standard actions such as opening a file and reissue them as if you were working with a folder. This command change prevents MigratePro from being able to properly open, copy and rename files.
It is our guess that the makers of ZipMagic recognize this issue. There are two ways to circumvent this issue. You can turn off ZipFolders for MigratePro only or you can turn off ZipFolders during the time you run your migration jobs.
To turn off the ZipFolders for MigratePro's migration engine, you can open the ZipMagic control panel, select the ZipFolders choice, and go to Applications. Click 'Add' on the Control Panel and browse to your MigratePro folder and choose MProFiles.exe from the file list. Then click 'Add' on the Add New Application dialog. Click 'Done' and 'OK' to save the new settings.
Or to turn ZipFolders off at a specific time, you can open the ZipMagic control panel, select the ZipFolders choice, and go to Schedule it allows you to schedule times for the ZipFolder option to be disabled. The text on the panel says "this can be useful for automatic activities done overnight". This implies that SureSync is not the only product that can not work with the ZipFolders feature on.
Note: The only files that MigratePro will not copy if ZipFolders is turned on are the zip files. All other files should copy normally.
Return to top of page
Known Issues in Latest Version (1.0.4)
Version 1.0.4 was posted on November 6, 2008.
This version contains all patches to previous versions as well as new fixes and features (see the ReadMe file for details). All issues listed for prior versions have been resolved.
There are no patches issued for this version at this time. We will report known issues as they come up.
If you have any problems not listed here, please contact our Support Team.
Return to top of page
MigratePro 1.0.3 Known Issues
Version 1.0.3 was posted on October 28, 2008
- "Object reference not set to an instance of an object" error messages could occur when reading license information. This has been fixed in 1.0.4.
Return to top of page