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 ZMF Plugin steps fail with error "Host address cannot be empty and cannot contain special characters"
Workaround: It is failing because of the period. As a workaround, you can enter a machine name in the plugin step. Then, edit the host file (by default , located at C:\Windows\System32\ drivers \etc) to map the machine name to the IP Address or full domain name.
TEXT 20083476.txt
MODULE NAME :(JDBC Thin Client) 2020-10-27T15:16:53.510284+02:00 *** ACTION NAME :() 2020-10-27T15:16:53.510293+02:00 *** CLIENT DRIVER :(jdbcthin) 2020-10-27T15:16:53.510300+02:
PDF Serena Deployment Automation Guide
7. Provide the JDBC connection string. The format depends on the JDBC driver and whether you are connecting using a service or an instance name .
PDF How to Move DA Server to new Hardware and Optionally Upgrade to a new Release
If necessary, update the database user/schema name . ... d . ... If upgrade from your old version to the new version is not supported, you will have to initially upgrade to a version that is a supported upgrade step. ... 13) If there are firewalls between the new DA server and any agents or data sources , you may need to update your firewall rules.
CMS-XML SRA 4.5:DEF247198: Group Name changes are not propagated to object default permissions
Default permissions are granted to a group e.g. GROUP1 in the context of ENVIRONMENT. The name of the group is changed from GROUP1 to "Deploy Team Admin" The Settings / Default Permissions, shows the new group name.
CMS-XML SDA: Cannot import artefacts from Nexus/Maven if group name is upper case
When using Group Names in Nexus ( Maven Repository) in upper case. The artefact import in SDA will fail.
CMS-XML DA: "Windows could not start the Agent Relay on the Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 0"
8. Select the user you want to grant logon service access to and click OK. 9. Click OK to save the updated policy. Enter the user account name including domain path to run the service as (for local use '.\' before login ), by default w
PDF 11019202a0ae7e6015d7a836d3a00701d#SDA 6.1.4 WebServices DA Tutorial.pdf
The results can also be stored as a file rather than step out. The file containing the JSON output will be stored in the default agent working-directory for the process name . E.g. E:\Program Files (x86)\Micro Focus\Deployment Automation Agent\core\var\work\RestTest1.
CMS-XML DA: Pre-populated plugin properties with slash in name not allowed in DA 6.1.4
Prior to DA 6.1.4, some plugins, such as Informatica and Websphere, included default process-step properties named similar to: ... Beginning with DA 6.1.4, a slash is not a legitimate character in a property name , thus "informatica/domain" would not be permitted.
CMS-XML SDA: Using Powershell plugin on Windows Agent with space in the installation directory name gives error
This has been submitted to Serena R& D for correction in a future release. Until this has been corrected, it is possible to workaround this problem by installing the agent into a pathname that has no spaces.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs