Error messages

A number of error messages can occur during the translation process. They are documented here for reference.

  • Operation Not Allowed – This message is thrown during the process of uploading the translated document, when the connector is copying the source document fields. If any of those fields cannot be updated by the integration user, this error is shown in the RWS Error Message box with details about the field it was trying to update.
  • Failed to create project – The user gets an error when submitting a translation project from the RWS iFrame. This message is thrown when communication cannot be established between the RWS connector and Vault or the RWS server. In many cases, this will resolve itself by trying again a few minutes later.
  • I/O errors – Once again, this message is thrown when communication cannot be established between the RWS connector and Vault or the RWS server. In many cases, this will resolve itself by trying again a few minutes later.
  • Document cannot be downloaded – This message is thrown during the Send to RWS Translation step when the RWS connector is initiated. If the integration service account does not have permission to download the document from Vault, this error is thrown and displayed in the red bar at the top of the RWS connector page.
  • Invalid Session ID – This message is thrown during the Send to RWS Translation step when the RWS connector is initiated. If the integration service account cannot connect to the RWS systems, this error is shown in the red bar at the top of the RWS connector page.
  • The red bar is displayed on the RWS connector page – This is due to a timeout while connecting to the server. Contact RWS support.
  • File format not supported – This message is thrown during the Send to RWS Translation step when the RWS connector is initiated. If the RWS system does not support the selected file type, this error is shown in the red bar at the top of the RWS connector page.

Vault API logs

A typical project round-trip in the Vault API logs would show the following API calls:
Date/TimestampTypeAPI Call
2019-10-23T07:32:17.932ZGET/api/v19.2/objects/domain
2019-10-23T07:32:18.547ZGET/api/v19.2/query
2019-10-23T07:32:47.444ZGET/api/v19.2/objects/documents/1830
2019-10-23T07:32:47.806ZGET/api/v19.2/objects/documents/1830/file
2019-10-23T07:32:48.792ZGET/api/v19.2/vobjects/sdl_translation__c/V1B000000001V02
2019-10-23T07:32:54.707ZPUT/api/v19.2/vobjects/sdl_translation__c
2019-10-23T07:35:00.768ZGET/api/v19.2/query
2019-10-23T07:39:00.432ZPUT/api/v19.2/vobjects/sdl_translation__c
2019-10-23T07:39:00.716ZGET/api/v19.2/objects/documents/1830/versions/0/1
2019-10-23T07:39:00.869ZGET/api/v19.2/query
2019-10-23T07:39:04.283ZPOST/api/v19.2/objects/documents
2019-10-23T07:39:04.561ZPUT/api/v19.2/vobjects/sdl_translation__c
2019-10-23T07:39:04.846ZGET/api/v19.2/objects/documents/1830/roles
2019-10-23T07:39:05.079ZPOST/api/v19.2/objects/documents/1875/roles
2019-10-23T07:39:05.339ZPOST/api/v19.2/objects/documents/1830/versions/0/1/relationships
2019-10-23T07:39:05.563ZPOST/api/v19.2/objects/documents/1875/versions/0/1/relationships
Submit a support ticket to retrieve further detailed logs from the RWS connector.