Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
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 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 KM-Dim9: Unix installation using Install script - Error: An SQL error was detected trying to check for PCMS_IDX
The user look into install script and look for following lines. ... ... lines for above two connect command for ... 2 . Confirmed set ... ... . If the user is re- ... , because of failure of installation. ... Failure to do this ... PATH =/usr/sbin:/usr/bin:/usr/ucb:/etc:/usr/local/bin:/usr/openwin/bin:/usr/dt/bin:/etc:/usr/platform/sun4u/sbin:/usr/lib/vxvm/bin:
CMS-XML Get$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 Composer switches to Offline after you open any application. Get "Failed to query environmnets" error in the Composer Log
This is caused by having more than one environment defined in the Application Repository with the same name. In the example above there were two environments created with the name "Default Environment"
A customer recently reported the following RC=8 failure that they encountered whilst executing the Db2 stored procedure utility program, CMNDB 2 DD: CMNDD004E Bad SQL code returned from processing this sentence. SQLCA messages follow:
CMS-XML DB2/SQL failure, reference DD CEEMSG for details
ESPUSACO,003I,SQL # 01 : Complete. ESPUSACO,004I, SQL # 02 : Issuing,WS-SYSPLAN-NAME=ESPYD 2 PL. ESPUSACO,005I,SQL # 02 : Complete.
CMS-XML Use of CMNDB2DD LINEFEED parameter in relation to debugging DB2 native SQL stored procedures
However, when doing this they discovered that they were unable to set any breakpoints in the stored procedures. Double-clicking in the margin failed to have any effect or the entire stored procedure was displayed as a single, continuous string of statements.
CMS-XML Required Operating System packages to run SLM 2.2.0 or SLM 2.3.0 on Red Hat Enterprise Linux (RHEL)
.) Note that the wrong ELF class: ELFCLASS64 variants of the errors indicate that only the 64-bit variant of the RPM was installed, and that the 32-bit library search path includes directories containing 64-bit libraries.
CMS-XML Agile Integration to SBM troubleshooting and research findings.
26 Aug 2011 08:14:31,904 [MashupEvents] (null) ERROR 14 - FAILED : Sending Mashup Event to http://localhost/eventmanager/services/ALFEventManager for transaction fc0daede-3a 2 d-42a8-a36c-a640c44897a3 in instance Agile. Exception: Unable to connect to the remote server
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs