If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Issues after cognos conversion to 8.3

Started by dstruck, 09 Oct 2008 02:38:16 PM

Previous topic - Next topic

dstruck

We upgraded to 8.3 about 4 weeks ago.  Last Friday our content store went into a some what zombie state - the content store was still communicating with the other nodes but end users were getting a CAM-AAA-0071 error message when trying to login.  I recycled the serices on the boxes and this resolved the issue but we crashed again this past Tuesday.  Our log files are full of the below error messages

xmlns:bus="http://developer.cognos.com/schemas/bibus/3/">
               <severity>error</severity>
               <errorCode>cmHeaderFault</errorCode>
               <bus:message>
                  <messageString>CM-REQ-4159 Content Manager returned an error in the response header.</messageString>
               </bus:message>
            </bus:exception>
         </detail>
170.6.137.4:9300   2316   2008-10-03 14:40:45.148   -5               Thread-20   caf   692   2   Audit.dispatcher.caf   Request         Warning      received SOAP fault during capability check: details => <detail>
            <bus:exception xmlns:bus="http://developer.cognos.com/schemas/bibus/3/">
               <severity>error</severity>
               <errorCode>cmHeaderFault</errorCode>
               <bus:message>
                  <messageString>CM-REQ-4159 Content Manager returned an error in the response header.</messageString>

I have a ticket open with cognos but they have no idea what root cause is.  We took the 01 box out of rotation - put our 02 box in as the content manager and we just started seeing the same error messages start again on this box as well.  Any help would be awesome
   

John_Russell

Conversion to 8.3 from what prior version?

SomeClown


dstruck

Thanks for your response - we upgraded from 8.2

dstruck

Is the memory leak for IIS?  We are using websphere