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 DA: Updating Component property with a value containing ":" fails
steps: 1 Create a date value in Linux shell script and write to a file : DATE=$(date +"%d %b %Y %H:%M:%S")
CMS-XML DA 6.2.2: Replication import fails if Security role used in Approval process was deleted
Create Security Role (Application, Component or Environment) Add Role step to Approval and Save Remove Role step from Approval and Save
CMS-XML Deployment Automation Agent installation on Linux fails with error in runWrapped.log file Permission denied
A workaround is to create a folder named agent-install in another filesystem. Assign write + exec permissions to this folder and create a symbolic link to this folder directly in /tmp. This should allow the agent installation to complete.
CMS-XML CM/SDA/SRA/SDA/RLM: Error "SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed"
to export the certificate. Save this as a .pem
CMS-XML DA: After upgrade to DA 6.3.3 we cannot see options for Execution or Deployment History Cleanup
4) In the right-hand, click on the pencil icon to the right of the group you are using, e.g., Admin 5) If it is not already checked, check the box next to "Clean Execution History", then click Save 6) Repeat steps 3 through 5 for Environments and "Web UI".
CMS-XML SDA Components with Source Type PVCS may fail to import files with long patnames
(on Unix/Linux). Save a copy of this file before proceeding. By default, this file is in a directory like: <tomcat_install_dir>/bin/
CMS-XML DA: Process step fails gives error like java.lang.SecurityException: Prohibited package name: java.lang
export CLASSPATH= Save the the file. Copy the file to your DA Agent installation directory and then into conf/bin/
CMS-XML SDA: Error "This version cannot be deleted because it is in use by the following" when deleting component version history
These details are stored in SDA and can be used to help you during an audit. When a deploy happens and the execution history is saved , a link the to component version is also saved . You can see this from within the application, go to the History and select a deploy (using the eye icon).
CMS-XML DA Agent log contains: Cannot allocate memory, Cannot allocate large pages
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os:: commit _memory(0x0000000085200000, 1430257664, 2097152, 0) failed ; error='Cannot allocate memory' (errno=12); Cannot allocate large pages, falling back to regular pages
CMS-XML SDA: WAS plugin Update step doesn't appear to be performing a Save operation
SDA: WAS plugin Update step doesn't appear to be performing a Save operation
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs