When you create a new report, it does not show up in the tree view of the DSM Reporter.
The Report creation may appear to succeed, but the new report does not get added correctly.
REPORTER |Reporter | |000000|WARNING| ADO Version 6.1 - COM Error: ErrorCode:-2147217873,WordErrorCode:3119, IDispatch error #3119, Violation of PRIMARY KEY constraint 'XPKrptree'. Cannot insert duplicate key in object 'dbo.rptree'. The duplicate key value is (0x00000000000000070000000000000000)., Microsoft SQL Server Native Client 11.0, (null)
REPORTER |CDb |CDb.cpp |000738|DETAIL | Create Recordset
REPORTER |RecImpl_Ado |RecImpl_Ado.cpp |000205|INFO | CRecImpl_AdoCreate() enter - (SELECT * FROM RPVIEW WHERE TPLID=-1 AND VIEWID=0) (3 3 3)
CA Client Automation - All Versions
There might not be any error message when creating report but the report never got saved correctly in the database.
If this is consistent for all Reporter instances running on that MDB, the problem may be caused by an inconsistency in
the range of IDs that are assigned to new objects in the Reporter.Be sure to run the statement exactly as stated,
and do a backup of the NCPROFIL table or entire MDB prior to making the changes.
The ID for reporter objects are stored in NCPROFIL table in the mdb. If the ID is out-of-sync
(less than the estimated number of reports/scheduling in the reporter tree), and re synced using the following SQL statement.
Login to SQL .
UPDATE NCPROFIL SET PROFILLN=(SELECT MAX(OBJID) FROM RPTREE) WHERE PROFILID=501
Be sure to run the statement exactly as stated, and do a backup of the NCPROFIL table or entire MDB prior to making the changes.
Please note when performing the above update directly in the database,
it is recommended that Reporter GUI application as well as CAF is shut down before the update.