Troubleshooting links between project areas

If you are unable to add links successfully between products using the Collaborative Application Lifecycle Management (C/ALM) integrations, check the following symptoms and solutions:
Table 1. Errors and solutions for linking between products using C/ALM integrations
Symptom Explanation Solution
Problem Fetching Remote Data: Unable to load URL, Status: 200 This probably means the root services URL to the remote server is incorrect
  1. Remove the entry in the cross server communication page.
  2. Add a new one with the correct URL.
  3. Reboot the server.
Problem Fetching Remote Data: Unable to load URL, Status: 403 This probably means the OAuth authorization pop-up window is being blocked
  1. Check the blocker setting for the current web site.
  2. Disable the blocker.
Access forbidden. Status: 403 The cross server configuration was performed with an invalid hostname. Perform the cross server configuration again and make sure to access the administration pages using the hostname chosen and configured in Setting the public URI for Jazz servers. Do not use hostname aliases.
Problem Fetching Remote Data: Unable to load URL, Status: 500 The consumer key is invalid. This could happen when the friends list contains same server twice.
  1. Double check whether there are duplicated entries in the friend configuration.
  2. Remove the invalid friend configuration.
  3. Reboot the server.
Problem Fetching Remote Data: Unable to load URL, Status: 500 The time stamp in the cross server request is refused. This could happen when the date/time setting in the two servers are largely different. The Jazz Team Server checks whether the setting is between an allowed scope. If it is not, it will refuse the cross server request.
  1. Double check whether the time setting is within the allowed difference, 10 minutes is the scope.
  2. Correct the setting and reset up the linking.
Problem Fetching Remote Data: Unable to load URL, Status: 500 The alias name is being used instead of the public URI. This could happen when there is alias name defined for your machine. Follow the instructions in Setting the public URI for Jazz servers to verify that the root service document can be correctly accessed and contains correct the server URLs. Always use the URI with the host name to access the web user interface.

For further information about Status 500 errors:

  1. Select the URL in the error message and copy it to the clipboard.
  2. Paste the URL to a new browser to see more details on the error message.

Feedback