\windows\system32\msadox.dll failed to register 1

[jozino01]

hi,
i have two problems with installing and running vb6 program on vista.

1)
the program runs well on xp, but during installation on vista i got this error:

*** ERROR: An error occurred while registering the file
'C:\Windows\System32\msadox.dll'

*** ERROR: (User Responded with 'Ignore')

2)
when I tried to run program after installation, i got message "Application already running" but nothing come to the scren.


here is contant of my setup.lst:
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,6/1/99 12:00:00 AM,101888,6.0.84.50
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,6/3/99 12:00:00 AM,17920,2.40.4275.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,3/8/99 12:00:00 AM,147728,2.40.4275.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 12:00:00 AM,164112,5.0.4275.1
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00 12:00:00 AM,598288,2.40.4275.1
File7=@msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),,11/13/05 10:40:10 PM,1386496,6.0.97.82

[IconGroups]
Group0=Liba
PrivateGroup0=-1
Parent0=$(Programs)

[Liba]
Icon1="liba.exe"
Title1=Liba
StartIn1=$(AppPath)

[Setup]
Title=Liba
DefaultDir=$(ProgramFiles)\Liba
AppExe=liba.exe
AppToUninstall=liba.exe

[Setup1 Files]
File1=@LIBC.mdb,$(AppPath),,,8/23/07 8:25:53 AM,229376,0.0.0.0
File2=@lib.ini,$(AppPath),,,8/9/07 9:13:03 AM,51,0.0.0.0
File3=@MDAC_TYP.EXE,$(AppPath),,,1/20/00 12:00:00 AM,7856352,25.0.4403.12
File4=@mscomctl.ocx,$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04 1:00:00 AM,1081616,6.1.97.82
File5=@MSStdFmt.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),2/23/04 1:00:00 AM,119808,6.1.97.82
File6=@MSDATGRD.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04 12:00:00 AM,275216,6.1.97.82
File7=@TABCTL32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04 12:00:00 AM,224016,6.1.97.82
File8=@EXCEL9.OLB,$(WinSysPath),,$(Shared),3/19/99 6:00:32 AM,638976,9.0.0.2719
File9=@msadox.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),12/26/06 6:07:23 AM,200704,2.81.1128.0
File10=@liba.exe,$(AppPath),,,8/23/07 11:18:14 AM,143360,1.0.0.0

 

[jozino01]

i found these articles:

Windows Data Access Components (Windows DAC) 6.0 is included in Windows Vista. It is not distributed separately and cannot be redistributed. Similarly, Microsoft Data Access Components (MDAC) 2.8 was included with Windows XP and Windows Server 2003. However, there is also a redistributable version of MDAC, MDAC 2.8 Service Pack (SP) 1. This topic provides information about redistributing MDAC 2.8 SP1. Note that this redistributable version should only be installed on Windows 2000. It should not be installed on any later versions of the data access components.

http://msdn2.microsoft.com/en-us/library/ms693148.aspx

Windows Data Access Components SDK Overview

Windows Data Access Components (Windows DAC) 6.0 is a set of technologies included in Microsoft Windows Vista to provide access to information across the enterprise. These technologies include Microsoft ActiveX Data Objects (ADO), OLE DB, and Microsoft Open Database Connectivity (ODBC). Data-driven client/server applications deployed over the Web or a LAN can use these components to easily integrate information from a variety of sources, both relational (SQL) and non-relational.

http://msdn2.microsoft.com/en-us/library/ms692897.aspx

Overview
Microsoft Data Access Components (MDAC) 2.8 contains core Data Access components such as the Microsoft SQL Server™ OLE DB provider and ODBC driver. This redistributable installer for the MDAC 2.8 release installs the same Data Access components as Microsoft Windows Server 2003.
This release does not include Microsoft Jet, the Microsoft Jet OLE DB Provider or ODBC driver, the Desktop Database ODBC Drivers, or the Visual FoxPro ODBC Driver.
System Requirements
* Supported Operating Systems: Windows 2000; Windows 98; Windows ME; Windows NT; Windows XP

http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&displaylang=en

so:
- mdac has been replaced by dac on vista
- mdad 2.8 is not supported on vista

???

 

[BobRodes]

<easily

They do so love that word....

 

[JoeAtWork]

If you just leave the DLL completely out of your install package chances are your application will run fine. Database components these days tend to be treated as part of the operating system and therefore you probably don't need to distribute it with your app.

 

[BobRodes]

One distribution strategy for MDAC is to simply check for it in your program on startup, and if it's not there, message the user that they have to install MDAC 2.whatever or greater.

 

[jozino01]

thanks everybody.
so should i edit setup.lst and remove msadox.dll entry or rather completely omit mdac in p&d process?

 

[BobRodes]

Well, that's one distribution strategy.

 

[jozino01]

> One distribution strategy for MDAC is to simply check for it in your program on startup
- starting with windows xp, mdac is a part of system. unless program runs on old version of windows (9x), there always should be mdac available.(?)

> that's one distribution strategy.
- what are other options?

 

[BobRodes]

<what are other options

Include the latest version of MDAC in the package, and hope that you don't run into any version problems in the target machines.

 

[jozino01]

> Include the latest version of MDAC in the package, and hope that you don't run into any version problems in the target machines.

I work on xp (mdac 2.8) and my program will be running on both xp (mdac 2.8) and vista (wdac/mdac 6)...?

 

[dilettante]

Don't attempt distribution of MDAC components at all then. For recent OSs these should normally be updated via OS Service Packs or the Windows Update mechanism used for all system components.


Where possible, develop against MDAC 2.5 functionality. By referencing the ADO Library 2.5 Type Library your program will be portable to any machine with 2.5 or later, and will use the most recent set of actual components installed on a target system.

The ADO 2.0 Type Library can be used in the same way (with even further reduced functionality) to achieve compatability with target systems having MDAC 2.0 or newer installed.

How To Develop with ADO Version 2.5 or Later and Install on ADO Version 2.0

 

[BobRodes]

That sounds best to me as well. The main difficulty that I've found with MDAC is that there are some backward compatibility problems. So, if you try to install the latest version on an older machine that has some application that's using an earlier version you can run into little problems here and there with that application.

 

[jozino01]

thanks everybody, specially dilettante; your suggestion works and solves my xp vs. vista dilemma.

 

[dilettante]

You want a really scary deployment scenario? Look at this pickle Microsoft has put us in just recently:

MS07-043: Description of security update for the Visual Basic 6.0 redistributable.

No Installer merge module available, and I'm not too fond of our options using the P&D Wizard either.