dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011)

[Dangerbird]

I have recently set up a Windows Home Server and I'm using dbPoweramp to rip my cd collection. Occasionally, I get an error report and the ripped file will not write to the server. The error report says "unable to open file etc. etc." So the ripping process is working, but dbPoweramp is not able to save the file to the server even though the user profile I'm using has the permission to write to the server. When this came up before I did a quick check by creating a small Word file and I was able to write that file to the server. I then erased the file and went back to dbPoweramp and it was once again able to write to the server! So there is something weird going on with the way dbPoweramp is interacting with the server. This happened a couple more times and each time I have been able to get it working again by recording and erasing a Word file although I have no idea why that fixed the problem.

I have been ripping with no problems all day today until I got to a cd where one track could not be ripped securely so I decided to get another copy of the cd and rip it again. Went into the server and deleted the copy that contained the unsecure rip and when I went back to ripping once again dbPoweramp could not write to the server - same error report. This time saving and then erasing a Word file would not fix the problem as it had before so now I am stuck. Anybody have any ideas on how to fix this?

[eaglescout1998]

Re: dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011

I do not know if this applies to your situation or not.

Beginning with Version 0.9.6, foobar2000 automatically "keeps track of any changes made to its folders." I always used to listen to music while ripping CDs (and foobar2000 is my music player of choice). Ever since this new version of foobar2000, I would occasionally get an error similar to yours. The only thing that made sense is that dBpoweramp and foobar2000's monitoring of music folders would, from time to time, cause a hiccup. If I don't have foobar2000 running, I don't get that error.

You're not running foobar2000 (or any other program that keeps track of changes to your music folder) while ripping with dBpoweramp?

[Dangerbird]

Re: dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011

No I'm using Asset Server which seems to be working fine. Seems to be a problem with the way dbPoweramp is interacting with the Windows Home Server.

[Spoon]

Re: dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011

It is at the file system level which is stopping access, this is very low level, ie we try to open a file to write, it is not allowed, program reports that.

[Dangerbird]

Re: dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011

Yes, that seems to be what is happening. It is difficult to understand why t server and my chat is happening sometimes but not others and why writing a file to the server in Word and then erasing it seemed to solve the problem (I had just done that to check tosee if the server was denying access to my computer or just dbPoweramp). I can still write to the server using Word but now dbPoweramp seems to be completely locked out. I have re-checked and re-set the server settings and re-booted both the server and my computer but that doesn't solve the problem either. That's about as far as a techno-peasant like me can go!

I hope somebody can suggest a fix as it is quite frustrating. Managed to rip a lot of CDs yesterday and they sound great. Everything else is working fine but the ripping process has come to a grinding halt.

[Spoon]

Re: dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011

Rip locally and move the albums using Explorer?

[Dangerbird]

Re: dbPoweramp (Occasionally) Denied Permission to Write to Windows Home Server (2011

Yes that seems to work, so it seems there is difinitely some kind of permission problem between dbPoweramp and the WHS. Very odd that it is intermittent - although persistent right now. Although the added steps are a bit of a pain, I'm happy to be able to rip again. Thanks for the help, I'll keep looking for a way to resolve the problem directly.