Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

errors occurred when running setup of VB6 program

Status
Not open for further replies.

tyedyejenn

Programmer
Jun 14, 2000
35
US
I wrote a program in VB6 and used the package and deployment wizard to create a cab file. The following errors occur when I run setup.

C:\Windows\system\MSVCRT20.DLL
an access violation occurred while copying the file

-----

An error occurred while registering the file
C:\Windows\system\simpdata.tlb

----

An error occurred while registering the file
C:\Windows\sysytem\msado21.tlb

Each error gives me three options--Abort Retry Ignore

I have tried Retry and that doen't work so I tried Ignore

then I get a message box that says Setup completed successfully

At this point my program runs without any issues, I am concerned that someday these errors will be an issue. Any suggestions on how to handle this would be greatly appreciated. Thanks in advance

Jenn
 
Hello there,

Here's a bit of a guess, but it sounds like you might be trying to write over files which are already registered and are in use, particularly considering the files you've listed are type libraries and dynamic link libraries.

You could *try* running regsvr32 on these files to unregister them and see how that affects things.

The reason, possibly, that your applcation runs without fault despite these errrors, is that these files are already registered on your system and you're not trying to replace them with more up to date versions.

You probably need some sort of script to run before you go for the installation, which will remove any dll's and tlb's from memory and unregister them prior to your install package trying to reinstall them.

I think the standard VB Installer has a warning on it that system files that are in use won't be replaced...this is what it means.

I may be wrong, but I hope this helps...


Cheerio,

Paul
 
From the looks of it, your application uses ADO. Open your script again from the P&D Wizard and add MDAC_TYP.EXE to the install. Then run the install again. This is the Microsoft Data Access Components that allows for ODBC configuration. I believe the package may have an updated version of the MSVCRT20.DLL in it, but don't quote me on it.

The reason the other two files are not registering is that the dependency files are probably not in place. Installing MDAC will put all the files in place for them to register properly. Be aware that adding MDAC to your install will increase its size by about 6 to 7 Meg.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top