Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

VBA 6.2 install error Win XP Pro

Posted on 2013-01-09
8
Medium Priority
?
747 Views
Last Modified: 2013-01-24
I have some old software I am trying to install on a Windows XP Pro machine.  I am receiving the following error message, "An error occurred while installing the Microsoft (tm) VBA 6.2 Object."

** I have installed this software dozens of times over the years...first on Win95 machines, then on Win98 and finally on WinXP Pro.


** The software is stored in a network share on the main server and I have always just installed it directly from the share by running the Setup.exe program.

** The machine is a member of the domain and I am logged on as the Domain Admin

I have Googled this error message verbatim and have not found any helpful info.

Can someone point me in the right direction to solving this issue?
0
Comment
Question by:Kerry Wilson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 30

Accepted Solution

by:
flubbster earned 2000 total points
ID: 38760445
Perhaps the core run-time files for VB6.0 are corrupted or missing. What version VBA are you using?
0
 

Author Comment

by:Kerry Wilson
ID: 38760502
I have no idea.  How can I tell?  This is old software and the company that produced it is out of business.  It is our main accounting software.
0
 
LVL 30

Expert Comment

by:flubbster
ID: 38760576
Try re-installing the run-time files, then installing SP6 to update it:

Run-time installer:
http://download.microsoft.com/download/vb60pro/install/6/Win98Me/EN-US/VBRun60.exe

SP6:
http://www.microsoft.com/en-us/download/details.aspx?id=24417
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 

Author Comment

by:Kerry Wilson
ID: 38760652
It's unclear to me if I need to do this on the client machine where I am trying to install the software or on the main server where the network share resides.  I think the client but please clarify.
0
 
LVL 30

Expert Comment

by:flubbster
ID: 38760695
It would be the client, where the software is being installed.
0
 

Author Comment

by:Kerry Wilson
ID: 38760860
Well, I was holding out high hopes for your recommendation.  I have not yet tried it.  I still plan to do that.

But, I had another WinXP Pro client I was working on and it gives me exactly the same error.  And it is a fresh, out of the box, Win7 Pro with XP Mode and all Win7 and XP updates installed.  So, I don't think it's a corruption problem with the client since this one's a fresh install.

The full network path to to installer is [ServerName]\[ShareName]\Macola70\Install\Setup.exe

There is a folder inside the Intall folder named VBA.  Inside the VBA folder are folders named Cc, MSI, pFiles, Sp, system and Windows.  Inside the MSI folder is a file named InstMsiw.exe.  I don't know if any of this information is useful to you or not.

About two years ago, we replaced our W2K server with a brand new VMware server.  We ported everything over from the W2K server and are still running it as a W2K virtual server.  I **think** but I am not certain these clients are the first ones where I've tried to install the program since the new server was installed.  So, I am now thinking perhaps we did not get a good copy ported over and we have some missing and/or corrupted files.  Does that make sense?  Any other ideas?
0
 
LVL 30

Expert Comment

by:flubbster
ID: 38761295
Actually it makes perfect sense. A coruupt install or missing files would make sense. One thing you could try is to copy the install folders/files to a memory stick, place it on the desktop of a client, and install it from there.

Or... take a look at a system that has it installed. If the install does not make any registry entries, then the entire program folder for it can simply be copied over to another system. It should just work if that is the case.
0
 

Author Closing Comment

by:Kerry Wilson
ID: 38816097
I found the problem.  Yes, several of the files in the installation folder were missing.  

I found an old backup and compared the contents of the folder on the backup to the folder in the production environment.  Again these are installation files so they should not have changed.  I copied the missing files from the backup to the production machine and voila! the installation is working again.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
Video by: Tony
This video teaches viewers how to export a project from Adobe Premiere Pro and the various file types involved.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question