DPR-ERR-2056 The Report Server is not responding

[Sarge]

I'm getting the following error message intermittantly when running a scheduled report:

DPR-ERR-2056 The Report Server is not responding. Handler trace back: [the_dispatcher] com.cognos.pogo.handlers.performance.PerformanceIndicationHandler [the_dispatcher] com.cognos.pogo.handlers.logic.ChainHandler [service_lookup] com.cognos.pogo.handlers.engine.ServiceLookupHandler [load_balancer] com.cognos.pogo.handlers.logic.ChainHandler [lb_forwarder] com.cognos.p2plb.clerver.LoadBalanceHandler [batchreportservicechain] com.cognos.pogo.handlers.logic.ChainHandler [warptask_with_authenticate] com.cognos.pogo.handlers.logic.ChainHandler [do_batch_warp] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmtaChain] com.cognos.pogo.handlers.logic.ChainHandler [warptaskmta] com.cognos.pogo.reportservice.BatchReportServerHandler


Any ideas as to why and how to fix it?

[Evorus]

Sarge,

Did you search the forums for similar post's, franciepants queried this and found a resolution I believe

http://www.cognoise.com/community/index.php?topic=3299.0

Evorus

[josepherwin]

We got exactly the same issue. And as we are using Sybase, the proposed solution does not apply to us :(

the worst thing is, it doesnt even generate and dmp files that we can send to Cognos to investigate... it appears that the BiBus just died "elegantly"

[JoOne]

We get the same error from time to time. I have searched IBM Cognos Support for a resolution, finding a lot of stuff but I´m not sure which one that applies to our problem...

Maybe there can be something wrong with how the tuning of the environment is set up. We have two application servers functioning as report servers running on Win Server 2003.
Any help would be appreciated.

BR
Johan

[Sarge]

Sarge,

Did you search the forums for similar post's, franciepants queried this and found a resolution I believe

http://www.cognoise.com/community/index.php?topic=3299.0

Evorus

We use SQL Server therefore this solution doesn't apply. Like other on this thread I have found several posts with the same or similar issue, but very little by the way of a solution from IBM

[josepherwin]

after investigating this issue for a long long time (almost 6 months now), I think this is an issue with 8.4 in relation to distributed cognos installation.

In our environment, we got 3 app server, 1 content manager server, and 1 web server.

When I had a chat with the Cognos consultant, he suspect that the request may have been lost when parsing the request from 1 app server to another.

I'd actually wanted to test what would happen in a single installation of Cognos in one server. Unfortunately doesnt have the time and enough resource to do it as just yet.

[JoOne]

after investigating this issue for a long long time (almost 6 months now), I think this is an issue with 8.4 in relation to distributed cognos installation.

In our environment, we got 3 app server, 1 content manager server, and 1 web server.

When I had a chat with the Cognos consultant, he suspect that the request may have been lost when parsing the request from 1 app server to another.

I'd actually wanted to test what would happen in a single installation of Cognos in one server. Unfortunately doesnt have the time and enough resource to do it as just yet.

I think that it might be something related to this also. I have checked when the report failed and done some research in the Audit package. When trying to view the error details for the report in query studio, it doesn´t show any errors, and in the status column there is neither "Failed" nor "Success". Would this mean that the report is still executing? Then the report would be executed for a couple of hours, which is unlikely.

Our environment is distributed as well, so there might be some issues between the servers.

[Sarge]

Sorry to thow a spanner in the works guys but ours is a single server install, so don't think it is related to a distributed install.

Thanks for all the replies thus far

[Evorus]

Sarge,

May seem like a daft question but what is the status of the cognos firewall?

E

[josepherwin]

Sorry to thow a spanner in the works guys but ours is a single server install, so don't think it is related to a distributed install.

Thanks for all the replies thus far

There goes my theory :(

[fasi]

after investigating this issue for a long long time (almost 6 months now), I think this is an issue with 8.4 in relation to distributed cognos installation.

In our environment, we got 3 app server, 1 content manager server, and 1 web server.

When I had a chat with the Cognos consultant, he suspect that the request may have been lost when parsing the request from 1 app server to another.

I'd actually wanted to test what would happen in a single installation of Cognos in one server. Unfortunately doesnt have the time and enough resource to do it as just yet.

Do you got this to work :) if yes can you please let me know the solution ?

[fasi]

if you are saving reports on network.

if you have distributed servers you need to use fully qualified server location on primary app

in Cognos configuration > action > edit global config > general > archive location file://\\server name\c$\Reports


it resolved my issue.

[vcurams]

Sarge- Did you ever get resolution to this issue? We have to clean up our Scheduler every morning, at least one of our daily's will fail each day.  We've sent Cognos trace files etc, loaded the latest patch (for Cognos 8.4), nothing has resolved it.  Thanks!

[FM]

looks like a bug that might be fixed in cognos 8.4.1 fix list 1 and 2. (two different bugs causing the same error.)

[cr]

Hi Friends,

Since 2 months back even I have the same issue, contacted the Cognos support team. Based upon my environments they said servers are not property synchronizing , they suggested me to implement the latest fix pack in both the servers , I have done with that. My problem got resolved, just have look in to this solution also..

Note: This is a generic error in Cognos and depends on different issues Cognos is throwing the same error. In my case above is the solution might be helpful guys..

Keep smiling....
Chalapathi


Keep smiling....
Cr