Cannot connect after W10 update (1 Viewer)

[Mat Walker]

So this is driving me silly and soo regret 'up'grading to Win10

All has been working great. MP1 server on a W10 box and clients on a mix of W10 and W7 boxes,

The Server installed a bunch of W10 updates and life became much harder. The file shares were the first I noticed had broken (outside MP); ended up having to reset IP/Winsock/etc on clients.

Then found that none of my MP clients could connect to TV server anymore. Complaining of inability to connect to server or database. The server has no firewall (disabled) and the local TV client running on the server works fine. The client logs don't show any errors (which is fair enough, there is no error as far as they are concerned; they just cant connect) and the server doesn't register any connection coming in. I've tried using server name and ip address when connecting and I can remote desktop in (so 3389 is not blocked by anything); its odd.

Has anyone else had this? Or is it just me? lol

Server & Clients at 1.15.0.0

 

[jmuellers]

I seem to have the same Problem, Server and Client, for 1.18 as well as 1.19pre.
Problem started after a power fail on the client.

Disabling firewalls on client and server did not help.
Only error I can find in MediaPortal-Error.log is:

[2018-02-09 10:46:56,047] [Error  ] [MPMain   ] [ERROR] - Tv NotifyManager: Exception at timer_tick System.TypeInitializationException: Der Typeninitialisierer für "Gentle.Framework.ProviderFactory" hat eine Ausnahme verursacht. ---> Gentle.Common.GentleException: FATAL ERROR: No configuration store was found!
Gentle is unable to continue!

The handlers emitted the following error messages:
Unable to create GentleSectionHandler for section named "gentle" in file "C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe.Config".

Unable to create FileHandler for file Gentle.config.
This usually means that the file could not be found in any of the default search locations.

The handlers threw the following exceptions:
System.Xml.XmlException: '.', hexidezimaler Wert 0x00, ist ein ungültiges Zeichen. Zeile 1, Position 1.
   bei System.Xml.XmlTextReaderImpl.Throw(Exception e)
   bei System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   bei System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
   bei System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlTextReaderImpl.Read()
   bei System.Xml.XmlValidatingReaderImpl.Read()
   bei System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   bei System.Xml.XmlDocument.Load(XmlReader reader)
   bei Gentle.Common.FileHandler.LoadXml(TextReader reader)
   bei Gentle.Common.FileHandler..ctor(String file)
   bei Gentle.Common.Configurator.AddFileHandler(String configStoreName, String fileName)


   bei Gentle.Common.Configurator.InitializeHandlers()
   bei Gentle.Common.Configurator.Configure(String configStoreName, Object instance)
   bei Gentle.Framework.ProviderRegistry..ctor()
   bei Gentle.Framework.ProviderFactory..cctor()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Gentle.Framework.ProviderFactory.GetProvider(Type type)
   bei Gentle.Framework.SqlBuilder..ctor(IGentleProvider provider, StatementType stmtType, Type type, LogicalOperator logicalOperator)
   bei TvDatabase.Recording.ListAllActive()
   bei TvPlugin.TvNotifyManager.AddActiveRecordings()
   bei TvPlugin.TvNotifyManager._timer_Tick(Object sender, EventArgs e) st :    bei System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   bei System.Environment.get_StackTrace()
   bei TvPlugin.TvNotifyManager._timer_Tick(Object sender, EventArgs e)
   bei System.Windows.Forms.Timer.OnTick(EventArgs e)
   bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   bei System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   bei System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   bei System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   bei System.Windows.Forms.Application.Run(Form mainForm)
   bei MediaPortalApp.Main(String[] args)

Edit:
It seems I have fixed to problem.
I was looking in this thread: please specify the ip address or hostname of the master tv service
And indeed, after I exchangend the gentle.config with a backed-up version (which luckily Mediaportal seems to create every now and then), it is running flawlessly again.

 

[Mat Walker]

I think I'm going to have to do a server rebuild. I was on it all last night. Tried uninstalling network 'card', re-installing, turning firewall on then off again, finding every 'tweak' I could and fiddling (admittedly relatively blindly - I'm techy, but there some stuff in W10 I find baffling lol) with it but no; MP clients just 'cant see' the server.

I can open file shares, access Remote Desktop and browse to a website being hosted on the server - but all the MP clients are quite adamant; they cannot connect to server or database. Local client running on the server is ok so thye TV server and database are running all ok.

Using TCPView from Sysinternals, I can see TVService is listening on 554 & 31456 and MySQL on 3306 - and also that the local client is hooked in to them. So why are the clients saying they cannot connect to the TV service or the database?

Is it really only me this has happened to?

 

[Mat Walker]

Ok, fixed.

As usual with things that are bizarre it was both simple and weird. After trying everything sensible and semi-sensible I slowly moved to the downright stupid. I run Viper as my antivirus as it has a small footprint and just gets on with the job quietly. I had the firewall on it turned off as I use a hardware firewall at the WAN level and so happy without firewalls inside. For no reason other than I'd not tried it, I turned it on allowing MP and MySql throught - hey presto, what problem!??? It just worked.

How bizarre is that. Windoze 10 was stating quite adamantly - almost shouting - that my computer was at risk as I had no firewall. I'd tried turning it/defender on and off to no avail. Yet, turn on the third party firewall, allowing MP through, and all was good!!! My guess is that there is - yet another - bug in W10 around the defender firewall and latest update that makes it misreport that it is off whereas it is actually on. Turning the 3rd party firewall really does turn off the defender firewall and hence allowing MP/MySql through when allowed.

- Just incase it helps any other unfortunate Microsoft customer (I actually only run Windows at home now for Media Portal - which I must repeat is fab)

 

[joecrow]

With respect to Windows Defender this may cast some light on the issue.

 

[Mat Walker]

Yes that's exactly it Joe.