11.2.1 -> DPR-ERR-2072 when testing any SQL data source - JDBC works fine

[gohabsgo]

Hey Folks,
Small background;
We're in the process of migrating all of our Cognos installations to our Azure Cloud and we're seeing the following behavior.

When we validate any data source connection (even just the audit db) we see the following error thrown

DPR-ERR-2072 Unable to load balance a request with absolute affinity, most likely due to a failure to connect to the remote dispatcher.

The JDBC connection configured on the same data source is successful in all cases.
'
When I monitor the processes I see the BmtMDProviderMain.exe spawn (this is the process that performs db connection issues) but then it immediately suspends and closes.

When I check the event.log on the server I see the following application errors;

Faulting application name: BmtMDProviderMain.exe, version: 11.2.1.503, time stamp: 0x60f0817c
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x51d4b57a
Exception code: 0xc0000409
Fault offset: 0x000a3fa2
Faulting process id: 0x1f4
Faulting application start time: 0x01d8bd6bc1dc27b8
Faulting application path: C:\Program Files\ibm\cognos\analytics\bin\BmtMDProviderMain.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 95787a8d-6361-4579-b533-f1e81b2aa1e5
Faulting package full name:
Faulting package-relative application ID:

We have 11.2.1 up and running without issues in our current on-prem systems, so it's something specific to this new Cloud solution.

Could it be something network/firewall related I wonder?

[MFGF]

Hey Folks,
Small background;
We're in the process of migrating all of our Cognos installations to our Azure Cloud and we're seeing the following behavior.

When we validate any data source connection (even just the audit db) we see the following error thrown

DPR-ERR-2072 Unable to load balance a request with absolute affinity, most likely due to a failure to connect to the remote dispatcher.

The JDBC connection configured on the same data source is successful in all cases.
'
When I monitor the processes I see the BmtMDProviderMain.exe spawn (this is the process that performs db connection issues) but then it immediately suspends and closes.

When I check the event.log on the server I see the following application errors;

Faulting application name: BmtMDProviderMain.exe, version: 11.2.1.503, time stamp: 0x60f0817c
Faulting module name: ucrtbase.dll, version: 10.0.17763.1490, time stamp: 0x51d4b57a
Exception code: 0xc0000409
Fault offset: 0x000a3fa2
Faulting process id: 0x1f4
Faulting application start time: 0x01d8bd6bc1dc27b8
Faulting application path: C:\Program Files\ibm\cognos\analytics\bin\BmtMDProviderMain.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 95787a8d-6361-4579-b533-f1e81b2aa1e5
Faulting package full name:
Faulting package-relative application ID:

We have 11.2.1 up and running without issues in our current on-prem systems, so it's something specific to this new Cloud solution.

Could it be something network/firewall related I wonder?

Hi,

Just to be clear, you're saying that any Compatible Query data sources produce the error, but any Dynamic Query sources work ok?

What specific type(s) of data source connection are you using? SQL Server, Oracle, DB2 etc

Have you made sure that the 32-bit version of the client libraries for your database has been installed on the Azure server? Are they the correct version for the version of the database you are trying to connect to? Are the ports the client libraries use open between the Azure server and wherever the databases live (or are they on the same server)?

The event log is showing issues from Framework Manager - BmtMDProviderMain.exe is the executable for FM. Have you looked in cognosserver.log to see what Cognos is logging? My guess is you might get more details from there, which might help pinpoint what Cognos is unhappy about.

Cheers!

MF.

[gohabsgo]

Hi MF, thanks for responding, Answers inline;

Hi,

Just to be clear, you're saying that any Compatible Query data sources produce the error, but any Dynamic Query sources work ok?

Correct, exactly this

What specific type(s) of data source connection are you using? SQL Server, Oracle, DB2 etc

SQL Server

Have you made sure that the 32-bit version of the client libraries for your database has been installed on the Azure server? Are they the correct version for the version of the database you are trying to connect to? Are the ports the client libraries use open between the Azure server and wherever the databases live (or are they on the same server)?

I have the the 32bit libraries installed, correct version vs sql 2019 and ports are opened

The event log is showing issues from Framework Manager - BmtMDProviderMain.exe is the executable for FM. Have you looked in cognosserver.log to see what Cognos is logging? My guess is you might get more details from there, which might help pinpoint what Cognos is unhappy about.

We dont have Framework Manager installed, this process is used when you make a datasource connection, take a look at your running processes and you'll see it.  If you have task manager open and watching the processes, if you test any data source connection you will see it fire up and tick away, in our case it starts up, then immediately fails.

The cognosserver.log shows the following, aside from the 2072 error that is presented in the UI;

dpr-errr-2105 the dispatcher was unable to communicate with the report server with pid {0}. (this is a single server deployment)

One other thing I'm focused on is the event log reference to ucrtbase.dll, apparently this is related to microsoft visual c++ Redistributable packages?

This the only difference I can see between our working 11.2.1 onprem servers that are working just fine, and the azure ones that aren't -> The azure ones are missing those packages completely.  Could this be an issue?  Are these required by the product?

Cheers!

MF.

Thanks!
-D

[MFGF]

Hi MF, thanks for responding, Answers inline;

Hi,

Just to be clear, you're saying that any Compatible Query data sources produce the error, but any Dynamic Query sources work ok?

Correct, exactly this

What specific type(s) of data source connection are you using? SQL Server, Oracle, DB2 etc

SQL Server

Have you made sure that the 32-bit version of the client libraries for your database has been installed on the Azure server? Are they the correct version for the version of the database you are trying to connect to? Are the ports the client libraries use open between the Azure server and wherever the databases live (or are they on the same server)?

I have the the 32bit libraries installed, correct version vs sql 2019 and ports are opened

The event log is showing issues from Framework Manager - BmtMDProviderMain.exe is the executable for FM. Have you looked in cognosserver.log to see what Cognos is logging? My guess is you might get more details from there, which might help pinpoint what Cognos is unhappy about.

We dont have Framework Manager installed, this process is used when you make a datasource connection, take a look at your running processes and you'll see it.  If you have task manager open and watching the processes, if you test any data source connection you will see it fire up and tick away, in our case it starts up, then immediately fails.

The cognosserver.log shows the following, aside from the 2072 error that is presented in the UI;

dpr-errr-2105 the dispatcher was unable to communicate with the report server with pid {0}. (this is a single server deployment)

One other thing I'm focused on is the event log reference to ucrtbase.dll, apparently this is related to microsoft visual c++ Redistributable packages?

This the only difference I can see between our working 11.2.1 onprem servers that are working just fine, and the azure ones that aren't -> The azure ones are missing those packages completely.  Could this be an issue?  Are these required by the product?

Cheers!

MF.

Thanks!
-D

Hi,

Interesting! The CQM engine is the only remaining part of the Cognos architecture that is written in C++, so it's possible the C++ packages not being there is causing an issue. I'd probably look at installing them if you can.

One other sanity-check also. You don't have the Report Service set to the 64-bit configuration, do you? This stops Compatible Query from working and limits you only to Dynamic Query, which is 64-bit.

Cheers!

MF.