Changed Network Configuration - SageTV Server no longer found

[AzJazz]

Hi - I had to change my home network configuration from the 192.168.1.x range to the 192.168.2.x range.

I'm seeing two problems now:

1) When I start up the SageTV9 Service Control app, I always see the "Sage TV Service" = Stopped. If I press If I press "Refresh" and wait a few minutes, the service shows "Stopped" again.

2) Also, none of my Media Extenders can find the SageTV server.

How can I fix this?

Thanks,

AzJazz

[Narflex]

Extenders probably can't find the server because it's on a different subnet....it sends out UDP broadcast packets, and those will not travel from something like 192.168.1.x to 192.168.2.x because they are limited to the same subnet.

I'm not sure about the service issue...would need to see a log file (if it's even generating one).

[NetworkGuy]

Originally Posted by AzJazz

2) Also, none of my Media Extenders can find the SageTV server.

Do you have your Media Extenders set to DHCP (Automatic) or Static (Manual)? If it is static, they are still on the old subnet.

[KryptoNyte]

Do you have the SageTCPServer plugin running on your server? If so, disable that plugin and see if Sage service will start running reliably again. Probably also why your extenders can't find Sage.

[SageWizdom]

A couple of questions as a clarification

Originally Posted by AzJazz

I had to change my home network configuration from the 192.168.1.x range to the 192.168.2.x range.

A) Am I correct in assuming that this means you changed all the IPs on your network and your DHCP server and that all your computers now have a 192.168.2.x address versus having two subnets?

Did you make any other network changes at the same time? Do you hard code any of your IP's or are they all DHCP'd from another network device?

B) You talk about Sage 9, but your signature says v7 in windows. Is your sage 9 running in Windows or Linux? The IP address of your host may not have moved over correctly. You may want to check by running ifconfig and see what your eth0 is configured as.

Originally Posted by AzJazz

2) Also, none of my Media Extenders can find the SageTV server.

C) If you are using HD300s (I don't know the other devices) can you connect to sage with a hardcoded IP versus the autodetect? If so, it may just be the firewall configuration. If not, there may be other problems floating around.

[AzJazz]

Hi - I got my system set back to the 192.168.1.xxx range. I had SageTV working again. The Media Extenders were working OK, too.

However, I still couldn't get the SageTV Service running reliably. If I rebooted my PC, the SageTV Service would start and stay running. But, if the SageTV Service was stopped, it could be restarted temporarily and then it would always stop a few seconds later.

So, I decided to upgrade to 9.0.12.xxx today, and now I can't start the SageTV Service at all anymore. It always immediately terminates, and it isn't running after rebooting my PC.

Originally Posted by Narflex

I'm not sure about the service issue...would need to see a log file (if it's even generating one).

Where would I find the log file (if it is generated)?

Originally Posted by KryptoNyte

Do you have the SageTCPServer plugin running on your server? If so, disable that plugin and see if Sage service will start running reliably again. Probably also why your extenders can't find Sage.

I don't think I have the SageTCPServer plugin installed. Unfortunately, I can't tell at this time, since SageTV doesn't get past the startup screen now.

Update: After booting up my PC, I now always see this error message:

An exception occured in Java:
java.lang.UnsatisfiedLinkError:
sage.media.image.ImageLoader.loadImageDimensionsFromFile(Ljava/lang/String; )Lsage/media/image/RawImage;

Image here:

I don't know what to do at this point.

[Narflex]

That error would coincide with ImageLoader.dll not being in the SageTV folder..so something is wrong with the install.

[AzJazz]

To clean up my installation, I uninstalled SageTV 9.0.12.506. I then rebooted the PC, and reinstalled 9.0.12.506 again.

After rebooting again, the SageTV service appeared to come up fine again. I don't see the error message associated with ImageLoader.dll anymore.

However, after rebooting my PC a second time, the SageTV service is once again immediately stopping after starting, and can't seem to run on my PC anymore.

[AzJazz]

I uninstalled SageTV once again, and this time I deleted the C:\Program Files (z86)\SageTV directory.

Then, I rebooted, and installed SageTV 9.0.12.506.

The SageTV Service seems to be working OK now - both through the app and auto-starting after rebooting.

Now, I guess I have to rebuild my SageTV configuration from scratch again. Is there anything special I'll need to do to get everything running again? I do see EPG data, and it looks like my previous recordings were recognized.

[Thomas Wischgol]

Did you make a copy of your sage.properties file and wiz.bin before you deleted the directory? If so you stop the service and copy those back over. That should restore most of your settings.