MVBA Troubleshooting

MicroStation VBA Verification Checklist (Steps that can help resolve most VBA: Crashes, Project Load, or Run issues)

1. Perform Microsoft Full Updates and Patching
   
   
   • Update Microsoft Windows (Version History) 
   • Update Microsoft Security and/or 3rd Party solutions
   • Update Microsoft Office Updates/Patching 
     
     NOTE: Verify (pendmoves) and Perform any Computer Reboots if prompted/required.
     
     
2. Start Software First Time and/or Install Software using "Run as Administrator"
   
   NOTE: This helps to ensure proper local admin rights/privileges and resources are allowed to finalize post install software needs (e.g. component registrations in registry, etc.) or software installer permission issues (network group policies constraints/conflicts) that can arise and do not provide sufficient user notification of an exact problem.  After First Start and/or Install as admin, in most cases Bentley software can then safely (unless noted otherwise in product documentation) be run in a Microsoft LUA (limited/restricted) user.
   
   
3. Verify Microsoft VBA Project References (Missing or needing to be Registered)
   
   
   1. Open Microsoft VBA Editor. Highlight your Project. Select: Tools > References
   2. Look for any References tagged with "MISSING". Remove Reference and update using Correct Path.
      
      
      
      
   3. Lastly you may need to Unregister and/or Register controls. See: Microsoft Troubleshooting with Regsrv32
      
      
4. VBA Related Crashes/Exceptions
   
   
   1. Review and Verify steps listed in: MicroStation VBA crashes on startup after Microsoft Office Updates
   2. Remove all Application and ActiveX control object caches (*.box, *.exd)
      • Application Caches (*.box) files located: %APPDATA%\Microsoft\Forms
      • ActiveX Control Caches (*.exd) files located: %LOCALAPPDATA%\Temp\VBE
        
        
5. If Problems Persists
   
   
   1. Review MicroStation VBA Help Topics
      • "Changes for 64-bit Processes" (See also: Microsoft ActiveX Control Recommendations)
   2. Review MicroStation VBA Logging
      • Set MS_VBALOGGING=1 at the Operating System variable.
      • Start MicroStation and reproduce the error.
      • Locate and Review the log file generated: C:\vba.log
   3. Review Microsoft Office VBA Permissions (When running MicroStation VBA code within Microsoft Office products)
   4. Collect and Process Microsoft Data
      • Microsoft Process Monitor (procmon) and/or
      • Microsoft Full Memory Dump (primer)
   5. Perform a Clean Install.
      • Though an extreme measure and does not permit a "root cause" to be discovered using techniques above, sometimes a clean install is the most prompt way to bring a user back into production.  Doing so ensures a completely up-to-date and clean software environment from which the software is run in.  If time is of the essence this option may make the most sense.  However performing the steps above can often lead to identifying a root cause and permit software vendors to correct any quality issues or fixes required and help all users by producing documentation for how to quickly resolve the issue (if not under one specific vendor's control) for more users in the future.