Unknown Error Sniping

Subscribe to Unknown Error Sniping 6 post(s), 3 voice(s)

 
Avatar (SF) Tori 1 post

The last several attempts at sniping have given me an “Unknown Error Sniping” message.

In a few cases, I got that message, and then after shutting down JBidWatcher, when it reopened, it tried to snipe that auction again, even though it was long over.

For instance, all this information is from the same auction/snipe attempt

Sat Mar 17 16:12:44 PDT 2007: Preparing snipe. (1)
Sat Mar 17 16:14:44 PDT 2007: Firing actual snipe. (1)
Sat Mar 17 16:14:45 PDT 2007: Unknown error sniping on… (1)
Sat Mar 17 23:29:45 PDT 2007: Preparing snipe. (1)
Sat Mar 17 23:29:50 PDT 2007: Snipe apparently failed, as the auction cannot be bid on anymore… (1)
Wed Mar 21 03:30:38 PDT 2007: Preparing snipe. (1)
Wed Mar 21 03:30:43 PDT 2007: Snipe apparently failed, as the auction cannot be bid on anymore:… (1)

It is difficult to trouble shoot as I don’t want to snipe on auctions I don’t actually want to win, but since it started happening, I have redownloaded and restarted etc. I have also refreshed the ebay session, updated auctions and resynchronized time.

Any ideas? I have an auction coming up in a few days that I really would like to have a chance at, but I am not even sure JBidWatcher is working for me at all right now.

 
Avatar Morgan Schweers Administrator 1,204 post(s)

Greetings,
If you can find the log file that contained that failed snipe, I can take a look at it, and figure out what went wrong.

Email me directly with it, though.

— Morgan

 
Avatar Morgan Schweers Administrator 1,204 post(s)

Greetings,
Secondary note… If you search for ‘test-jbidwatcher-sales’ on eBay, I have a number of items up for sale which you can bid on and test. There’s no actual payment, etc., expected, they’re just for testing that bidding is working for you.

— Morgan Schweers, CyberFOX!

 
Avatar coneyisland 2 post(s)

I also have excatly the same problem as the OP.

mine says:

Mon Apr 30 09:55:05 EDT 2007: Communications failure talking to the server. (1) Mon Apr 30 09:55:05 EDT 2007: Failed to load from server! (1) 
Mon Apr 30 22:01:43 EDT 2007: Communications failure talking to the server. (1) Mon Apr 30 22:01:43 EDT 2007: Failed to load from server! (1) 
Tue May 01 08:27:01 EDT 2007: Communications failure talking to the server. (1) Tue May 01 08:27:01 EDT 2007: Failed to load from server! (1) 
Tue May 01 09:53:47 EDT 2007: Communications failure talking to the server. (1) Tue May 01 09:53:47 EDT 2007: Failed to load from server! (1) 
Tue May 01 11:27:26 EDT 2007: Communications failure talking to the server. (1) Tue May 01 11:27:26 EDT 2007: Failed to load from server! (1) 
Tue May 01 13:20:02 EDT 2007: Communications failure talking to the server. (1) Tue May 01 13:20:02 EDT 2007: Failed to load from server! (1) 
Tue May 01 15:40:55 EDT 2007: Communications failure talking to the server. (1) Tue May 01 15:40:55 EDT 2007: Failed to load from server! (1) 
Tue May 01 15:41:07 EDT 2007: Communications failure talking to the server. (1) Tue May 01 15:41:07 EDT 2007: Failed to load from server! (1) 
Wed May 02 08:26:31 EDT 2007: Communications failure talking to the server. (1) Wed May 02 08:26:31 EDT 2007: Failed to load from server! (1) 
Wed May 02 10:52:55 EDT 2007: Communications failure talking to the server. (1) Wed May 02 10:52:55 EDT 2007: Failed to load from server! (1) 
Wed May 02 11:37:37 EDT 2007: Communications failure talking to the server. (1) Wed May 02 11:37:37 EDT 2007: Failed to load from server! (1) 
Wed May 02 12:34:28 EDT 2007: Communications failure talking to the server. (1) Wed May 02 12:34:28 EDT 2007: Failed to load from server! (1) 
Wed May 02 15:46:15 EDT 2007: Communications failure talking to the server. (1) Wed May 02 15:46:15 EDT 2007: Failed to load from server! (1) 
Thu May 03 08:25:35 EDT 2007: Communications failure talking to the server. (1) Thu May 03 08:25:35 EDT 2007: Failed to load from server! (1) 
Thu May 03 12:29:19 EDT 2007: Communications failure talking to the server. (1) Thu May 03 12:29:19 EDT 2007: Failed to load from server! (1) 
Thu May 03 15:17:02 EDT 2007: Communications failure talking to the server. (1) Thu May 03 15:17:02 EDT 2007: Failed to load from server! (1) 
Thu May 03 16:16:32 EDT 2007: Communications failure talking to the server. (1) Thu May 03 16:16:32 EDT 2007: Failed to load from server! (1) 
Thu May 03 16:21:25 EDT 2007: Cancelling snipe. (1) 
Thu May 03 20:19:51 EDT 2007: Preparing snipe. (1) 
Thu May 03 20:21:51 EDT 2007: Firing actual snipe. (1) 
Thu May 03 20:21:52 EDT 2007: Snipe apparently failed, as the auction cannot be bid on anymore

same thing happened the second time i tried to snipe. same because “the auction cannot be bid on anymore” error.

 
Avatar Morgan Schweers Administrator 1,204 post(s)

Greetings,
Hrm… Does your computer have a sleep mode? The pattern of communication failures is surprisingly regular, and a communication failure always happens when the computer wakes up out of sleep. (The networking hasn’t been enabled yet.) It’s not the only time comm failures happen, but seeing regular communication failures like that suggests to me that (for instance) you probably wake the computer up at around 8:30am each day.

In any case, knowing the item number would give some more insight.

— Morgan Schweers, Cyber*FOX*!

 
Avatar coneyisland 2 post(s)

Well i have a macbook and uptill then it worked fine.. overnight. it does have a sleep mode but my setting is that it will only go to sleep if i flip down the screen completely, and only darken the screen to save energy/but not put the computer to sleep.

i have no idea why it wont snipe.