Issue with delete of recordings from PC Client

[ptyler13]

I am currently running GBPVR 0.98.08 on a server and a minimal XP client. All is working properly with streaming video and live TV. Actually it works quite stellar! The only bug I need to report is from the PC Client. If I am viewing the Recording (that exist on the server) I can play back and delete all recorded episodes with the exception of the last one listed. While on the server, I can delete the last listing with no issues. Example: 4 recordings of "Grey's Anatomy" - I delete 3 with no problems from the PC Client and I attempt to delete the last one and no errors are thrown, it just won't do it. If I console into the server and do it, it works just fine. Has anyone reported this as a bug yet?

[zed]

I've noticed this too, altho I didn't connect it to the last delete...maybe because there was only one episode for each show when I noticed it. I kind of suspected it might have something to do with network permissions but haven't had time to investigate it further.

I'm running streaming too, and it works just fine except for this little glitch.

[ptyler13]

Zed,

I am not sure its a rights issue... I have full admin rights from the PC Client to the server and all other deletes work just fine. I think it may just be related to the way the recordings lists are generated and viewed from the PC Client. It could be that the remote view will not allow for a 0 bounds return to bring it back to the main recodings menu and will also not complete the final delete transaction. If it did, the current view would not longer be valid, so the transaction is not completed. Just a theory...

[agidius]

I got past that by mapping my recordings directory to a drive letter, then pointing GBPVR to it via the drive letter.

not sure why it worked, but it did for me.

[jsebright]

I have the same problem on 0.98.13b running with the client in file sharing mode. Recordings share is set via a drive letter (on capture sources tab), same directory set on Directories tab. Will delete fine on the server.

[sub]

Reproduce the problem, then zip and attach the logs and I'll take a look.

[jsebright]

Hi Sub,

having a quick look at the log (snippet below) showed that it was trying to connect on 7967, so I opened that up on the server and it all worked fine. Zip contains client logs of port closed & delete failing, then port open and delete succeeding.
I've now got 7647, 7697, 7698 & 7967 opened up on the server related to gbpvr - is that right?

Regards & respect,

Jon.

Code:

0/10/2006 19:36:09.062    VERBOSE    [1]    getValue: /settings/ClientModeMediaPort : 7967
30/10/2006 19:36:09.062    VERBOSE    [1]    getValue cached value: /settings/ClientRemoteServer : Hal
30/10/2006 19:36:30.109    VERBOSE    [1]    Unexpected error deleting file from server: System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at GBPVR.Backend.Common.xfd4ccc57ec7c0067.xe46950d2ff2fd619(String x8b1d9e3189e6e73d)
30/10/2006 19:36:30.109    VERBOSE    [1]    Unabled to remove recording file (M:\Recordings\Natural World\Natural World_20061029_18101900-2.mpg)...leaving recording in place
30/10/2006 19:36:30.109    VERBOSE    [1]

[sub]

having a quick look at the log (snippet below) showed that it was trying to connect on 7967, so I opened that up on the server and it all worked fine

Ok, glad you got it working.

I've now got 7647, 7697, 7698 & 7967 opened up on the server related to gbpvr - is that right?

7647 is default web server port. 7967 is the client services port. 7968 is the recording serve .net remoting port. I'm not sure what the other ports are.

[jsebright]

A quick review of the firewall shows my fingers weren't working properly when I set them up.
I did have 7968 open (but typed the description as 7698! - referred to above)
I had also set up 7697 in error (should have been 7967!)

Sorted and double checked now - thanks for your help.