Could not load VBA errors - ABD 593 - AECOsim | speedikon Forum - AECOsim | speedikon - Bentley Communities

Could not load VBA errors - ABD 593

We have one Vista laptop here which we get a bunch of "Could not load vba..." errors when we try to run Aecosim.  Any ideas what could be causing this?

John K.

17 Replies (Most Recent Reply)

  • Hi John,

    One possibility is that Windows UAC is not allowing the VBA to run, please try turning off UAC (unless you have already tried that).



  • In reply to Marc Thomas:

    Hi Marc,

    Yes this was one of the first things that I checked.  UAC is turned completely off.  It's the only Vista machine we have so I'm wondering if that has something to do with it.  Thanks for your input.

    John K.

  • In reply to jkknighton:

    hi John,

    The other thing is whether 'Run as Administrator' was used at installation?

    Is the first message:

    "Can not load VBA project file C\Program Files (x86)\Bentley\AECOsimBuildingDesigner V8i Ss4\AECOsimBuildingDesigner\vba\BMECH_CheckReferences.mvba."

    Reinstallation using  'Run as Administrator' fixed the last instance of that I came across.



  • In reply to Marc Thomas:

    Yes I do believe that is the first error message.  The user is an administrator on that machine but I will try what you suggest anyway.  I'll let you know if it works.

    John K.

  • In reply to jkknighton:

    Well I tried doing what you suggested Marc but I'm still getting the same errors.  Aside from this computer only having Vista, it also does not have MS Office installed.  That wouldn't cause VBA issues, would it?

  • In reply to jkknighton:

    Was UAC also disabled when ABD was first installed?  This is necessary so that certain registry keys can be generated.  

    In regards to Office... which version is installed?

  • In reply to Steve Cocchi:

    Yes the UAC was always disabled and there is no Office installed.

  • In reply to jkknighton:

    Has this machine ever run ABD?   The absence of Office could be a factor.

  • In reply to Steve Cocchi:

    We have experienced those errors as well, a bit strange as they did not come up right after installation. Must be something strange, probably connected to Windows Update.

    A reinstallation of AECOSim fixed the problem.

  • There was an ST in previous versions of building apps related to Microsoft Office (might also include MS Windows) security patches rendering MSVBA COM control inaccessible.  It produced similar errors to what you've encountered, as well as errors utlizing specific VBA tools in ABD and other building products.

    Not sure if it's related, but may be worth a try to implement. 

    "ST Description: user is unable to draw pipe/bar joist



    Our V8i SELECTseries2 BIM applications were not tested with Office 2010

    installed, so there may be an issue with how our VBA tools behave with this

    combination. We are hoping to have this resolved in the upcoming AECOsim

    Building Designer release, but in the interim it is recommended to use Office 2007

    instead which has been fully tested against our applications.


    Currently, Structural VBA macros throws VBA interface errors when ABD is

    installed with MS Office 2010.

    The workaround is to manually register MSCOMCTL.Ocx. 

    Win7 (32-bit):

    "regsvr32 C:\Windows\System32\MSCOMCTL.OCX"

    Win7 (64-bit):

    "regsvr32 C:\Windows\SysWOW64\MSCOMCTL.OCX"

    1. To register it right click that file and choose ‘open with’  ‘select

    program from list’  click ‘browse’ and browse to the following file

     C:\WINDOWS\system32\ and double click on the ‘regsvr32.exe’ file. You will

    get a message that it was successfully registered.

    Additionally there is Microsoft documentation and Fix it applet related.

  • In reply to Bobbles:

    Just a general question related to all that VBA stuff.

    It seems that Bentley has a tremendous problem supporting all those different Office versions. The only supported version it seems is Office 2007, while testing with Office 2010 is going on at the moment. The version we have on our latest PC's is 2013.

    As far as I know Microsoft wants to abandon VBA in its Office products and wants to move over to something more adapt. A step overdue, if you ask me.

    That said, I wonder what the strategy for Bentley is regarding that.

  • In reply to Andreas Zieritz:

    FWIW, ABD has always fully supported Office 2010 - that's the combination I've been running for the last 1-1/2 years.   Office 2013, however, is not yet tested nor certified.

    While it would be wonderful to remove the VBA related code from ABD, it is a huge task to cover all the tools that currently use it - Structural assembly and translators, HVAC and plumbing tools, hooks into drawing rules, etc.   I believe it's "on the list", but it will simply take time.   The new Bar Joist and Deck tools on the Structural side are two examples of where we are now using non-VBA code.

  • In reply to Steve Cocchi:

    Just curious - what are the alternatives?

    Generative Components is more or less C#, isn't it?

  • In reply to Andreas Zieritz:

    Yes, it would most likely be a programming language like C++ or C# or whatever it is they use.   That doesn't mean that functionality from other apps such as GC can't come into play in some cases, but probably not for the majority of the current VBA tools.

  • In reply to Steve Cocchi:

    It seems that this error has revisted us again.  We are now getting this error on a couple of our computers running Windows 7.  Has anyone come across anything new about this error?

    John K.

  • In reply to jkknighton:

    Were there any recent Windows or system level changes? Other new software installed? Any noticeable differences between machines experiencing these errors and those that are not?

    AFAIK, the things that "break" VBA for Bentley apps are the same things that can do so for other non-Bentley apps: Unregistered OCX files, missing or invalid registry keys, folder/file-level permissions, missing or incorrect versions of core VB system files, etc.. IOW, it's a system or environment issue at its core, but can be difficult to troubleshoot because VBA has many "roots" into that system.

  • In reply to jkknighton:

    Hi John,
    If Microsoft office is installed on the affected machines it is always worth running a repair install as a quick and easy first step, that will often sort out the Windows components responsible.



^ Go to first post