tv service not beeing loaded automatically on startup (1 Viewer)

[Sebastiii]

Hi

And without Ramdisk or whatever memory tool, does it work correctly ?
If yes that's not an MP issue lol

 

[HomeY]

No, it doesn't. The order of services being installed is not configurable. Since I am calling the script via Task Scheduler upon Startup, one may run into the described issues. In your case because you are logging in as a user, the login/autostart will not be executed before all services are initialized. This would not reliably change when using the RamDiskStarter service and I would still have to check if the service was started.

That's not entirely true. On a Server 2012 installation you can also set task to 'Run whether user is logged on or not'. (General Tab). Besides that you can check the option to 'Run with highest priviliges', so IMDisk should go before anything else.
If you don't log into the server, it should be idle, and as an alternative you can set up conditions for a specific task. For example to start the task only if the computer is idle for xx minutes (Conditions tab).
This is configurable as long as you select 'Create Task....' instead of 'Create Basic Task...'

 

[HTPCSourcer]

@HomeY : I wanted to keep things simple. Yet the option "Highest privileges" has nothing to do with the order the tasks are executed, but rather grants administrator privileges - something necessary for ImDisk anyway. Playing with idle time properties is just a work around, and not really an option because the RamDisk is also containing the Temp path for Windows. Delaying this means that you are prone to shoot yourself in the foot because Windows will not find the path and use the standard on the HD/SSD.

Also there are other tasks executed on a server, therefore you can never be sure that it is idle.

 

[Lehmden]

And without Ramdisk or whatever memory tool, does it work correctly ?

No it doesn't. TVServer simply fails to start automatically. This has nothing to do with another Service or task on the System, It's pure MP1.8 TV Server issue.

And today I've encountered another really strange behaviour... I only was able to tune to HD channels on one of the two tuners on my card. Every SD channel reports "No Signal", no matter on witch transponder it was. Every HD channel (DVB-S and DVB-S2 channels) could be tuned on that tuner. The second tuner was able to tune SD and HD channels. And the channel mapping was correct, I've checked that. Only thing to get rid of this was a restart of the whole PC. Restarting TV Server did not help... I have no logs as I was in a hurry because I needed my tuners. If this will happen again I will try to collect logs for sure. BTW, only FTA channels, so CAM could not be the cause as there is no CAM...

Never had so much issues with any other version of TV server before.... I think I will go back to 1.6 as this was running stable.

 

[Sebastiii]

I have one server as 2012 and my other PC as win8.1 and didn't run into this issue (TvService not start).

Yep it's strange and surely a cause somewhere and maybe related to different hardware or soft installed.
Hope you can find the culprit or go back to your last stable running version.

 

[mm1352000]

<sigh>

No it doesn't. TVServer simply fails to start automatically. This has nothing to do with another Service or task on the System, It's pure MP1.8 TV Server issue.

Claus, you have the right to your opinion. However my opinion is [still] that this statement is not correct. I maintain that if there is nothing in the TV Server logs then Windows hasn't attempted to start the TV service.

Please post your system event logs as previously requested so we can have something substantial to talk about rather than continuing to say "I'm right; you're wrong".

And today I've encountered another really strange behaviour... I only was able to tune to HD channels on one of the two tuners on my card. Every SD channel reports "No Signal", no matter on witch transponder it was. Every HD channel (DVB-S and DVB-S2 channels) could be tuned on that tuner. The second tuner was able to tune SD and HD channels. And the channel mapping was correct, I've checked that. Only thing to get rid of this was a restart of the whole PC. Restarting TV Server did not help...

Sounds like a tuner driver or other issue. Almost 100% sure this has nothing to do with TV Server.

I have no logs as I was in a hurry because I needed my tuners. If this will happen again I will try to collect logs for sure.

Sorry but I don't understand this. Logs don't disappear. It takes less than two minutes to zip up and attach a folder and doesn't prevent you from using your tuners either.

Never had so much issues with any other version of TV server before.... I think I will go back to 1.6 as this was running stable.

It is easy to blame TV Server, but I honestly think the problems are elsewhere. Remember that TV Server has been under code freeze since MP 1.6. Yes, there have been some changes since then, but not substantial changes and IMO not changes that would cause these things. Even if I'm wrong and these changes really are causing problems, the cause(s) should be easy to find (due to very few changes between 1.6 and 1.8) as soon as log files are provided.

So once again I ask: please post your log files. Until then my hands are tied. It's completely up to you...

 

[Lehmden]

Hi.
I've started my system without the workaround. Then I started watchdog. MP Client needs to start TV Server (waiting for TV Service to start...). After start of client was finished I exit MP client and here are the logs.

 

[mm1352000]

Thanks Claus
Unfortunately it looks like your system and/or application event logs were cleared:
[2014-07-13 08:55:29,606] [Log ] [MPMain ] [INFO ] - Main: MediaPortal v1.8.0.0 is starting up on Windows 7 ( Service Pack 1 ) [6.1.7601.65536]
"13.07.2014 08:55:29";"Microsoft-Windows-Eventlog";"(104)";"Information";"Die Protokolldatei "System" wurde gelöscht.";"104"

So, I can't see what I'm really interested in, which is what happened during system boot.

mm

 

[Lehmden]

Hi.
Did not do this myself. So how can I avoid this?

 

[Sebastiii]

Maybe system is fucked up ?
Maybe you could try a fresh restart of your PC + debug first option