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 RLC.log gives error: liquibase.exception.LockException: Could not acquire change log lock. (Liquibase FAQ)
nested exception is org.springframework.beans.factory .BeanCreationException: Error creating bean with name 'configuration' defined in class path resource
CMS-XML DA: Process step fails gives error like java.lang.SecurityException: Prohibited package name: java.lang
DA: Process step fails gives error like java.lang.SecurityException: Prohibited package name: java.lang
CMS-XML SDA 6.1.2 UI incorrect names for dialogs when editing a resource group
SDA 6.1.2 UI incorrect names for dialogs when editing a resource group
CMS-XML DA 6.2.2: Incorrect values shown for component properties with same names if component inherited from template
DA 6.2.2: Incorrect values shown for component properties with same names if component inherited from template
CMS-XML SDA 5.1.6: Wrong property value randomly used duplicate names are defined for a Component
A problem was reported where the wrong component property value was being used at random where duplicates were defined. For example:
CMS-XML SDA: Using Powershell plugin on Windows Agent with space in the installation directory name gives error
In Serena Deployment Automation, when using the Powershell plugin and executing on an Agent machine where the Agent is installed into a directory path that contains spaces (e.g., "C:\Program Files\...") yields an error similar to the following
CMS-XML SDA: Informatica Plugin step Deploy Deployment Group generates an incorrect control file and thus fails the transaction
The Informatica plugin for SDA has a step named Deploy Deployment Group. This step will generate a control file and then call Informatica to use the control file to connect and ultimately deploy a deployment group. Unfortunately, the control file generated is missing the first two lines and this causes Informatica to fail to take any action.
CMS-XML Reports: Incorrect title for "Deployment Count" report if no application selected in filter
When the Application filter is set to "Any (None Selected)", the graph portion of the Deployment Count report has an application name in the title. This is not correct because the report is actually for all applictions, not just the one given in the title.
CMS-XML DA: Replication Import generates message "Environment Import Failed: Environment with name [NAME] already exists in this application"
When attempting to perform a Replication Import in DA the following message was generated: Error ! Environment Import Failed: Environment with name [NAME] already exists in this application
CMS-XML Jenkins Plugin for DA get errors trying to Submit a Build Process that is in a sub folder or sub project
Using the Jenkins plugin from a DA process the process step Submit Build may fail to work when submitting a job that is in a folder or subproject. Job names that include a slash to denote the folder or subproject will not work.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs