Client Install Hosed Server Install?

[PeteCress]

Had Client on my laptop and found it was not able to play some .mkv files - which played a-ok on an HD200 and ok under Server on the Server PC.

Trying to localize the problem, I installed Client on the Server PC figuring that if Client could play those .mkv files there, that would tell me something.

Beeeeg surprise: Not only does Client not work on the Server PC (some kind of Java error....) but my SageTV Server install is hosed: no SageTV.exe, no Service...

Now, of course, as soon as I try to re-boot from a memory stick to re-image the system the PC's BIOS is acting weird and I can't get a Boot Menu....

That being the case, I figured I'd put up the Client-Hoses-Server story here and see if I am the only one.

Hopefully moot in the big picture - once I can get this thing re-imaged - but inquiring minds want to know....

[nyplayer]

Originally Posted by PeteCress

Had Client on my laptop and found it was not able to play some .mkv files - which played a-ok on an HD200 and ok under Server on the Server PC.

Trying to localize the problem, I installed Client on the Server PC figuring that if Client could play those .mkv files there, that would tell me something.

Beeeeg surprise: Not only does Client not work on the Server PC (some kind of Java error....) but my SageTV Server install is hosed: no SageTV.exe, no Service...

Now, of course, as soon as I try to re-boot from a memory stick to re-image the system the PC's BIOS is acting weird and I can't get a Boot Menu....

That being the case, I figured I'd put up the Client-Hoses-Server story here and see if I am the only one.

Hopefully moot in the big picture - once I can get this thing re-imaged - but inquiring minds want to know....

Don't know what to tell you maybe the install of the client on the server pc probably uninstalled the server.

Why would you even Install the client on the server pc why not just bring up the server SageTV ui it is the same as a client.

[stanger89]

I'm pretty sure SageTV and SageTVClient install to the same directory by default (Program Files/SageTV), so if you didn't change that that very well could have hosed your SageTV install, especially if the server was running at the time, files may have been locked that the client tried to overwrite.

I think you can have both installed, but you need to make sure you install them to different directories.

[PeteCress]

Originally Posted by stanger89

I'm pretty sure SageTV and SageTVClient install to the same directory by default (Program Files/SageTV), so if you didn't change that that very well could have hosed your SageTV install, especially if the server was running at the time, files may have been locked that the client tried to overwrite.

I think you can have both installed, but you need to make sure you install them to different directories.

Uninstalled Client, installed SageTV... and the problem went away... sort of.

Now (after an extra re-install to clear up something else) Sage is working normally when I open it on the Server PC, except that the "SageTV Media Center Version 7" splash screen never goes away... it just sits there forever with "SageTV Service is initializing".

The good part is that it does not stay in the foreground: the SageTV user interface covers it up. The bad part is that it's obscuring part of the Windows Desktop.

Any suggestions for a quick fix? Or are there a few more uninstall-reinstall cycles in my future?

[stanger89]

I have not seen that before. Worst case, backup your SageTV directory, then unsintall, blow it away, reinstall, and then replace your sage.properties and wiz.bin.

[PeteCress]

Originally Posted by stanger89

I have not seen that before. Worst case, backup your SageTV directory, then unsintall, blow it away, reinstall, and then replace your sage.properties and wiz.bin.

Yeah... I think that's what is next. I was grasping at straws.

FWIW, using a TaskManager-like utility called Process Lasso I found four instances of things calling themselves "SageTV" open. Closed 3, got lucky, and the UI stayed open. One of the three must have been the Service...

Restarted the Service via SageTV Service Control and things look normal.