E03020586: Could not write the form template file
Article ID: 74826
Updated On:
Products
Issue/Introduction
When creating a package I see this error:
Form Template "Application Change Request.xml" could not be retrieved from server.
Reason:
E03020586: Could not write the form template file.
And Workbench's output log shows the same error, but otherwise the package was successfully created.
E03020586: Could not write the form template file.
---------- Begin <Create Package> Process ---------------
I000206ad: Created package <package name>.
---------- End <Create Package> Process ---------------
Environment
Harvest Software Change Manager v14.x and higher
Cause
The form template specified in the error message box (in the above example the "Application Change Request" form type) was not successfully added to the Harvest database.
Resolution
Identify if the form type identified in the error message box is one of the "default form types" that can be optionally added to the Harvest database during database creation, or if it is a custom form type. The "default" form types include:
- Application Change Request
- Comment
- Defect Tracking
- ESD Change Request
- Modification Request
- OnDemand Project Request
- Problem Report
- Q and A
- Testing Info
- User Contact
If the problem is with a default form type the simplest solution involves going to the "hdbsetup" utility and executing the "LF" option which will automatically load the "default" forms. For example:
If the problem is with a custom form type, the solution involves locating the files associated with that custom form type and following the proper steps to define and load that form type in Harvest. Each Harvest form design has a minimum of one, or at most 4 types of files associated with it:
- <form type name>.hfd
- <form type name>.htm
- <form type name>.sql
- <form type name>.xml
(Of those for types, the <form type name>.hfd file is the most important. The other three can be generated from this one.) For information on how to find these custom form type files, see the Additional Information below.
The online documentation covers this topic in detail in the "Create and Modify Form Types" chapter, but the basic steps involve:
- If the htm, sql, and xml files do not exist or are not found, use the Form Wizard utility to generate those from the <form type name>.hfd file
- Make any necessary updates to the form type's xml file to include such features as custom javascript, multiple columns, read only fields, etc.
- Execute the <form type name>.sql script using SQL*Plus for Oracle or SQL Server Management Studio for SQL Server.
- Execute the hformsync command to upload the form type's xml file to the Harvest database.
Additional Information
Finding the custom form type's files:
By default, these custom form type files are found in the "C:\ProgramData\CA\SCM\Forms" folder (for Windows) or the "$CA_SCM_HOME/Forms" folder (for Unix/Linux), but they could have been saved in another custom folder, selected by the person who created the form. Additionally, by default, the form type's files are found on the broker machine, but could also have been saved on another user's computer, depending on which computer was used to open the Harvest Administrator Tool and design the custom form type. A best practice to track the files associated with your custom forms is to create a project in Harvest specifically for files related to custom forms and UDP scripts. This idea makes it easier to locate and track changes to these files.
Feedback
