SP failing with access denied error message

  • Thread starter Thread starter Bjarni
  • Start date Start date
B

Bjarni

Towards the end of SP2 install I get access denied error
messages.... I have admin rights, this is on stand alone
PC. I have done the update using both downloaded SP2 and
via automative update. Have done hundreds of these and
have not had one hickup like this one...

according to setupapi.log I have these following error
messages, actualy hundreds of them:

#E197 Writing "C:\WINDOWS\INF\mdmrpci.inf"
to "C:\WINDOWS\INF" is not an approve
d method of installing INF files. Use a 'CopyINF' entry
instead.
#E197 Writing "C:\WINDOWS\INF\mdmlt3.inf"
to "C:\WINDOWS\INF" is not an approved
method of installing INF files. Use a 'CopyINF' entry
instead.
#E197 Writing "C:\WINDOWS\INF\mdmirmdm.inf"
to "C:\WINDOWS\INF" is not an approv
ed method of installing INF files. Use a 'CopyINF' entry
instead.

any ideas anyone??
 
Towards the end of SP2 install I get access denied error
messages.... I have admin rights, this is on stand alone
PC. I have done the update using both downloaded SP2 and
via automative update. Have done hundreds of these and
have not had one hickup like this one...

according to setupapi.log I have these following error
messages, actualy hundreds of them:

#E197 Writing "C:\WINDOWS\INF\mdmrpci.inf"
to "C:\WINDOWS\INF" is not an approve
d method of installing INF files. Use a 'CopyINF' entry
instead.
#E197 Writing "C:\WINDOWS\INF\mdmlt3.inf"
to "C:\WINDOWS\INF" is not an approved
method of installing INF files. Use a 'CopyINF' entry
instead.
#E197 Writing "C:\WINDOWS\INF\mdmirmdm.inf"
to "C:\WINDOWS\INF" is not an approv
ed method of installing INF files. Use a 'CopyINF' entry
instead.
Click to expand...

Bjami,

please have a look at http://www.michna.com/kb/WxSP2.htm.

Hans-Georg
 
Thanks both for your response. here is what I did, I
created another account on this PC, with administrator
rights, and was then able to complete the update..
however, now when logging onto any other account other
then the new one the desktop takes about 5 minutes to
come up, and I have the following error messages in
system event viewer:
The server {BA126AD1-2166-11D1-B1D0-00805FC1270E} did not
register with DCOM within the required timeout.

The app event viewer has:
The COM+ Event System detected a bad return code during
its internal processing. HRESULT was 80004002 from line
44 of d:\qxp_slp\com\com1x\src\events\tier1
\eventsystemobj.cpp. Please contact Microsoft Product
Support Services to report this error.

I am currently researching this issue but would
appreciate any feedback that ayone might have

Thanks

bjarni
 
Back
Top