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 Message: "Failed execution of "commit". Please investigate children for status of individual objects." during deploy
Message: " Failed execution of " commit ". Please investigate children for status of individual objects." during deploy
CMS-XML Commit Failed using Subversion to SBM connector with error "Unable to access jarfile C:\Program"
Commit Failed using Subversion to SBM connector with error "Unable to access jarfile C:\Program"
CMS-XML Unable to edit templates in Configurator when using Oracle - save fails
Unable to edit templates in Configurator when using Oracle - save fails
CMS-XML SBM: Deploy fails with "Couldn't synchronize deployment folder with database.. Cannot save workflow"
Deploy fails with the following error in the deployment log: ERROR -- Cannot deploy BPEL definition for process model alf/8347744b-0382-46ff-9d5b-78f478ec4090/ - Couldn't synchronize deployment folder with database.. Cannot save workflow !. Failed to complete the deployment to server "Default BPEL Server" at 13/01/20 17:20.
CMS-XML Opening SBM Configurator gives error "Failed to read authentication settings" and clicking Apply gives error "Failed to write authentication settings"
If you then change the authentication settings and click Apply to save the changes, you may receive this error:
CMS-XML When clocks go back from daylight saving elapsed times calculations on transitions cause incorrect elasped time or transition failure with error : Calculation underflow error with operands ....
(2) Elapsed2 = Last modifed date minus submit date This occurs for 1 hour in a year for transitions occuring between midnight and 2am for when return from daylight saving . Example to reproduce:
CMS-XML SBM Composer error - Save attempt failed. A generic error occurred in GDI+.
SBM Composer error - Save attempt failed . A generic error occurred in GDI+.
CMS-XML Work center deploy/promote failed if search settings option is defined
Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Transaction marked as rollbackOnly
CMS-XML SiteMinder causes the Sourcebridge link between Version Manager and Team Track to fail
With SiteMinder enabled the labels are not written to the Version Manager Archive and the change history in the Team Track record does not reflect the association. A possible work around is to use another authentication source like LDAP if local corporate policy allows that.
CMS-XML Attaching large files from the Rich text editor fails if the file is larger than 10Mb
Rich text fields (the RTE editor) have the ability to save attachments so a link to the attachment shows in the Rich Text field as well as in the attachment section. Atta ching large files from the Rich text editor fails if the file is greater than 10Mb.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs