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 Dim12: Comparing item revisions with long filename gives Error: Unable to access the following file for reading:
Dim12: Comparing item revisions with long filename gives Error: Unable to access the following file for reading :
CMS-XML Unable to read notification e-mails with a memo field in the subject line
Unable to read notification e-mails with a memo field in the subject line
CMS-XML Error when deploying Process App - ....ERROR -- Cannot deploy BPEL definition for process model ... 500 ... bpel-definition.xml could not read wsdl document
Error when deploying Process App - ....ERROR -- Cannot deploy BPEL definition for process model ... 500 ... bpel-definition.xml could not read wsdl document
CMS-XML Cannot deploy Orchestration - [ERROR] META-INF/bpel-definition.xml could not read wsdl document
Cannot deploy Orchestration - [ERROR] META-INF/bpel-definition.xml could not read wsdl document
CMS-XML Merge error: Unable to access the following file for reading... no file name reported
Merge error: Unable to access the following file for reading ... no file name reported
CMS-XML Unable to validate escaped app script with multiple quotes.
The following code is valid vbscript and is used to escape a double quote but when you try to validate it in composer you get the error below. It's hard to read but there are six double quotes total, three on each side of the text variable used.
CMS-XML Notification events for archived items give Application Log error: "Record xx, in Table xxx could not be found"
The complete warning messages from the Event Viewer Application Log is: NOTIFICATION_NAME: (notification) context - Unable to read item with id xx from database. And:
CMS-XML Using read() in MashupScript can lead to Server Error 500
The transition was not executed. The record with ID 0 could not be found in the 'TS_TRANSITIONS' table. Row not found: The record with ID 0 could not be found in the 'TS_TRANSITIONS' table.
CMS-XML Orchestration with WS call that uses dynamic endpoint not able to find service
The problem is reproduced if WSDL that describes the service which dynamic endpoint accords to imports any XSD or WSDL - in this case WSDL read operation failes as child XSD/WSDL are not prepared in the local system as it is performed in the case of static endpoints usage due to the following:
CMS-XML Screen reader has an issue with column headers on some reports
Column and row headers are not able to be read by a screen reader (508 compliance) on some built in reports
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs