Vista Ult and BRP error13 driving me nuts!!

[Hunter]

My system has a new install of Vista Ult and BRP with TVxb grabber. Have followed all the install instructions from the TVxb site to the letter (many times) without success.

Have tested loading the IIS web pages, BRP+TVxb in manual mode and everything works fine, with files written to the relevant folders etc. No errors at this point.

Under Vista's MCE everything is Ok until the end of the guide setup process wnere the error occurs.

I think im my case the error 13 is real as I have watched the TVxb log file and the BRP guide folder for any signs of activity during the down load process. Nothing happens. Its Just like BRP did not start.

Can anyone tell me how the BRP process is started or suggest some fixes for this. I have read many posts and carried out the suggestions without any luck.

Any Help appreciated.

[ozbear]

Originally Posted by Hunter

Any Help appreciated.

Subscribe to IceTV.

You said any.

Oz

[billd]

Originally Posted by Hunter

...I have watched the TVxb log file and the BRP guide folder for any signs of activity during the down load process. Nothing happens. Its Just like BRP did not start.

Can anyone tell me how the BRP process is started or suggest some fixes for this...

The sequence of events is:

1. You can setup BRP as a scheduled task - nightly or every 2 days suggested - or you can manually run it.
2. BRP invokes TVxb which will create a listings2.xml file (or xmltv.xml file - depending on what you have specified in TVxb.ini) and a ChannelInfo.xml file under the relevant ehome/BladeRunner folders.
3. BRP will then convert these xml files to guide.bin
4. Sometime later, completely unrelated to the BRP/TVxb task, either you will force a guide download, or MCE will automatically download - from the guide.bin file created earlier. (Presumably this is when you get your Error 13.) Note that neither BladeRunner nor TVxb are involved in the guide download. They have already created the gudie.bin at an earlier time. Nothing else for them to do.

Assuming guide.bin is being created and can be accessed through the browser, and ChannelInfo.xml contains valid channels ids - no repeated channel numbers/names or numbers out of sequence, then your error 13 is most likley due to MCE/Vista setup.

I had a similar Error 13 message in a Vista system I setup recently. The guide downloads had been working fine for a week, but stopped working after I made some unrelated changes to the system. In the end I had to reinstall Vista to get the guide working again. I never identified the root cause, however the two likely suspects were turning on the Vista firewall and installing ActivKey/MSRA software so I could tunnel into my company's network. There was nothing I could do with Vista setup /registry setting resets etc. to get it to work again.

Quite possibility these are not the cause of your problem. I guess my point is that - just maybe - MCE/Vista is messed up enough for whatever reason, you might need to go back to square 1.
As a first step run the MCE setup again - completely through. Then make sure keepkey is successfully retaining the download URL. Then expand the scope of the rebuild from there. Good luck and persevere!

[Hunter]

Thanks for your very informative post.

Now I feel like such a nob!!

The BRP and TVxb process is working fine, and generating the appropiate files, which I have checked for valid info etc. No issues here.

The ISS stuff is also working fine and I can access the NATIVE files and guide.bin as advertised.

Keepkey installed and operational.

The only issue seems to be some nobhead with admin rights to my pc has been deleting guide.bin manually and waiting to see if it get regenerated during the guide download process from MCE which doesn't happen, as you have so clearly explained.

I will try again later without first deleting guide.bin. I have a warm feeling things will be different.

Thanks once again, I'll keep you posted.

[mikehayton]

You might want to check out this post. If you install KB935685 and add the registry key to enable it (instructions in the previous link), then there's no need for keepKey. Instructions on how to uninstall keepkey are in this post.

Cheers

Mike