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. |
|
Problem Fetching Remote Data: Unable to load URL, Status: 403 | This probably means the OAuth authorization pop-up window is being blocked. |
|
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 can happen when the friends list contains same server twice. |
|
Problem Fetching Remote Data: Unable to load URL, Status: 500 The time stamp in the cross server request is refused. | This can 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. |
|
Problem Fetching Remote Data: Unable to load URL, Status: 500 The alias name is being used instead of the public URI. | This can happen when there is an 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: