I'm having the exact same problem; also on Win2k, and VS 2005 Pro.
I tried uninstalling MDAC 2.8 hotfix 1, and reinstall VS, and that did not
help. When I try installing from VS's WCU folder or the downloaded version,
I get the exact same error as above.
The link Stefan references below does NOT offer a solution. It refers to a
similar problem when installing Exchange Instant Messaging Client, however
it's a fundamentally different problem, as the Admin account DOES have access
the registry key noted.
Based on Google results, this link appears to deal with the problem, however
it's broken and google no longer has it cached:
http://support.microsoft.com/newsgroups/newsReader.aspx?dg=microsoft.public.vsnet.setup&tid=aa2149db-ff34-4a4b-bcf2-d7b10fa4a43d&p=1 After much searching it appears nobody has a solution for this. :(
[quoted text, click to view] "Stefan" wrote:
> I suspect that I have several versions of MDAC (2.5+) on a Windows 2000
> computer and this is causing VS 2005 Pro installer to fail.
>
> I have been trying to install VS 2005 Pro but am getting the following error:
>
> [08/19/06,16:32:35] Microsoft Data Access Components 2.8 SP1: [2] Error code
> -2147024891 for this component means "Access is denied.
> "
> [08/19/06,16:32:35] Microsoft Data Access Components 2.8 SP1: [2] Component
> Microsoft Data Access Components 2.8 SP1 returned an unexpected value.
> [08/19/06,16:32:35] Microsoft Data Access Components 2.8 SP1: [2] Return
> from system messaging: Access is denied.
>
> When I try to install MDAC 2.8 SP 1 as a seperate download I get the error:
>
> INF Install failure. Reason: Access is denied.
>
> Ran MS Component Checker Version 2 to try to sort out all the MDAC DLLs but
> I'm lost with the results. Running it gives me the error:
>
> The following product releases were matched: UNKNOWN
>
> Some links I found useful of a description of the problem (but including
> very confusing solution):
>
>
http://www.webnewsgroups.net/group/microsoft.public.win2000.general/topic22969.aspx
>
>
> Thanks for any input,
>
> Stefan
> CSC Inc.
I'm having the exact same problem; also on Win2k, and VS 2005 Pro.
I tried uninstalling MDAC 2.8 hotfix 1, and reinstall VS, and that did not
help. When I try installing from VS's WCU folder or the downloaded version,
I get the exact same error as above.
The link Stefan references below does NOT offer a solution. It refers to a
similar problem when installing Exchange Instant Messaging Client, however
it's a fundamentally different problem, as the Admin account DOES have access
the registry key noted.
Based on Google results, this link appears to deal with the problem, however
it's broken and google no longer has it cached:
http://support.microsoft.com/newsgroups/newsReader.aspx?dg=microsoft.public.vsnet.setup&tid=aa2149db-ff34-4a4b-bcf2-d7b10fa4a43d&p=1 After much searching it appears nobody has a solution for this. :(
[quoted text, click to view] "Stefan" wrote:
> I suspect that I have several versions of MDAC (2.5+) on a Windows 2000
> computer and this is causing VS 2005 Pro installer to fail.
>
> I have been trying to install VS 2005 Pro but am getting the following error:
>
> [08/19/06,16:32:35] Microsoft Data Access Components 2.8 SP1: [2] Error code
> -2147024891 for this component means "Access is denied.
> "
> [08/19/06,16:32:35] Microsoft Data Access Components 2.8 SP1: [2] Component
> Microsoft Data Access Components 2.8 SP1 returned an unexpected value.
> [08/19/06,16:32:35] Microsoft Data Access Components 2.8 SP1: [2] Return
> from system messaging: Access is denied.
>
> When I try to install MDAC 2.8 SP 1 as a seperate download I get the error:
>
> INF Install failure. Reason: Access is denied.
>
> Ran MS Component Checker Version 2 to try to sort out all the MDAC DLLs but
> I'm lost with the results. Running it gives me the error:
>
> The following product releases were matched: UNKNOWN
>
> Some links I found useful of a description of the problem (but including
> very confusing solution):
>
>
http://www.webnewsgroups.net/group/microsoft.public.win2000.general/topic22969.aspx
>
>
> Thanks for any input,
>
> Stefan
> CSC Inc.
FINALLY found the solution. Some file or folder somewhere that it needed was
marked as ReadOnly. The solution was to mark the major root folders (winnt,
program files, documents and settings etc.) as readonly, then mark them as
NOT readonly and apply the settings to all subfolders and files. Microsoft,
Don't see what you're looking for? Try a search.
