-
Titre
Installation name on our SCP(xxxxxx) is different from the configured installation name (DEFAULT). -
Description
Trying to open the Client and there is an error message.
'There was an error connecting to the coordinator service. Check the client log for errors'.
Checking the Coordinator status it is noted that the Coordinator is not started. Attempting to start the Coordinator fails, and checking the Coordinator log the error
"[ERROR] Installation name on our SCP (NEW) is different from configured installation name (DEFAULT). Aborting coordinator." -
Cause
The installation name stored in the Coordinator Service Connection Point (SCP) objects differs then what is the expected installation name.
This can occur if the Coordinator is installed with the wrong installation name configured during the installer.
-
Résolution
1. Confirm the expected installation name within the ChangeAuditor database:
SELECT [PropKey],[PropValue]FROM [dbo].[SystemProperty]Where PropKey='InstallationName'2. Uninstall the Coordinator and re-install with the correct SQL/Database settings and the installation name returned by the query.
3. The Coordinator should now start properly.
Should the error persist regarding the SCP objects...
1. Open ADSIEDIT and browse to the computer object for the Change Auditor Coordinator and delete the SCP child-objects themselves:
CN=Dell.ChangeAuditor.Repository,CN=Server1,CN=Computers,DC=domain,DC=comCN=Dell.ChangeAuditor.Coordinator,CN=Sever1,CN=Computers,DC=domain,DC=com2. Remove the Coordinator Service Principal Name (SPN) from the computer object itself:
CN=Server1,CN=Computers,DC=domain,DC=comAttribute name: servicePrincipalNameAttribute value: NPRepository4(INSTALL_NAME)/Server1.domain.dom3. Wait for or force replication to occur.
4. Start the Coordinator
5. Should start normally now.
Quest does not provide support for problems that arise from improper modification of objects using ADSI Edit. The following statement about ADSI Edit was taken directly from Microsoft TechNet:
ADSI Edit acts as a low-level editor for Active Directory. By using ADSI Edit, administrators can view all objects (and associated properties) in the directory (including schema information), modify objects, and set access control lists on objects. If you use the ADSI Edit snap-in and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems.