Error Messages and Resolution Tips


You may notice one or more of the error messages given below when using XPlica to connect to SharePoint and perform a migration. This is not an exhaustive compilation of all error messages, but an attempt to include as many known error messages and how to resolve the errors. Please refer Troubleshooting section of online help document for more information.

Error Message

Resolution

The remote server returned an error: (407) Proxy Authentication Required.

Enable the Bypass proxy server for local addresses option available at LAN Settings of Internet Options of Internet Explorer Browser.

The server could not sign you in. Make sure your user name and password are correct and then try again. Check if you have a persistent session if you use federated identity.

If you use federated identity to connect to the SharePoint sites, XPlica expects a persistent connection (already established connection) to be available for the SharePoint sites to commence the migration task in unattended mode or scheduled mode. You can use the Web Single Sign-on Dashboard to establish a persistent session.

Unable to establish existence of the account specified.

The user account specified in the scheduled task should be a trusted domain user account.

String was not recognized as a valid Date Time

Ensure that the date value given in external reference file is in correct format. If the given date value format is different from the current system date time format, then specify the appropriate Date Time format mask to use in your migrate task.

Lookup ID not found

Ensure that the given column value is available in the Lookup field reference list and column. XPlica will search for the value in the corresponding column of the referenced list and assign the ID of the first item matching the column value to the lookup column of the imported file, only if the column value exists. Note: if the specified column value is of folder type, the ID of the folder will not be assigned.

User or Group ID not found

Ensure that the given user or group name exists in the respective site. Unavailability of user or group name causes this error.

User ID not found

Ensure that the given user name exists in the corresponding SharePoint Site. This error may occur if the specified user name does not exist.

Multiple User IDs found

The user value specified to assign in SharePoint People / Group column must be unique in the SharePoint repository and Active Directory Services. This error may occur if the specified user value has multiple user entries with the same name in SharePoint.

The column values could not be assigned for this file since there was no corresponding entry in the external reference file.

Ensure that the given Source Path or Destination Path in external reference file exists in Source and Destination library respectively. Differences in reference file and original source location will also result in this error. Also, ensure that the metadata values are provided for all documents that are migrated.

There is no entry for this file in the external reference file.

Ensure that the metadata values are provided for all documents that are imported.

Source folder or file not found

Ensure that the given Source Path is valid and available. Invalid or unavailable source paths will result in this error.

Unable to locate list in the target location (or) Unable to locate destination folder / file in the target location.

Ensure that the given Destination Path is valid and exists.

XPlica will not apply metadata for standard folders.

Ensure that you can assign a folder content type to the given destination folder. XPlica will not assign metadata for a standard folder.

The following file(s) have been blocked by the administrator: <filename>

Ensure that the file formats that are migrated are not blocked in the target SharePoint web application. File formats such as ASP, CHM, MDB etc. files are generally blocked in SharePoint by administrators.

The file is checked out or locked for editing by user

If the given file is checked out by another user and you are trying to check-in the file, then this error may occur.

Could not create document as mandatory columns do not have values

The values are required for mandatory columns in a SharePoint library. The file will be skipped as mandatory columns do not have values. The column value for a mandatory column may not available in either the external reference file or source SharePoint library columns. Ensure all mandatory columns have values in the respective files added for migrate.

<fieldname> must contain a metadata value or its corresponding library column must have a default value defined.

This field is defined to be a required field in SharePoint, meaning column value cannot be empty. Moreover, the default value of the column may also be empty. Ensure that a default value is specified for the required field in SharePoint or enter a value for this field in the corresponding file.

XPlica Server Agent version mismatch

Ensure XPlica application version matches with XPlica Server Agent version installed in the destination SharePoint Server. Ensure the same version of XPlica desktop application and XPlica Server Agent is used when Exporting the Created Date and Last Modified Date fields to SharePoint.

[Created Date], [Modified Date] could not be updated

Ensure XPlica Server Agent is installed and running in the destination SharePoint Server. XPlica will carry forward the two date fields to a SharePoint library residing in the SharePoint server in which XPlica Server Agent is installed.

[Created By], [Modified By] could not be updated

Ensure XPlica Server Agent is installed and running in the destination SharePoint Server. XPlica will carry forward the two user fields to a SharePoint library residing in the SharePoint server in which XPlica Server Agent is installed.

[Approval Status] could not be updated

Ensure XPlica Server Agent is installed and running in the destination SharePoint Server. XPlica will apply the approval status to a folder or file in the SharePoint library residing in the SharePoint server in which XPlica Server Agent is installed.

You must fill out all required properties before checking in this document.

Some of the required fields in a SharePoint library may be empty. Ensure all mandatory columns have values in the respective files added for migrate.

Permission migration related errors:
1. Could not add/update the group [Group_name]. The request failed with HTTP status 401: Unauthorized.
2. Could not add/update the permission level [Permission_level_name]. The request failed with HTTP status 401: Unauthorized.
3. Could not load associated roles for group [Approvers] The request failed with HTTP status 401: Unauthorized.
4. Could not add/assign roles to this item, Access denied. You do not have permission to perform this action or access this resource.

Ensure that the given user account has Full Control permission to manage the permission settings in the destination site collection.

User/Group [group_name] is not found

Check whether the reported group exists in the destination site collection. If it is a user name, ensure that the given user name exists in the corresponding SharePoint site or Active Directory domain.

Permission level [Permission_level_name] is not found

Check whether the reported permission level exists in the destination site collection.

Checkin operation failed

Check-in operation will fail, in case mandatory fields of SharePoint library do not have values (empty) provided to them at the time of check-in.

Checkout operation failed

Checkout operation will fail in case access is denied (or) file is already locked by some other user.

Content Type <name> could not be found in the library

Ensure that the specified content type is available in the destination SharePoint library.

Content Type '<content type name>' found in the library, but it is not a valid file content type

Ensure that the list content type is derived from a 'Document' parent content type in the SharePoint site.

Content Type '<content type name>' found in the library, but it is not a valid folder content type

Ensure that the list content type is derived from a 'Folder' parent content type in the SharePoint site.

The Microsoft Jet database engine cannot open the file '<file name>'. It is already opened exclusively by another user, or you need permission to view its data.

Ensure that the specified file is not currently in use / open by any other application or user. Close the file and try again (or) close and re-launch XPlica application.

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.

Ensure that the machine running XPlica has either Office 2007 System Suite or Office 2007 System Driver (Data Connectivity Components) installed.

Web / List / Content Type / Field could not be created.

Ensure XPlica Server Agent is installed in the target SharePoint server. This error may also occur if any dependencies such as features, templates etc., are not available in the target SharePoint site.

Unable to find the termset << termset name >> in the target SharePoint server.

Ensure that termset with the specified name exists in the target SharePoint server. You can also specify new termset available in target SharePoint server using Column Definitions template for the corresponding field.

No matching ShowField exists in the target user information list.

Ensure that Show field selected in the Person / Group column exists in the User Information List (http://sitecollectionurl/_catalogs/users) in the target site collection.

Unable to find the content type details for << content type name>> in the target SharePoint server.

Ensure external content type with the specified name exists in the target SharePoint server.