ZapImport fails (manifest discrepancy?)

[BobAtTorrey]

[EDIT: I can't explain this, because I believe I've changed nothing since, but yesterday zapimport consistently failed, as described below, but today it works. So please ignore this post.]
I just installed gbpvr .97.9, and converted to SQLite. Seemed to go OK.

I then used ZapConvert, per the instructions, in a separate directory. It ran without error, and I copied the resulting .db3 file into the gbpvr directory. Then I extracted the new ZapTools into the gbpvr directory, and tried to run ZapImport. It bombs with an unhandled FileLoadException. It complains that: "The located assembly's manifest definition does not match the assembly reference". Makes me think I've somehow got this mis-installed, but I followed the instructions as I understood them. Please help !?!?

Here is the error text:

Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'ICSharpCode.SharpZipLib, Version=0.84.0.0, Culture=neutral, PublicKeyToken=1b03e6acf1164f73' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'ICSharpCode.SharpZipLib, Version=0.84.0.0, Culture=neutral, PublicKeyToken=1b03e6acf1164f73'
at zapmetadata.HttpWebResponseDecompressed.GetResponseStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at zapmetadata.xtvdWebService.download(String startTime, String endTime)
at zapmetadata.MainClass.downloadListings(String login, String password)
at zapmetadata.MainClass.Main(String[] args)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Below is the ZapImport.log file:
Using Path C:\Program Files\devnz\gbpvr\

Begining zapdb.mdb update process...

Removing GBPVR Recording Entries...
Loading GBPVR Recording Entries...
Removing Program Data without a corresponding GPBR Recording...
Removing Schedule Data without a corresponding GPBR Recording...
Removing Genre Data without a corresponding GPBR Recording...
Removing Crew Data without a corresponding GPBR Recording...

Start downloading Zap EPG data...

[thunder]

I'm getting the exact same error as you. Did you figure out how to fix it yet??

Thanks,

[BobAtTorrey]

I don't know for sure what made the problem go away, but I did have two observations.

1. It appeared to me that the version of zapinterface.dll is different in the most recentt versions zaptools.zip and in xrecord.zip from the wiki. The version in xrecord is dated something like Oct-05, which pre-dates the SQLite change. So, if you install zaptools, and then install xrecord, zaptools ends up trying to use an old .dll. [I BELIEVE this to be true. I installed each a couple of times, and each time I installed XRecord the zapinterface.dll file seemed to revert to the older version. However, I didn't go back and make absolutely certain that what I seemed to observe was true.]
If this is the case, then I think you need to install the XRecord plugin before installing ZapTools.

2. The second thing I THINK I observed was that when I invoked Zaptools manually it failed, whereas I think it seemed to work when it (PostUpdateEPG.bat) was invoked directly from gbpvr. Again, once it started working, for reasons that aren't completely clear, I didn't go back to absolutely verify this observation.]

Good luck!

[UncleJohnsBand]

Upgrade to the latest version....the SQLite provder was changed with the latest release of GBPVR so I had to recompile to pick up the new version of the provder.....