Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Report server cannot connect to Mariner App server by name - Query execution failed for data set 'xxxxx'
2 . Update ReportServerName for Reporting in the registry of the Report Server path \HKEY_LOCAL_MACHINE\SOFTWARE\Pacific Edge Software\Reporting to reflect the full qualified domain name of the server.
CMS-XML DimCM: Upgrade: ORA-28003: password verification for the specified password failed error during basedatabase upgrade
select profile from dba_users where username='[base database name in ALL CAPS]'; Now query for password verification function used by this profile , this will be needed to revert the changes once upgrade completes ( query 2 ): select limit from dba_profiles where resource_name=’PASSWORD_VERIFY_FUNCTION’ and profile='[result from query 1]';
CMS-XML RM 2009 R2 SyncEngine to QC 10 – log entry QC Error : IDispatch error #490Failed to Run Query
2 ... To do this, update the following path : ... each instance of the following path : C:\Program Files\Microsoft SQL
CMS-XML Question: #667 Problems fixed in the 5.206 patch
- Under OS/ 2 Warp, you encounter a General Protection Fault ... long path name, you may encounter a General Protection Fault. ... This maintenance release is for NT users only. ... from retaining OS/ 2 extended attributes for workfiles that are checked ... This maintenance release is for OS/ 2 users ... to delete OS/ 2 extended attributes from revisions when they are checked ... This maintenance release is for OS/ 2 users only. ... * The Version Manager 5.2 graphical interface fails with a General ... Version 5.2.01 prevents application failure , it does not add support
CMS-XML KM-Dim9: Dimension & .Net 2003 SCC integration causes: Error: query 15155 read. Error: invalid message number 15155
2003 SCC integration causes: Error: query 15155 read. ... 2 . Selected correct product, workset, and design part and project path . ... Error: query 15155 read ... Error: Failed to get item option data for product <productID>
CMS-XML Reports: Some users (not all) get error: Query execution failed for dataset 'DataSet1' or Query execution failed for dataset 'DataSet2'
An error has occurred during report processing. Query execution failed for dataset 'DataSet1'
CMS-XML Dim10: LDAP: Failed to connect to Dimensions Server, LDAP: (10) Referrals, PRG4500325E Error: User authentication failed - LDAP search failed, ACL4500326E Error: User authentication failed when connecting to host occurs
This error can occur because of one of two problems: 1. Referrals are not working correctly on the LDAP Server 2. There is white space after the LDAP_BASE_NAME variable within the dm.cfg. White space can include either extra spaces and/or tabs.
CMS-XML Get com.serena.sbm.data.Notification.lambda$findCCUsers in ns.log when user has bogus entry in CC list in user profile and nobody gets the notification sent to them, not even the primary recipient
For MSSql users there are two sql scripts attached below that can be run that will help identify any users in the system with a bogus username in the CC List for their account. The difference between the two scripts is that one looks for a comma seperator and the other looks for a semicolon seperator in the cc list. Take the results from each query to find the real bogus entries.
CMS-XML DIM10: Upgrade to Dimensions CM 10, now gets error when browsing change requests: SQL-24812(4207) ORA-24812: character set conversion to or from UCS2 failed
DIM10: Upgrade to Dimensions CM 10, now gets error when browsing change requests: SQL -24812(4207) ORA-24812: character set conversion to or from UCS 2 failed
CMS-XML KM-Dim7: 1019-DBIO: oracle error occured SQL-0904 3531 ORA-08102: index key not found, obj# 5669, dba 67170180 '2' 9505- failed to delete from table 'table name'
KM-Dim7: 1019-DBIO: oracle error occured SQL -0904 3531 ORA-08102: index key not found, obj# 5669, dba 67170180 ' 2 ' 9505- failed to delete from table 'table name'
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs