Importer Pro Error - #201 Map Data to Files - System.IO.FileNotFoundException: Could not load file or assembly 'log4net, Version=1.2.11.0'
A customer is using Importer to add items into FileBound.
It is noticed that the items are not uploading as expected, and the Importer error log shows this type of error:
4/24/2014 12:47:58 PM - Error 16: Error reported in 'Upload to FileBound':
Error saving file: System.Exception: System.IO.FileNotFoundException: Could not load file or assembly 'log4net, Version=1.2.11.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a' or one of its dependencies. The system cannot find the file specified. File name: 'log4net, Version=1.2.11.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a' at FileBound.FBException..ctor(ErrorCodes ErrorNumber, Exception ex) at FileBound.Business.BaseBusiness.SaveObjectItem(Object Sender)
This type of error is normally caused as a result of having either a missing log4net.dll or Aspose.dll or both.
Resolution:
1) Below is a list of ALL dlls that need to be listed in the Importer Professional folder. Navigate to this folder location and make note of any dlls that you are missing;
C:\Program Files (x86)\FileBound\Importer Professional
Here is the list of all dlls that need to be listed in the Importer Professional folder:
Aspose.BarCode.DLL
Aspose.Cells.DLL
Aspose.Email.DLL
Aspose.Pdf.DLL
Aspose.Words.DLL
Log4Net.dll
2) The log4net error usually means that Importer Professional is missing the log4net.dll
If FileBound is on premise, any missing dll can be located in the C:\inetpub\FileBound BIN folder. If FileBound is Cloud hosted, the missing dll can be found in the local viewer dlls. Here are example folder locations to each of those locations if a reference is needed;
On Premise - C:\inetpub\FileBound\FB7360\bin
Cloud - C:\Users\abaltz\AppData\Local\FileBound\DLLs\7.3.6.1
3) Copy the needed files from the Bin and paste them into the Importer Folder;
C:\Program Files (x86)\FileBound\Importer Professional
You should now be able to launch / relaunch Importer and run the configuration without error