UpdateEPG.bat not being triggered. (Using Webgrab+Plus)

[mvallevand]

Well done. So rather than being helpful, you decided to go the obnoxious route.

Correct otherwise other users might also miss the forum search and waste unnecessary time (for them and us) and like you did.

Martin

[pmcdon]

Just some final points to help anyone who may arrive here with the same issue. I experienced a couple of stumbling points when figuring this out:

The first on is the WebGrab+Plus documentation is quite sparse. So for example, it offers an UpdateEPG.bat file for NPVR which is not commented or otherwise documented. At line 14, it passes a parameter (not mentioned anywhere in the official documentation) "C:\ProgramData\ServerCare\Webgrab" to the executable but does not explain why. On examination, there is only a log file in that location. The given UpdateEPG.bat file will then fail because the 'WebGrab+Plus.config.xml' and the needed site.ini files are not in that location by default (As stated in Configuration->HowTo, they are in "%LOCALAPPDATA%/Webgrab+Plus") . Adding to the confusion, the documentation states (in Quickstart) that the file IS located in "C:\ProgramData\ServerCare\WebGrab" (it really isn't). At least not in my Windows 10 x64 install. When you do put it there, it turns out that you didn't need to pass that directory parameter to the .exe anyway, as it will find it there automatically.

The second point is that it has been suggested in other posts that running 'WebGrab+Plus.exe' via the user account might solve the problem. I.e. using: runas /user:UserAccountName The issue with this approach is that the batch operation will halt prompting for input of the UserAccount password, which is not useable for unsupervised execution. Even if you can automate password entry, the user password is not something you should be putting into a plaintext batch file.

So to sumarise, When NPVR fires up the UpdateEPG.bat file, it does so using the LOCALSYSTEM account (Thank you sub). This account does not have full control of the files in the \Users account folders. So you need to relocate the necessary configuration .xml files to a LOCALSYSTEM accessable location. If you are just setting this up for the first time, it's best to also output your guide.xml file there also. You can pass the parameter of the new location via the parameter described above OR just place eveything in "C:\ProgramData\ServerCare\Webgrab" where it will be found by the .exe. If necessary elevate the security levels of 'WebGrab+Plus.exe' as described in a previous post. THE END

[pmcdon]

Correct otherwise other users might also miss the forum search and waste unnecessary time (for them and us) and like you did.
Martin

Martin, I am well aware how to search both Google and the forum. How else do you think I solved the problem? Definitely not with your help. The first link you posted (deliberately and obnoxiously too late) is to a batch file that I was already well aware of. It is uncommented and is not otherwise documented. It also does not work as set out on that page, for reasons I have given in my previous post. The second link is to a similar thread but I note that it presents a solution as elevating the security privileges of the folder in which the config files reside as well as using runas switches which did not work for me and was not a usable solution for the issue I had on my system.

I clearly mentioned in my first and subsequent post that I was aware of other users with similar issues and had read those posts and was also reading the official documentation. Neither of your provided links suggest relocating the config files from their default location OR elevating WebGrab+Plus.exe privileges, which was the actual required solution.

Personally, I always give help to others when I can in any forum but there is always a smug knob on every forum who is too important to do anything other than offer vague comments after the fact and make it known how tedious it is to have to read and respond to something that has already been discussed in 2014. If it's all so odious, why do you insist on commenting?