Desktop App crashes after recent upgrade

[zaldwaik]

What do you need to do in NextPVR?  You can also nlite, knewc  or the web for most things.

Martin

I find the client more user friendly and intuitive to use. I have used it for 15 years, so it is hard to part with it.

[mvallevand]

But nlite and knewc on Kodi are the same UI  just like the PCH so I was wondering what specifically you meant.

Martin

[sub]

Thanks. That works. It is slow to respond to key presses, but I can live with that.

what CPU is in the server? Is it a fairly slow machine?

[mvallevand]

I just used RDP to connect to my WIn 11 server and NextPVR.exe works without crashing.

Martin

[adis99]

For me it is not running correctly on new update too:

Event logs show:

Application: NextPVRServer.exe
CoreCLR Version: 4.700.21.35901
.NET Core Version: 3.1.18
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.Sockets.SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions.
  at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName)
  at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
  at System.Net.Sockets.Socket.Bind(EndPoint localEP)
  at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
  at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
  at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.<>c__DisplayClass21_0`1.<<StartAsync>g__OnBind|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
  at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.AnyIPListenOptions.BindAsync(AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context)
  at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IServerAddressesFeature addresses, KestrelServerOptions serverOptions, ILogger logger, Func`2 createBinding)
  at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServer.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
  at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token)
  at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host)
  at NPVR5.Program.Main(String[] args)



Faulting application name: NextPVRServer.exe, version: 1.0.0.0, time stamp: 0x60ef187c
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0xc9db1934
Exception code: 0xe0434352
Fault offset: 0x0000000000034f99
Faulting process id: 0x4e08
Faulting application start time: 0x01d7ababf374b6d7
Faulting application path: C:\Program Files\NextPVR\NextPVRServer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 1552f084-53a3-4f55-a342-2c477142d759
Faulting package full name:
Faulting package-relative application ID:

[mvallevand]

The minidump might help sub but can you provide the logs too.

Are you also running NextPVR via RDP if not you really should have opened this in a new post?

Martin

[adis99]

The minidump might help sub but can you provide the logs too. 

Are you also running NextPVR via RDP  if not you really should have opened this in a new post?

Martin

Minidump is in attachment

[mvallevand]

I know that is why I asked for logs and you didn't say if you were using RDP.

Martin

[adis99]

I know that is why I asked for logs and you didn't say if you were using RDP.

Martin

I do not use RDP, its local on my box.Logs attached

[mvallevand]

Ok so you completely hijacked the topic. Typically that error is simply a firewall antivirus, internet suite or VPN not permitting you to open the server ports. default 8866 TCP and 16891 UDP

Martin