KB911562 installation fails - Error Code 0x8007F0DA

[stickweldnow]

I got my solution:
"Dear Richard,



Thank you for your update.



From your reply, I understand that there are two files that named
SQLSRV32.DLL. The one which is located in C:\WINDOWS\SYSTEM32 has the version
2000.85.1117.0 and the other one that is located in C:\WINNT\system32 has the
version 3.70.9.61. Now we can find that the same DLL file in the two folders
have been different version. The behavior can be the root cause of our issue.



At this time, please locate the folder C:\WINDOWS\SYSTEM32 and rename the
SQLSRV32.DLL to SQLS.DLL. Then please copy the SQLSRV32.DLL in
C:\WINNT\system32 and paste it to the folder C:\WINDOWS\SYSTEM32. Thank you
for your cooperation.



After completing above steps, please try to run Windows Update again.



If the issue persists, please help me check the following points:



1. Were two Operation Systems were installed in the C: hard drive?



2. Whether Windows XP is used when running Windows Update?



Please let me know the results at your earliest convenience. If anything is
unclear in the email, please do not hesitate to tell me and I will be glad to
help.



I look forward to hearing from you.



Best Regards,



Austin Gu



v-30augu@mssupport.microsoft.com

Microsoft Windows Support Professional

I had 2 copies of windows 2000 installed.

[4thn5]

I have the same issue as above getting failed installation for security
update KB911562 on a Windows 2000 Server SP4. I've tried all the above
suggestions without luck. The one difference is that I am also unable to
install MDAC 2.8 SP1 even after reinstalling MDAC 2.8. I get the error
message INF install failure. Reason: access denied.

Any advice?

"stickweldnow" wrote:

>
> I got my solution:
> "Dear Richard,
>
>
>
> Thank you for your update.
>
>
>
> From your reply, I understand that there are two files that named
> SQLSRV32.DLL. The one which is located in C:\WINDOWS\SYSTEM32 has the version
> 2000.85.1117.0 and the other one that is located in C:\WINNT\system32 has the
> version 3.70.9.61. Now we can find that the same DLL file in the two folders
> have been different version. The behavior can be the root cause of our issue.
>
>
>
> At this time, please locate the folder C:\WINDOWS\SYSTEM32 and rename the
> SQLSRV32.DLL to SQLS.DLL. Then please copy the SQLSRV32.DLL in
> C:\WINNT\system32 and paste it to the folder C:\WINDOWS\SYSTEM32. Thank you
> for your cooperation.
>
>
>
> After completing above steps, please try to run Windows Update again.
>
>
>
> If the issue persists, please help me check the following points:
>
>
>
> 1. Were two Operation Systems were installed in the C: hard drive?
>
>
>
> 2. Whether Windows XP is used when running Windows Update?
>
>
>
> Please let me know the results at your earliest convenience. If anything is
> unclear in the email, please do not hesitate to tell me and I will be glad to
> help.
>
>
>
> I look forward to hearing from you.
>
>
>
> Best Regards,
>
>
>
> Austin Gu
>
>
>
> v-30augu@mssupport.microsoft.com
>
> Microsoft Windows Support Professional
>
> I had 2 copies of windows 2000 installed.

[GeekGirl]

I am having this same problem, but I only have one instance of SQLSRV32 so
this solution does not apply to me. Everything I have tried so far has been
unsuccessful. Can I reinstall 2.81? Does anyone have any new info on this
problem?

"stickweldnow" wrote:

>
> I got my solution:
> "Dear Richard,
>
>
>
> Thank you for your update.
>
>
>
> From your reply, I understand that there are two files that named
> SQLSRV32.DLL. The one which is located in C:\WINDOWS\SYSTEM32 has the version
> 2000.85.1117.0 and the other one that is located in C:\WINNT\system32 has the
> version 3.70.9.61. Now we can find that the same DLL file in the two folders
> have been different version. The behavior can be the root cause of our issue.
>
>
>
> At this time, please locate the folder C:\WINDOWS\SYSTEM32 and rename the
> SQLSRV32.DLL to SQLS.DLL. Then please copy the SQLSRV32.DLL in
> C:\WINNT\system32 and paste it to the folder C:\WINDOWS\SYSTEM32. Thank you
> for your cooperation.
>
>
>
> After completing above steps, please try to run Windows Update again.
>
>
>
> If the issue persists, please help me check the following points:
>
>
>
> 1. Were two Operation Systems were installed in the C: hard drive?
>
>
>
> 2. Whether Windows XP is used when running Windows Update?
>
>
>
> Please let me know the results at your earliest convenience. If anything is
> unclear in the email, please do not hesitate to tell me and I will be glad to
> help.
>
>
>
> I look forward to hearing from you.
>
>
>
> Best Regards,
>
>
>
> Austin Gu
>
>
>
> v-30augu@mssupport.microsoft.com
>
> Microsoft Windows Support Professional
>
> I had 2 copies of windows 2000 installed.

[willow]

"webhostingcanada@gmail.com" wrote:

> Yes...Please do post a solution if you get one. Thanks for your
> perserverence. I have gotten nowhere with this issue either.
>
>

Did MS ever fix this? There's like a million posts but no one seems to have
found a solution. It's probably a long shot being 2 years later but I would
have hoped that MS would have fixed this by now.

Thanks,

Jake

[TaurArian]

You cannot install some updates or programs
http://support.microsoft.com/kb/822798
When you examine the %systemroot%\Windowsupdate.log file, you may see an entry for one of
the following errors:. 0x80096001
.. 0x80096005 . 0x80096010 . 0x800B0001 . 0x800B0003 . 0x800B0004 .
800B0109 . 0x8007f0da

--

TaurArian [MVP] 2005-2008 - Update Services
http://taurarian.mvps.org
======================================
How to ask a question: http://support.microsoft.com/kb/555375
Computer Maintenance: Acronis / Diskeeper / Paragon / Raxco


"willow" <willow@discussions.microsoft.com> wrote in message
news:191EB652-53F5-4E55-9743-E3621FCB7307@microsoft.com...
|
|
| "webhostingcanada@gmail.com" wrote:
|
| > Yes...Please do post a solution if you get one. Thanks for your
| > perserverence. I have gotten nowhere with this issue either.
| >
| >
|
| Did MS ever fix this? There's like a million posts but no one seems to have
| found a solution. It's probably a long shot being 2 years later but I would
| have hoped that MS would have fixed this by now.
|
| Thanks,
|
| Jake