<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VBA Interface error: Unable to load the project - 0x80004002</title><link>https://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/109059/vba-interface-error-unable-to-load-the-project---0x80004002</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: VBA Interface error: Unable to load the project - 0x80004002</title><link>https://communities.bentley.com/thread/331707?ContentTypeID=1</link><pubDate>Wed, 22 Jul 2015 13:10:59 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:1b3afb23-7bf7-451f-bb12-d487d22c20e6</guid><dc:creator>Robert Hook</dc:creator><description>&lt;p&gt;A good data point to know for troubleshooting this type of issue is:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;- Is the problem&amp;nbsp;affecting: all users, all locations, and&amp;nbsp;all macros?&amp;nbsp; Or some users, some locations, some macros, some of the times?&lt;/p&gt;
&lt;p&gt;1. Along the lines of Jon&amp;#39;s recommendation if you use MS_VBA_OPEN_IN_MEMORY you may want to see if the value was modified.&amp;nbsp; Most larger organizations will set it to &amp;quot;ALL&amp;quot; to allow 20+ users to open the same macro over a network share and avoid file server quota restrictions.&amp;nbsp; This has helped at times with VBA Interface errors: 0x80004002, 0x80004003.&lt;/p&gt;
&lt;p&gt;2. Check to see if re-registering the Microsoft VBA engine can help correct the issue.&amp;nbsp; Simply start MicroStation using Run as Administrator within the current user account.&amp;nbsp; This action will permit MicroStation to re-register the Microsoft VBA engine and correct any necessary/required registry keys that a restricted user normally would not have permission to set/correct and be somewhat difficult for most to detect the underlying issue(s).&lt;/p&gt;
&lt;p&gt;3. If there is no evidence your configuration was modified I always recommend the following Microsoft Administrative steps be performed as the first step for VBA project Load or Run issues - testing on one client then deploying similar actions once proven to correct the issue:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Run Microsoft Update to ensure the client is current with all Microsoft Windows updates&lt;/li&gt;
&lt;li&gt;Similarly, ensure the client is current with all Microsoft Office updates&lt;/li&gt;
&lt;li&gt;Lastly, apply the appropriate Microsoft Office Hot fix for your version of Microsoft Office&lt;/li&gt;
&lt;/ol&gt;
&lt;p style="margin-left:60px;"&gt;MS12-060: Description of the security update for Office 2010, 2007, and 2003 respectively (August 14, 2012)&lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/2597986"&gt;https://support.microsoft.com/kb/2597986&lt;br /&gt;&lt;/a&gt;&lt;a href="http://support.microsoft.com/kb/2687441"&gt;https://support.microsoft.com/kb/2687441&lt;br /&gt;&lt;/a&gt; &lt;a href="https://support.microsoft.com/kb/2687323"&gt;https://support.microsoft.com/kb/2687323&lt;/a&gt;&lt;/p&gt;
&lt;p style="padding:0;margin:0;"&gt;4. Lastly though not likely and would only affect a few fringe cases, determine if the Microsoft KB3057839 security patch is installed.&amp;nbsp; This has been known to affect some GUI applications when started as or through a Microsoft service&amp;nbsp;and the application would appear to almost immediately not start or hang in Windows Task Manager.&lt;/p&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;strong&gt;UPDATED NOTE&amp;nbsp;with respect to option #4&lt;/strong&gt;&lt;/p&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;em&gt;&lt;span style="background-color:#ffff00;"&gt;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;div style="direction:ltr;"&gt;
&lt;div style="direction:ltr;"&gt;
&lt;table style="border:1pt solid #a3a3a3;border-collapse:collapse;direction:ltr;" border="1" cellspacing="0" cellpadding="0"&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style="padding:4pt;border:1pt solid #a3a3a3;width:9.138in;vertical-align:top;"&gt;
&lt;p style="margin:0in;font-family:Calibri;font-size:11pt;"&gt;A few users having reported MicroStation hanging on startup when running a MicroStation VBA autoload project started through the Windows Task Scheduler (non-interactively) affected by Microsoft security patch KB3057839 have reported after installing Microsoft updates containing &lt;a href="https://support.microsoft.com/en-us/kb/3070102"&gt;Microsoft security patch 3070102&lt;/a&gt; resolved the issue.&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;em&gt;&lt;span style="background-color:#ffff00;"&gt;&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;HTH,&lt;br /&gt;Bob&lt;/p&gt;
&lt;p style="padding:0;margin:0;"&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VBA Interface error: Unable to load the project - 0x80004002</title><link>https://communities.bentley.com/thread/331689?ContentTypeID=1</link><pubDate>Wed, 22 Jul 2015 11:14:47 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4407c54f-7ad7-43d3-aca2-0c8be981479f</guid><dc:creator>Jon Summers</dc:creator><description>&lt;p&gt;[quote user=&amp;quot;Zoe Mair&amp;quot;]This has just recently become an issue, the software was working fine across the business up until the past week or so[/quote]&lt;/p&gt;
&lt;p&gt;Probably someone reconfigured something, somewhere, that affects MicroStation.&amp;nbsp; Perhaps IT has changed the network; perhaps a CAD administrator has modified one of your group&amp;#39;s MicroStation configuration files.&amp;nbsp; It&amp;#39;s hard to say.&lt;/p&gt;
&lt;p&gt;My guess is that either&amp;nbsp;MicroStation configuration variable &lt;span style="font-family:courier new,courier;"&gt;MS_VBASEARCHDIRECTORIES&lt;/span&gt; has been redefined to an incorrect value, or it may be pointing to an invalid location if the network was reconfigured.&amp;nbsp; Either way, you (or your CAD administrator) should analyse MicroStation&amp;#39;s configuration to find what has changed.&lt;/p&gt;
&lt;p&gt;Use the &lt;span style="font-family:courier new,courier;"&gt;-msdebug&lt;/span&gt; &lt;a target="_blank" title="LA Solutions: MicroStation command-line switches" href="http://www.la-solutions.co.uk/content/CommandLineSwitches.htm"&gt;command-line switch&lt;/a&gt; to obtain a text list of configuration variables that you can pore over.&amp;nbsp; Here&amp;#39;s an article that explains &lt;a target="_blank" title="LA Solutions: Debugging MicroStation Configuration Variables" href="http://www.la-solutions.co.uk/content/CfgVarDebug.htm"&gt;how to get an msdebug.txt dump&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You can use this freeware app. &lt;a target="_blank" title="LA Solutions: Configuration Verifier" href="http://www.la-solutions.co.uk/content/CfgVarDebug.htm#ValidateCfgVar"&gt;Configuration Verifier&lt;/a&gt; to test an individual configuration variable such as &lt;span style="font-family:courier new,courier;"&gt;MS_VBASEARCHDIRECTORIES&lt;/span&gt;.&amp;nbsp; However, since it is itself a VBA project, it can&amp;#39;t help you in this situation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>