All Content Manager Errorcodes

CM-CFG-5136;A Content Manager error occurred while processing the /configuration routingTable property. The entire routing table configuration will be ignored.
CM-CFG-5137;Content Manager was unable to complete the initialization of the content store. For more information, review the log file. Before you restart Content Manager, you may need to recreate the content store database or clean it using dbClean_*.sql.
CM-CFG-4138;Content Manager encountered the error β€˜β€™ while parsing the plugin descriptor file β€˜β€™.
CM-CFG-5139;Content Manager detected that the namespaces with names β€˜β€™ and β€˜β€™ have the same namespace IDs. The namespace IDs differ only in capitalization (’’ and β€˜β€™). You must use unique namespace IDs.
CM-CFG-5140;Content Manager cannot create the namespace object with the namespace name β€˜β€™ and ID β€˜β€™. A namespace β€˜β€™ with the same ID but different capitalization (’’) already exists in the Content Manager data store.
CM-CFG-5141;The current version of the CognosCMDerby.jar file is incompatible with this version of your Cognos product. Version of the file is required.
CM-CFG-5142;The CognosCMDerby.jar file may not have been installed correctly in the Cognos Content database. Make sure the file is installed and available.
CM-CFG-5143;The version of the CognosCMDerby.jar file installed in the Cognos Content database is unknown.
CM-CFG-5024;Content Manager is unable to update the content store database schema from version β€œβ€ to β€œ
” because it cannot access the upgrade file(s) β€œβ€.
CM-CFG-5110;The dispatcher URL specified in cogstartup.xml is not a valid URL.
CM-CFG-5121;Content Manager is unable to update the content store database schema because Content Manager is starting in standby mode.
CM-CFG-5123;Content Manager encountered an error while accessing the Content Manager URLs from the startup configuration file.
CM-CFG-5125;Content Manager cannot create a namespace with the name β€œβ€ and ID β€œβ€ because a namespace with the same name but with a different ID β€œβ€ already exists in the Content Manager data store.
CM-CFG-5195;Content Manager encountered the error β€˜β€™ while parsing the plugin observer file β€˜β€™.
CM-CFG-4144;The URI scheme is not supported.
CM-CFG-4145;The file path β€˜β€™ does not exist or you do not have read permission.
CM-CFG-4146;The configured archive root will not be set.
CM-CFG-5211;Content Manager started initializing the Subscription Manager.
CM-CFG-5212;Subscription Manager started parsing the subscription descriptor file β€˜β€™.
CM-CFG-5213;A Content Manager configuration error occurred while loading the notification implementation class β€˜β€™.
CM-CFG-5214;Content Manager encountered the error β€˜β€™ while parsing the subscription descriptor file β€˜β€™.
CM-CFG-5215;There are no subscriptions loaded by Subscription Manager.
CM-CFG-5216;Notification Manager added observer β€˜β€™.
CM-CFG-5217;Notification Manager couldn’t add observer β€˜β€™ because another observer with the same name already exists.
TR1
CM-TR1-3001;Content Manager request processing is starting.
CM-TR1-3002;Content Manager request processing is finishing.
CM-TR1-3003;Invoking the Cognos Access Manager function β€œβ€.
CM-TR1-3004;Cognos Access Manager function β€œβ€ returned.
CM-TR1-3005;Cognos Access Manager function β€œβ€ signaled exception β€œβ€.
CM-TR1-3006;Content Manager is starting a β€œβ€ operation.
CM-TR1-3007;Content Manager is finishing a β€œβ€ operation.
CM-TR1-4008;Content Manager is performing a content store query β€œβ€ for properties β€œβ€.
CM-TR1-4009;Content Manager has created a query result set of class β€œβ€.
CM-TR1-4010;Access check of object, : .
CM-TR1-4011;Reading properties of object .
TRQ
CM-TRQ-2002;Response:

CM-TRQ-2001;Request:


CM-TRQ-2004;Request MIME part : content type=; content encoding=; content transfer encoding=; saved size=; data size=; compressed=; cached in file=.
CM-TRQ-2005;The Content Manager client at β€œ
” did not receive the complete HTTP response.
CM-TRQ-2006;Response MIME part : content type=; content encoding=; content transfer encoding=; size=; compressed=.
CM-TRQ-2003;Content Manager did not record the request because a Content-length header is not present.
CM-TRQ-4007;The request was removed because an error occurred while filtering out the password.
TIN
CM-TIN-2001;Content Manager internal request:
<br />CM-TIN-2002;Content Manager internal response:

SQL
CM-SQL-3001;SQL statement execution: conID() stmtID()

CM-SQL-3002;SQL connection operation: conID()

CM-SQL-3003;SQL connection exception: conID()

TCH
CM-TCH-3001;Although policy data was released, it could not be freed for use.
CM-TCH-3002;Content Manager has initialized the cache record set for the objects.
CM-TCH-3003;Content Manager has initialized the cache record set for the reference table.
CM-TCH-3004;Content Manager cache initialization is starting.
CM-TCH-3005;Content Manager cache initialization is starting, without using Cognos Access Manager.
CM-TCH-3006;Content Manager has allocated cache blocks.
CM-TCH-3007;Content Manager cache initialization has finished.
CM-TCH-3008;Content Manager cache initialization has finished, without using Cognos Access Manager.
CM-TCH-3009;Content Manager is creating a cache object named β€œβ€.
CM-TCH-3010;Content Manager allocated ID () to the new cache object.
CM-TCH-3011;Content Manager obtained a cache symbol table entry while creating a new cache object.
CM-TCH-3012;Content Manager set the cache entry class type to β€œβ€ while creating a new cache object.
CM-TCH-3013;Content Manager set the cache entry β€œhasSecurity” value to β€œβ€ while creating a new cache object.
CM-TCH-3027;Content Manager is allocating a cache query handle.
CM-TCH-3028;Content Manager is increasing the memory size of its cache for the query.
CM-TCH-3029;Content Manager allocated cache query handle .
CM-TCH-4030;Content Manager released cache query handle .
CM-TCH-3014;The new cache entry for the object has the name β€œβ€.
CM-TCH-3015;Content Manager is linking the cache entry for the object to its parent .
CM-TCH-3016;Content Manager linked the cache entry for the object to its parent .
CM-TCH-3017;Content Manager is adding a cache entry for the child object named β€œβ€ with parent object .
CM-TCH-3018;Content Manager added a cache entry for the object .
CM-TCH-3019;Content Manager is deleting child cache entries for the object β€œβ€.
CM-TCH-3020;Content Manager deleted all cache child entries for the object β€œβ€.
CM-TCH-3021;Content Manager is deleting the cache entry for the object .
CM-TCH-3022;Content Manager deleted the cache entry for the object .
CM-TCH-3023;Content Manager is enumerating children of the object .
CM-TCH-3024;Content Manager is enumerating children of the object named β€œβ€.
CM-TCH-3025;The cache query selected children of the object .
CM-TCH-3026;The cache query selected children of the object named β€œβ€.
CM-TCH-4031;Content Manager is searching its cache for β€œβ€ with options β€œβ€.
CM-TCH-4032;Content Manager is searching its cache starting at objects for β€œβ€ with options β€œβ€.
CM-TCH-4033;Content Manager is accessing policies for objects .
CM-TCH-4034;Content Manager is accessing the current security context.
CM-TCH-4035;Content Manager is checking whether the current user is the owner of the object .
CM-TCH-4036;Content Manager is checking for traverse permissions for the selected objects.
CM-TCH-4037;Content Manager completed the first pass of checking for traverse permissions for the selected objects. The Cache needs to retrieve policies to complete the permission check.
CM-TCH-4038;Content Manager completed checking for traverse permissions for the selected objects.
SDS
CM-SDS-2001;Request:


CM-SDS-2002;Response:


DEP
CM-DEP-2001;Exporting .
CM-DEP-2002;Importing .
CM-DEP-2003;Updating deployment history: .
CM-DEP-2004;Creating deployment history.
CM-DEP-2005;Creating deployment history detail.
CM-DEP-2006; object(s) were imported. object(s) failed.
CM-DEP-2007; object(s) were exported. object(s) failed.
TLM
CM-TLM-2040;Content Manager is obtaining an exclusive lock for the object β€œβ€.
CM-TLM-2041;Content Manager is releasing an exclusive lock for the object β€œβ€.
CM-TLM-2042;Content Manager is obtaining a shared lock for the object β€œβ€.
CM-TLM-2043;Content Manager is releasing a shared lock for the object β€œβ€.
CM-TLM-2044;Content Manager is obtaining a shared descendant lock for the object β€œβ€.
CM-TLM-2045;Content Manager is releasing a shared descendant lock for the object β€œβ€.
CM-TLM-2046;Content Manager is obtaining a shared exclusive descendant lock for the object β€œβ€.
CM-TLM-2047;Content Manager is releasing a shared exclusive descendant lock for the object β€œβ€.
CM-TLM-2048;Content Manager is obtaining the child mutex for object β€œβ€.
CM-TLM-2049;Content Manager is releasing the child mutex for the object β€œβ€.
CM-TLM-4046;Content Manager is requesting a β€œquery” lock for the object β€œβ€.
CM-TLM-4047;Content Manager is requesting an β€œadd” lock for the object β€œβ€.
CM-TLM-4048;Content Manager is requesting an β€œadd-replace” lock for the object β€œβ€.
CM-TLM-4049;Content Manager is requesting an β€œupdate” lock for the object β€œβ€.
CM-TLM-4050;Content Manager is requesting an β€œupdate rename” lock for the object β€œβ€.
CM-TLM-4051;Content Manager is requesting a β€œdelete” lock for the object β€œβ€.
CM-TLM-4052;Content Manager is requesting a β€œcopy source” lock for the object β€œβ€.
CM-TLM-4053;Content Manager is requesting a β€œcopy destination” lock for the object β€œβ€.
CM-TLM-4054;Content Manager is requesting a β€œmove source” lock for the object β€œβ€.
CM-TLM-4055;Content Manager is requesting a β€œmove destination” lock for the object β€œβ€.
CM-TLM-4056;Content Manager is requesting a β€œsecurity object reference” lock for the object β€œβ€.
CM-TLM-4057;Content Manager is releasing all object locks.
CM-TLM-4058;Content Manager has denied access to the object β€œβ€.
CM-TLM-3080;The Content Manager Lock Manager is temporarily suspending the thread β€œβ€ due to lock contention.
CM-TLM-3081;The Content Manager Lock Manager is resuming the thread β€œβ€ after waiting β€œ
” seconds.
CM-TLM-3081;The Content Manager Lock Manager is notifying the thread β€œβ€ that it can resume.
CM-TLM-1058;Content Manager lock state:
CM-TLM-1059;Content Manager Lock Manager Scheduler state:
CM-TLM-5059;Content Manager has encountered an invalid Lock Manager state:
CLS
CTR
ADM
CM-ADM-4001;The user did not log on to any external namespace. ConsistencyCheck was not performed on the security references.
CM-ADM-4002;The user did not log on to the namespace named β€œβ€. ConsistencyCheck was not performed on this namespace.
CM-ADM-4003;Content Manager failed to add historyDetail.
CM-ADM-4005;The object named β€˜β€™ at first logon, created at β€˜β€™, of class β€˜β€™, and with the search path β€˜β€™ was deleted from the namespace β€˜β€™ in the content store.
CM-ADM-4007;unknown name
CM-ADM-4008;The object named β€˜β€™ at first logon, created at β€˜β€™, of class β€˜β€™, and with the search path β€˜β€™ was not deleted from the namespace β€˜β€™.
CM-ADM-4009;An error occurred while attemping to determine the find mode value. A consistency check to find indefinite security references was not performed.
CM-ADM-4010;An error occurred while attempting to determine the fix mode value. A consistency check to repair security references was not performed.
CM-ADM-5011;An error occurred while performing the content task.
CM-ADM-4006;The object named β€˜β€™ at first logon, created at the time β€˜β€™, of class β€˜β€™, with the search path β€˜β€™, no longer exists in the extenal authentication provider with the namespace name β€˜β€™.
CM-ADM-4012;During consistency check, an error occurred while validating the search path () in external namespace.
UPG
CM-UPG-2001;The object with searchPath was successfully upgraded.
CM-UPG-4003"
CM-UPG-3004;An error occurred during the initialization of the Content Store dataUpgradeStore.
CM-UPG-3005;An SQL exception occurred while accessing the CMDATAUPGRADE table.
CM-UPG-4006;During the data upgrade, Content Manager encountered an error when querying objects with the searchPath (). Objects referred by this searchPath will not be upgraded.
CM-UPG-3002"
CM-UPG-2007"
CM-UPG-4008;An error occurred when Content Manager tried to log upgrade information to β€˜β€™.
CM-UPG-2009;Refer to β€˜β€™ for upgrade results.
CM-UPG-4010;Content Manager failed to set default values for the properties of all account objects during the data upgrade.
CM-UPG-4011;The plugin β€˜β€™ failed to upgrade the object with searchPath β€˜β€™.
CM-UPG-2012;The Content Manager database schema upgrade started.
CM-UPG-2013;The Content Manager database schema upgrade is complete.
CM-UPG-2014;The Content Manager content upgrade started.
CM-UPG-2015;The Content Manager content upgrade is complete.
CM-UPG-2016;The Content Manager is upgrading the content objects of β€˜β€™ using the plugin β€˜β€™.
CM-UPG-2017;Upgrade results
CM-UPG-2018;Object class
CM-UPG-2019;Total
CM-UPG-2020;Success
CM-UPG-2021;Failure
CM-UPG-2022;No change is required
CM-UPG-2023;Errors
CM-UPG-2024;Error
CM-UPG-2025;Search Path
CM-UPG-2026;Invalid references
CM-UPG-2027;Message
CM-UPG-2028;Content Manager is upgrading β€˜β€™.
CM-UPG-2029;The object was upgraded.
CM-UPG-4030;The object was not upgraded.
CM-UPG-4031;The object β€œβ€ was not upgraded. No error message was received from the plugin.
CM-UPG-2032;Your β€˜β€™ content store requires a special upgrade for content objects of type β€˜β€™.
CM-UPG-2033;Step of the data upgrade: Content Manager is processing objects.
CM-UPG-2034;Object of is being processed.
CM-UPG-4035;During model upgrade, Content Manager was unable to add to the property β€˜β€™ of the package β€˜β€™.
CM-UPG-2036;The object β€œβ€ was not imported because the data upgrade plugin β€œβ€ requested Content Manager to skip it.