New HD300's crashing SageTV

[valnar]

I have two HD300's that work perfectly (have for years) with my SageTV 7 setup, and I bought two more during the sale. I tried to use them today on a TV and my SageTV service ended up crashing & stopping. I don't know why.

• Both new HD300's cause this to happen
• Only a full PC restore from a backup of Windows & all apps fixes this. Fortunately it was just done.
• One of my working HD300's on the same TV with the same ethernet cable work fine. 'Verified just in case.
• Firmware on both units updated to either latest release or latest beta. (Both my working units have the May 2011 beta and are fine).

I've tried factory resets on them. No workie.

For a moment I thought I had a bad HD300 but confirmed it happens on BOTH new units. Service stops after about 30 seconds or so. If I try to restart it, it dies again in under a minute. Only a full PC restore fixes it. Both HD300's work in standalone mode just fine. It's the server connection that kills it.

Any ideas?

[Bartok]

I'm not sure what the problem is for certain, but I've had a similar issue. Both HD200 and HD300 units that were new to me. When it crashes it actually corrupts the sage.properties file I think so that Sage service doesn't actually launch properly afterwards.

When I disabled most of my plugins I was able to get a new one to connect, and play content just fine. However, with the plugins enabled it would crash again.

My guess is that it has to do with allocating more memory for the new HD units, and the plugins also needing to allocate memory, and with the current 32 bit limitations on memory causing me issues.

[Stu Gare]

I've had similar and narrowed my issue down to one of the power saving plugins.
Disabled that and the problem went away.

[valnar]

Originally Posted by Bartok

I'm not sure what the problem is for certain, but I've had a similar issue. Both HD200 and HD300 units that were new to me. When it crashes it actually corrupts the sage.properties file I think so that Sage service doesn't actually launch properly afterwards.

When I disabled most of my plugins I was able to get a new one to connect, and play content just fine. However, with the plugins enabled it would crash again.

I'm out for the night, but will try disabling plugins tomorrow. However, why would it work for the other two? Could it be a permissions issue within NTFS on that file?

I don't think it is memory related since I had my other two HD300's off when I tried the new one, or in the case of the older one I tested, it was the only one and worked fine.

[Bagal]

I had a similar problem connecting another Windows client, it was to do with the SageTCPServer plugin, which only supports a fixed number of clients and was trying to allocate the same port number again.

To fix it, I edited the sage.properties file on the server to remove the SageTCPServer properties (can't remember which ones exactly) but that then allowed the new client to connect.

[KryptoNyte]

Had a problem very similar, I went with the same route initially, restoring an old system backup.

After some digging, I resolved it by disabling the SageTCPServer as Bagal mentioned, so I would definitely start there. I think I was only using the TCPServer with the SageTV Android remote control app.

[KryptoNyte]

I think things start getting to the point down on post #169.

http://forums.sagetv.com/forums/show...t=53764&page=9

[valnar]

That did it! I cleared out all the extenders from the sage.properties since I had ones going back to HD100's and HD200's that I've sold. The three HD300's I'm using now are all good.

Thanks everyone.