I use the import wizard to migrate contents from BO XI R2 SP4 to XI 3.1. The connections are migrated but the universes and reports fail.
Universes fail with the following error:
“Committing the export object to the destination CMS failed. Reason: Failed to commit the associated files of objects to the file repository server: (obj xxxxxx, id 2075 ) : File Repository Server error : Could not complete the file transfer…”
Reports fail with the following error:
Committing the export object to the destination CMS failed. Reason: File Repository Server error : File system operation for a_126\008\000\2174~ce8b457b3506cea5.rep on File Repository Server failed. If the problem persists, please contact your system administrator for event log information.
I had a similar problem to export users from xir2 to xi3.0 (can’t get SI_PASSWORD from source).
This is what i did:
1)Exporting them from xir2 into a biar file and then from biar to xi 3.0.
2)Migrating from source to another xir2 environment and after into xi 3.0.
3)Repeat a lot of time migration.
The issue seems to be with the Xi 3.1 File Repository Servers. I created a report using the eFashion universes and tried to export it to the repository. Export failed with the following error message:
[repo_proxy 30] InfoStore::ObjectExport::commit - (Helpers::InfoStore::ObjectExport::commit) Failed to commit the associated files of objects to the file repository server:
(obj Store-Revenue, id 3060 ) : File Repository Server error : Could not complete the file transfer…(hr=#0x80042a47)(Error #-2147210681
Where is your file store running? What OS is running your system.
What this looks like is that the File store services are running an account that doesn’t have full access to the directories where it needs to store information.
I have run numerous tests migrating and found it important to have the file store working correctly.
Here’s something I noticed:
WEBI reports that use a filter with Matches Pattern, drops the % from constants.
I.e. We have
Account matches pattern %890%
that after the migration is
Account matches pattern 890
Still trying to determine if the % signs are still needed as there are issues with the same report not displaying data correctly from multiple queries
-----Update - the matches pattern seems to work without % (MS SQL 2005)