Routing rules looks not to work for background reports

[Yoshick]

Hi Gurus.

Faces the following problem.
System:

• Cognos Analytics 11.0.10.18070608. Multiple instances working in 32-bit or 64-bit mode grouped into 2 server groups according to their bitness. Any dispatcher is in one or another server group.
  There are routing rules defined in the system that directs reports to corresponding server group. The last rule directs reports with no tags to the server group for 32-bit instances.
  

Run of any reports in interactive mode works fine, reports are routed to corresponding server groups.
But run of the report in background mode (Run as > Run in background > PDF or Excel) fails with a message:
The report service is configured as 64-bit and only supports packages published with the dynamic query mode

It is clear that routing rules for some reasons are ignored for batch report service.
There is a registered bug/defect IBM PH01027: QFS-ERR-0141 IN CQM REPORT PROMPTS WHEN ROUTING RULES ARE CONFIGURED with quite similar description. And recommended solution is upgrade to 11.0.13.
But the tricky thing is that another our environment with exactly the same kit version and same architecture and configuration parameters works fine.

I will much appreciate your welcome suggestions/assumptions/explanations on the issue or directions what and where to look more.

Thank you in advance for your valuable time.

Kind regards,
Yosh.

[Blue]

I am migrating a 10.2.1 system to a fresh 11.1.2 system. The routing rules and tags are identical.
But similar to Yosh, the CQM package reports are trying to run in the 64bit dispatcher ReportService! This is both background and interactive.
This is a big show stopper for the project.

[Yoshick]

Hi.

In our case interactive reports do respect routing rules.
As for 11.1.2 from posts on forums it is known as quite buggy. Probably it will be good to check the possibility to use 11.1.1.

Yosh.

[Blue]

Routing Rules issue fixed!
BUT it is a "feature" that has been address in the next release, 11.1.3. There is a hot fix on request if you have the same issue.