Trying to update this Windows XP SP2 box to SP3. Went to the update web site,
downloaded OK. During installation, had registry access errors (!) on
HKCR\RDSServer.DataFactor.2.8.1 and a couple of related keys. Changed
permissions, tried again. No pop-up errors about the registry this time, but
XP3 update failed again, error code 0x80070005.
Found the comments from people who had similar problems on XP2, with
especial regard to KB873148. Using the info in that KB article, checked
%windir%\svcpack.log and, yep, had DoRegistry falures in there..
So, turned on full debug as described in the article, reran the thing until
it died. Fired up my local text editor (xemacs, what the heck), and went
looking for the failed registry keys in %windir%\setupapi.log.
Only problem - no failed registry keys! Instead, have the following error
messages at the end of the log:
#-198 Command line processed: "C:\WINDOWS\system32\sysocmgr.exe" /y
/i:C:\WINDOWS\system32\sysoc.inf
#E077 Could not locate a non-empty section [iis_common_install] when
calculating disk space in "C:\WINDOWS\INF\iis.inf". Error 0xe0000102: The
required line was not found in the INF.
#E077 Could not locate a non-empty section [iis_inetmgr_install] when
calculating disk space in "C:\WINDOWS\INF\iis.inf". Error 0xe0000102: The
required line was not found in the INF.
#E077 Could not locate a non-empty section [iis_pwmgr_install] when
calculating disk space in "C:\WINDOWS\INF\iis.inf". Error 0xe0000102: The
required line was not found in the INF.
#E077 Could not locate a non-empty section [iis_www_install] when
calculating disk space in "C:\WINDOWS\INF\iis.inf". Error 0xe0000102: The
required line was not found in the INF.
#E077 Could not locate a non-empty section [iis_doc_install] when
calculating disk space in "C:\WINDOWS\INF\iis.inf". Error 0xe0000102: The
required line was not found in the INF.
#E077 Could not locate a non-empty section [iis_ftp_install] when
calculating disk space in "C:\WINDOWS\INF\iis.inf". Error 0xe0000102: The
required line was not found in the INF.
OK. I am now at a loss. The other suggestion in KB873148 was to use
secedit.exe and reset the permissions to something better. But this machine
is running XP2 Home, and that doesn't have the program.
What now? Or do I have to wipe this machine and start over? Help, somebody?
Bookmarks