Synchronizer can run only one task at a time for a particular link. When you have multiple links configured, Synchronizer can run only one full synchronization task at a time, or five incremental tasks from different links.

During synchronization, Synchronizer monitors the amount of available disk space.

If the remaining available disk space is lower than a predefined threshold (500 MB by default):

• The synchronization stops.
• An error message is added to the synchronizer.log file.
• Synchronizer sends an email to the address configured in the link's Failure Notification Settings.

Clean up the hard drive to free more disk space, and start ALM Synchronizer for Agile Manager again.

To modify the disk space threshold:

1. Open the <Synchronizer installation folder>\dat\server.properties

2. Add a line to the file: minimum.free.space.threshold=<number of megabytes>

3. Restart the ALM Synchronizer service.

Increase the number of seconds before a timeout occurs. The default is 200 seconds.

1. On the Synchronizer server machine, navigate to the <Synchronizer installation directory>\adapters\dat\HP-Agile-Manager directory.

2. In a text editor, create a file named adapter.properties, or open this file if it exists.

3. Define the following property:

   connection.timeout=<timeout per request to Agile Manager in milliseconds>

   Example

   connection.timeout =300000

4. Restart the Synchronizer server.

If a new Application is added to a user story or defect in Agile Manager, the new Product value is not automatically created in ALM. To synchronize these new Product and Application values, add the new Product value in ALM.

This error may occur if you have a mandatory user field in one endpoint mapped to an optional user field in the opposite endpoint, and the optional field has a blank value.

User fields that are mapped to mandatory fields in the other endpoint cannot be blank. Enter values for these fields and synchronize again.

This error may occur if there is a user field in either endpoint that is not mapped to a corresponding field in the other endpoint. In such cases, do one of the following:

• Add the corresponding user field to the other endpoint, and map the two fields.

• Define a default user for any user fields without mapped values. For details, see Map user list fields using a .csv file.

Your Agile Manager site is not enabled for synchronization. open a support ticket requesting that the synchronization be enabled.

You must restart the Synchronizer service after configuring the proxy.

If authentication fails and errors 401 and 407 display in the restClient.log, verify that the contents of the proxy.properties file are syntactically correct and contain valid values.

If your Synchronizer administrator has updated the server version, you must also update your client version to match.

If Synchronizer cannot connect to ALM, you can use a script file to check that the ALM endpoint’s API is functioning properly.

1. On the Synchronizer server machine, open the Navigate to the <Synchronizer installation directory>\bin directory and locate the checkQcConnectivity.vbs file.

2. Edit the script file to include the connection properties for the endpoint. For details, see Assign ALM endpoint connection properties.

3. Double-click the script file. If connection is successful, a confirmation message displays.

Simply remove the filter's previous name from the list of filters for the selected link.

Map specific field values to define the full path of the release. For example, you can map each value of the Target Release field to a value in a corresponding field in the other endpoint.

Define the full path of the ALM release in the format \<Release_Folder_Name>\<Release_Name>. For example, \Flight Application\Release_2.

You do not need to include the root Releases folder in the path.

Problem: The Synchronizer server may have errors when installed on a computer that uses a locale other than an English-based locale.

Workaround:

1. On the Synchronizer server, create a user account with an English locale setting, such as United States.
2. Copy the locale settings to the System Local account using the Windows Copy settings functionality (Control Panel > Region and Language > Administrative tab).
3. Restart the Synchronizer server.

If the Synchronizer service does not start, verify the following:

Verify the following:

• The user running the installation has administrator permissions on the machine on which the Synchronizer is being installed.

• The user account you enter during server configuration has administrator permissions.

• The user account you enter during server configuration has permissions to log on as a service:

  1. From the Start menu, select Run and type secpol.msc.

  2. In the Local Security Policy dialog box, select Security Settings > Local Policies > User Rights Assignments.

  3. In the right pane, double-click Log on as a service.

  4. In the Log on as a service Properties dialog box, verify that your user is listed, or click Add User or Group to add it to the list.

Then on the Synchronizer server machine, run the following files located in the <ALM Synchronizer installation directory>\bin folder:

1. To uninstall any previous version of the service, run stop_and_remove_synchronizer_service.bat.

2. To install the service, run sync_service_install.bat.

During installation, an error message indicates that the previous Synchronizer version was not uninstalled. This can occur even when ALM Synchronizer in not listed in the Windows Add or Remove Programs Control Panel.

This error indicates that references to the previous installation may remain in the vpd.properties file, located in the Windows system root folder.

To remove all remaining references to a previous installation:

1. Verify that the Synchronizer was uninstalled by checking that it is not listed in Windows Add or Remove Programs Control Panel.

2. Navigate to the Windows system root (%systemroot%) folder and backup the vpd.properties file.

3. In a text editor, open the vpd.properties file and delete all rows containing references to Synchronizer.

The Synchronizer service fails to start if the msvcr71.dll file is not in the system path.

Workaround: Add <Synchronizer-Install-Dir>/java/bin to the system PATH variable.

If you uninstalled a previous installation of PostgreSQL, verify that it was removed completely, and rerun the server configuration.

For more information on uninstalling PostgreSQL, see Uninstall PostgreSQL.

To rerun the server configuration, on the Synchronizer server machine, navigate to the <ALM Synchronizer installation directory>\bin folder, and run the run_config_tool.bat file.

Verify that PostgreSQL access is not locked by another user, and rerun the server configuration.

To rerun the server configuration, on the Synchronizer server machine, navigate to the <ALM Synchronizer installation directory>\bin folder, and run the run_config_tool.bat file.