When I start the beta I get this VBA error:
Picking debug produces this:
Interestingly enough, I just followed up with another user who was getting the same error. Maybe that response will help here as well...
There are system level files that Architecture relies on for using VBA and for Office integration which MicroStation may not. I was able to dig up a few potential solutions, both from our internal database and from general Google-ing:
1) Try reinstalling the required MicroStation Prerequisite Pack. If this does not correct the issue, also try ininstalling and reinstalling the vertical application (BA) as well.
2) The Microsoft® Scripting Runtime nay need to be installed from the Microsoft® Windows Script components. The Microsoft® Windows Script components are installed by a self-extracting EXE. Please download and install the Microsoft® Windows Script Installer at the following Microsoft® Web site:
http://msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp
This link may also bring you directly to the download: http://www.microsoft.com/downloads/details.aspx?FamilyId=C717D943-7E4B-4622-86EB-95A22B832CAA&displaylang=en
3) Try re-registering Office applications such as Excel. To re-register Excel, in the Windows Run dialog box, type C:\Program Files\Microsoft Office\Office\Excel.exe /regserver and press OK. Note: The path specified may change based on your operating system and Office version.
4) Registry errors could be involved. You can try downloading a reputable Registry Cleaner to see if it picks up any errors.
In the end, this error typically indicates that some Windows level file(s) is either not installed correctly or is missing altogether.
HTH
Thanks Steve,
I've already tried step 1, I'll go through 2 to 4 and let you know how I get on.
Regards
Marc
None of the steps suggested in the thread below worked for us but the following cleared the problem: 1. Log into the affected workstation as administrator and add the affected user to the local Powerusers group 2. Log back in as the affected user and run Structural - the 429 error message doen't appear 3. Log back in as administrator and remove the affected user from the local Powerusers group The problem won't reoccur after this. I'm still unsure of what caused this to happen but suspect it was a security update or group policy change that required the active X component to be reloaded on the workstation. Our security policies restrict domain users from installing active X components hence the reason I carried out the steps above.
Regards,
Jeremy Littman