Have you tried to rename a company (from the Companies page or from PowerShell (Rename-NAVCompany cmdlet) in Microsoft Dynamics NAV 2018 and you get this error: “The task cannot be run because the user account that is assigned to run the task has been altered”, you are hit by a side effect of a new Service Tier Setting.
A quick google of the error message yields a few results – especially this one: https://forum.mibuso.com/discussion/72652/job-queue-with-task-scheduler-and-user-id… which suggest that it has something to do with the Service Tier Setting “EnableUserConsistencyValidationOnTasks”.
If we look at Microsoft description of that Service Tier Setting at https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/configure-server-instance, we see this description:
Specifies whether user consistency checks are done on tasks. Setting this to true helps guard against impersonation of users in tasks. When enabled, only the user who created the task can edit the task. If a task is edited by different user account, an error similar to the following occurs: The task cannot be run because the user account that is assigned to run the task has been altered. The task has been canceled.
Dynamically Updatable: No
…so if this protection is not important to you – you can easily work around the error by setting this key to false. If this protection is important to you, you should off cause just set it to false while renaming the company and then set it back to true again.
Have a Merry Christmas and a Happy New Year!