IBM Support

Report execution sporadically fails with QFS-ERR-0141 error in a system which uses advanced routing for Dynamic Query Mode reports.

Troubleshooting


Problem

In a system using Dynamic Query Mode and Compatible Query Mode at the same time where the required advanced routing has been set up, still some reports intermittendly fail to execute and lead to an error. On subsequent executions the same report may work, the problem is not necessarily reproducible at will.

Symptom

Sporadically report execution leads to the following error being returned in Cognos Connection:
QFS-ERR-0141 This report service is configured as 64-bit and only supports packages published with the dynamic query mode.

Cause

The issue occurs due to an incomplete set of routing rules being defined.
When mixing Query Modes in a system, advanced routing is required to ensure that reports requiring Dynamic Query Mode (DQM) are routed to instances of Report Service which use the 64bit ReportServer execution Mode. If the remaining reports requiring Compatible Query Mode (CQM) don't get routed explicitly either, the Dispatcher by design is free to route them to any instance of ReportService available in the current Server Group including those using 64bit Report Server execution mode. In that case however, the report cannot be executed and the error QFS-ERR-0141 is returned.

Environment

The IBM Cognos BI system contains multiple installs of Application Tier components which run instances of Report Service. Those offer a mix of Report Server instances running in 32 ReportServer execution mode (CQM) and 64bit ReportServer execution mode (DQM). Advanced Routing has been set up for explicitly routing DQM package reports as follows:

Diagnosing The Problem

Review routing rules. Ensure a default route to a named server group is specified.

Resolving The Problem

To resolve the issue one must explicitly route reports requiring CQM as well. This is achieved by defining at least one additional server group containing Dispatchers only which run Report Service instances using 32bit ReportServer execution mode. This server group then gets referenced by additional routing rules for CQM packages.

For example, In IBM Cognos Administration for at least one Dispatcher running an instance of ReportService which uses the 32bit ReportServer execution mode specify its Server Group property. Implicitly define a new server group by providing a name for it in that property. In this example it's "BASE_SERVER".



Next append a new routing rule to the end of the list of defined routing rules. Routing rules are defined and processed in sequence, and once the first matching rule for a request is found no further rules are evaluated.
The new routing rule will act as a catch-all, default rule for all requests that don't match any of the preceding rules. To achieve this, the rule is defined to apply to any package run by users from any group and any role. The requests matching this rule will be routed to the new server group defined in the previous step.



Click OK to save the updated set of rules. Now run reports based on packages for CQM and ensure the issue does not occur any more.

This is only a very simple example of resolving this issue. The main point is to explicitly route requests for DQM and CQM. Whether each set of reports is routed to a single server group per query mode (M:1 mapping) or if the setup is more complex like mapping to several target server groups for each query mode (M:N mapping) is irrelevant for this issue as long as ALL requests get routed explicitly for systems which mix query modes.

For details about the IBM Cognos BI Dispatcher and its routing concepts, refer to the Document listed in the related URL section.

[{"Product":{"code":"SSEP7J","label":"Cognos Business Intelligence"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Cognos Connection","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.2;10.2.1;10.2.2","Edition":"Edition Independent","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2018

UID

swg21600737