Hi Vivien,

Hard to diagnose in french, but you need to make sure the FQDN is the same throughout.  The Configuration Group and Cryptography->Cognos tabs in Cognos Config are the likely culprits.  Check these and try it again.

-Todd

------------------------------
Todd Schuman
------------------------------

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.

Hi,

Just a few thoughts from me.

1.. Can you reach your dispatcher URI from the browser in your gateway? It might not be able to see it or communicate over port 9300. 

2.. I always use fully qualified domain names everywhere to rule out networking name issues. If I have to use netbios names I use them consistently not mixing FQDN and NETBIOS.

3.. As Todd mentioned you might have an issue with your server group settings, again i always go FQDN for those.

4.. The subject verification part references files on your dispatcher, when you save your config on the dispatcher does everything pass and give you a green tick. There is an issue with the PDF Algorithm files that needs to be patched which are in the same area but that might be a different issue.

Regards

Andy

------------------------------
Andrew Copeland
------------------------------


Original Message:
Sent: Thu December 24, 2020 09:15 AM
From: Vivien
Subject: Server name error when testing gateway cognos configuration

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.

Hi,

Just a few thoughts from me.

1.. Can you reach your dispatcher URI from the browser in your gateway? It might not be able to see it or communicate over port 9300. 

2.. I always use fully qualified domain names everywhere to rule out networking name issues. If I have to use netbios names I use them consistently not mixing FQDN and NETBIOS.

3.. As Todd mentioned you might have an issue with your server group settings, again i always go FQDN for those.

4.. The subject verification part references files on your dispatcher, when you save your config on the dispatcher does everything pass and give you a green tick. There is an issue with the PDF Algorithm files that needs to be patched which are in the same area but that might be a different issue.

Regards

Andy

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.

Hello,

as FDQN seems important in this setting, I create a ACtive Directory Domain Controller on a third VM.Then I add to this domain the 2 Cognos VM and update the setting with different parameters (below one of them), but still failed on gateway cognos configuration test.

On VM with Content Manager/App Tiers :

On VM with Gateway :

Hi,

Just a few thoughts from me.

1.. Can you reach your dispatcher URI from the browser in your gateway? It might not be able to see it or communicate over port 9300. 

2.. I always use fully qualified domain names everywhere to rule out networking name issues. If I have to use netbios names I use them consistently not mixing FQDN and NETBIOS.

3.. As Todd mentioned you might have an issue with your server group settings, again i always go FQDN for those.

4.. The subject verification part references files on your dispatcher, when you save your config on the dispatcher does everything pass and give you a green tick. There is an issue with the PDF Algorithm files that needs to be patched which are in the same area but that might be a different issue.

Regards

Andy

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.

Hi Vivien,

The DNS line in your CM Crypto->Cognos config looks odd.  It seems like you have multiple entries in here.  Just put only the FQDN for the specific server here (CM for CM, GW for GW).   Also, try and remove the IP from both servers as well as it can sometimes cause an issue.

------------------------------
Todd Schuman
------------------------------


Original Message:
Sent: Sat December 26, 2020 10:46 AM
From: Vivien
Subject: Server name error when testing gateway cognos configuration

Hello,

as FDQN seems important in this setting, I create a ACtive Directory Domain Controller on a third VM.Then I add to this domain the 2 Cognos VM and update the setting with different parameters (below one of them), but still failed on gateway cognos configuration test.

On VM with Content Manager/App Tiers :

On VM with Gateway :

Hi,

Just a few thoughts from me.

1.. Can you reach your dispatcher URI from the browser in your gateway? It might not be able to see it or communicate over port 9300. 

2.. I always use fully qualified domain names everywhere to rule out networking name issues. If I have to use netbios names I use them consistently not mixing FQDN and NETBIOS.

3.. As Todd mentioned you might have an issue with your server group settings, again i always go FQDN for those.

4.. The subject verification part references files on your dispatcher, when you save your config on the dispatcher does everything pass and give you a green tick. There is an issue with the PDF Algorithm files that needs to be patched which are in the same area but that might be a different issue.

Regards

Andy

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.

Hi Vivien,

I ran into same issue after upgrading to v11.1.7 FP2. I did a over the top install on 11.1.3 on a single server. IBM support suggested adding an ip/server name mapping entry in hosts file. The file will be located at: C:\Windows\System32\drivers\etc. After adding the entry, my issue was resolved. Good luck.

------------------------------
Vithal Madhira
------------------------------


Original Message:
Sent: Mon December 28, 2020 08:58 AM
From: Todd Schuman
Subject: Server name error when testing gateway cognos configuration

Hi Vivien,

The DNS line in your CM Crypto->Cognos config looks odd.  It seems like you have multiple entries in here.  Just put only the FQDN for the specific server here (CM for CM, GW for GW).   Also, try and remove the IP from both servers as well as it can sometimes cause an issue.

------------------------------
Todd Schuman


Original Message:
Sent: Sat December 26, 2020 10:46 AM
From: Vivien
Subject: Server name error when testing gateway cognos configuration

Hello,

as FDQN seems important in this setting, I create a ACtive Directory Domain Controller on a third VM.Then I add to this domain the 2 Cognos VM and update the setting with different parameters (below one of them), but still failed on gateway cognos configuration test.

On VM with Content Manager/App Tiers :

On VM with Gateway :

Hi,

Just a few thoughts from me.

1.. Can you reach your dispatcher URI from the browser in your gateway? It might not be able to see it or communicate over port 9300. 

2.. I always use fully qualified domain names everywhere to rule out networking name issues. If I have to use netbios names I use them consistently not mixing FQDN and NETBIOS.

3.. As Todd mentioned you might have an issue with your server group settings, again i always go FQDN for those.

4.. The subject verification part references files on your dispatcher, when you save your config on the dispatcher does everything pass and give you a green tick. There is an issue with the PDF Algorithm files that needs to be patched which are in the same area but that might be a different issue.

Regards

Andy

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.

Hi Vivien,

The DNS line in your CM Crypto->Cognos config looks odd.  It seems like you have multiple entries in here.  Just put only the FQDN for the specific server here (CM for CM, GW for GW).   Also, try and remove the IP from both servers as well as it can sometimes cause an issue.

------------------------------
Todd Schuman
------------------------------


Original Message:
Sent: Sat December 26, 2020 10:46 AM
From: Vivien
Subject: Server name error when testing gateway cognos configuration

Hello,

as FDQN seems important in this setting, I create a ACtive Directory Domain Controller on a third VM.Then I add to this domain the 2 Cognos VM and update the setting with different parameters (below one of them), but still failed on gateway cognos configuration test.

On VM with Content Manager/App Tiers :

On VM with Gateway :

Hi,

Just a few thoughts from me.

1.. Can you reach your dispatcher URI from the browser in your gateway? It might not be able to see it or communicate over port 9300. 

2.. I always use fully qualified domain names everywhere to rule out networking name issues. If I have to use netbios names I use them consistently not mixing FQDN and NETBIOS.

3.. As Todd mentioned you might have an issue with your server group settings, again i always go FQDN for those.

4.. The subject verification part references files on your dispatcher, when you save your config on the dispatcher does everything pass and give you a green tick. There is an issue with the PDF Algorithm files that needs to be patched which are in the same area but that might be a different issue.

Regards

Andy

Hello team,

I still facing the issue with Cognos 11.1 R7 FP2

I install Cognos CM/App on a windows VM named : WIN-P3AB9LBKJ83

Cognos on WIN-P3AB9LBKJ83  start well and works fine.

Then I install Cognos Gateway on a windows VM named : Cognos-GTW

I open Cognos Configuration to configure Cognos :)

But when I test configuration I got this message :

note : it will appear only the first time Cognos Configuration is open and until configuration will be saved. After save configuration no more error message will be displayed.