Need to intermittently restart NPVR Service to get NPVR and KODI to work correctly

[elstaci]

After moving to version 5 from version 4, With help from Martin and Sub I was finally able to configure my 4 TV Tuner card correctly in Settings by enabling all my Tuners and correctly mapping all the channels in each of the 4 tuners.

But now, once in a while, when I start up KODI I receive an error that the "NPVR ADDON failed to load" and then I immediately go to NPVR Desktop app and it gives me a warning "Unable to connect to Remote Server"

I immediately go to Windows Services and stop and restart the NPVR Service. Once again both NPVR and KODI are working normally again except for the usual lag or Buffering while watching Live TV or TV Recording. I can live with that. Possibly it will be fixed when both NPVR and KODI are updated next time.

[mvallevand]

Things don't typically just get fixed. Someone needs to upload logs to show what might be going on. In addition in situations like this I would include information from the Windows Event Viewer.

Martin

[elstaci]

Things don't typically just get fixed.  Someone needs to upload logs to show what might be going on.  In addition in situations like this I would include information from the Windows Event Viewer.

Martin

Just got the information from Event Viewer after reading another thread similar to mine right now:

Error 3/29/2020 9:30:57 AM Application Error 1000 (100)
Faulting application name: NextPVRServer.exe, version: 1.0.0.0, time stamp: 0x5dedc13b
Faulting module name: KERNELBASE.dll, version: 10.0.18362.719, time stamp: 0xb31987d3
Exception code: 0xe0434352
Fault offset: 0x000000000003a859
Faulting process id: 0x3db8
Faulting application start time: 0x01d605328089d199
Faulting application path: C:\Program Files\NextPVR\NextPVRServer.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: eb33e323-6f8c-4080-96f3-4665b6a8f26a
Faulting package full name:
Faulting package-relative application ID:

Error 3/28/2020 2:53:23 PM Application Error 1000 (100)Faulting application name: NextPVRServer.exe, version: 1.0.0.0, time stamp: 0x5dedc13b
Faulting module name: KERNELBASE.dll, version: 10.0.18362.719, time stamp: 0xb31987d3
Exception code: 0xe0434352
Fault offset: 0x000000000003a859
Faulting process id: 0x1cb0
Faulting application start time: 0x01d604c936faed87
Faulting application path: C:\Program Files\NextPVR\NextPVRServer.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 71261469-044d-4943-b645-9f64ca4b089e
Faulting package full name:
Faulting package-relative application ID:

Also last time I uploaded my logs it had sensitive information in it.

Let me check my NPVR logs first to make sure there isn't any sensitive data in it like last time.

I didn't include NPVR Recording logs since those have sensitive data in it.

[mvallevand]

Yes it is crashing. If you followed my instructions then there wouldn't be sensitive information anymore to redirect stdout using
> NUL there won't be any sensitive information.

Martin

[elstaci]

Yes it is crashing.  If you followed my instructions then there wouldn't be sensitive information anymore to redirect stdout using
> NUL there won't be  any sensitive information.

Martin

Trouble is you never gave me explicit instructions on how to apply >NUL and where when I asked you the last time.

I add >NUL at the beginning of my UpdateEPG.bat right before the Login data the last time you mentioned it. but I don't know if that is what you meant or where it should go.

[mvallevand]

You didn't include the nrecord logs so that won't help.

I did post that I wouldn't support SD because users that use zap2xml don't consider the impact of the time their questions cost trying to save them $2.50 a month. I wish zap2xml users would help each other more by creating a wiki page

Anyway, edit you batch file (this is Windows batch file 101 easily found on the Internet) and add this so your command line doesn't show

@echo off

When you run zap2xml add > nul 2>&1 at the end.

The -q option might do the same thing you can try and see.

Martin

[elstaci]

You didn't include the nrecord logs so that won't help.

I did post that I wouldn't support SD because users that use zap2xml don't consider the impact of the time their questions cost trying to save them $2.50 a month.  I wish zap2xml users would help each other more by creating a wiki page

Anyway, edit you batch file  (this is Windows batch file 101 easily found on the Internet) and add this so your command line doesn't show

@echo off

When you run zap2xml add > nul 2>&1 at the end. 

The -q  option might do the same thing you can try and see.

Martin

I added %echo off as the first line of my UpdateEPG.bat.

after my last command I copied & pasted your command in the .BAT file.

Should I delete all of my NRecording logs now and see if the new logs doesn't include the sensitive data?

[mvallevand]

You failed 101 it is @echo off.

Stop the recording service, delete the files in the log folder and restart the server. Next crash upload the logs.

Martin

[elstaci]

You failed 101  it is @echo off.

Stop the recording service, delete the files in the log folder and restart the server.  Next crash upload the logs.

Martin

Didn't fail just accidentally click on the wrong key.

But thanks for pointing out the noobie error.

Stopped NPVR Service and deleted all NRECORDING LOGS.

Next time the Service crashes I will upload the logs with any Event Viewer errors.

[elstaci]

Okay I am now able to upload next time NPVR NRECORD Logs without any sensitive data on it.

I needed to first convert the UpdateEPG.bat to UpdateEPG.exe file using a free program called Batch Compiler (Source Forge).

My original BATEXE program didn't convert a my .BAT file into a working .EXE file.

Next I created a new UpdateEPG.bat with the command START UpdateEPG.exe.

Deleted all NRECORD Logs and Scripts XML file and Cache Folder.

Went to Web client Settings and  Emptied EPG and ran Update EPG.

Ran like it was the original .BAT Files before I converted it into a .EXE file. and populated NPVR's TV GUIDE.

Needed to do this because even with @echo off and >NUL, NPVR logs still showed the same sensitive data. Now it doesn't.