Onfolio
About Us  |  Contact Us   
Home Products Free Download Purchase Support Press Search

OKB-112: Resolving problems with capture

If capture only fails for images and files (e.g. PDFs) and your Onfolio.log (see below for note on finding your Onfolio.log file) contains 'Error capturing: Error calling URLDownloadToFile':

This problem is likely being caused by an incompatibility between Onfolio and a download manager that you have installed (eg. GetRight, Adobe Download Manager, etc.). What's happening is this: Onfolio uses a system command called URLDownloadToFile to download all the images, pdfs and such during capture. If your download manager has registered itself to do all the downloading, then when URLDownloadToFile tries to download these files, your download manager tries to step in and take over. That's why capture is broken.

Unfortunately, while we are researching a fix for this problem to be included in a future version of Onfolio, at the current time the only way to get Onfolio working again is to uninstall the download manager.

If capture fails always and your Onfolio.log contains 'Error capturing: QueryInterface for interface mshtml.IHTMLElement failed.':

Re-registering the mshtml DLL should fix this problem:

  1. Open a command prompt by going to Start > Run, typing in "cmd" and pressing OK.
  2. At the command prompt, type "regsvr32 mshtml.dll".

If capture fails always and your Onfolio.log contains 'System.NullReferenceException: Object reference not set to an instance of an object. At Project31.MindShare.View.CollectionComboBox.FindCollectionId.'

The most likely cause of this problem is that the user is running a beta version of the .NET Framework version 1.2 (codenamed 'Whidbey'). Onfolio has not been verified as a compatible with the 1.2 version of the .NET Framework.

The whidbey_config file, available on the Tools page, contains a set of configuration files that can be used to ensure that Onfolio uses the correct version of the .NET Framework. Instructions for using the file are contained within the readme.txt file.

Note: To find out how to locate your Onfolio.log file, please refer to KB article OKB-115.