Hi,
I've come across a weird problem since our upgrade to Cognos Series 7 Version 3. When I publish a PowerPlay cube to Upfront (from the PPES software installed on the PPES machine), it works fine. I can then access the cube and reports through upfront for the rest of the day. Then, the next morning, even though the cube file still exists exactly where it did when i published the cube, when i try and access the cube I published, and any associated reports from Upfront, I get the following message:
"The request failed because there is no valid cube mapping to handle the request"
However, if i go in through the PowerPlay web table of contents (instead of Upfront) and open the cube, it works fine, and something is happening that makes the upfront cube and reports work again permanently.
I've logged this with cognos but they were unable to provide an explanation, and i was wondering if anyone else had come across the same problem.
My cube has no model security applied, and the mdc file resides on the PPES server itself, so it isnt a network/firewall problem.
Any ideas??
J
I've come across a weird problem since our upgrade to Cognos Series 7 Version 3. When I publish a PowerPlay cube to Upfront (from the PPES software installed on the PPES machine), it works fine. I can then access the cube and reports through upfront for the rest of the day. Then, the next morning, even though the cube file still exists exactly where it did when i published the cube, when i try and access the cube I published, and any associated reports from Upfront, I get the following message:
"The request failed because there is no valid cube mapping to handle the request"
However, if i go in through the PowerPlay web table of contents (instead of Upfront) and open the cube, it works fine, and something is happening that makes the upfront cube and reports work again permanently.
I've logged this with cognos but they were unable to provide an explanation, and i was wondering if anyone else had come across the same problem.
My cube has no model security applied, and the mdc file resides on the PPES server itself, so it isnt a network/firewall problem.
Any ideas??
J