all my MVBA does not start anymore : error code: 0x800a02c9

What changed?  OS? MicroStation install?  Security policies?  Are you able to run the mvba on another computer?  Did you do some simple searching with Google?  I found many hits on issues like this usually traced to some component that is not registered.

HTH,

Thank you Mark,

IMHO I changed nothing since a Ie8 install last week. After the IE8 install I changed the internet secutirty settings an d added some local intranet server adresses to the local sites!

Yes, I read that component things found by google, and after that I did a MS office repair install.

Yes, my vba's are running on other companies computers.

Are your projects using any controls that are not part of MicroStation?  Here is some information that we have been gathering related to this type of stuff:

1.       Open your VBA project and verify the references.  The ones in particular would be 3rd party controls like mscomctrl is suggested.  One posting below stated that detach and re-attach resolved the issue.  There are other things to try in that link, but I would start there.

ERROR:                 "Object library invalid or contains references to object definitions that could not be found" or "Element not found"

ARTICLE:              "Object library invalid or contains references to object definitions that could not be found" or "Element not found"

blogs.msdn.com/.../object-library-invalid-or-contains-references-to-object-definitions-that-could-not-be-found-or-element-not-found.aspx

2.       At the beginning of the article there is mention to Microsoft article 960715 (Update Rollup for Active X Kill Bits) causing the problem.  This is the more common reason for VBA projects to not load after updating Microsoft security patches or Office products.  I recommend using Microsoft Procmon to capture the full load of an application that has a failing VBA project.  Then filter for the ActiveX kill bit paths and review those that have errors loading (the kill bit is a data value of 1024) and selectively decide to backup and remove those component kill bit keys from the registry.  Once you know which ones are the problem you can create a registry file to remove those keys everytime a new Microsoft update attempts to re-activate “known bad controls” through a security update (Microsoft or your IT policies delploy), or Office Upgrade/patches roll out

I think this might be related to the Internet Explorer update.

HTH,

Thanks Mark,

As mentioned in that blog.msdn.com/....

I opened any MVBA that still was loading and go to the references and did a manually browse and attach  to mscomctl.ocx and FM20.dll. After that I could open and load my MVBAs that are using this controls again.

Strange for me, but working....

A clean uninstall and reinstall of MS Office resolved my problem

A clean uninstall and reinstall of MS Office resolved my problem