5
The pre-configured system account "axrunner" is created with an empty user name in the "user" form.
After a database copy you will not be able to enable this user, if it were disabled. There will be an error message saying:
"Field 'User name' must be filled in."
When then trying to update the user name with the value "AXRunner", a new error message pops up:
"Cannot edit a record in User Information (UserInfo). The corresponding AOS validation failed."
So the solution is to post a service request to Microsoft asking for activation of this user.
My suggestion is to always create a user name for user ID "axrunner". And insert a user name for "axrunner" if it is missing.
System account:
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/sysadmin/pre-configured-system-accounts
After a database copy you will not be able to enable this user, if it were disabled. There will be an error message saying:
"Field 'User name' must be filled in."
When then trying to update the user name with the value "AXRunner", a new error message pops up:
"Cannot edit a record in User Information (UserInfo). The corresponding AOS validation failed."
So the solution is to post a service request to Microsoft asking for activation of this user.
My suggestion is to always create a user name for user ID "axrunner". And insert a user name for "axrunner" if it is missing.
System account:
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/sysadmin/pre-configured-system-accounts
STATUS DETAILS
Needs Votes
Comments
This is an additional problem if you have code that is searching for a userID based on a name match in an external system, and happen to search with an empty string, axrunner will be returned.
Category: System administration