Receiving an error message in Microsoft Project "VBE6EXT.OLB could not be loaded"

Document ID : KB000044609
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem: 

When opening Microsoft Project to use the CA PPM MSP Interface, an error message is shown displaying "VBE6EXT.OLB could not be loaded".  This occurs when launching Microsoft Project on its own, or when launching the Visual Basic Editor in Project. 

vbe6extPNG.PNG

Pressing OK on the message prompt may be followed by another error "Error: Target: System.Object.ForwardCallToInvokeMember..." or similar error, and causes Microsoft Project to freeze or hang. 

 

The error itself propagates from Microsoft Project (associated with Microsoft Visual Basic for Applications) and isn't an inherent error from the CA PPM MSP Interface. It typically occurs when an Office product using a Visual Basic Application is corrupted.

 

Solution:

The CA PPM MSP Interface and related components should be removed in this case. This can be completed by navigating to Control Panel → Programs and Features and removing:

  • CA PPM Microsoft Project Interface
  • CA PPM Schedule Connect
  • CAClarityAddIn

These steps should be followed by a reboot to complete the removal of any residual files. Once done, launch Microsoft Project to verify the error message is no longer occurring, and navigate to View → Macros → Visual Basic and double-clicking ThisProject (Global.MPT). Clear out anything remaining in the window. 

If the "VBE6EXT.OLB could not be loaded" message continues to display either when launching Microsoft Project, or when navigating to View → Macros → Visual Basic, then the Office product installation either should be repaired through the Programs and Features list (right-click Microsoft Project → Change →  Repair) or reinstalled. 

Once the error message is resolved, the CA PPM MSP Interface can be reinstalled. 

Notes: 

Occasionally, the error may be due to a corrupt or missing installation of Microsoft Visual Studio 2010 Tools for Office Runtime (x64), so this should be checked as well.