"Cannot register engine due to mismatch in connection to the repository parameter: repository.storage.host" (4375245)

"Cannot register engine due to mismatch in connection to the repository parameter: repository.storage.host"

Messages like the following appear in database agent log files for SQL PI where the current value for repository.storage.host differs from a previous value. The current value and engine value be two different servers or the same server but one entry includes the FQDN (Fully Qualified Domain Name).

ERROR [AGENTNAME-lowPriorityPool-1-[DBSS_PI_Engine_Maintenance][]] com.quest.qsi.fason.sqlserver.common.spi.BaseSpiController - Failed to initialize SQL PI engine
java.lang.RuntimeException: Cannot register engine due to mismatch in connection to the repository parameter: repository.storage.host. Current value: [MYSERVERB], engine value: [MYSERVERA]

or

ERROR [AGENTNAME-lowPriorityPool-1-[DBSS_PI_Engine_Maintenance][]] com.quest.qsi.fason.sqlserver.common.spi.BaseSpiController - Failed to initialize SQL PI engine
java.lang.RuntimeException: Cannot register engine due to mismatch in connection to the repository parameter: repository.storage.host. Current value: [MYSERVER.MYDOMAIN.COM], engine value: [MYSERVER]
 

The SPIRepository or DBSS-SPIRepository agent was deleted and then recreated when (rather than using the restore agents script) the PI extension was added back with different connection values. After this change, agents where the PI extension was newly added will use the newer connection details to the PI repository host while the agents added earlier will use the original values. It is important for users to re-enter in the correct repository connection details (if prompted) when adding the PI extension to addition agents on the same FglAM.

NOTE: When the FglAM restarts it uses the hostname from the first agent that starts up causing the other agents with the different value to display this message. Some of the PI agents may work because they have the correct connection values while others on the same FglAM will not work.

This may occur for example when the DBSS-SPIRepository agents were deleted during the HA process

The following groovy script when run through Script Console will list the SQL Server database agents and the PI repository that each is associated with. This can be adjusted for other cartridges and can be used for the investigation.

def out = new StringBuilder();
def agentService = server.get("AgentService");
def configService = server.get("ConfigService");
def agents = agentService.findByAdapterAndType("FglAM", "DB_SQL_Server");
out.append(String.format("FglAM ID, Agent Name, Repository Host, Repository Database, Monitored Key, Enabled, Monitoring Key, Paused\n"));
for (agent in agents) {
    def primaryASP = configService.getAgentInstancePrimaryAsp(agent.getAgentNamespace(), agent.getTypeId(), agent.getId());
    if (primaryASP) {
        out.append(String.format("%s, %s, %s, %s, %s, %s, %s\n", agent.getRemoteClientId(), agent.getName(), primaryASP.getString("parcStorageHost"), primaryASP.getString("parcStorageDatabase"), primaryASP.getString("paecEnable"), primaryASP.getString("paecMonitoredKey"), primaryASP.getString("paecPaused")));
    }
}
 
return out.toString();

 

The SPIRepository agents and the database agents have their mappings mixed up because the wrong hostname was entered. To resolve this issue for SQL Server agents (as an example).

1). Disable the PI extension from all SQL Server agents (Select the SQL Server tab in Databases | Select All agents | Enter the PI Admin panel | disable the PI extensions for all SQL Server agents)

2). In Agent Status, delete the SPIRepository agents 

3). Enable the PI extension from all SQL Server agents (Select the SQL Server tab in Databases | Select All agents | Enter the PI Admin panel | enable the PI extensions for all agents. When you try to enable PI it will prompt for the database connection information. Enter in the correct PI repository host and then choose the correct database to connect back to. These new values will be associated for all of the agents on each FglAM.

These steps can be used similarly for other database cartridges.