Tivoli and MS MDAC 2.8
Hi,
I am having a problem with MS MDAC 2.8 (and 2.7) where once packaged using Tivoli Soft Dist 4.1 fix pack 4, and distributed to the client (Windows 2000), generates the following error ADODB._Command failed when trying to run the MDAC reliant software.
This error relates to MDAC not being installed onto the client.
Now I have packaged with Veritas WinINSTALL (7.5) and it works but I need to get the Tivoli package working, I have tried removing the exculsions etc and also comparing the 2 packages, Tivoli and WinINSTALL and cannot see any difference.
I think it maybe down to DLL registration but have run out of ideas can anyone help?[:(]
I am having a problem with MS MDAC 2.8 (and 2.7) where once packaged using Tivoli Soft Dist 4.1 fix pack 4, and distributed to the client (Windows 2000), generates the following error ADODB._Command failed when trying to run the MDAC reliant software.
This error relates to MDAC not being installed onto the client.
Now I have packaged with Veritas WinINSTALL (7.5) and it works but I need to get the Tivoli package working, I have tried removing the exculsions etc and also comparing the 2 packages, Tivoli and WinINSTALL and cannot see any difference.
I think it maybe down to DLL registration but have run out of ideas can anyone help?[:(]
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
bkelly
20 years ago
I would recommend against repackaging MDAC. There are just so many dependancies on this component that you really don't want to take a chance on getting it wrong. There is command line installation support you may take advantage of, and for MSI packages, there is a merge module (pre packaged MSI component) available from Microsoft. You can include this in your MSI to get the job done programmatically. The merge module itself actually performs a silent installation of MDAC using its command line support from a custom action within your MSI package. For more information and links on the deployment of MDAC, see our
" class="migrated-link">MDAC Package Knowledge Base entry.
Posted by:
BarryB
20 years ago
Hi Bob,
I found an option to execute a Microsoft install in Tivoli and following your advice, I packaged the extracted install files and got Tivoli to execute the dasetup.exe /q and all is now working nicely [:D]
Thanks for your help! [:)]
Barry
I found an option to execute a Microsoft install in Tivoli and following your advice, I packaged the extracted install files and got Tivoli to execute the dasetup.exe /q and all is now working nicely [:D]
Thanks for your help! [:)]
Barry
Posted by:
jecouch66
19 years ago
Bob,
I have a medical package that wants to attempt the install of mdac even though I've already manually installed it (and rebooted the computer). How do I get the mdac_install out of the msi? I'm new to the whole packaging business, though I'm learning a lot every day. I'm using Tivoli to distribute the package, but that is by snapshot. The snapshot method is not very reliable and we keep finding registry entries that the new computer does have or can't create. If you could assist me with how that's done, I'd appreciate it. And if it's explained somewhere else, I'm more than happy to read that. I just can't find what I'm looking for, or don't recognize it if I have.
Thanks,
John
I have a medical package that wants to attempt the install of mdac even though I've already manually installed it (and rebooted the computer). How do I get the mdac_install out of the msi? I'm new to the whole packaging business, though I'm learning a lot every day. I'm using Tivoli to distribute the package, but that is by snapshot. The snapshot method is not very reliable and we keep finding registry entries that the new computer does have or can't create. If you could assist me with how that's done, I'd appreciate it. And if it's explained somewhere else, I'm more than happy to read that. I just can't find what I'm looking for, or don't recognize it if I have.
Thanks,
John
Posted by:
bkelly
19 years ago
It depends on what tools you have at your disposal, but I would recommend creating a transform that removes MDAC from the package. In your tool, create a new MST and specify the vendor provided MSI as the package you are basing it on. From here any changes you make will not be to the MSI directly, but saved to an MST and this can be any change. Go to "merge modules" and you should see MDAC there- just delete it, save your MST and deploy the resulting MST with your MSI. Exactly how this works would depend on your software- but this process should get you what you need.
Best of luck,
Bob
Best of luck,
Bob
Posted by:
jecouch66
19 years ago
I was afraid of that...I did just that....and then the package won't install for some reason. Grrr. I'm using Wise Studio 4 to make the transform. I have contacted the developer to see I can get them to remove it...or tell us why removing it causes the error. Either way, I apprciate your response.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.