VBA Interface error: Unable to load the project - 0x80004002

I am unable to carry out numerous tasks in Microstation V8i Select Series 3 and I am receiving the following errors in the Message Centre:

VBA Interface error: Unable to load the project - 0x80004002

VBA Interface error: Unable to run macro

When I try to access the Visual Basic Editor, an error also appears saying that there are no loaded projects. This has just recently become an issue, the software was working fine across the business up until the past week or so.

Is this a known issue? Any support would be greatly appreciated.

Kind Regards

Zoe Mair

Trainee Engineering Systems Technician

Amec Foster Wheeler

Oil and Gas

Northern Europe and CIS

City Gate, Altens Farm Road, Nigg

Aberdeen AB12 3LB United Kingdom

(01224 838479

+zoe.mair@amecfw.com

þ amecfw.com

Parents
  • Unknown said:
    This has just recently become an issue, the software was working fine across the business up until the past week or so

    Probably someone reconfigured something, somewhere, that affects MicroStation.  Perhaps IT has changed the network; perhaps a CAD administrator has modified one of your group's MicroStation configuration files.  It's hard to say.

    My guess is that either MicroStation configuration variable MS_VBASEARCHDIRECTORIES has been redefined to an incorrect value, or it may be pointing to an invalid location if the network was reconfigured.  Either way, you (or your CAD administrator) should analyse MicroStation's configuration to find what has changed.

    Use the -msdebug command-line switch to obtain a text list of configuration variables that you can pore over.  Here's an article that explains how to get an msdebug.txt dump.

    You can use this freeware app. Configuration Verifier to test an individual configuration variable such as MS_VBASEARCHDIRECTORIES.  However, since it is itself a VBA project, it can't help you in this situation.

     
    Regards, Jon Summers
    LA Solutions

Reply
  • Unknown said:
    This has just recently become an issue, the software was working fine across the business up until the past week or so

    Probably someone reconfigured something, somewhere, that affects MicroStation.  Perhaps IT has changed the network; perhaps a CAD administrator has modified one of your group's MicroStation configuration files.  It's hard to say.

    My guess is that either MicroStation configuration variable MS_VBASEARCHDIRECTORIES has been redefined to an incorrect value, or it may be pointing to an invalid location if the network was reconfigured.  Either way, you (or your CAD administrator) should analyse MicroStation's configuration to find what has changed.

    Use the -msdebug command-line switch to obtain a text list of configuration variables that you can pore over.  Here's an article that explains how to get an msdebug.txt dump.

    You can use this freeware app. Configuration Verifier to test an individual configuration variable such as MS_VBASEARCHDIRECTORIES.  However, since it is itself a VBA project, it can't help you in this situation.

     
    Regards, Jon Summers
    LA Solutions

Children
No Data