#1
|
|||
|
|||
No permission to write to disk error
Hi,
I have jDownloader v7.569 with firefox 3.5.2 flashgot 1.2.0.2. I have a rapidshare premium account. While downloading files, I keep getting "No permission to write to file" error mostly when the files are in 90% range. This is not consistent and i am unable to find a particular reason for this. I have gone through other threads in this forum and have tried to set my max connections to 1 and max dw to 3. This still doesn't help and its frustrating as each time I have to reset and download again. Please check out this problem and resolve at the earliest as this affects the basic functionality of jDownloader. Last edited by Jiaz; 15.11.2009 at 15:49. |
#2
|
|||
|
|||
Disk Space Problem
Naturally I get this message when JD don't find enough space at the destination drive to write down the file it's downloading, so, are you sure there is enough disk space ? is there any other active program that may be messing with your HDD ?
|
#3
|
|||
|
|||
No i don't have any disk space problems. I forgot to mention that in my post. I don't see any other program accessing the same space while downloading.
|
#4
|
|||
|
|||
Typical recommendations when this happens, are :-
- use less chunks - allow java.exe, javaw.exe and jDownloader in your firewall - unstable internet connection, contact you ISP - reboot PC - uninstall/re-install firewall - uninstall/re-install virus scanner - torrent client using too many connections - uninstall JRE (java) and re-install latest JRE version |
#5
|
||||
|
||||
we need a logfile!
__________________
JD-Dev & Server-Admin |
#6
|
|||
|
|||
Log file + screenshot in zip
Hi Jiaz,
Please find the logfile and the screen shot (you may need to zoom in on the screen shot) inside the zip file attached. See I have 2 chunks per file going on with 3 files at a time and I am still getting this error message. I have 125 GB free space on that drive. So no question of less disk space. Please let me know if you need anything else. |
#7
|
||||
|
||||
java.net.SocketTimeoutException: Read timed out
could be Instable Connection, Firewall, Virusscanner
__________________
JD-Dev & Server-Admin |
#8
|
|||
|
|||
It can't be firewall or virus scanner. Regarding unstable IP connection, I have a broadband service, providing 24 x 7 connectivity.
If this is the culprit, how do I ensure that I have a stable connection ? Or is it up to my ISP ? |
#9
|
||||
|
||||
of course it can be firewall
many firewalls can act weird from one moment to another if not setup correct.
__________________
JD-Dev & Server-Admin |
#10
|
|||
|
|||
I keep getting this annoying error daily also, I used to use several other downloaders before coming to jdownloader and never experienced this error.
I try enabling, resuming, always the same error, only way seems to be to reset it. There is definitely something wrong. I have no firewall, no virus scanner, a stable internet connection, and even if it isn't stable, why would that cause problems resuming the thing? the only way seems to be to reset and start from scratch... im running .8.129 on windows server 2003.. |
#11
|
|||
|
|||
Add me to the list, I'm getting the same message.
It is definitely not filespace, I have the better part of 1tb free. furthermore, if i have the Max Dls. set >1, one file will get stuck, and the others will merrily continue writing to disk. It is definitely not the anti-virus (i've had my anti-virus stop a 'write to disk' before, and it's always at 99% -- this problem occurs well before 99%, and besides, there is no log entry in my anti-virus about stopping anything at that time). It is definitely not the firewall, since I don't run one. It could be a timeout/ISP error -- although if that is the case, I would think that JD would be able to resume -- it can not... Pressing 'stop' fills the "stopping current downloads" bar and it sits there full - it never completes the stop command. as such, if we click File, Restart, JD restarts, but when we restart these files are unable to continue where they left off. they need to be right-click reset (delete the partial download), then right-click resume. (so they will start again from the beginning) -- Resetting and resuming fixes the problem and they seem to download fine after doing this. What does JD code do when presented with a timeout/ISP connection issue? What does JD code do when asked to 'stop all running downloads' and is unable to? Can we change JD behavior so that it an ISP timeout does not hang current downloads? Is it possible to keep the partial file up to the last successful chunk so that a reset will resume the download? Can we put a timer in the 'stop all current downloads' so that if it exceeds a set amount of time (?30seconds?) that it will kill the stop process? If the stop process times out, it'd be nice if JD would keep the partial files instead of marking them as corrupt. |
#12
|
|||
|
|||
This is a very old problem that hasn't been solved yet.
I found another potential solution to the problem :- Quote:
- A properly configured reconnect - A properly configured firewall means that jdownloader.exe, java.exe and javaw.exe are excluded. Also nod32 and some other firewalls need to be configured properly. Even if you think you haven't a firewall, Windoze customers still have a Windoze firewall. - Disable http/web scanners, whatever that means. Also slow lines with wrong jD configuration settings (too many parallel downloades, too many connections) could mean trouble. |
#13
|
|||
|
|||
Quote:
None of the above apply to me yet I get this error daily. Anyway hopefully they will find the fault sometime and fix it |
#14
|
||||
|
||||
java.net.SocketTimeoutException: Read timed out
Connection Reset and such things. are NOT a JD problem!! this is not in our hands...these are 100% issues caused by something else (most times by wrong configured firewalls)
__________________
JD-Dev & Server-Admin |
#15
|
|||
|
|||
I agrees that isp issues (timeouts, connection resets, etc) are not a JD problem. However, if JD's purpose is to automate downloading, and isp issues prevent successful downloads, I think there is a case to wite some additional code to add functionality.
maybe to see if a download is perpetually stalled, and to do something about it? |
#16
|
|||
|
|||
Quote:
Thanks for replying but that doesn't really help me understand in my situation. I am running win 2003, it doesn't have a firewall. In windows 2003 you actually have to install the windows firewall, it isnt bundled like xp etc. This isn't installed I just checked. I don't have any AV software on it. The network is perfectly configured. Also, why does this happen when it gets to about 90% all the time on a file? I could understand what you are saying above if it happened all the time but it seems funny that its random and never at the start of a file. If i reset the same file it will come down perfectly, from the same server etc so that makes no sense at all. I can use other download software like IDM and never have this problem. If I can reset the file in Jdownloader and it comes down perfectly then why is jdownloader unable to resume the thing? |
#17
|
|||
|
|||
Note that not all downloads can be resumed.
What file hoster(s) are you talking about? Are you using a premium account? |
#18
|
|||
|
|||
Quote:
They can definitely be resumed. |
#19
|
|||
|
|||
Quote:
Anyway this needs to be resolved so that JDownloader may be useful again. As of now I've reverted to Firefox for Rapidshare, as it offers the most stable downloading by not cutting off any download without warning. Another good thing about using Firefox for RS is the drop down menu selection to pick the best server for download. With JDownloader I find that it always seems to fail to select the fastest server. Last edited by updown; 03.09.2009 at 12:37. |
#20
|
|||
|
|||
I'm a freeloader for all the hosters I've ever used.
RS is working in v.0.4, v.0.5 and this week I tested v.0.7 and it worked there as well. It means that the RS plug-in is one of the most stable ones. It's an annoying problem you have, but if you follow the recommendations in this thread, you should be able to solve your problem. If you can't, send a bug report with detailed logs. |
Thread Tools | |
Display Modes | |
|
|