[confirm] tvservice dying very often (1 Viewer)

[bounguine]

1. Do you mean I should change 255.255.255.0 for MS loopback adapter? Sound strange, as I used MS loopback adapter long ago when MP was unstable without changing the submask. And that did the trick perfectly. When MP became stable, I revert to *.67 (real PC's IP).
2. TVServer is not accassible normally neither with 192.168.1.67 nor with 192.168.1..7. I decided to change back to MS loopback adapter, as problems came right after upgrading to 1.1.0*

 

[arion_p]

1. Do you mean I should change 255.255.255.0 for MS loopback adapter? Sound strange, as I used MS loopback adapter long ago when MP was unstable without changing the submask. And that did the trick perfectly. When MP became stable, I revert to *.67 (real PC's IP).
2. TVServer is not accassible normally neither with 192.168.1.67 nor with 192.168.1..7. I decided to change back to MS loopback adapter, as problems came right after upgrading to 1.1.0*

Either change the loopback IP address to another subnet (eg 192.168.2.7/255.255.255.0) or change the subnet on both loopback and physical adapters so that their addresses fall on different subnets (eg loopback 192.168.1.7/255.255.255.192, physical 192.168.1.67/255.255.255.192). Of course in the latter case you have to make sure all devices on your physical network have the same subnet mask

 

[bounguine]

I'd better change MP to work with the real IP and post logs here tomorrow.
I can't understand why 1.1.0* fails to work as previous versions.

 

[bounguine]

Now I reconfigered MP and TVServer to use 192.168.1.67.
But errors come again and again.

I see that there's an SQLServer error in logs.
Actually, in early releases to solve this problem and not to use loopback adaptor I wrote MSSQL$SQLEXPRESS in registery and restarted PC.
But if I do it now in 1.1.0* this record is automatically deleted anyway after restarting my PC.