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

Cognos 10 Migration - Trigger Issue

Started by vinooraps, 16 Sep 2013 11:23:55 AM

Previous topic - Next topic

vinooraps

Hi,

I am trying to trigger a Cognos schedule from Unix server in Cognos 10.1, I am getting the below error message while triggering the schedule.

Please note that i am successfully triggering the schedule in my current Production environment Cognos 8.4.1.

Also all the permission to the schedule and the folders have been provided similar to Cognos 8.4.1 in Cognos 10.1

CNC-BAL-0507 There was an error communicating with Content Manager. Consult the log files
CNC-SEC-3402 Security Error: The current user does not have the necessary privileges for the request.

Error Message
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: CNC-BAL-0503 The Client has failed.
faultActor:
faultNode:
faultDetail:
        {http://developer.cognos.com/schemas/bibus/3/}exception:<ns1:severity>error</ns1:severity><ns1:errorCode>CNC-BAL-0502 Error Number: 3402
                        </ns1:errorCode><ns1:message><ns1:messageString>CNC-BAL-0507 There was an error communicating with Content Manager. Consult the log files.</ns1:messageString><ns1:nestingLevel>0</ns1:nestingLevel></ns1:message><ns1:message><ns1:messageString>CNC-SEC-3402 Security Error: The current user does not have the necessary privileges for the request.</ns1:messageString><ns1:nestingLevel>1</ns1:nestingLevel></ns1:message>

CNC-BAL-0503 The Client has failed.


Please let me know if there is any solution for this

Grim

"Honorary Master of IBM Links"- MFGF
Certified IBM C8 & C10 Admin, Gamer, Geek and all around nice guy.
<-Applaud if my rant helped! 8)

vinooraps

All the steps mentioned in the lBM link have been implemented already, still facing the issue.
The set up has been done similar to Cognos 8.4.1 in Cognos 10.1, we never faced this issue in Cognos 8.4.1.

sunny_cu

were you able to fix this? Please let me know, I not seeing issues running triggers in one environment and seeing issues in other environments. not sure why...