Hi Team,

I have installed Cognos Analytics 12.0.4 all components on two separate machines/servers. I have a single DB2 machine as content database.
1. cognosprod01 - primary
2. cognosprod02 - secondary

I have updated the two content manager URIs in the environment configuration.
1. https://cognosprod01:9300/p2pd/servlet
2. https://cognosprod02:9300/p2pd/servlet

I have updated the dispatcher URIs for gateways also as below.
1. https://cognosprod01:9300/bi/v1/disp
2. https://cognosprod02:9300/bi/v1/disp

When I'm starting the cognos services on both servers. Only prod01 is getting started properly. prod02 server get stuck at CM-REQ-2378 A request was received to start the negotiation process to determine which content manager instance should become active.

as of now each server has its own entry in Gateway URI field.

Content DB server is reachable from both server.

Cognos services start successfully on the server where I start them first, the second one goes into this error.

Do I need to configure HTTP server before I start the services on both cognos server and update the Gateway URI. So that cognos services comes up properly on each server?

OR

Do I need to exchange keys between these servers, so that they can communicate with each other. I'm using TLS1.2, HTTPS and Third Party Certificate Authority.

Or this error is because of something else?

Kindly guide me, if I need to so some other configuration.

Will follow this link to configure HTTP server (https://www.ibm.com/docs/en/cognos-analytics/12.0.x?topic=server-configuring-http-v9)

Issue is resolved after I exchanged the Certificate of servers with each other. Thank You.

Hi everybody, I'm getting error related to dispatcher now. dispatcher of second server is not getting registered in content manager.

Can anybody guide what I'm missing now in configuration.

Hard to judge what is actually happening without looking at logs.  But there are a few things it could be.  Here are some things to check:
1. Start Cognos on cognosprod01 first and wait until it is fully up.
Then start Cognos on cognosprod02.
On prod02, check cognosserver.log for messages like "unable to register with Content Manager". If you still see that, it almost always points back to keys or URIs not matching.

2. Verify the Content Manager URIs are identical on both servers
In Cognos Configuration on both prod01 and prod02, under Environment, the Content Manager URIs list should be exactly the same. For example.
https://cognosprod01:9300/p2pd/servlet
https://cognosprod02:9300/p2pd/servlet
Same order, same protocol, same host names that match the certificates.

3.Make sure both servers share the same Cognos encryption keys
It is not enough that the HTTPS server certificates trust each other. The Cognos "internal" crypto keys also have to match or the dispatcher will not register in the content store.

On the server that starts cleanly (cognosprod01):
Stop the Cognos service.
Open Cognos Configuration.
Use Tools > Export encryption keys (or similar wording in 12.0.4) and create the keys ZIP file with a deployment password.
Copy that ZIP to cognosprod02.

On cognosprod02:
Stop the Cognos service.
Open Cognos Configuration.
Use Tools > Import encryption keys, point to the ZIP from prod01, and enter the same deployment password.
Save the configuration.

Not sure any of that helps... but if it does great :)

-Daryl