If you see an "Error" in any exchanges upload history, simply hover over he word "Error" to get an idea of what may be causing it.
Common Error Responses
- Login or password was incorrect
- 530 User "XYZ" cannot log in
- This exchange only allows one upload per 15 minutes
- An import job is already in progress for this user
- Unknown SSL protocol error
- AWS::S3::NoSuchKey: The specified key does not exist
- 550 "filename": The process cannot access the file because it is being used by another process.
- Connection reset by peer
- 421 Timeout (120 seconds): closing control connection
- SocketError: getaddrinfo: System error
Login or password was incorrect
Problem: This means that the user name or password you have input is incorrect. Typically this would be because you are trying to use your credentials for that exchange's online portal but they need to provide you separate FTP credentials specifically for uploading. The exchanges that require separate ftp credentials are EventInventory, Razorgator, Ticket Technology and Seatgeek.
** Solution:** Please contact this exchange directly to verify your credentials or obtain you separate ftp credentials for uploading.
530 User "XYZ" cannot log in
Problem: This means that the user name or password you have input is incorrect. Typically this would be because you are trying to use your credentials for that exchange's online portal but they need to provide you separate FTP credentials specifically for uploading. The exchanges that require separate ftp credentials are EventInventory, Razorgator, Ticket Technology and Seatgeek.
** Solution:** Please contact this exchange directly to verify your credentials or obtain you separate ftp credentials for uploading.
This exchange only allows one upload per 15 minutes
Problem: Some exchanges limit the amount of uploads that can be sent within a given period as it takes them longer to process the inventory files. These exchanges will return an error if you attempt to upload more than one time within that period (typically about 15 minutes). For brokers that upload more frequently than this period, you should see a success followed by a few erros, than another success, followed by a few erros and so on for these particular exchanges.
** Solution:**There is nothing that can be done as you cannot restrict the frequency of uploads through the Auto-Uploader for a single exchange. We recommend disabling your failed upload alerts for these exchanges so you do not get inundated with emails.
An import job is already in progress for this user
Problem: Similar to the above error "This exchange only allows one upload per 15 minutes" this error also means that you have attempted an upload to an exchange before they were able to process your last uploaded inventory file. Some exchanges cannot process these files as fast as others and will simply return an error in this instance. Please see above error "This exchange only allows one upload per 15 minutes" for additional information.
** Solution: **There is nothing that can be done as you cannot restrict the frequency of uploads through the Auto-Uploader for a single exchange. We recommend disabling your failed upload alerts for these exchanges so you do not get inundated with emails.
Connection reset by peer
Problem: Some exchanges limit the amount of uploads that can be sent within a given period as it takes them longer to process the inventory files. These exchanges will return an error if you attempt to upload more than one time within that period (typically about 15 minutes). For brokers that upload more frequently than this period, you should see a success followed by a few erros, than another success, followed by a few erros and so on for these particular exchanges.
** Solution:**There is nothing that can be done as you cannot restrict the frequency of uploads through the Auto-Uploader for a single exchange. We recommend disabling your failed upload alerts for these exchanges so you do not get inundated with emails.
Unknown SSL protocol error
Problem: This is typically only seen with Stubhub and are the result of issues Stubhub is experiencing on their end.
** Solution:** Typically when the bulk ftp uploads are down you are still able to login to stubhub.com and you use the manual bulk uploader to upload temporarily. There is nothing that can be done in the Auto-Uploader as you will simply begin seeing "Success" again once the issues on their end have been resolved.
AWS::S3::NoSuchKey: The specified key does not exist
Problem:This is an error returned from the Amazon S3 servers that we are looking into further. If you have received this error it should be very infrequent.
** Solution:**There is nothing currently on your end that needs to be done, we are hoping to push out a fix for this issue in the form of an Auto-Uploader release the latter part of the week of 2/28/11.
550 "filename": The process cannot access the file because it is being used by another process.
Problem: This error should be very infrequent. If you see this error it would typically imply that there is another process currently accessing the remote file that our uploader is trying to overwrite on the server.
** Solution:** You can wait a few minutes and attempt an upload to this exchange again as you may have attempted to upload while that exchange is processing your last upload. This would lock the file and prevent us from overwriting the remote file on the server. If it persists please contact that specific exchange so they can examine the file on their server.
421 Timeout (120 seconds): closing control connection
Problem:
** Solution:**
SocketError: getaddrinfo: System error
Problem:
** Solution:**