2005-10-17, 10:44 PM
I setup GB-PVR to record to a network drive. Unfortunately, it didn't work and I didn't really know why so I took a look into the log files and found this:
10/17/2005 6:16:34 PM.000 ERROR [23] Error starting recording: Could not find a part of the path "\\SERVER\Videos".
10/17/2005 6:16:34 PM.031 ERROR [23] Error starting recording: at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path)
at System.IO.Directory.CreateDirectory(String path)
at GBPVR.RecordingService.RecordingManager.GetFileNameAndCreateDirectories(ScheduledRecording xe41d2b9d98dc1269)
at GBPVR.RecordingService.RecordingManager.WorkerThread()
I tried it with a mapped drive letter (ie "Z:\") but that still didn't work. Since I have a server called "SERVER" that has a much bigger hard drive (but not enough CPU to run GB-PVR) I wanted a way to make this work.
After searching, I found out that I needed to create a new account on the server account and another account with the same name on my gb-pvr machine (the client machine). I then changed the GB-PVR recording service to run as this account and it worked!
To summarize, the steps I used to get GB-PVR to successfully record on a network share were:
- Create an account on both the network machine and the local machine with the same password
- Change the GB-PVR service to run as that account (in Control Panel -> Services)
If you are using a domain then you need to add the service account for the client computer to a domain share (not entirely sure about this but it shouldn
't be too hard).
I wonder if a detection routine could be built into the GB-Config util that would alert the user if a network path were selected that it won't work unless you take the above steps.
10/17/2005 6:16:34 PM.000 ERROR [23] Error starting recording: Could not find a part of the path "\\SERVER\Videos".
10/17/2005 6:16:34 PM.031 ERROR [23] Error starting recording: at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path)
at System.IO.Directory.CreateDirectory(String path)
at GBPVR.RecordingService.RecordingManager.GetFileNameAndCreateDirectories(ScheduledRecording xe41d2b9d98dc1269)
at GBPVR.RecordingService.RecordingManager.WorkerThread()
I tried it with a mapped drive letter (ie "Z:\") but that still didn't work. Since I have a server called "SERVER" that has a much bigger hard drive (but not enough CPU to run GB-PVR) I wanted a way to make this work.
After searching, I found out that I needed to create a new account on the server account and another account with the same name on my gb-pvr machine (the client machine). I then changed the GB-PVR recording service to run as this account and it worked!
To summarize, the steps I used to get GB-PVR to successfully record on a network share were:
- Create an account on both the network machine and the local machine with the same password
- Change the GB-PVR service to run as that account (in Control Panel -> Services)
If you are using a domain then you need to add the service account for the client computer to a domain share (not entirely sure about this but it shouldn
't be too hard).
I wonder if a detection routine could be built into the GB-Config util that would alert the user if a network path were selected that it won't work unless you take the above steps.