Chatee ahora con Soporte
Chat con el soporte

Content Matrix 9.9 - File Share Edition

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Enabling and Disabling Optimistic Mode Connecting to a File System Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Job Log Files Using PowerShell with Content Matrix
Content Matrix PowerShell Commandlet List
Modifying Content Matrix Configuration and Settings Frequently Asked Questions About Us

Created Dates Not Retained

Question

We reviewed the upload process and observed that created date was not retained but all other attributes (modified date, modified by and created by) were all correctly set. What could cause this?

Answer

In some cases customer try to set a created date that is more recent than the modified date. This is not allowed by SharePoint. As a result, the created date will be set to the current date.

General Limitation Questions

Question

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?

Answer

1.This partly depends on the machine that is running the 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.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.

License Key Troubleshooting

Question

I have been unable to get 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.

Answer

Here are some things to check:

·Make sure that the license covers the product edition.  (For example, if you are licensed for SharePoint Edition and try to activate the license for Public Folder Edition, the invalid error will display.)

·Confirm that the license you are installing is for the correct application versions of Content Matrix. Contact Quest to verify that it is. (For example, license keys beginning with 823, 824, and 827 are not compatible with File Share Edition since its reintroduction in version 9.9.)

·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 plicy 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 .exe file, and choose 'Run as Administrator'. Then re-enter the license key.

Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment

Question

Why am I getting an error when I try to connect to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-enabled environment?

Answer

Content Matrix uses some assemblies for FIPS compliance that are not supported for certain SharePoint 2019 and SharePoint Server Subscription Edition connections.  

For a remote object model (MEWS) connection (displays for the top node) for SharePoint 2019:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <!DOCTYPE html> <html>

For a local object model (OM) connection (displays at the item level for SharePoint 2019 and SharePoint Server Subscription Edition):

The type initializer for 'Microsoft.SharePoint.ApplicationRuntime.SPRequestModule' threw an exception

In addition, errors will display in Browser View and Items View.  

For SharePoint Server Subscription Edition, you can connect using a remote object model (MEWS) connection.  

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación