X
Gunnar Peipman

Could not load file or assembly CabLib or one of its dependencies

When using WSPBuilder from command line you may get the following error: “Could not load file or assembly ‘CabLib, Version=10.2.0.0, Culture=neutral, PublicKeyToken=5c838b77b53f84a0’ or one of its dependencies. An attempt was made toload a program with an incorrect format.” This error occurs if there is something wrong with CabLib.dll or if CabLib.dll doesn’t exist in same folder with WSPBuilder.

Steps to fix:

  1. Make sure CabLib.dll is in same folder with WSPBuilder.exe
  2. Make sure you have correct version of CabLib.dll (32bit or 64bit)

On 64bit virtual server I replaced the old CabLib.dll with 64bit version and I got this error solved.

Liked this post? Empower your friends by sharing it!
Categories: SharePoint
Leave a Comment
Related Post
  1. SharePoint 2013 Autohosted apps

    MSDN subscribers can activate Office 365 developers benefit that gives them free Office 365 development…

  2. Automatically describing and tagging pictures on SharePoint using Azure Cognitive Services

    Azure Cognitive Services has wider audience than cool young guys developing very cool mobile apps.…

  3. Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive

    When IIS is not configured properly after creating SharePoint application and there are web parts…

  4. SharePoint: Changing comments of document versions in code

    During one SharePoint migration project I had problem with document versions comments. I needed some…

  5. The program w3wp.exe, with the assigned process ID, could not authenticate locally by using the target name HTTP/WEBSITENAME.

    You may face this error when you are running your development environment on virtual server…