VBA interface error: failed creating the comp manager - 0x80040583

Does that message appear every time you try to run any VBA macro? If so, there may be something going on with the installation. You could try reinstalling just the VBA part. Is there anything "unique" about this computer compared to your other ones? What OS is it running? How is it accessing MicroStation (and the VBA macro)? Locally? Over a network?

Hello Mr. Chouinard,

I have the same problem as stated in :

communities.bentley.com/.../44243.aspx.

We use the latest French release of MicroStation (8.11.07.446) and the problem occurs in every installation but one that uses the English release.

It is very easy to duplicate : just open any document and try to create a macro :

1) Go to Utilitaires | Macros | Gestionnaire (Utilities | Macro | Project Manager)

2) Click on the first icon to create a macro, give it a name.

3) As soon as you click on «Save», you get this message :

erreur d'interface VBA´: échec lors de la création du comp manager : 0x80040502

You suggest reinstalling VBA.  Do you have a link we could follow to solve the problem.

Is the development team able to duplicate this bug using the French release?

Thank you in advance!

Pierre Caron

Hello Mr. Chouinard,

I have the same problem as stated in :

communities.bentley.com/.../44243.aspx.

We use the latest French release of MicroStation (8.11.07.446) and the problem occurs in every installation but one that uses the English release.

It is very easy to duplicate : just open any document and try to create a macro :

1) Go to Utilitaires | Macros | Gestionnaire (Utilities | Macro | Project Manager)

2) Click on the first icon to create a macro, give it a name.

3) As soon as you click on «Save», you get this message :

erreur d'interface VBA´: échec lors de la création du comp manager : 0x80040502

You suggest reinstalling VBA.  Do you have a link we could follow to solve the problem.

Is the development team able to duplicate this bug using the French release?

Thank you in advance!

Pierre Caron

Finally, I solved the problem by adding a new variable :

MS_VBALCID with a value of 3084.

According to the Bentley technician I consulted, you could also try with a value of 1033 but it is 3084 that worked in my case.