View Full Version : "already uploaded a file" when I really really hav
Hi.
I've twice now tried to upload a file and it says it's already been uploaded. It's happened roughly 24 hours apart and I've tried to upload the files just moments after I pressed "stop sniffing" which makes it totally impossible for it to be an old file.
Inbetween these two occurences it's worked fine. I've saved both files.
I'm running L2Drop 3.0 on an XP Pro machine. More info, let me know what you need.
Just to make it clear, it's two distinct files I've tried to upload, and yes I did retry to upload the first one twice and it said the same thing for that attempt as well.
I can't remember how I quit playing the first time but the second time I got disconnected from the server, if that makes a difference?
Happened again now with L2Drop 3.1.
Quit the game, pressed Stop Sniffing, pressed Upload Drops, got that message.
With the lag as it is right now I can hardly play more than a short while which means I won't have any access to the DB either.
Anyone have anything similar ?
If the "upload completed" page is refreshed/reloaded, it automatically re-sends the file (from same path).
If this happens while sniffing, anything the sniffer adds afterwards is lost since the file is considered "alreay uploaded".
Maybe that is your problem, it happens to me also when I quit/relauch my browser, as it restores the page.
That re-send on refresh should be fixed.
Good idea, sad it's not true though :(
I always just click the Upload button which launches the browser, click the file selector, select the file, press OK, press upload..
If you have the sniffer running and upload what you have so far, and want to keep sniffer, you need to find the file and delete it after you uploaded it. This will then make a new file and log all the drops after you uploaded. You do not need to relog into the game, or restart the sniffer.
You mean if I leave the program running , press STOP SNIFFING, upload the drops, when I then press START SNIFFING it will continue on the same file?
no, dont press stop sniffing. When you press that you will need to relog for the program.
start sniffing, gets a bunch of drops.
leave sniffing and upload what you have.
leave sniffing and delete the file you just uploaded.
leave sniffing and it will make a new file that hasnt been reported yet.
If you leave the program running, you can delete that file as many times as you want and it will continue to make new ones that are fresh and can be uploaded.
The trick is, once you upload a file, the file is marked, and you need a new file for it to accept it. If you just delete the file you uploaded, when it makes a new file, nothing on it has been marked as uploaded already and it will accept it.
I think we're talking about different things actually.
This is when I've gotten this issue:
Start l2drop
Start game
Play
Stop game
Stop L2drop
Upload Drops file
Turn off computer
Sleep
Wake up
Start L2Drop
Start game
Play
Stop Game
Stop L2Drop
Upload Drops file
Get "already uploaded file".
If L2Drop overwrote the old file and started fresh I shouldn't get this error, but it's happened across reboots. After I added "delete l2drop file" before "turn off computer" I haven't gotten the issue again (or before "Start L2Drop").
Am I really doing something wrong ? I currently have 4 or so drop files that have had that same issue.
Hmmm... what could be wrong ?
-Having 2 (or more) copies of the sniffer installed and uploading file from the one that did not run.
-Intrusive software (security, sharing...) that locks files, preventing sniffer from deleting and starting from scratch.
But then you would get an error when deleting manualy.
-Corrupted OS leading to file management incoherence.
(good excuse for any kind of failing)
-Bad clock setting ?
Maybe the sniffer uses the clock to generate id number ?
All of this is unlikely... I ran out of ideas.
Hmmm... what could be wrong ?
-Having 2 (or more) copies of the sniffer installed and uploading file from the one that did not run.
Only one copy installed. Fresh windows install from a couple of weeks ago and this one is much better organised.
-Intrusive software (security, sharing...) that locks files, preventing sniffer from deleting and starting from scratch.
But then you would get an error when deleting manualy.
Well, Symantec Client Security is only thing I have of that kind, but I agree with the second comment, I wouldn't be able to manually delete it would I.
-Corrupted OS leading to file management incoherence.
(good excuse for any kind of failing)
Well, it IS Windows we're talking about ..
-Bad clock setting ?
Maybe the sniffer uses the clock to generate id number ?
Clock synced to an atomic clock...
All of this is unlikely... I ran out of ideas.
Yeah, pretty much where I'm standing too.
I've gotten no troubles after manually deleting the file though.
vBulletin® v3.6.7, Copyright ©2000-2010, Jelsoft Enterprises Ltd.