/build/static/layout/Breadcrumb_cap_w.png

MDAC 2.8 Reboot

After installing MDAC 2.8 with local admin privilages and rebooting I get a series of errors to the following effect on the next log in with a non administrative account.


Windows Update

X An error has occurred while setting up "C:\Program Files\Common Files\System\ADO\msado15.dll". This error has been logged, the installation will continue
OK



How do you handle unattended distribution of MDAC to managed restricted clients?

0 Comments   [ + ] Show comments

Answers (6)

Posted by: craig16229 18 years ago
Third Degree Brown Belt
0
Did you install MDAC from the Microsoft binary?


Craig --<>.
Posted by: xythex 18 years ago
Orange Senior Belt
0
I've tried using just the MDAC_TYP.EXE with no switches and also silently with the extracted files with dasetup.exe. Also it works fine if that first login after the reboot is with an administrative account, but this would be very difficult to automate. FYI it is XP SP1.
Posted by: DuncanPaul 18 years ago
Orange Belt
0
Hi All,

sorry to bring back this thread, but I've the exact same issue. I've tried using DASetup, or passing the command line through MDAC_TYP, and the result is always the same. I can install it, but at first restart the Runonce keys register dlls and return errors if the account being used isn't an admin.
I've also tried using Microsofts msm,
http://support.microsoft.com/default.aspx?scid=kb;en-us;320788

however this appears to be the redistributable with a merge module wrapped around it.
also tried installshield merge module
http://www.installshield.co.kr/products/x/features/InstallShield%20%20Downloads%20%20Modules.html
but issues are the same.

Am using XP Sp1. At the moment our org has no plans to deploy SP2, so need to fill this gap in interim. We deploy with a custom solution installing in user context with elevated privileges, hence the issue.

If anyone can confirm for me it is possible to install the MDAC 2.8 without using admin privileges I would be very grateful.

thanks,
Posted by: xythex 18 years ago
Orange Senior Belt
0
Never did find a solution to this issue. Just ended up waiting until it was time to deploy SP2, which of course it is bundled with.

I kicked around the idea of creating an admin account on the pc with a randomized username and password, and setting the pc to reboot, autologin with this account, then delete the account and reboot again after the second part of the setup completed.
Posted by: DuncanPaul 18 years ago
Orange Belt
0
cheers xythex, exactly what we're thinking, but really isn't worth the dev cost to do, think will be another reason for sp2, although thats miles off for us. thanks for your reply.
Posted by: aogilmor 18 years ago
9th Degree Black Belt
0
Duncan, This guy seems to have found a solution. certainly not easy, but do-able.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ