MDAC 2.6 merge still has problems

[James P. Hoffman]

I downloaded the new mdac 2.6 merge module from the web page, copied it on
top of the old version and changed my project to include MDAC 2.6 and
DCOM95. On a WinME machine, installing an upgrade of my software seems to
run successfully. However, the installed version of my software does not run
correctly unless MDAC_typ is run manually. I verified that my project
included DCOM95 and MDAC 2.6. The properties windows for both files
indicate a date of 2/16. Do I have the wrong files, or did they just not
update the display? Suspiciously, the DCOM95 field has precisely the same
number of bytes as did my prior version.

[reply@installshield.com Chandima Rajakaruna]

I downloaded the Modules from the website itself and ran a few tests to
verify it was the correct version. It is (despite the file dates).

Is this scenario correct?

You install version 1 of your app
Now you install version 2 of your app which also includes MDAC26 and DCOM
(through an Upgrade Path)
When you run your App, it doesn't work
If you manually install MDAC_TYP.exe 2.6, it works.

After running the Upgrade, look in the C:\Program Files\Common
Files\System\msadc folder and see if the files have versions of 2.6. If not,
that means MDAC 26 failed to install. If so, give me more details and I will
look into it.

"James P. Hoffman" <jpho...@velocenet.net> wrote in message
news:3ba391fe$1...@news.installshield.com...

[James P. Hoffman]

First, your scenario is correct, except that the version 1 also has DCOM 95
included. Version 1 has MDAC_typ as a custom action, Version 2 has MDAC 2.6
included in the installation. Otherwise, the two installation project are
identical, version 2 being a modification of a copy of version 1.

After running version 2 as an upgrade through a path, I get error negative
2147352567, regardless of whether or not I've rebooted. If I then either run
mdac_typ manually, or run project 1 as an upgrade, the error is removed.
The error does not occur on WIN98s2.

Here's the odd thing, C:\Program Files\Common Files\System\MSADC contains 14
dll's. Whether I check the version before or after project 1 or project 2,
all files have the version 2.60.6526.0.

btw, I'm leaving on a very early flight for a vacation on Wednesday morning.
I'll try to do an desired tests or file transfers before I go; but, if not,
I'll get them done early next week.

Pete Hoffman

"Chandima Rajakaruna" <no re...@installshield.com> wrote in message
news:3ba5fdd6$1...@news.installshield.com...

[reply@installshield.com Chandima Rajakaruna]

The MDAC_Typ you install with version 1 is for MDAC 2.6? If so do you need
to distribute MDAC merge module with your Version 2 (Unless a new customer
uses the version 2). I will take a look in to this scenario and get back to
you.

I did a small search in MSDN and it looks like this error returns from many
Microsoft operations. If you are using any sort VB code to connect to a
server or something you could check out

http://support.microsoft.com/support/kb/articles/Q186/0/63.ASP

Might be related. Nevertheless, I shall perform some tests of my own and get
back to you with this. Thanks.

"James P. Hoffman" <jpho...@velocenet.net> wrote in message

news:3ba68b87$1...@news.installshield.com...