-
Titel
After changing the service account password the properties of Domain Pair cannot be accessed. Error {0} is shown -
Beschreibung
Error {0} popup is appearing when going into domain pair properties and setting credentials up after a service account password change.
-
Ursache
ADAM database is using cached credentials for the service account on the project.
-
Lösung
Resolve by clearing the data from ADAM - AMMProject_GUID | Projects | Project GUID | Properties. Attributes to clear:
Aelita-Amm-Extension,1 Aelita-Amm-Extension2, Aelita-Amm-Extension3, Aelita-Amm-Extension4,
It is tricky to clear these attributes. Please use the following steps:
-Click EDIT, which will display the attribute properties,
-Highlight the content and press Backspace to remove the entry,
-Click the Clear button before clicking OK
-Repeat the above steps to clear all 4 attributes,
-When clicking OK, you will encounter an error, so press Escape instead. The attributes will have been cleared successfully, regardless of clicking Escape instead of OK.IMPORTANT: After cleaning these attributes please start QMM, go to domain pair properties, specify the credentials for the source domain BUT DON'T click OK, switch to the target domain and specify the credentials for the target domain and only then click OK. This is the only way to make it work. Once these credentials cleared out in ADAM for both domain pairs, they need to be populated simultaneously, in one step. Full Directory Resync will be required then.
In some cases the ADAM Instance Service may have to be restarted.
Update: if error is still happening after populating both domains with correct credentials, it means that QMM is running an outdated version. Please upgrade QMM to at least latest 8.14 Hotfix or 8.15+.
It's possible that old QMM version is using no longer supported encryption type (non FIPS compliant) to store credentials in ADAM database, which are being rejected by domain.
-
Weitere Informationen
More keywords, because this SOL can never be found: error zero error null blank error error with no information error and a blank empty description error {0}