• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 758
  • Last Modified:

VBA 6.2 install error Win XP Pro

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
Kerry Wilson
Asked:
Kerry Wilson
  • 4
  • 4
1 Solution
 
flubbsterCommented:
Perhaps the core run-time files for VB6.0 are corrupted or missing. What version VBA are you using?
0
 
Kerry WilsonAuthor Commented:
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
 
flubbsterCommented:
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
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Kerry WilsonAuthor Commented:
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
 
flubbsterCommented:
It would be the client, where the software is being installed.
0
 
Kerry WilsonAuthor Commented:
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
 
flubbsterCommented:
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
 
Kerry WilsonAuthor Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now