I'm wondering how I can use Metalogix Content Matrix Console to help users bulk load their existing files into a SharePoint site with their business specific data for each image, and ultimately remove the files from the network share. I would like to provide for the users, perhaps on a network folder basis, a CSV containing a list of file names and perhaps some of the attributes that are identified during the import process, with the additional columns added to the CSV file, and then they could update the CSV with the values per file. The users would hand the CSV back to me for import to the SharePoint site using Metalogix Content Matrix Console - File Share Edition. I would map the new columns to the SharePoint columns before the actual migration. The basic steps would be:
·Import metadata from the file system into File Share Edition.
·Export that info to a CSV file.
·Modify the CSV to include the column headings and values for files to be uploaded to SharePoint.
·Import the CSV into Metalogix Content Matrix Console with the updated metadata information.
·Migrate to SharePoint, mapping new columns from the CSV into SharePoint columns.
Can you let me know if the software is designed to work as I described above?
This scenario is entirely supported by Metalogix Content Matrix Console. This scenario is also supported for use with Import/Export using Excel.
Note: The CSV options are only available when Advanced Mode is enabled.
1.Is there a limit to the number of items you can be listed under a File Share Connection?
2.Is there a limit to the number of rows and columns that you can have in the File Share Edition?
3.Is there an expected amount of memory usage?
1.This partly depends on the machine that is running the Metalogix Content Matrix Console. Depending on the machine it is recommended to only go as high as 5000 items under a File Share connection.
2.This is similar to the number of items. Since it is recommended to only go as high as 5000 items under a File Share connection, and each item is the same as one row in the Items View tab, we recommend to only go up to 5000 rows under a specific File Share connection. While there is no limit to this for columns, since these are only related to rows in that it is information for items, it would still be a good general rule to not exceed 5000 columns, but going over this should not be an issue.
3.Metalogix Content Matrix Console uses an in memory Database (DB) for it's project files, so the amount of memory used can get quite large depending on the number or rows and columns that are included under the File Share connection. To help reduce the in-memory footprint any long strings are stored in the DB, and not in the memory. Since each user's migration scenario is different, we can't accurately give an expected amount of memory usage.
What is MSI error 2869? I am seeing this error when I try to install File Share Edition on Windows Vista.
MSI Error 2869 is a common issue with MSI installations on Windows Vista.
"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2869"
This error can occur when the User Access Control (UAC) feature of Windows Vista is enabled. If you are defined as administrator on Vista, you are only temporary granted administrator privileges when running programs. Therefore, MSI Custom Actions that interact with the system and require administrative privileges will fail to run because MSI Custom Actions will impersonate by default.
A workaround is to run this command from a command line prompt (as an administrator): msiexec /i MySetup.msi
I have been unable to get Metalogix Content Matrix to recognize my license key. When I copy and paste it into the box, I get a "the specified license key is invalid" error.
Here are some things to check:
·Confirm that the license you are installing is for the correct application versions of Metalogix Content Matrix. Contact Quest to verify that it is.
·When performing an offline key activation, make sure to enter the long key in its entirety, including the "=" symbol at the end of it.
·Verify that you have write privileges to the registry. The installer will fail if the registry is locked. In some cases there may be a group policy that is preventing the user from adding the key in the registry, despite the user having the correct permissions.
·Some versions of Windows will automatically block write access to the registry under the user account, even if that account has write access to the registry. In this case you can go to the application installation folder, right click on the application executable, and choose 'Run as Administrator'. Then re-enter the license key.