Advertising banner:
 
 
 F1270
 
81203_43854_21.png81203_43840_19.png

This section addresses various problems that you may encounter during client migration:

Question
Answer
My FirstClass server has a large Directory. Whenever the Client Migrator starts migration, the initial "List Directory" operation puts a strain on the server. Is there a way to skip it?
Change the "Application mode" of Client Migrator from the default "Compliant mode" to "Stand Alone mode".

Occasionally, users receive a "Script reply timeout" error during migration. What causes this error? How can I avoid it?
The "Script reply timeout" error may occur under the following circumstances:
       you run migration in "Compliant mode" and you have a large FirstClass Directory
       you have a heavy FirstClass server load
       the migration scripts contain too many messages
       your connection with the FirstClass server is slow or stalls occasionally.
To minimize the chance of this error, increase the value of the "FirstClass script reply timeout" field for Client Migrator.
A user receives the error "Failed to write the message body/attachments into a temporary file." on his machine during migration, but no other users encountered the error. What's wrong with his machine?
Make sure his System Temporary Folder has enough space to accommodate the temporary files created by Client Migrator during migration. For more information about the System Temporary Folder, see the related Microsoft documentation.
Why is the Created time shown in the Properties form of migrated messages the time when the messages were migrated instead of the original Microsoft Exchange Creation Time?
The Created time shown on the Message Properties form is when the message was created on the FirstClass server, and is currently not modifiable using FirstClass scripting.
When migrating a large PST file, errors like "Unable to open message" occur frequently in various messages.
This is a "Microsoft Personal Folder/Address Book Service Provider" performance issue, which says that handling PST files containing a large number of messages may cause an "Out of memory" error (Error code = 8007000E). To bypass this issue, copy the PST content to the remote Microsoft Exchange mailbox using Microsoft Outlook. You can migrate the PST file again from the remote mailbox.
81203_42521_14.png Note
Sometimes the above copy operation will cause Microsoft Outlook to hang. If this occurs, terminate the nonresponsive Microsoft Outlook process and try again.


hirosue Shino Web Site