Home | Contact Us | Sitemap

Home Resource Center FAQ/Technical Notes   FAQ/TECHNICAL NOTES   Answers to Frequently Encountered Issues:   Updated April 2, 2008   Transend Migrator   Scroll to the email system you are converting from or to and click the appropriate issue.   General:   Transend Upgrade Policy   I enter my license key, but the program is still in evaluation mode.   I downloaded the current version, but my old key does not work with it.   How do I create a log file?   Non-English characters do not convert correctly.   The time for each calendar entry or message seems to be off by a certain amount.   On my display, I cannot see all the fields mentioned in the documentation.   Outlook/Exchange:   I get the error message “Cannot load Uniaexh.dll error: 182”   Unable to load UNIAEXH.DLL -or- Unable to initialize output for folder XXXXXX -or- various errors about being unable to connect to the mail client   I'm having trouble accessing my Outlook calendar, contacts or PAB.   How do I avoid needing an Outlook profile for each conversion?.   I'm having trouble converting from Groupwise to Outlook   Notes   Trying to access Lotus Notes, I get error 126 or 1157, unable to connect, or errors about missing DLL files   I can't see all the Notes folders in the list of folders to convert.   Groupwise:   I'm having trouble converting from Groupwise to Outlook.   When I import into Groupwise, the dates are all the same and messages are in draft mode.   How do I convert my GroupWise Archives?   Netscape:   Transend Migrator is converting deleted messages.   Eudora:   Transend Migrator is converting deleted messages.   Pegasus:   Transend Migrator is converting deleted messages.   Html:   My converted messages contain HTML coding, and do not display correctly.   Unix:   How do I convert from ELM/PINE or another Unix e-mail system?   cc:Mail:   Unable to initialize VIM   Exporting cc:Mail private address books   Importing Messages into cc:Mail   Connectorware Import for cc:Mail   What is MAPI?   What Windows platforms does ConnectorWare Import for cc:Mail support?   What cc:Mail post offices does ConnectorWare Import for cc:Mail support?   Is ConnectorWare Import for cc:Mail Year 2000 compliant?   When trying to import folders, certain folders don't get imported and I get an error message.   When importing Private Mail Lists into Outlook Contacts, there are no addresses in the lists but the individual address entries are in the Contacts.   Colored text is not preserved in Outlook.   When I import messages from my cc:Mail folders, why do all the dates get changed to the current date?     Transend Upgrade Policy Transend Migrator and Transend Migrator Forensic Edition come with 30 days of free technical support; during this time, any new versions are free. The purchase of Annual Support extends free upgrades to one year from date of purchase. Please be sure to obtain the latest version prior to the expiration of your free maintenance period.   If you download the current software and your old license key does not work with the new version, AND if you are within the maintenance period, please email your license key (name, organization, and key value) to us; we will confirm your status and issue a new key.   If you have an older license and have misplaced your software, please contact us.   If you are not within the maintenance period and wish to upgrade, pricing is as follows: 50% of the original purchase price.  We will confirm the original sale and provide payment options.  Upgrading provides an additional 30 days of technical support, including new versions available during the period.   I enter my license key, but the program is still in evaluation mode To activate Transend Migrator, you must enter the license key you received when it was purchased. To do this, run Transend Migrator as normal (you don't have to re-install it). In the menu area in the upper left corner of the screen (right above the graphic) there is an "Edit License" option. Select this, and enter the three information items (Name, Organization, and Key) *exactly* as given, including case and punctuation. You may not substitute a different name.   Note: the key does not contain the letter "O" - anything that looks like an O is actually a zero. Similarly, there is no letter "L" - anything that looks like "l" is actually the number one. In order for the license to take effect, you must re-start Transend Migrator.   If for some reason Transend Migrator still says that it is an evaluation version, you may have an older version of the configuration file that needs to be re-written. You will need to delete the file UA.CFG. The UA.CFG file is stored in the C:\Documents and Settings\All Users\Application Data\Transend folder for Windows XP and inside the C:\Program Data\Transend folder on Windows Vista. Go to the appropriate directory and delete the file UA.CFG. Then re-start Transend Migrator and re-enter the license information as directed above. If it still does not work, please send the UA.CFG file to us.   If you would like to avoid entering the license for each machine you install Transend Migrator on, you can copy the file UA.CFG from a licensed machine to a new one. Alternatively, you can copy the UA.CFG file to a shared directory on your LAN (this directory must be writable). Then alter the shortcut for Transend Migrator on the client machine as follows:   TM.EXE /S <directory>   where <directory> is the location of the configuration file. (Example: TM.EXE /S E:\Windows) Please note that if you are using this switch, and you do not put a valid UA.CFG in the referenced directory, Transend Migrator will be in evaluation mode.   If the Transend Migrator license works OK in interactive mode (tm.exe) but not batch mode (tmb.exe), the problem may be that you are using the /S switch when starting tmb.exe. Make sure that you copy the config file to that location.   TOP   I downloaded the current version, but my old key does not work with it Transend Migrator comes with 30 days of free technical support; during this time, any new versions are free. Please be sure to obtain the latest version prior to the expiration of your free maintenance period.   If you download the current software and your old license key does not work with the new version, AND if you are within the maintenance period, please email your license key (name, organization, and key value) to us; we will confirm your status and issue a new key.   If you have an older license and have misplaced your software, please contact us.   If you are not within the maintenance period and wish to upgrade, pricing is as follows: 50% of the original price.  Please email or fax us your original order information (name/company, purchase order #, date).  We will confirm the original sale and provide payment options.  Upgrading provides an additional 30 days of technical support, including new versions available during the period.   TOP   How do I create a log file? If you are having problems with Transend Migrator, it may be helpful for our support staff to get a log file of a sample run. A log file contains specific events written to the file "ualog.txt". Normally this file will be created in the c:\windows directory. If you are running under Windows NT it may be located in c:\winnt. Also, if you have started Transend Migrator with the command line switch /S, the log file will be created in whatever directory you named following the /S switch. If you cannot find ualog.txt,make sure you have started Transend Migrator correctly (see below) and also search your system for it, as the default windows directory may be something unexpected.   To enable logging, a special command line switch is needed. A command line switch is entered following the program name (tm.exe).   If you are starting Transend Migrator by clicking on it's icon, modify the command line as follows: Right click on the icon and select "Properties". You will get a dialog box that has a "Shortcut" tab. Click on that tab, and look for a field named "Target". This should be set to "tm.exe". Modify this value, adding a space at the end of tm.exe, followed by the switch /L. The space and switch should be outside the quotes. The new Target value should be something like:   "c:\transend\tm.exe" /L   Click OK to save the shortcut modification. Run Transend Migrator as usual and shut it down.   Two other ways to start Transend Migrator with a command line switch:   Go to Start | Run and type the path to tm.exe, then a space and then the command line switch /L (eg. c:\transend\tm.exe /L -- your path may be different).   Open a DOS box and type the command directly. This is done by going to the Accessories menu (from your Start button) and running the program "Command Prompt" or "MS DOS Prompt". In the window that opens, enter the commands: cd \transend tm /L Note: you may have installed Transend Migrator into a directory other than "transend" in which case modify the cd command above.   After Transend Migrator has run, look for the ualog.txt file as described above. The file should be emailed to us. Make sure to include your contact information and details about what the problem is.   TOP   Non-English characters do not convert correctly Transend Migrator attempts to automatically determine what type of character set conversion is necessary for your migration. However, this process sometimes fails, so it may be necessary to select a different type of conversion. In addition to this, the system environment (i.e. Windows) must be set up to support the various language formats  To set up Windows for a given language format follow the recommendations below: Windows XP Windows XP defaults to "Category View" in the control panel.  Switch to "Classic View" for the following steps. Go to the Control Panel Double-click the Regional and Language Options icon Select the Advanced Tab "Select a language to match the language version of the non-Unicode programs you want to use" from the drop down selection box Reboot the computer Windows 2000 Go to the Control Panel Double-click Regional Options Select General Select Language Settings for the System Select the language to use for your conversion Click Apply to complete the installation, and follow the prompts.  You may need your Windows 2000 CD-ROM Reboot the computer Windows 95/98 Go to the Control Panel Double-click Add/Remove Programs Click Windows Setup Select Multi-Language Support Click Details (at the bottom of the Window panel) Select the Language Support you require Click OK to complete the installation.  You may need your Windows 95/98 CD-ROM Reboot the computer Microsoft Outlook Select Tools from the menu Select Options Select the International Options button Select the language from the Preferred encoding for Outgoing Messages drop down selection window Click OK Close and restart Outlook Command Line Option Details   If you notice a problem with non-English character sets not displaying properly, try one of the following command line switches when starting Transend Migrator (TM.EXE): /NOCC (No character conversion) /CC2 (Use Western Europe Character Set)   The following switches are used for converting codepage 850 character set into Windows 1252. These command line switches are mainly used for Notes to Outlook migrations, and may not work for other systems:   /CCC (Portugese) /CCN (Nordic, i.e. Danish, Swedish) /CCP (Polish) /CCI (Italian) /CCZ (Czech) /CCJ (Asian languages) /CC (Alternative Western Europe Character Set) /CCA (Arabic) /CCG (Greek) /CCISO (Latin) /CCR (Russian) /CCT (Turkish)   The following switch calls a Notes API to convert the Lotus Multi Byte Character set (LMBCS) data into Unicode.  Then, it calls a Windows API to convert the Unicode to a given codepage. By default, the codepage will be 1252 (Western European) but you can specify a different one by putting the number after the switch, e.g. "/CC3 1253" for Greek. Following is a list of the different codepages:   http://www.microsoft.com/globaldev/reference/WinCP.mspx Note: May not work for all codepages.  Won't work for Asian languages.   /CC3 <codepage> The following switch is used for UTF-8 to codepage 850. Mainly used for Internet clients to Lotus Notes.   /CCW   The following switch is used for UTF-8 to codepage 1252.  Mainly used for Internet clients to Microsoft Outlook. /CC8 TOP   The time for each calendar entry or message seems to be off by a certain amount Some email systems store email dates and times in Greenwich Mean Time (GMT) or Universal Time (UT).  Both are the same thing. Systems that store email with the GMT date maintain the correct date or time no matter which time zone you are in.  For example, if a person sends you an email from the eastern United States at 12:00pm, and you are in the Pacific Time zone, you will receive the email at 9:00am of the same day.  The email system used to send and receive the email adjusts the time so it will reflect the current time zone.   Explanation If you are converting from an email program that doesn't store messages in GMT format then the converted email may not display the correct date and time.  In many cases, it will be stored within your time zone and with the GMT offset for your time zone. If this is the case, it may be necessary to tell Transend Migrator what your GMT offset is.  If, after a test run, you determine that the start and end times for events or message timestamps are incorrect, find the difference (in minutes) between the displayed time at the correct time.   You may enter this offsent in one of three ways: Start Transend Migrator with the command line switch.  The value is the number of minutes you wish to use.  This value can be either positive or negative. /TZD <value> You can create an environment variable called TZD and assign the desired value.  In a batch file or at the DOS prompt type: Set TZD = <value> Sometimes, you may need to alter the number of minutes that Transend Migrator assumes is the difference between daylight and standard times (default is -60). /DSTOFFSET <value> Also, you may change your machine time to reflect the time zone of the originating email, or even set your machine time to GMT.  Always remember to verify the output to ensure the correct offset value is used.   TOP   On my display, I cannot see all the fields mentioned in the documentation Under certain conditions the Transend Migrator screen may appear enlarged and some controls are not visible. To correct, use the following procedure:   Run the Windows Control Panel Run the "Display" application Select "Settings" Select "Advanced" Set "Font Size" to "Small Fonts" Press OK for all dialogs, and re-start Transend Migrator   This may vary depending on which operating system you are running but the basic idea is to change the default font size within Windows.   TOP   Outlook/Exchange:   I get the error message "Cannot load Uniaexh.dll error: 182" The error indicates that mapi32.dll is so old that it doesn't contain one or more vital API routines.  Transend suggests going through all the ideas in the note below, in particular copying the mapi dlls from the Outlook directory into the Windows directory.   Unable to load UNIAEXH.DLL -or- Unable to initialize output for folder XXXXXX -or- various errors about being unable to connect to the mail client When converting to Outlook or Exchange, you may get the error message "Unable to initialize output for folder XXXXXX" (where XXXXXX is the name of the folder you selected for conversion). This is usually caused by some other application having previously installed itself as your default MAPI client. MAPI is the API that Transend Migrator uses to communicate with Outlook/Exchange, so if it is replaced, it probably won't work correctly. This situation is common with Netscape and GroupWise.   To correct, go to your "Internet Settings" in either the Windows control panel or Internet Explorer, and select the option that controls which application is used as the default MAPI client. This should be set to Outlook or the Exchange client. This can also be done by right clicking on Internet Explorer, selecting "Properties", then going to the "Programs" tab. The "E-mail" field should be set to Outlook or Exchange. You can also set Outlook as the default client from Outlook. Select Tools | Options | Other. Under the "General" section, click the checkbox labeled "Make Outlook the default...".   If this fails, you may need to run Microsoft's fixmapi.exe utility, which is located in the \windows\system directory in Windows 98. See Microsoft technet article Q199823 for more information.   Some recent versions of Outlook install in their own directory the mapi drivers needed to work with it, but fail to update the mapi drivers located in the Windows system directory. Use a search utility to find all examples of mapi32.dll. If there are multiple copies, you may need to rename the older versions to something else, so that the most recent will take priority. For example, one release of Outlook 2000 copies its mapi drivers to the directory:   c:\program files\common files\system\mapi\1033\95   If the mapi drivers located in \windows\system are incorrect, you should copy all files found in the above directory to the system directory.   Other possible fixes:    - If you are accessing a .pst file, make sure that it is installed on a drive with read/write access, and that the "read-only" attribute is not set. This is necessary even if you are not planning to write to the .pst file - MAPI itself does this.    - Make sure Outlook is in "WorkGroup" (Corporate) mode. Click on Tools, Options, Mail Services, Reconfigure Mail Support, and select "Corporate/Workgroup". NOTE: Outlook Express is an Internet-only version of the full Outlook and does not have "WorkGroup" (Corporate) mode.   - If you are specifying a .pst file name in the "Profile or .pst file" field, try using a profile name instead.  Some versions of MAPI have problems creating a temporary profile (the technique Transend Migrator uses to allow specifying a .pst file).   - If you are specifying a .pst file, make sure the lines:   MSPST AB=Personal Address Book MSPST MS=Personal Folders   are in the "services" section of the file c:\windows\system\mapisvc.inf (if you don't have the file in that directory, search your system for it). You can usually find a copy of this file in the Outlook install directory tree - it may help to just copy the file from there to your Windows system directory.   - In some cases we have seen, it is necessary for you to keep your Outlook or Exchange client open while running Transend Migrator.   - Create a new Outlook "profile". This is done using the "Mail" application from the control panel. Add as few services as possible, preferably just a single "Personal Folders" mapped to a local .pst file. Use the new profile name during the Transend Migrator logon.   - Disable any Outlook Add-ins. This is done as follows: Tools | Options | Other | Advanced | Add-in   - If nothing else works, it may help to reinstall your Outlook client.   If you are unable to connect with your Exchange or Outlook system, please run tm.exe with the command line switch /L and send us the resulting \windows\ualog.txt for analysis.   Public Folders Bug If you get a prompt for an Outlook profile, but after selecting it Transend Migrator seems to hang, it may be another problem unrelated to MAPI. During the login phase Transend Migrator attempts to build a table of all folders that it sees in the message store. Some systems have several thousand public folders, which can cause an internal bug in Transend Migrator. To correct, tell Transend Migrator to skip the public folders by using the command line switch:   tm.exe /skip public_folders   Where "public_folders" is the name of the message store. Spaces are replaced by the underscore.   Other Problems If nothing above helps your situation, please run the Transend Migrator executable, tm.exe, with the command line switch /L (best way: open a DOS command window, use the CD command to change to the directory where Transend Migrator is installed, and type "tm /L"). Run your test until you get the error, then look for the file c:\windows\ualog.txt (it may also be in \windowsnt or \windows32). Send this file back to us for analysis.   TOP   I'm having trouble accessing my Outlook calendar, contacts or PAB If you have a non-English version of Exchange or Outlook, there will be a problem when you try to convert to or from the Personal Address Book or Contacts folder. This is because Transend Migrator is locating the correct folder by searching for its default English name. There is a command line switch that will allow you to specify a different name. Start Transend Migrator as follows:   tm.exe /PAB <pabname>   where <pabname> is the first word of the name of the personal address book. For example, for the French version, enter:   tm /PAB Carnet   For the Contacts folder, use the switch /CF, i.e.   tm /CF <Contacts folder name>   For the Calendar folder, use the switch /CAF, i.e.   tm /CAF <Calendar folder name>   If you have any trouble, run tm.exe also with the command line switch /L. In the file ualog.txt, it will tell you the names of the address books that it finds.   TOP   How do I avoid needing an Outlook profile for each conversion? Transend Migrator has the capability to produce Outlook .pst files directly. It does this by creating a temporary MAPI (Outlook programming interface) profile, adding a "Personal Folders" message store, and assigning a new or existing .pst file to the message store. Occasionally, there is an installation problem with MAPI that prevents this from working correctly.  Although this can be corrected by various means, you may find it easier to create .pst files using an existing profile. This is done as follows:   On the machine doing the conversion, create a new profile. In the profile, configure a single message store, called "Personal Folders" which will map to a local .pst file (which will be created for you). A profile is created using the "Mail" application within the Windows Control Panel.   Make a copy of the new .pst file and save it somewhere.   Do a single conversion, converting from your source system to to Exchange/Outlook, specifying your new profile. After the conversion, the .pst file will be filled with that user's mail. Copy the file to the local user's machine. You may have to overwrite his existing .pst file, or modify his profile to add a new message store for the .pst file.   On the converting machine, copy the original, new .pst file over the one that the profile is using. Now you have an empty .pst file, and can begin again with a new conversion.   NOTE: You may already have a profile that has a "Personal Folders" message store. This can also be used as-is. The "Miscellaneous Options" screen in Transend Migrator contains a drop-down list box that allows you to specify which message store should be used.   TOP   I'm having trouble converting from Groupwise to Outlook. In some situations it is difficult to do a conversion directly from Groupwise to Outlook/Exchange. This is because both the GroupWise and Outlook clients use MAPI, and they sometimes conflict. In many cases this can be resolved by using one of the methods discussed in the MAPI. It is also usually helpful to keep Outlook open during the email conversion.   However, it may be simpler to do a two step conversion using the Transport File in order to avoid debugging MAPI driver conflicts. The Transport File (TF) conversion choice is not a typical email format.  Instead, the TF is a container or database, and it is created for the purpose of a two-step migration, or for email storage. The TF contains all the email and attachments from a single migration, and its size limit is 4GB.  It is recommended that a single TF be created for each email account being migrated.   The basic technique is to use the Transport File as the intermediate file format when attempting a GroupWise to Outlook/Exchange (or the reverse) migration.  One machine can be set up to migrate GroupWise email accounts to the TF, and another machine would migrate the TF to the Exchange Server or .pst file.   For address books, we suggest using the "Novell Address Book" (or NAB) format. You can export this using the Groupwise client itself, or use Transend Migrator.   TOP   NOTES   Trying to access Lotus Notes, I get error 126 or 1157, unable to connect, or errors about missing DLL files If you get the error message "Cannot load uniants.dll, error 1157", (or error 126) this means that Transend Migrator is not able to locate the Notes API, a set of DLLs that is installed with the Notes client. (Transend Migrator requires the Notes client, versions 4 thru 7, to be present. It is possible to use the free Notes evaluation client for this purpose, without installing a Notes server).   To fix this, search your system for the file nnotes.dll. The directory in which this is located (usually c:\notes) must be on your system's PATH statement. In Windows 9x this is done via the MSConfig utility; in Windows 2k/XP this is done via the SYSTEM utility in the Control Panel (System | Advanced | Environment Variables | Path).   Another way to avoid the problem is to change the shortcut for Transend Migrator so that the default directory is the the Notes EXE directory. Right click on the Transend Migrator icon, select Properties, then click on the Shortcut tab. Change the "Start in" field to the directory you identified as containing nnotes.dll.   If the above does not work, it may help to re-install Transend Migrator into the Notes exe directory located above. This means that all the Transend Migrator files (.exe and .dll) should be in the same directory as nnotes.dll - it does *not* mean that there should be a Transend Migrator subdirectory there. When you run Transend Migrator (tm.exe) make sure to run the new copy in the Notes exe directory, not the original tm.exe which may be in its own directory.   If you avoid the above problem, but Transend Migrator seems to "hang" before getting to the Notes Information screen, check the following: Find your notes.ini file (usually in the Notes or Windows directory). Search for the variable "MailFile". If it is not found, add a new entry (using a text editor). Set the value equal to the local pathname of your mail.nsf file, including the drive letter and directory name. Also, a hang can also be caused by the API problem discussed in the first paragraph.   A crash can also be caused by a corrupt version of notes.ini. You probably have at least two copies - one in the Windows directory, and one in the Notes directory. Try getting rid of one or the other (after making a backup). In some cases it may be necessary to re-install the Notes client to get the API working correctly.   If you seem to be accessing the Notes database without error, but are getting empty messages, there are at least two possibilities:   The .nsf file is encrypted. Make sure that you have installed the Notes ID file owned by the original creator of the .nsf file, and that you can read the messages using the Notes client.   The .nsf file is set to read-only. The Notes API needs to write back to the .nsf file, even during a read-only operation. The file attribute needs to be set to read/write, and the .nsf file must be in a directory that is writable. If you are converting from Notes, but are seeing only the Notes Inbox and Sent Items, go back to the Notes login screen, and enable the checkbox "Shared Folders".   Other Problems If nothing above helps your situation, please run the Transend Migrator executable, tm.exe, with the command line switch /L (best way: open a DOS command window, use the CD command to change to the directory where Transend Migrator is installed, and type "tm /L"). Run your test until you get the error, then look for the file c:\windows\ualog.txt (it may also be in \windowsnt or \windows32). Send this file back to us for analysis.   TOP   I can't see all the Notes folders in the list of folders to convert If you are converting from Notes, but are seeing only the Notes Inbox and Sent Items, go back to the the Transend Migrator "Notes Information" screen and check the "Shared Folders" checkbox.   TOP   GROUPWISE:   I'm having trouble converting from Groupwise to Outlook In some situations it is difficult to do a conversion directly from Groupwise to Outlook/Exchange. This is because both the GroupWise and Outlook clients use MAPI, and they sometimes conflict. In many cases this can be resolved by using one of the methods discussed in MAPI. It is also usually helpful to keep Outlook open during the email conversion.   However, it may be simpler to do a two step conversion using the Transport File in order to avoid debugging MAPI driver conflicts.   The Transport File (TF) conversion choice is not a typical email format.  Instead, the TF is a container or database, and it is created for the purpose of a two-step migration or for email storage The TF contains all the email and attachments from a single migration, and its size limit is 4GB.  It is recommended that a single TF be created for each email account being migrated.   For address books, we suggest using the "Novell Address Book" (or NAB) format. You can export this using the Groupwise client itself, or use Transend Migrator.   TOP   When I import into Groupwise, the dates are all the same and messages are in draft mode   When converting to GroupWise 5.x and because of the way the GroupWise 5.x Object API works, converted messages will appear to be unsent.  You will have a Send button active, instead of Reply. The distribution list will be shown within the text of the message, instead of the header.  A reply is not possible unless you manually fill in the distribution list. Also, in order for the message date to be correctly set, you must be connected to the GroupWise server via a mapped drive, rather than in Client/Server mode. These are not restrictions when migrating GroupWise 6 and greater. A. Message Dates When importing messages into Groupwise you may notice that the date of imported messages is set to the date that the import occurred, instead of the actual receive date of the message. There are two possible reasons for this:   If you are importing into Groupwise via the API Gateway (running a separate program to import files produced by Transend Migrator), the date should be set properly. However some Groupwise clients are set to display the import date rather than the message date. Reconfigure your client to display the correct date. (This is usually done by right clicking the folder name and selecting the correct date field from the pop-up display).   If you are importing into Groupwise via the Object API (direct conversion from Groupwise): The Object API does not have any facility to set the message date (Novell considers this to be a security issue). Transend Migrator attempts to get around this limitation by setting the system date of the computer it is running on, for each message. This method only works if you are making a "mapped drive" connection to your Groupwise server. If you are running in client/server mode, the date is obtained from the server, and there is nothing we can do about it. If dates are important to you, you must either switch to a mapped drive connection or use the API Gateway. To make a mapped drive connection:   Run the Novell Admin program, select your post office, right click, and select "details". In the resulting dialog, change "Access Mode" to "Direct", and enter a valid UNC path to your post office directory on the file server.   Novell considers this type of access "dangerous" (no explanation given) so after your conversion, you should switch back to the standard connection method.   B. Draft Messages If you import your messages via the Object API, messages appear to be in "draft" mode. This is a limitation of the Groupwise API - there is no facility for creating messages that appear to have been received normally.   Also, such messages are not viewable with the current version of Groupwise Web Access.   If this is not acceptable for your conversion, the only workaround is to use the Groupwise API Gateway, the official Novell method of performing a migration. In Transend Migrator, select "Groupwise Gateway" as the output type. Transend Migrator will create files in the format required by the gateway, which must be installed separately. See the Transend Migrator online help for more information.   Note: the link to download the API gateway is:   http://developer.novell.com/ndk/gwgateway.htm   C. "Imported For" Messages When you use the API Gateway to import messages into Groupwise, the message, when viewed in the Groupwise client, will say "Imported For ..." at the beginning of the message. This is a feature of the gateway and cannot be removed by Transend Migrator.   By default, Transend Migrator uses the keyword "FROM-TEXT" when building the API gateway input files. This is a display-only field, and does not affect the address that Groupwise uses for replies. Transend Migrator can also use the "FROM" field, where a return address is specified. In order for this to work, the source system emails must have email addresses included. This is usually the case for Internet clients such as Netscape or Eudora. To allow this field to be used, do the following: in the Transend Migrator "API Gateway Information" screen, in the field "Groupwise User", enter the target Groupwise user as usual, but append at the end a semicolon, followed by the domain.postoffice that you have defined as the Internet gateway for Groupwise. For example:   Groupwise User: mydomain.mypo.userid;inetdomain.inetpo   If you want the full distribution list to be inserted into the text of the message, use the command line switch /DLIST when starting tm.exe or tmb.exe.   TOP   How do I convert my GroupWise Archives? Here is how archives work with the GroupWise client:   To set up a new archive, or to access a different one, with the GroupWise client, select Tools | Options | Environment | File Location | Archive Directory   Enter the directory where you want to create a new archive, or where an existing one is. In this directory, it will create, or you will already have, a subdirectory that looks something like "OF7WLARC" (it will be slightly differently on your system). Within the OF7WLARC directory, you will have several files that comprise the database, with files such as user.db and msg.db, plus others. So to summarize, you will have a top level directory such as C:\MYARCH. Within that you have OF7WLARC. You use the value "C:\MYARCH" as what you give to the GroupWise client and to Transend Migrator.   Once the archive is created, you put messages into it by pointing at a message or group of messages, and selecting from the GroupWise menu Actions | Archive. The message(s) are moved to the archive and deleted from the mailbox.   To see your archived messages, select from the GroupWise menu File | Open Archive. If you need to point to a different archive, first go to the Tools menu as described above. After the archive is open, all your Mailbox folders disappear and are replaced by whatever folders you have archived.   In Transend Migrator, if you enable the "Use Archive" checkbox in the Groupwise login screen, you will be presented with a list of folders found in the default archive (the default archive being what is currently selected in the Archive Directory field in the GroupWise client). If you want to specify a different archive, run tm.exe with the command line switch /GWARCH <directory>, e.g. tm.exe /L /gwarch c:\myarch   Note: you don't actually have to use the /gwarch switch. It will go by default to whatever you have configured in the GroupWise client. The switch is only if you want to point to something else and don't want to reconfigure the client.   Converting Archives from GroupWise 4.x Transend Migrator cannot work directly with GroupWise 4.x - you must have the GroupWise client 5.5 or above installed on your PC. Once you do, archives can be copied from 4.x clients and converted using Transend Migrator. Use the following procedure:   From the GW Client, you must provide the Archive Path under TOOLS | OPTIONS | ENVIRONMENT | FILE LOCATION (e.g. c:\archive). Be sure there are no other files or folders in this directory.   Copy the GW v4.1 Archive folder (e.g. ofX7Tarc) to the archive location c:\archive.   Rename the folder name to match the 3 character FID of your GW v5 account (e.g. RU4). For example, rename ofX7Tarc to ofRU4arc. If you don't know your GW FID, it can be found from within the GroupWise Client under HELP | ABOUT GROUPWISE. It will be displayed next to your username.   Simply open the GW Client again and you should be able to view the archived mail by selecting FILE | OPEN ARCHIVE. The first time that you view the GW v4.x archive, you will be prompted to convert the Database to the new version. Once this is done, you may run Transend Migrator to convert it. If you need to change the FID for a GroupWise v5 or v6 archive, Novell provides a FID Editor Utility that will accomplish this for you. It can be found at the following URL:   http://support.novell.com/cgi-bin/search/searchtid.cgi?/2944905.htm   Novell's TID #10014261 explains in detail how to use this utility.   TOP   Netscape:   Transend Migrator is converting deleted messages When converting Netscape, Eudora, or Pegasus folders, you may find that Transend Migrator seems to convert messages that you thought were deleted. This happens because Transend Migrator reads the data file directly, and does not have knowledge of messages that were marked as deleted in the index, but not cleared from the data file. To correct this behavior, it is necessary to run the "folder compact" function as appropriate for each system. In Netscape, choose "File | Compact Folders". In Eudora, choose "Special | Compact Mailboxes". In Pegasus, right-click a folder and select "Recover deleted space". Each of these systems may also be configured to automatically run the compact routine on a regular basis.   TOP   Eudora:   Transend Migrator is converting deleted messages When converting Netscape, Eudora, or Pegasus folders, you may find that Transend Migrator seems to convert messages that you thought were deleted. This happens because Transend Migrator reads the data file directly, and does not have knowledge of messages that were marked as deleted in the index, but not cleared from the data file. To correct this behavior, it is necessary to run the "folder compact" function as appropriate for each system. In Netscape, choose "File | Compact Folders". In Eudora, choose "Special | Compact Mailboxes". In Pegasus, right-click a folder and select "Recover deleted space". Each of these systems may also be configured to automatically run the compact routine on a regular basis.   TOP   Pegasus:   Transend Migrator is converting deleted messages When converting Netscape, Eudora, or Pegasus folders, you may find that Transend Migrator seems to convert messages that you thought were deleted. This happens because Transend Migrator reads the data file directly, and does not have knowledge of messages that were marked as deleted in the index, but not cleared from the data file. To correct this behavior, it is necessary to run the "folder compact" function as appropriate for each system. In Netscape, choose "File | Compact Folders". In Eudora, choose "Special | Compact Mailboxes". In Pegasus, right-click a folder and select "Recover deleted space". Each of these systems may also be configured to automatically run the compact routine on a regular basis.   TOP   HTML:   My converted messages contain HTML coding, and do not display correctly Some target systems have no way for Transend Migrator to tag them as HTML.  In this case, try the switch /HTMLATTACH.  This will convert HTML messages into separate attachments.  The reader can then click on the link to bring up a browser which will display the message correctly.   Note: when importing into Outlook, you must have it configured as a "Workgroup" installation in order for the above to work. Click on Tools, Options, Mail Services, Reconfigure Mail Support, and select "Corporate/Workgroup".   TOP   UNIX:   How do I convert from ELM/PINE or another Unix e-mail system? In most cases Transend Migrator is capable of converting mail from standard Unix systems, such as Elm, Pine, or Sun Mail. This assumes that the mail files are stored in standard RFC-822 format.   Basically you will select "Netscape" in your Convert-From option in Transend Migrator. Transend Migrator will ask for the directory where the Netscape mail is stored. Enter the directory in which your Unix mail files are located. (Note: you may need to map a drive to your Unix system using NFS or some other facility).   The problem that you will run into is that Transend Migrator is trying to identify Netscape files by looking for files with the extension .snm (Netscape index files). It then strips the extension to get the real file name. So for this method to work, you will have to create dummy .snm files for each Unix mail file. For example, if you have a mail file called "January Messages", create a file called "January Messages.snm" and place it in the same directory. The contents of the .snm file are not relevant. If your mail files have an extension such as .mbx, the extension must be removed.   We have seen some cases where the message delimiter found in Unix mail file is non-standard, in which case Transend Migrator will fail. If this appears to be the case, open your data file with a text editor and look at the first line. It will probably be something like:   from user@domain.com   In this case the message delimiter is "from ". (Note: without the quotes, and including a space after from). You can tell Transend Migrator to use a different delimiter using the switch /msgdelim <delimiter>. If the delimiter includes a space, substitute an underscore. For the above example, the command line would be:   tm.exe /msgdelim from_   TOP   ccMail:   Unable to initialize VIM Transend Migrator uses VIM (Vender Independent Messaging) to access cc:Mail folders. VIM consists of a series of DLL files, starting with VIM32.DLL. Usually these files are located in the \windows\system directory, or in the cc:Mail directory.   The above error message is usually cased by the VIM dlls being missing or out of date. To correct, go to http://www.transend.com/ftp/vdlw32.zip and download the file VDLW32.ZIP. Unzip this to your \windows\system directory (all files). Use a search utility to find any other copies of VIM32.DLL. If found, delete or rename the file.   TOP   Exporting cc:Mail private address books In its address book converter, Transend Migrator has an entry for cc:Mail private address books. Unfortunately this works only with version 6 (DB6) of the cc:Mail post office (due to Lotus's refusal to update their API).   It is possible to get these addresses by using the Lotus Export utility, which is shipped with cc:Mail and is located in the same directory as the other administrator utilities. The output of the utility is a text file, which Transend Migrator can then read and convert to any other supported format.   To use this method you must have version 8.5+ of Export. It may be stored on your system as export.exe or export32.exe.   To run Export, use the following command line:   export /n<user> /p<password> /d<directory> /@<file> /PAB   where:   <user> is the cc:Mail user name <password> is the password for the user <directory> is the location of the cc:Mail database <file> is the output file to create   Once the output file is created, run Transend Migrator and specify a "Convert from" of "cc:Mail Imp/Exp". Enter the name of the file you just created.   TOP   Importing Messages into cc:Mail cc:Mail import has some peculiarities that force you to accept tradeoffs for various features. The default way that we create the import file involves use of the "altinbox" keyword to denote the folder name. This method requires that you run import signed on as the postoffice (the /N switch). It also requires that the folders referenced by altinbox already exist. If they don't exist, the messages go to the inbox.