Transmission Error Solution

General Solutions for the Uploading/Downloading Problems:

1.     Double click the failed uploading/downloading task and the progress detail will pop up. (Pay attention to relevant transmission related information with respective Task ID).

2.     The file transferring is ongoing when the uploading/downloading progress or speed bar is moving.

3.     When the notification continuously prompting "Connecting access server", please contact your local internet administrator and make sure the relevant IP and port are open to access. If the problem still persists, contact our online customer service.

4.     When the notification non-stop prompting between "Failed to connect to the access server" and "Connect to access server successfully", this shows that the user is able to connect to the access server, however did not manage to connect to the transmission server. Please contact our online customer service for further assistance.

5.     When the notification shows "Error X", please refer to the following “Notification Reference List” for the error solution.   

Notification Reference List:

0: Succeeded – Can be ignored.                              

1: Failed – Mostly can be ignored, however (i) If several files stick at the same location of a particular file, please pause all the uploading task, restart the desktop client and re-start one of the tasks until it has finished transferring before continuing the remaining tasks. (ii) If the problem still persists, the main reason for this problem is mainly due to failed connection to the transmission server, please allow us to perform a local test to verify whether a similar problem exists locally.

2: Remote transferring cancelledCan be ignored. This is due to dropped connection or different clients are transferring the same file at the same time.

3: Failed to open local fileThe local file might not exist or being occupied or failed access to the file etc. (The file path can be a network path) . 

4: Remote creating file failed – (i) The remote file saving path is too long (If the path is kept within 240 bytes, it will notify Error 4 instead of Error 7, since the remote end consists of a path-prefix), full remote storage or access failure to the remote path etc. (ii) The file might have been uploaded previously and is currently occupied (such as rendering), which leads to the failure of deleting both old same named file and creating the new file.

5: Message waiting timeout – Can be ignored. This is due to internet connection issue or the transmission server is down.

6: Transmission timeout – Can be ignored. This is due to no data is transferred within a minute or the transfer is completed.

7: File path is too long – Please keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)     

8: Renamed file path is too longPlease keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)    

9: Failed to analyze the directory information returned by the transmission – Failed to analyze XML, please try to download via Sync.

10: Failed to save file directory locally – This is due to the failure of creating the local directory. (Long path name or a network path that is unable to be accessed)

11: Download folder does not exist – This is mainly due to incomplete frames, can be ignored. If the frames are completed, then it could be the transmission engine problem.

12: Transmission server could not be found – This is due to access server issue, the access server failed to visit the transmission server or the transmission server is down. Please wait for a few minutes and see whether if it recovers, if not, please contact the online customer service (R&D team) to restart the both servers.

13: Failed to create transferring connection – This is due to a failure in requesting the opening of transferring pass which only happens in forwarding mode only.

14: Failed to save file directory remotely – Creating remote directory has failed. (Messy code might exist in the path).  

15: Failed to rename file – The file name might be too long, unable to be accessed or does not support renaming at the remote end.

16: Downloading directory information failed – The directory may not exist.

17: Failed to get STS – This happens only in the transferring mode of OSS on W7. It might be caused by failing to access to W7 or failing to visit STS server on Alibaba Cloud. The problem will not last long and can be ignored.

18: Failed to analyze STS – Less likely to happen, but once this shows up for a long time, please contact online customer service to report this problem.

19: Local path does not exist – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed)

20: Failed to obtain path information – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed or user access permission issue under the directory of C:/Users/ or D:/Users/)

21: Failed to open folder – This is due to the upload folder could not be found. (The upload path is a network path which cannot be accessed or user access permission is denied)

22: Failed to create folder – This is mainly due to (i) Failed to create the download folder (the download path is a network path which cannot be accessed), please check the download path location and make sure the path exists. (ii) The user is using 32-bit operation system which is not supported on our farm. (iii) If the path is OK and the user is using 64-bit operation system, please check whether the desktop client is installed on C drive or another drive that is subjected to access control or administrative limit restrictions, if yes, it is recommended that the user install the desktop client on another drive which is not subjected to any control or restrictions. (iv) The download folder has “Read-only” attribute, which means the folder cannot be written nor edited. (v) Close any running antivirus software. 

23: Failed to connect with OSS communication – This error is only for Platform W7 OSS uploading mode, if the error is non-stop prompting, this shows that Platform W7 has connection issues with Alibaba Cloud servers. Please contact our online customer service for further assistance. 

24: Other transmission thread is transferring the file – Can be ignored. After the other transmission thread has finished or failed to transfer the file, the current transmission thread will automatically retry.

25: Invalid project ID – This error only happens in Aspera transfer, please contact our online customer service for further assistance.   

26: Failed to create an Aspera session – This error only happens in Aspera transfer due to full storage. It is recommended to restart the desktop client and try again.

80: Invalid storage ID

81: Rayvision transmission server is down

100: Uncertain local error

101: Failed to create internal events locally – This is due to the memory is full, it is recommended to restart the desktop client and try again.

102: Invalid data received locally

103: Invalid channel data connection locally

104: Failed to access local path

105: Local path does not exist

106: Local path is a file

107: Local path is a directory

108: Local path is too long to support the engine

109: Local file creation failed

110: Local file open failed

111: Local file read failed

112: Local file write failed

113: Local file migration failed

114: Local path rename failed

115: Local path deletion failed

116: Local file is not complete – This is due to the download is completed, however, the size is smaller than expected.

117: Local file overflow – This is due to the download is completed, however, the size is larger than expected.

118: Local directory creation failed

119: Local directory open failed

120: Failed to analyze the directory information of the files which will be downloaded locally

121: Failed to analyze the storage root directory information of the storage server locally

122: Failed to set the download folder locally – This happens with Rayvision engine

123: Multiple transmission threads are uploading the same file locally – This problem can recover itself, otherwise please stop all the uploading activities and try to upload one by one.

124: Failed to a send request to the server locally – This is due to disconnection problem which can be ignored as the problem can recover itself.

125: The engine disconnection is caused by failing to receive any file data for a long time during transferring – The transfer will retry automatically.

126: The engine disconnection is caused by failing to receive a response for a long time after a local request is sent – The request will retry automatically.

127: Failed to communicate with the OSS server

128: Failed to get the temporary login key to the OSS server locally – This is due to Platform W7 web access is unreachable, relevant functional issues happening in Platform W7 or failed access to the STS server of Alibaba Cloud server. The error will not last long and can be ignored.

129: Failed to analyze the temporary OSS server login key returned from Platform W7 locally

130: Local Aspera engine failed to create session

131: Local connection failed to open the channel – This is due to connection error and it will retry automatically.

132: Local disconnection – This is due to the user has cancelled the transfer.

133: Local system error

134: Local Aspera error

135: Local ambiguous path – This is due to the possibility of the user has mistakenly included a space or other special character in the path.

136: Local license failure

137: Local authentication failure

138: Too many files are opened locally

139: Local path is invalid

140: Local path is already existing

141: Local file is too big

142: Local file list is too big

143: No transfer task is present locally

144: Local disk storage is full

200: Uncertain remote error

201: Failed to create internal events remotely – This is due to the memory is full, it is recommended to restart the server and try again.

202: Invalid data received remotely

203: Invalid channel data connection

204: Failed to access remote path

205: Remote path does not exist

206: Remote path is a file

207: Remote path is a directory

208: Remote path is too long to support the engine

209: Remote file creation failed

210: Remote file open failed

211: Remote file read failed

212: Remote file write failed

213: Remote file migration failed

214: Remote path rename failed

215: Remote path deletion failed

216: Remote file is not complete – This is due to the download is completed, however, the size is smaller than expected.

217: Remote file overflow – This is due to the download is completed, however, the size is larger than expected.

218: Multiple connections are uploading the same file remotely – This problem can recover itself, wait until all transfer connections are successfully connected or experienced connection fail, the current connection will automatically retry.

219: Failed to create the directory remotely

220: Failed to open the directory remotely

221: Failed to structure the directory information of the to be downloaded files remotely

222: Failed to structure the storage root directory information on the storage server remotely

223: Failed to set the download folder remotely – This happens with Rayvision engine

224: Remote connection disconnects – Rayvision transmission server disconnects with Rayvision engine, which can be ignored, otherwise, there might be due to server error.

225: Remote pathname is invalid

226: Remote path is already existing

227: Remote file is too big

228: Remote file list overflow

229: No transfer task is present remotely

230: Remote disk storage is full

231: Remote path is outside of reach

300: Unknown error – This error will not show up, only for internal use.



Transmission Error Solution

General Solutions for the Uploading/Downloading Problems:

1.     Double click the failed uploading/downloading task and the progress detail will pop up. (Pay attention to relevant transmission related information with respective Task ID).

2.     The file transferring is ongoing when the uploading/downloading progress or speed bar is moving.

3.     When the notification continuously prompting "Connecting access server", please contact your local internet administrator and make sure the relevant IP and port are open to access. If the problem still persists, contact our online customer service.

4.     When the notification non-stop prompting between "Failed to connect to the access server" and "Connect to access server successfully", this shows that the user is able to connect to the access server, however did not manage to connect to the transmission server. Please contact our online customer service for further assistance.

5.     When the notification shows "Error X", please refer to the following “Notification Reference List” for the error solution.   

Notification Reference List:

0: Succeeded – Can be ignored.                              

1: Failed – Mostly can be ignored, however (i) If several files stick at the same location of a particular file, please pause all the uploading task, restart the desktop client and re-start one of the tasks until it has finished transferring before continuing the remaining tasks. (ii) If the problem still persists, the main reason for this problem is mainly due to failed connection to the transmission server, please allow us to perform a local test to verify whether a similar problem exists locally.

2: Remote transferring cancelledCan be ignored. This is due to dropped connection or different clients are transferring the same file at the same time.

3: Failed to open local fileThe local file might not exist or being occupied or failed access to the file etc. (The file path can be a network path) . 

4: Remote creating file failed – (i) The remote file saving path is too long (If the path is kept within 240 bytes, it will notify Error 4 instead of Error 7, since the remote end consists of a path-prefix), full remote storage or access failure to the remote path etc. (ii) The file might have been uploaded previously and is currently occupied (such as rendering), which leads to the failure of deleting both old same named file and creating the new file.

5: Message waiting timeout – Can be ignored. This is due to internet connection issue or the transmission server is down.

6: Transmission timeout – Can be ignored. This is due to no data is transferred within a minute or the transfer is completed.

7: File path is too long – Please keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)     

8: Renamed file path is too longPlease keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)    

9: Failed to analyze the directory information returned by the transmission – Failed to analyze XML, please try to download via Sync.

10: Failed to save file directory locally – This is due to the failure of creating the local directory. (Long path name or a network path that is unable to be accessed)

11: Download folder does not exist – This is mainly due to incomplete frames, can be ignored. If the frames are completed, then it could be the transmission engine problem.

12: Transmission server could not be found – This is due to access server issue, the access server failed to visit the transmission server or the transmission server is down. Please wait for a few minutes and see whether if it recovers, if not, please contact the online customer service (R&D team) to restart the both servers.

13: Failed to create transferring connection – This is due to a failure in requesting the opening of transferring pass which only happens in forwarding mode only.

14: Failed to save file directory remotely – Creating remote directory has failed. (Messy code might exist in the path).  

15: Failed to rename file – The file name might be too long, unable to be accessed or does not support renaming at the remote end.

16: Downloading directory information failed – The directory may not exist.

17: Failed to get STS – This happens only in the transferring mode of OSS on W7. It might be caused by failing to access to W7 or failing to visit STS server on Alibaba Cloud. The problem will not last long and can be ignored.

18: Failed to analyze STS – Less likely to happen, but once this shows up for a long time, please contact online customer service to report this problem.

19: Local path does not exist – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed)

20: Failed to obtain path information – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed or user access permission issue under the directory of C:/Users/ or D:/Users/)

21: Failed to open folder – This is due to the upload folder could not be found. (The upload path is a network path which cannot be accessed or user access permission is denied)

22: Failed to create folder – This is mainly due to (i) Failed to create the download folder (the download path is a network path which cannot be accessed), please check the download path location and make sure the path exists. (ii) The user is using 32-bit operation system which is not supported on our farm. (iii) If the path is OK and the user is using 64-bit operation system, please check whether the desktop client is installed on C drive or another drive that is subjected to access control or administrative limit restrictions, if yes, it is recommended that the user install the desktop client on another drive which is not subjected to any control or restrictions. (iv) The download folder has “Read-only” attribute, which means the folder cannot be written nor edited. (v) Close any running antivirus software. 

23: Failed to connect with OSS communication – This error is only for Platform W7 OSS uploading mode, if the error is non-stop prompting, this shows that Platform W7 has connection issues with Alibaba Cloud servers. Please contact our online customer service for further assistance. 

24: Other transmission thread is transferring the file – Can be ignored. After the other transmission thread has finished or failed to transfer the file, the current transmission thread will automatically retry.

25: Invalid project ID – This error only happens in Aspera transfer, please contact our online customer service for further assistance.   

26: Failed to create an Aspera session – This error only happens in Aspera transfer due to full storage. It is recommended to restart the desktop client and try again.

80: Invalid storage ID

81: Rayvision transmission server is down

100: Uncertain local error

101: Failed to create internal events locally – This is due to the memory is full, it is recommended to restart the desktop client and try again.

102: Invalid data received locally

103: Invalid channel data connection locally

104: Failed to access local path

105: Local path does not exist

106: Local path is a file

107: Local path is a directory

108: Local path is too long to support the engine

109: Local file creation failed

110: Local file open failed

111: Local file read failed

112: Local file write failed

113: Local file migration failed

114: Local path rename failed

115: Local path deletion failed

116: Local file is not complete – This is due to the download is completed, however, the size is smaller than expected.

117: Local file overflow – This is due to the download is completed, however, the size is larger than expected.

118: Local directory creation failed

119: Local directory open failed

120: Failed to analyze the directory information of the files which will be downloaded locally

121: Failed to analyze the storage root directory information of the storage server locally

122: Failed to set the download folder locally – This happens with Rayvision engine

123: Multiple transmission threads are uploading the same file locally – This problem can recover itself, otherwise please stop all the uploading activities and try to upload one by one.

124: Failed to a send request to the server locally – This is due to disconnection problem which can be ignored as the problem can recover itself.

125: The engine disconnection is caused by failing to receive any file data for a long time during transferring – The transfer will retry automatically.

126: The engine disconnection is caused by failing to receive a response for a long time after a local request is sent – The request will retry automatically.

127: Failed to communicate with the OSS server

128: Failed to get the temporary login key to the OSS server locally – This is due to Platform W7 web access is unreachable, relevant functional issues happening in Platform W7 or failed access to the STS server of Alibaba Cloud server. The error will not last long and can be ignored.

129: Failed to analyze the temporary OSS server login key returned from Platform W7 locally

130: Local Aspera engine failed to create session

131: Local connection failed to open the channel – This is due to connection error and it will retry automatically.

132: Local disconnection – This is due to the user has cancelled the transfer.

133: Local system error

134: Local Aspera error

135: Local ambiguous path – This is due to the possibility of the user has mistakenly included a space or other special character in the path.

136: Local license failure

137: Local authentication failure

138: Too many files are opened locally

139: Local path is invalid

140: Local path is already existing

141: Local file is too big

142: Local file list is too big

143: No transfer task is present locally

144: Local disk storage is full

200: Uncertain remote error

201: Failed to create internal events remotely – This is due to the memory is full, it is recommended to restart the server and try again.

202: Invalid data received remotely

203: Invalid channel data connection

204: Failed to access remote path

205: Remote path does not exist

206: Remote path is a file

207: Remote path is a directory

208: Remote path is too long to support the engine

209: Remote file creation failed

210: Remote file open failed

211: Remote file read failed

212: Remote file write failed

213: Remote file migration failed

214: Remote path rename failed

215: Remote path deletion failed

216: Remote file is not complete – This is due to the download is completed, however, the size is smaller than expected.

217: Remote file overflow – This is due to the download is completed, however, the size is larger than expected.

218: Multiple connections are uploading the same file remotely – This problem can recover itself, wait until all transfer connections are successfully connected or experienced connection fail, the current connection will automatically retry.

219: Failed to create the directory remotely

220: Failed to open the directory remotely

221: Failed to structure the directory information of the to be downloaded files remotely

222: Failed to structure the storage root directory information on the storage server remotely

223: Failed to set the download folder remotely – This happens with Rayvision engine

224: Remote connection disconnects – Rayvision transmission server disconnects with Rayvision engine, which can be ignored, otherwise, there might be due to server error.

225: Remote pathname is invalid

226: Remote path is already existing

227: Remote file is too big

228: Remote file list overflow

229: No transfer task is present remotely

230: Remote disk storage is full

231: Remote path is outside of reach

300: Unknown error – This error will not show up, only for internal use.



Transmission Error Solution

General Solutions for the Uploading/Downloading Problems:

1.     Double click the failed uploading/downloading task and the progress detail will pop up. (Pay attention to relevant transmission related information with respective Task ID).

2.     The file transferring is ongoing when the uploading/downloading progress or speed bar is moving.

3.     When the notification continuously prompting "Connecting access server", please contact your local internet administrator and make sure the relevant IP and port are open to access. If the problem still persists, contact our online customer service.

4.     When the notification non-stop prompting between "Failed to connect to the access server" and "Connect to access server successfully", this shows that the user is able to connect to the access server, however did not manage to connect to the transmission server. Please contact our online customer service for further assistance.

5.     When the notification shows "Error X", please refer to the following “Notification Reference List” for the error solution.   

Notification Reference List:

0: Succeeded – Can be ignored.                              

1: Failed – Mostly can be ignored, however (i) If several files stick at the same location of a particular file, please pause all the uploading task, restart the desktop client and re-start one of the tasks until it has finished transferring before continuing the remaining tasks. (ii) If the problem still persists, the main reason for this problem is mainly due to failed connection to the transmission server, please allow us to perform a local test to verify whether a similar problem exists locally.

2: Remote transferring cancelledCan be ignored. This is due to dropped connection or different clients are transferring the same file at the same time.

3: Failed to open local fileThe local file might not exist or being occupied or failed access to the file etc. (The file path can be a network path) . 

4: Remote creating file failed – (i) The remote file saving path is too long (If the path is kept within 240 bytes, it will notify Error 4 instead of Error 7, since the remote end consists of a path-prefix), full remote storage or access failure to the remote path etc. (ii) The file might have been uploaded previously and is currently occupied (such as rendering), which leads to the failure of deleting both old same named file and creating the new file.

5: Message waiting timeout – Can be ignored. This is due to internet connection issue or the transmission server is down.

6: Transmission timeout – Can be ignored. This is due to no data is transferred within a minute or the transfer is completed.

7: File path is too long – Please keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)     

8: Renamed file path is too longPlease keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)    

9: Failed to analyze the directory information returned by the transmission – Failed to analyze XML, please try to download via Sync.

10: Failed to save file directory locally – This is due to the failure of creating the local directory. (Long path name or a network path that is unable to be accessed)

11: Download folder does not exist – This is mainly due to incomplete frames, can be ignored. If the frames are completed, then it could be the transmission engine problem.

12: Transmission server could not be found – This is due to access server issue, the access server failed to visit the transmission server or the transmission server is down. Please wait for a few minutes and see whether if it recovers, if not, please contact the online customer service (R&D team) to restart the both servers.

13: Failed to create transferring connection – This is due to a failure in requesting the opening of transferring pass which only happens in forwarding mode only.

14: Failed to save file directory remotely – Creating remote directory has failed. (Messy code might exist in the path).  

15: Failed to rename file – The file name might be too long, unable to be accessed or does not support renaming at the remote end.

16: Downloading directory information failed – The directory may not exist.

17: Failed to get STS – This happens only in the transferring mode of OSS on W7. It might be caused by failing to access to W7 or failing to visit STS server on Alibaba Cloud. The problem will not last long and can be ignored.

18: Failed to analyze STS – Less likely to happen, but once this shows up for a long time, please contact online customer service to report this problem.

19: Local path does not exist – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed)

20: Failed to obtain path information – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed or user access permission issue under the directory of C:/Users/ or D:/Users/)

21: Failed to open folder – This is due to the upload folder could not be found. (The upload path is a network path which cannot be accessed or user access permission is denied)

22: Failed to create folder – This is mainly due to (i) Failed to create the download folder (the download path is a network path which cannot be accessed), please check the download path location and make sure the path exists. (ii) The user is using 32-bit operation system which is not supported on our farm. (iii) If the path is OK and the user is using 64-bit operation system, please check whether the desktop client is installed on C drive or another drive that is subjected to access control or administrative limit restrictions, if yes, it is recommended that the user install the desktop client on another drive which is not subjected to any control or restrictions. (iv) The download folder has “Read-only” attribute, which means the folder cannot be written nor edited. (v) Close any running antivirus software. 

23: Failed to connect with OSS communication – This error is only for Platform W7 OSS uploading mode, if the error is non-stop prompting, this shows that Platform W7 has connection issues with Alibaba Cloud servers. Please contact our online customer service for further assistance. 

24: Other transmission thread is transferring the file – Can be ignored. After the other transmission thread has finished or failed to transfer the file, the current transmission thread will automatically retry.

25: Invalid project ID – This error only happens in Aspera transfer, please contact our online customer service for further assistance.   

26: Failed to create an Aspera session – This error only happens in Aspera transfer due to full storage. It is recommended to restart the desktop client and try again.

80: Invalid storage ID

81: Rayvision transmission server is down

100: Uncertain local error

101: Failed to create internal events locally – This is due to the memory is full, it is recommended to restart the desktop client and try again.

102: Invalid data received locally

103: Invalid channel data connection locally

104: Failed to access local path

105: Local path does not exist

106: Local path is a file

107: Local path is a directory

108: Local path is too long to support the engine

109: Local file creation failed

110: Local file open failed

111: Local file read failed

112: Local file write failed

113: Local file migration failed

114: Local path rename failed

115: Local path deletion failed

116: Local file is not complete – This is due to the download is completed, however, the size is smaller than expected.

117: Local file overflow – This is due to the download is completed, however, the size is larger than expected.

118: Local directory creation failed

119: Local directory open failed

120: Failed to analyze the directory information of the files which will be downloaded locally

121: Failed to analyze the storage root directory information of the storage server locally

122: Failed to set the download folder locally – This happens with Rayvision engine

123: Multiple transmission threads are uploading the same file locally – This problem can recover itself, otherwise please stop all the uploading activities and try to upload one by one.

124: Failed to a send request to the server locally – This is due to disconnection problem which can be ignored as the problem can recover itself.

125: The engine disconnection is caused by failing to receive any file data for a long time during transferring – The transfer will retry automatically.

126: The engine disconnection is caused by failing to receive a response for a long time after a local request is sent – The request will retry automatically.

127: Failed to communicate with the OSS server

128: Failed to get the temporary login key to the OSS server locally – This is due to Platform W7 web access is unreachable, relevant functional issues happening in Platform W7 or failed access to the STS server of Alibaba Cloud server. The error will not last long and can be ignored.

129: Failed to analyze the temporary OSS server login key returned from Platform W7 locally

130: Local Aspera engine failed to create session

131: Local connection failed to open the channel – This is due to connection error and it will retry automatically.

132: Local disconnection – This is due to the user has cancelled the transfer.

133: Local system error

134: Local Aspera error

135: Local ambiguous path – This is due to the possibility of the user has mistakenly included a space or other special character in the path.

136: Local license failure

137: Local authentication failure

138: Too many files are opened locally

139: Local path is invalid

140: Local path is already existing

141: Local file is too big

142: Local file list is too big

143: No transfer task is present locally

144: Local disk storage is full

200: Uncertain remote error

201: Failed to create internal events remotely – This is due to the memory is full, it is recommended to restart the server and try again.

202: Invalid data received remotely

203: Invalid channel data connection

204: Failed to access remote path

205: Remote path does not exist

206: Remote path is a file

207: Remote path is a directory

208: Remote path is too long to support the engine

209: Remote file creation failed

210: Remote file open failed

211: Remote file read failed

212: Remote file write failed

213: Remote file migration failed

214: Remote path rename failed

215: Remote path deletion failed

216: Remote file is not complete – This is due to the download is completed, however, the size is smaller than expected.

217: Remote file overflow – This is due to the download is completed, however, the size is larger than expected.

218: Multiple connections are uploading the same file remotely – This problem can recover itself, wait until all transfer connections are successfully connected or experienced connection fail, the current connection will automatically retry.

219: Failed to create the directory remotely

220: Failed to open the directory remotely

221: Failed to structure the directory information of the to be downloaded files remotely

222: Failed to structure the storage root directory information on the storage server remotely

223: Failed to set the download folder remotely – This happens with Rayvision engine

224: Remote connection disconnects – Rayvision transmission server disconnects with Rayvision engine, which can be ignored, otherwise, there might be due to server error.

225: Remote pathname is invalid

226: Remote path is already existing

227: Remote file is too big

228: Remote file list overflow

229: No transfer task is present remotely

230: Remote disk storage is full

231: Remote path is outside of reach

300: Unknown error – This error will not show up, only for internal use.



Transmission Error Solution

General Solutions for the Uploading/Downloading Problems:

1.     Double click the failed uploading/downloading task and the progress detail will pop up. (Pay attention to relevant transmission related information with respective Task ID).

2.     The file transferring is ongoing when the uploading/downloading progress or speed bar is moving.

3.     When the notification continuously prompting "Connecting access server", please contact your local internet administrator and make sure the relevant IP and port are open to access. If the problem still persists, contact our online customer service.

4.     When the notification non-stop prompting between "Failed to connect to the access server" and "Connect to access server successfully", this shows that the user is able to connect to the access server, however did not manage to connect to the transmission server. Please contact our online customer service for further assistance.

5.     When the notification shows "Error X", please refer to the following “Notification Reference List” for the error solution.   

Notification Reference List:

0: Succeeded – Can be ignored.                              

1: Failed – Mostly can be ignored, however (i) If several files stick at the same location of a particular file, please pause all the uploading task, restart the desktop client and re-start one of the tasks until it has finished transferring before continuing the remaining tasks. (ii) If the problem still persists, the main reason for this problem is mainly due to failed connection to the transmission server, please allow us to perform a local test to verify whether a similar problem exists locally.

2: Remote transferring cancelledCan be ignored. This is due to dropped connection or different clients are transferring the same file at the same time.

3: Failed to open local fileThe local file might not exist or being occupied or failed access to the file etc. (The file path can be a network path) . 

4: Remote creating file failed – (i) The remote file saving path is too long (If the path is kept within 240 bytes, it will notify Error 4 instead of Error 7, since the remote end consists of a path-prefix), full remote storage or access failure to the remote path etc. (ii) The file might have been uploaded previously and is currently occupied (such as rendering), which leads to the failure of deleting both old same named file and creating the new file.

5: Message waiting timeout – Can be ignored. This is due to internet connection issue or the transmission server is down.

6: Transmission timeout – Can be ignored. This is due to no data is transferred within a minute or the transfer is completed.

7: File path is too long – Please keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)     

8: Renamed file path is too longPlease keep your file name within 256 bytes, it is best to be kept within 200 bytes. (Each Chinese character equals to at least two English alphabets)    

9: Failed to analyze the directory information returned by the transmission – Failed to analyze XML, please try to download via Sync.

10: Failed to save file directory locally – This is due to the failure of creating the local directory. (Long path name or a network path that is unable to be accessed)

11: Download folder does not exist – This is mainly due to incomplete frames, can be ignored. If the frames are completed, then it could be the transmission engine problem.

12: Transmission server could not be found – This is due to access server issue, the access server failed to visit the transmission server or the transmission server is down. Please wait for a few minutes and see whether if it recovers, if not, please contact the online customer service (R&D team) to restart the both servers.

13: Failed to create transferring connection – This is due to a failure in requesting the opening of transferring pass which only happens in forwarding mode only.

14: Failed to save file directory remotely – Creating remote directory has failed. (Messy code might exist in the path).  

15: Failed to rename file – The file name might be too long, unable to be accessed or does not support renaming at the remote end.

16: Downloading directory information failed – The directory may not exist.

17: Failed to get STS – This happens only in the transferring mode of OSS on W7. It might be caused by failing to access to W7 or failing to visit STS server on Alibaba Cloud. The problem will not last long and can be ignored.

18: Failed to analyze STS – Less likely to happen, but once this shows up for a long time, please contact online customer service to report this problem.

19: Local path does not exist – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed)

20: Failed to obtain path information – This is mainly due to the failure of finding the uploading path. (The upload path is a network path which cannot be accessed or user access permission issue under the directory of C:/Users/ or D:/Users/)

21: Failed to open folder – This is due to the upload folder could not be found. (The upload path is a network path which cannot be accessed or user access permission is denied)

22: Failed to create folder – This is mainly due to (i) Failed to create the download folder (the download path is a network path which cannot be accessed), please check the download path location and make sure the path exists. (ii) The user is using 32-bit operation system which is not supported on our farm. (iii) If the path is OK and the user is using 64-bit operation system, please check whether the desktop client is installed on C drive or another drive that is subjected to access control or administrative limit restrictions, if yes, it is recommended that the user install the desktop client on another drive which is not subjected to any control or restrictions. (iv) The download folder has “Read-only” attribute, which means the folder cannot be written nor edited. (v) Close any running antivirus software. 

23: Failed to connect with OSS communication – This error is only for Platform W7 OSS uploading mode, if the error is non-stop prompting, this shows that Platform W7 has connection issues with Alibaba Cloud servers. Please contact our online customer service for further assistance. 

24: Other transmission thread is transferring the file – Can be ignored. After the other transmission thread has finished or failed to transfer the file, the current transmission thread will automatically retry.

25: Invalid project ID – This error only happens in Aspera transfer, please contact our online customer service for further assistance.   

26: Failed to create an Aspera session – This error only happens in Aspera transfer due to full storage. It is recommended to restart the desktop client and try again.

80: Invalid storage ID

81: Rayvision transmission server is down

100: Uncertain local error

101: Failed to create internal events locally – This is due to the memory is full, it is recommended to restart the desktop client and try again.

102: Invalid data received locally

103: Invalid channel data connection locally

104: Failed to access local path

105: Local path does not exist

106: Local path is a file

107: Local path is a directory

108: Local path is too long to support the engine

109: Local file creation failed

110: Local file open failed

111: Local file read failed

112: Local file write failed

113: Local file migration failed

114: Local path rename failed

115: Local path deletion failed

116: Local file is not complete – This is due to the download is completed, however, the size is smaller than expected.

117: Local file overflow – This is due to the download is completed, however, the size is larger than expected.

118: Local directory creation failed

119: Local directory open failed

120: Failed to analyze the directory information of the files which will be downloaded locally

121: Failed to analyze the storage root directory information of the storage server locally

122: Failed to set the download folder locally – This happens with Rayvision engine

123: Multiple transmission threads are uploading the same file locally – This problem can recover itself, otherwise please stop all the uploading activities and try to upload one by one.

124: Failed to a send request to the server locally – This is due to disconnection problem which can be ignored as the problem can recover itself.

125: The engine disconnection is caused by failing to receive any file data for a long time during transferring – The transfer will retry automatically.

126: The engine disconnection is caused by failing to receive a response for a long time after a local request is sent – The request will retry automatically.

127: Failed to communicate with the OSS server

128: Failed to get the temporary login key to the OSS server locally – This is due to Platform W7 web access is unreachable, relevant functional issues happening in Platform W7 or failed access to the STS server of Alibaba Cloud server. The error will not last long and can be ignored.

129: Failed to analyze the temporary OSS server login key returned from Platform W7 locally

130: Local Aspera engine failed to create session

131: Local connection failed to open the channel – This is due to connection error and it will retry automatically.

132: Local disconnection – This is due to the user has cancelled the transfer.

133: Local system error

134: Local Aspera error

135: Local ambiguous path – This is due to the possibility of the user has mistakenly included a space or other special character in the path.

136: Local license failure

137: Local authentication failure

138: Too many files are opened locally

139: Local path is invalid

140: Local path is already existing

141: Local file is too big

142: Local file list is too big

143: No transfer task is present locally

144: Local disk storage is full

200: Uncertain remote error

201: Failed to create internal events remotely – This is due to the memory is full, it is recommended to restart the server and try again.

202: Invalid data received remotely

203: Invalid channel data connection

204: Failed to access remote path

205: Remote path does not exist

206: Remote path is a file

207: Remote path is a directory

208: Remote path is too long to support the engine

209: Remote file creation failed

210: Remote file open failed

211: Remote file read failed

212: Remote file write failed

213: Remote file migration failed

214: Remote path rename failed

215: Remote path deletion failed

216: Remote file is not complete – This is due to the download is completed, however, the size is smaller than expected.

217: Remote file overflow – This is due to the download is completed, however, the size is larger than expected.

218: Multiple connections are uploading the same file remotely – This problem can recover itself, wait until all transfer connections are successfully connected or experienced connection fail, the current connection will automatically retry.

219: Failed to create the directory remotely

220: Failed to open the directory remotely

221: Failed to structure the directory information of the to be downloaded files remotely

222: Failed to structure the storage root directory information on the storage server remotely

223: Failed to set the download folder remotely – This happens with Rayvision engine

224: Remote connection disconnects – Rayvision transmission server disconnects with Rayvision engine, which can be ignored, otherwise, there might be due to server error.

225: Remote pathname is invalid

226: Remote path is already existing

227: Remote file is too big

228: Remote file list overflow

229: No transfer task is present remotely

230: Remote disk storage is full

231: Remote path is outside of reach

300: Unknown error – This error will not show up, only for internal use.