I think IBM support is the right place for this issue. We also found that restarting Cognos provides temporary relief but issues come back. As well that the issue doesn't seem to be confined to credentials / login. We saw the same error combinations and similar behaviors with with groups getting 'locked-up' (CM-REQ-4036, CM-REQ-4192 and ADMIN-GEN-0001). Once the issue starts seems to fail consistently in the UI as well as with API calls until CA is restarted. Best Paul
Original Message:
Sent: Tue May 19, 2026 06:08 AM
From: Dhanush
Subject: Issues After Upgrading to Cognos 12.1.1 – Share Your Experience
Hi Paul,
Thankyou very much for your response. We have informed Cognos support and awaiting their response.
We did notice that issue surface again after restart, where User who was not able to create session, after restart, session creation was successful , but then issue came up after few days of restart.
Thanks!
------------------------------
Dhanush
------------------------------
Original Message:
Sent: Mon May 18, 2026 10:07 PM
From: Paul Hulford
Subject: Issues After Upgrading to Cognos 12.1.1 – Share Your Experience
Hi Dhanush,
We also just ran into what sounds like the same issue after upgrade to 12.0.4 IFP4 and have been working on determining the cause the last few days. Everything so far points to a CA defect. We have one new test case from development that we intend to run in production tomorrow. Once we run this will share the test case and our result. Our next step will be to try our test case against the recently released 12.0.4 FP2 to see if the issue has already been fixed.
Best Paul
------------------------------
Paul Hulford
paul.hulford@attaininsight.com
Attain Insight - IBM Business Partner
Original Message:
Sent: Mon May 18, 2026 09:37 PM
From: Dhanush
Subject: Issues After Upgrading to Cognos 12.1.1 – Share Your Experience
Hi Jeam,
We do face this issue where we get an error as CM-REQ-4036.
We did not delete the CMID of affected user, but it did not help.
This does not happen for the first time login. User have been using the system after upgrade to Cognos 12.0.4, but all of a sudden session creation is failing.
We have multiple cognos environments (100+) and we have started receiving error in 10+ environments. We use Custom Authentication Provider, where it works for 90% of users while it is failing for 10% of user.
Once Cognos Content manager is restarted (complete restart and not through UI), User is able to succesfully login.
Has any found a solution for this issue?
Thanks!
------------------------------
Dhanush
Original Message:
Sent: Mon January 12, 2026 04:21 PM
From: Jeam Coelho
Subject: Issues After Upgrading to Cognos 12.1.1 – Share Your Experience
Hi
The following UPDATE SQLs should resolve the issue for Db2 content Store
1. Update names to make them unique. You can pick a different string to separate original name
and CMID. Note that resulting name must match OBJD that will be assigned in the
second query.
db2 "update CMOBJNAMES set NAME=(NAME CONCAT '---' CONCAT CAST(CMID as VARCHAR))
where CMID in (select d1.CMID from CMOBJPROPS1 d1 inner join
CMOBJPROPS1 d2 on d1.OBJID = d2.OBJID and d1.CMID != d2.CMID where d1.OBJID is not null )" ; db2 commit;
2. Update OBJIDs to make them unique. Make sure that new ID would never be used by namespace provider.
db2 "update CMOBJPROPS1 set OBJID=(OBJID CONCAT '---' CONCAT CAST(CMID as VARCHAR))
where CMID in ( select d1.CMID from CMOBJPROPS1 d1 inner join CMOBJPROPS1 d2 on d1.OBJID = d2.OBJID and d1.CMID !=
d2.CMID where d1.OBJID is not null)" ; db2 commit;
------------------------------
Jeam Coelho
Cognos Solution Architect
IBM Champion
LinkedIn: https://www.linkedin.com/in/jeamcoelho/
Original Message:
Sent: Thu December 18, 2025 07:53 AM
From: Sławomir Zawiślak
Subject: Issues After Upgrading to Cognos 12.1.1 – Share Your Experience
Hello Jeam,
Thank you for the helpful query - it's a known issue in Cognos 12.0.4.In our environment (12.1.0), some users encounter the error "CM-REQ-4036 The object already exists at this location" during login attempt. We ran the diagnostic SQL you provided against our content store, and here are the results:
Query | Count |
|---|
query 1 | 16 |
query 2 | 16 |
cs lock | 1 |
Could you please share the procedure (or the specific SQL updates/scripts) to clean up these duplicates and resolve the lock issue in our environment?
Thank you in advance for your assistance!Best regards,
------------------------------
Sławomir Zawiślak
Original Message:
Sent: Mon November 10, 2025 03:30 PM
From: Jeam Coelho
Subject: Issues After Upgrading to Cognos 12.1.1 – Share Your Experience
Hi,
We have a quite same issue "CM-REQ-4159" in 12.0.4. It's an old problem.
But, in our case, the first time that user try to login, get this error. So, we need to restart CM to solve.
Theres a SQL that you can run against your content store database to check if there are some problems with AD folders also. If counts >1, there a procedure that you can do in your environment to fix, some SQL updates.
select 'query 1' query, count(*) qtdfrom CMOBJNAMESwhere CMID in (select d1.CMID from CMOBJPROPS1 d1 inner joinCMOBJPROPS1 d2 on d1.OBJID = d2.OBJID and d1.CMID != d2.CMID where d1.OBJID is not null )union select 'query 2', count(*) qtdfrom CMOBJPROPS1where CMID in ( select d1.CMID from CMOBJPROPS1 d1 inner join CMOBJPROPS1 d2 on d1.OBJID = d2.OBJID and d1.CMID !=d2.CMID where d1.OBJID is not null)unionselect 'cs lock', count(*) qtd from CMCAPACITY where USAGE=4
------------------------------
Jeam Coelho
Cognos Solution Architect
IBM Champion
LinkedIn: https://www.linkedin.com/in/jeamcoelho/