Error - COMException (0x86DB0898) when opening map file

 This article is suitable for an IT Adminstrator

Ref: 201111111720 
Last Edited: February 12th, 2016
When a map is opened in Visio, an error is reported in the User Actions Required window.
11/11/2011 15:57:06
An exception occurred.
An error occurred in the VisEventProc event
=== Begin For Triaster Support ===
The following content may be useful to the Triaster support team.
Please copy and paste it into an e-mail to
and attach any referenced files if you would like help understanding
how to avoid this issue reoccurring.
An exception occurred.
An error occurred in the VisEventProc event
System.Runtime.InteropServices.COMException (0x86DB0898):
An exception occurred.
   at Microsoft.Office.Interop.Visio.IVDocument.get_VBProject()
   at Triaster.ProcessNavigator.Common.ProcessObjects.mdlMain.VBAVersion(Document docObj)
   at Triaster.ProcessNavigator.Common.ProcessObjects.mdlMain.UpgradeVBA(Document docObj)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Map..ctor(Document& docObj, Boolean blnEnableUpgrade)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Maps.Add(Document docArg, Boolean blnEnableUpgrades, String strFullPathAndFileName)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Maps.Add(Document docArg, Boolean blnEnableUpgrades)
   at Triaster.ProcessNavigator.Common.ProcessObjects.DocumentsBase.Add(Document docArg)
   at Triaster.ProcessNavigator.MappingEdition.Wrapper.clsAppEventSink.HookDocument(Document docObj)
   at Triaster.ProcessNavigator.MappingEdition.Wrapper.clsAppEventSink.VisEventProc(Int32& eventCode, Object& sourceObj, Int32& eventID, Int32& seqNum, Object& subjectObj, Object& moreInfo)
=== Finish For Triaster Support ===
Cause 1:
There is a corruption in the VBA project that's embedded within the file.
Please contact Triaster Support (, who may ask that the file be forwarded for repair.
We recommend that users of Visio 2007 apply Service Pack 3 (SP3), where one of the documented improvements is fixing an issue which may lead to this problem.

Cause 2:
Visual Basic for Applications (VBA) isn't installed.

Visual Basic for Applications is usually installed with Microsoft Office products, including Visio, as a component of 'Office Shared Features'. However, it may not be. It can be added to an existing installation.

1. Open 'Control Panel'.
2. Click 'Programs and Features'.
3. Right-click 'Microsoft Visio <Version>' > 'Change'.
4. Choose 'Add or Remove Features', and click 'Continue'.
5. Expand 'Office Shared Features'.
6. Click on the drop-down arrow next to 'Visual Basic for Applications', and choose 'Run from My Computer'.

Install Visual Basic for Applications

7. Continue the installation.

A simple test is to:
1. Open a Visio drawing.
(A simple blank drawing could be created for this.)
2. Press ALT+F11.

That should open the 'Microsoft Visual Basic for Applications' window. If not, it would suggest that VBA (at least the required version) isn't installed.

Applies to:
  • Process Navigator
  • Visio 

Need further help? Contact the Triaster Support team by e-mailing or by calling us on  +44 (0)870 402 1234.
Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail