Troubleshooting

This page lists known errors that can occur when running the Project Online to Altus migration scripts, and how to resolve them.

"You cannot run this script on the current system"

Issue. The error appears as soon as you try to run any of the migration scripts.

Resolution. Open the script file > Properties > tick Unblock > Apply. Repeat for each blocked script. (Unblocking the source .zip before extraction usually avoids this — see Migration Process § 1.)

Export Project Online data — CO_E_SERVER_EXEC_FAILURE

Issue. The export script fails with CO_E_SERVER_EXEC_FAILURE.

Resolution. Try the following in order:

1. Close MS Project and re-run the script.
2. Close SharePoint Online Management Shell and re-run the script.
3. Restart your laptop and re-run the script.

"Running scripts is disabled on this system"

Issue. PowerShell refuses to execute the script because the execution policy disallows it.

Resolution. In PowerShell, run:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process -Force

"No files found matching project_*_published.mpp"

Issue. The schedule publish script reports no files found matching 'project_*_published.mpp' under files folder.

Resolution. Move the exported .mpp and matching .json files into 2.Project-and-Resource-Migration\Files before running Publish-MPPsToAltus.ps1.

MS Project not open

Issue. The schedule migration script errors because MS Project is not open / not connected to Altus.

Resolution. Open MS Project, sign in via the Altus tab, and connect to the target Altus environment as described in Migration Process § 8. Then re-run the script.

"Application with identifier was not found in the directory"

Issue. A script fails because the supplied ClientId does not exist in the target Project Online tenant.

Resolution. Confirm you have copied the ClientId correctly. If you are using your own Azure App Registration, double-check the value on the Overview page in Microsoft Entra ID. See Altus POL Migration SharePoint App.

Project Open = Deny

Issue. Running the export scripts produces an error mentioning FileOpenEx and a permission denied state.

Cause. The Project Open PWA permission is set to Deny for the executing account.

Resolution. In PWA Settings, change the Project Open permission to Allow and re-run the export scripts.

Error accessing REST API (UnauthorizedAccessException)

Issue. When exporting lookup tables you see:

Error accessing Project Server REST API: {"odata.error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Attempted to perform an unauthorized operation."}}}
Make sure you're connected to a Project Online PWA site.

Cause. Inadequate Project Online account permissions or an incorrect ClientId.

Resolution.

1. Confirm the executing account has the permissions described in Prerequisites § Create accounts.
2. Confirm the ClientId matches the application created via Altus POL Migration SharePoint App.
3. Update the script with the correct ClientId and re-run.

Renamed project that hasn't been published

Issue. When the export scripts are run, an error is returned and the draft version of the schedule is not exported.

Cause. The project was renamed in MS Project but never published back to Project Online.

Resolution.

1. Open the project.
2. Rename it.
3. Publish the project.
4. Close and check in the project.
5. Re-run the export.

Script currency issue

Issue. When the schedule migration script runs, it stops with a currency mismatch error and schedules are not migrated.

Cause. The Project Online and Altus environments are using different currencies and the script has not been told which one to use.

Resolution. Pass -ProjectCurrency set to the appropriate currency.

Example:

.\Publish-MPPsToAltus.ps1 `
  -BaselineNumber 0 -IsReportable $true `
  -Path "<path>\2.Project-and-Resource-Migration\Files" `
  -ProjectCurrency "AUD"

Issues connecting to Altus via MS Project

Issue. When trying to connect to Altus from MS Project, none of the target environments are listed.

Cause. Altus for Project is auto-logging in to the last environment you connected to.

Resolution.

1. Open MS Project.
2. Open the Altus tab > Linked Project Info.
3. Change Account Prompt to Prompt to select account > OK.

You will then be prompted to choose your account the next time you select Connect to Altus.