I’m happy to report that the .137 beta version fixed the problem for me. Orders were marked as dispatched quickly and without errors. I haven’t been updating tracking numbers though.
I have the same problem marking the orders as dispatched. Version .136.
My logs show errors like this:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. [System.Data.SqlClient.SqlException] The wait operation timed out [System.ComponentModel.Win32Exception]
Stack Trace
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at SixBit.Data.Database.SBDB.ExecuteQuery(String query, Boolean NonQuery)
End Stack Trace
(ExecuteQuery:UPDATE Shipments SET Shipments.NotifySite = 0 WHERE Shipments.ShipmentID = 196590)
Thank you for your response. I did reset the order refresh dates but that didn’t help. To be precise, Sixbit didn’t download any orders when I used a Quick Refresh like I normally do. Strange thing is that I was able to download my orders using a Full Refresh so I may have a different problem. I’m using version 4.00.017
The problem still exists. I’m unable to download my orders. Same happened yesterday. It seems that Sixbit still surpasses its call limits.
At the same time, I’m revising my listings without problems. It’s a mystery to me.
The problem still exists. I’m unable to download my orders. Same happened yesterday. It seems that Sixbit still surpasses its call limits.
Thank you John for confirming the issue is on eBay’s end. Does the API allow to ignore the category change and force the listing to a category of my choice? Reporting to eBay every time this happens will be a pain. I currently have about 1000 listings that were moved by eBay to an incorrect category. They were not removed in the end as in the example above but are in wrong categories (Antiques, Computers, etc.) and I don’t want to leave them there as this affects search results and also some of these categories have higher FVF.
The problem is that even if I list this particular book in the required category they will still move it to a wrong category during listing. I know I could contact eBay and ask them to correct the error but that would mean I need to do that every time they make such mistake which would be time consuming (hours on the phone). It would be best if Sixbit (optionally) ignored the category change eBay suggests during listing – if such thing is possible.
In short:
Clicking Refresh from the toolbar or Quick Refresh from the menu also does nothing for me. I have to choose from the toolbar Refresh All Orders->Refresh All eBay orders.
Full Refresh from the menu does work.
I’m also using 3.00.141 beta.