|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
SageTV + SageTV Client = Read error ??
I'm using version 1.4.10 of SageTV and the SageTV client. Just last night, I setup the client and it _was_ working great. Then later on in the evening I tried loading it up again and it sat there saying "Object DB is backing up and compressing itself..." for a while and came back to me with an error window titled "Connection Error" which reads "Unable to connect to the SageTV Sever at:<omitted> java.net.SocketTimeoutException: Read timed out" (this is different than the error message given when the server is off). I've read about this problem occuring before here on the forms and the thread indicated that the problem just "went away".. The problem hasn't gone away yet. Any advice?
Thanks Dan |
#2
|
||||
|
||||
Try restarting the SageTV server. That should fix it. Let me know.
__________________
Jeffrey Kardatzke Founder of SageTV |
#3
|
||||
|
||||
tried this... didn't work. Tried reinstalling SageTV client, didn't work. I want to avoid reinstalling the server.
|
#4
|
||||
|
||||
If you don't care about losing your settings/infromation, deleting the Wiz.bin and Wiz.bak files on the server will fix the problem for sure.
__________________
Jeffrey Kardatzke Founder of SageTV |
#5
|
||||
|
||||
Yea.. I noticed that my EPG information was starting to get a lot of "BAD AIRING"s and the 'next update' said "0"... very strange. I just deleted the wiz.bin file and the EPG is fixed now, I assme the client will work now too (I'll post back if it doesn't). Any idea what caused the wiz.bin corruption?
|
#6
|
||||
|
||||
Were you running 1.3.8 before and did an upgrade? If so, then it was probably something from 1.3.8 that finally manifested itself. So far in 1.4.10 I'm not aware of any DB corruption anymore. If 1.4.10 is new, then you probably just had some hard disk corruption due to an improper shutdown (XP is really bad about that if you've got disk caching enabled).
__________________
Jeffrey Kardatzke Founder of SageTV |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|