Share
Report
119I kind-of-solved an issue I encountered and which cost me a lot of time (others would have been faster, I am sure), so I want to share my solution (since I did not find much on the web on that particular issue), and ask if there maybe is a better one around.
My problem was:
When installing any binary update to a specific existing customer-side AX 2012 R2 installation, I received an error when updating the AOS component.
The setup log simply said, "Fehler beim Setup von 'Anwendungsobjektserver (AOS)'.", which would translates to "Error in setup of 'application object server (AOS)'".
In file "C:\ProgramData\Microsoft\Dynamics AX\Dynamics AX Setup Logs\yyyy-mm-dd hh-mm-ss\ObjectServer64 (01-aosname) Log.txt", I noticed this error:
Error 1609. An error occurred while applying security settings. VORDEFINIERT\Benutzer is not a valid user or group. This could be a problem with the package, or a problem connecting to a domain controller on the network. Check your network connection and click Retry, or Cancel to end the install. Unable to locate the user's SID, system error 1332
"VORDEFINIERT\Benutzer" translates to BUILTIN\USERS.
My solution was:
I changed the registry string HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.0\01\Original (installed configuration)\SetupProperties\LOCALIZED_BUILTIN_USERS from VORDEFINIERT\Benutzer to another, existing group (in my case, domainname\Domänen-Benutzer, which would translate to domainname\domain-users)
Afterwards, installations of updates of AOS were working.
My question to the forum is:
Is there a better solution? I do not know too much about these Builtin-groups. Maybe some problem with the group, maybe some problem on sql (as I think that this is why AX would care in the first place.)
All responses (
Answers (
