Hi @deetchiga ,

Is the issue solved, can you please let me know the reason?

Regards,
Sreeni.

Hi @dougp

Tried that too still same issue.

Regards,
Sreeni.

On the command line you use to call trigger.bat, have you tried putting quotes around the password?

Hi All,

We have setup trigger concept in our cognos vm, when we try to test it fails with below error:

Tried things:
1. Changed password from special characters to plain password(alpha numeric)
2. Tried service account tagged to system admin role
3. Also scheduling and run with options capability explicitly defined for sys admin.
4. Same service account able to login from Cognos UI.
5. Tried individual user access same below error.

So basically when we try to trigger it using trigger.bat we are facing this issue.

Please provide your thoughts.


AxisFault
faultCode: Client
faultSubcode:
faultString: CM-REQ-4342 An error occurred with the client.
faultActor:
faultNode:
faultDetail:
{http://developer.cognos.com/schemas/bibus/3/}exception:
<severity>error</severity>
<errorCode>caf</errorCode>

<ns1:message><messageString>CM-CAM-4005 Unable to authenticate. Check your security directory server connection and confirm the credentials entered at login.</messageString></ns1:message><ns1:message><messageString>CAF-WRN-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2026-03-03-05:07:49.245-#25</messageString></ns1:message>

CM-REQ-4342 An error occurred with the client.
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:610)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1718)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2883)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:605)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:534)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:888)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1216)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:635)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:324)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:698)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.cognos.developer.schemas.bibus._3.ContentManagerServiceStub.logon(ContentManagerServiceStub.java:8165)
at Trigger.login(Trigger.java:111)
at Trigger.main(Trigger.java:276)

Thanks for sharing your knowledge. That makes sense because Cognos would generate the SQL based on the recent version and every version of every programming language has some changes in the way it gets compiled by the compiler and subsequently executed by the database. I have spent quite a bit of time comparing the SQLs generated for the same report in different versions and found some changes.

I think the reports should be upgraded as a best practice, to inherit the newer features and to prevent them from stop working. 

My experience has been that report upgrades are typically not needed.  But I like to get new features -- like moving from 10 to 11 and enabling interactivity -- so that my users can have more streamlined workflows.  I also converted as much as I reasonably could from CQM to DQM to prepare for a possible move to the IBM Cloud.  One thing I have found is that any of these upgrades can cause problems.  Reports must be reviewed.  In my environment, with 12,000 reports, 3000 distinct users total, 250 distinct users per day, and hundreds or thousands of report runs per day, I let users do the "testing" in the normal course of their duties.  This works for me because I find that most report problems can be corrected quickly.  (Keep in mind that this is in the context of system upgrades.  Naturally, if we're making database changes, reports get tested before inflicting them on users.)

One thing I have seen -- and I think this relates to DQM -- is that performing multiple layers of calculations in a query can get a little sketchy.  An example is if you create a data item that summarizes another data item that is calculated from a third one that is sourced from an upstream query and use it as a filter.  While this type of thing worked flawlessly for years, I have found that some are failing in recent Cognos versions.  The solution is to break the steps into separate queries (Query1 -> Query2 -> Query3) to get the aggregation correct at each stage.

Hello everybody

We use IBM Cognos v.11.1.7

We have a main goal to optimize the Enterprise report system by dropping or editing schedules with very high frequency or with very large periods of dates. Now in our system there are 3140 schedules created by business users. The original reports are located in different folders. Usually, business users make a copy of the original report and save it in their own folders, and then create a schedule for that copy.

For that purpose, we use MotioPI third-part application - to find the schedule, its creator and the original name of the report, from which the copy was made.

But recently we faced a problem with a "deserialized object" — when the XML of the object becomes invalid and a third-party application cannot open it (while the native Cognos apps can open it without any problem).

Here is the description of the problem: https://support.motio.com/portal/en/kb/articles/motiopi-error


The question is — what can cause this error, and what can we do to prevent it?

Depends on the skills you have and what you are looking for. I see lot of job ads including ads allowing remote work. Definitely more opportunities than an year ago. Looks like Cognos is coming back up though Power BI still dominates. 

Found a good course from Texas A&M University. 6 month fully remote course, can be done in your own time and covers Python, ML and other things for becoming an AI developer. Going to start on it soon

I know this is a dead forum but posting this just in case..

I saw today's demo by Rachel Su ad wanted to ask if anyone has seen Agentic AI make metadata models and/or reports. She did not show that in the demo and I wonder if that AI can actually make reports without the need of a report developer? As everyone knows, most organizations do not have a self-service BI model and the packages they have allows only to pull the data which requires a developer. Can AI just take the data from the database and do the rest to be able to make the reports? Can AI make the metadata models from an ERP schema which is in the snowflake design?

The generative AI I have seen so far in google etc. scans the sites and interpretes the content like a human brain..