How to solve "Could not set content file... / No valid folders to scan" error?

Users often configure the migration-center jobs to store and load the content files from file shares, e.g. "\\server\share\folder\content.pdf". The migration-center jobs are executed in the context of the "Migration Center Job Server" Windows service. This service usually runs under the built-in "Local System" account, which has no access to network file shares. As a result, you will see the following or similar error messages in the job run log file: "No valid folder to scan" or "Could not set content file...".

To solve the issue, please follow these steps:

  1. If not available, create a service account in your Windows domain and grant access permission for the network file share to it.
  2. Login to the migration-center job server machine with that domain service account.
  3. Change the user account of the "Migration Center Job Server" service to the domain service account.
  4. Restart the "Migration Center Job Server" service and run your migration-center job again.

You could also use a local service account and add appropriate credentials for the network file share in the Windows Credential Manager:

  1. Login to the migration-center job server machine and create a local service account.
  2. Login as the local service account.
  3. Set in the Windows Credential Manager the credentials for accessing the network file share.
  4. Change the user account of the "Migration Center Job Server" service to the local service account.
  5. Restart the "Migration Center Job Server" service and run your migration-center job again.
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.