TV Server not starting Win 10 (1 Viewer)

[joecrow]

Note that in W8 and newer, shutdown does not actually seem to shutdown; it seems to be some kind of power saving mode. Reboot does a proper power cycle. Perhaps your hardware has problems with the power saving mode?

[edit: Windows refers to this fancy shutdown as "fast startup" in the Control Panel power settings.]

To my knowledge the "fast startup" option saves some parts of the OS to disk to speed up the next startup. This has similarities to hibernation although I am fairly sure it then fully shuts down as opposed to entering a power saving mode, certainly the fans stop and the lights go out. Regardless I am booting from an SSD and when I initially upgraded from Win 7 I tested the boot times with and without the "fast startup" option, there was no difference at all but with the option enabled the shutdown time was considerably lengthened so I left it diasabled! Please note the restart I refer to is a system restart, i.e. an automatic shutdown and reboot which as mentioned does NOT clear/toggle the problem. I would suggest the toggling of the problem with a shutdown is more to do with leaving it with the power off for some while as opposed to any reboot hardware issue. I will however re-enable the fast startup mode to see if there is any change and report back here.
Is there any info. available I could supply (SQL logs etc.) that might point us to the cause of the error?

 

[mm1352000]

Please note the restart I refer to is a system restart, i.e. an automatic shutdown and reboot which as mentioned does NOT clear/toggle the problem.

In my opinion the fact that a restart doesn't clear/toggle the problem is another sign that you have a hardware, power or network (eg. address conflict) problem, as I previously said. After all, a system restart mostly restarts the operating system. It doesn't fully reinitialise the hardware (because the power is never completely removed).

I would suggest the toggling of the problem with a shutdown is more to do with leaving it with the power off for some while as opposed to any reboot hardware issue.

Yes, as above: a proper/complete shutdown and boot reinitialises the hardware. When shutdown has an effect but restart does not, it should tell you that the problem is likely to be hardware, power or network related. I did not say anything about a reboot hardware issue.

I will however re-enable the fast startup mode to see if there is any change and report back here.

There's been a misunderstanding here. I [wrongly] assumed that you would've been using the fast startup mode (since it appears to be enabled by default). I was trying to recommend to disable it. If it's already disabled then that's fine, and please leave it that way. Please do not enable it.

Is there any info. available (SQL logs etc.) that might point us to the cause of the error?

You can read the system event log (which I already pointed to).

The Windows system event log entries that I posted already told you that Windows is not attempting to start MySQL or TV Server due to whatever is causing the problem, so there will be no logs from either MySQL or TV Server.

The first errors in the system event log for the boot cycle on the 16th seem to be:
[collapse]
"16.10.2015 09:46:14";"Microsoft-Windows-DriverFrameworks-UserMode";"(101)";"Information";"WUDFPf (part of UMDF) did not load yet. After it does, Windows will start the device again.";"10114"
"16.10.2015 09:46:14";"Microsoft-Windows-Kernel-PnP";"(212)";"Warning";"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Canon&Prod_MG6300_series&Rev_0201#7&6f2971f&0&11FF72&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.";"219"
"16.10.2015 09:46:14";"Microsoft-Windows-DriverFrameworks-UserMode";"(101)";"Information";"WUDFSvc (part of UMDF) did not load yet. After it does, Windows will start the device again.";"10114"
"16.10.2015 09:46:14";"Microsoft-Windows-Kernel-PnP";"(212)";"Warning";"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_SD#MMC&Rev_1.00#8&bc7c096&0&058F63646476&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.";"219"
"16.10.2015 09:46:14";"Microsoft-Windows-DriverFrameworks-UserMode";"(101)";"Information";"WUDFSvc (part of UMDF) did not load yet. After it does, Windows will start the device again.";"10114"
"16.10.2015 09:46:14";"Microsoft-Windows-Kernel-PnP";"(212)";"Warning";"The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Generic-&Prod_Compact_Flash&Rev_1.01#8&bc7c096&0&058F63646476&1#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.";"219"[/collapse]

I'm ignoring them. They appear to be related to SD/flash card storage and/or printer, and I don't think an SD/flash card or printer error could cause this problem. Maybe I'm wrong.

The next error is:
"16.10.2015 09:46:15";"Service Control Manager";"(0)";"Error";"The Net.Tcp Listener Adapter service depends on the Net.Tcp Port Sharing Service service which failed to start because of the following error: %%1058";"3221232473"

That Net.Tcp Port Sharing Service relates to networking, which is why I've been saying that the problem could be network related.

Earlier in the log (15th) you can also see:
[collapse]
"15.10.2015 15:26:20";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"
"15.10.2015 16:50:05";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"
"15.10.2015 16:50:05";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"
"15.10.2015 18:57:55";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"
"15.10.2015 18:57:55";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"
"15.10.2015 19:09:01";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"
"15.10.2015 19:09:03";"NetBT";"(0)";"Error";"A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.";"3221229791"[/collapse]

Those entries another reason why I've been mentioning networking...

 

[joecrow]

I will however re-enable the fast startup mode to see if there is any change and report back here.

There's been a misunderstanding here. I [wrongly] assumed that you would've been using the fast startup mode (since it appears to be enabled by default). I was trying to recommend to disable it. If it's already disabled then that's fine, and please leave it that way. Please do not enable it.
.

Sorry but I did not see this response till after I tried it with fast startup enabled. Much to my surprise though, since re-enabling it the problem has not occurred, MP starts up fine every time both with or without power being connected durring the shutdown. I will need to do some longer term testing to convince myself that this has fixed but so far it is looking very good.

 

[joecrow]

Sorry but I did not see this response till after I tried it with fast startup enabled. Much to my surprise though, since re-enabling it the problem has not occurred, MP starts up fine every time both with or without power being connected durring the shutdown. I will need to do some longer term testing to convince myself that this has fixed but so far it is looking very good.

Further to the above, enabling the fast startup is certainly not fixing the root cause of the problem but it may be work around! My guess is that when enabled the fast startup saves a copy of the some parts of the OS to disc such that in the case when the TV Server is functional repeated shutdowns and reboots will consistently load a functional copy as opposed to starting everything up following the power reset with it disabled! I also verified that with the TV Server non-functional and fast startup enabled repeated shutdowns and reboots never returned it to operation unlike the toggle I am seeing with it disabled.
I also played round with the second NIC and can confirm that under some very variable and non-consistent circumstances it was knocking the TV Server out although as mentioned earlier uninstalling it did not stop the toggle effect of shutdown and reboot.

Is a 2 NIC setup a no go for the TV Server?????

Generally I am reasonbly confident that this problem is a software/hardware issue with this PC and at some stage I should do a clean install to clean things up and retry. Please let me know your opinion on that and many thanks for your help and anaysis of this problem

 

[mm1352000]

Further to the above, enabling the fast startup is certainly not fixing the root cause of the problem but it may be work around!

Sounds like a really really dodgy situation. If I were you I would avoid doing critical work on that PC (or if you must, take backups very often) and test the hardware properly (memtest86 etc.) ASAP.

My guess is that when enabled the fast startup saves a copy of the some parts of the OS to disc

According to various sources on the internet that's exactly what it does.

Is a 2 NIC setup a no go for the TV Server?????

TV Server can work with 2 NICs. You need to make sure that the NIC that you configure TV Server to use is the same NIC used by your database, that it has a static IP address, and that it will always be available.

Please let me know your opinion

I've already shared my full opinion in this and previous posts.

many thanks for your help and anaysis of this problem

You're very welcome.

 

[RobNorthcott]

FWIW, I'm running a single-seat setup on Windows 10 64bit (clean install rather than upgrade) and it's working fine. I have disabled the fast startup because I'm using an SSD, so I can't say if it works with that setting on.