Office XP SP3 fault on Terminal Services 2003 Server

I have a Windows 2003 Server setup as a Terminal Services Server. I have
installed Office XP onto it (using Add/Remove Programs), then in Install
mode applied SP1 - OK, then SP3 (realising SP3 is cumulative, didn't bother
with SP2). This gave a fault as follows -

Error 1931 - cannot update c:\program files\common files\microsoft
shared\web server extensions\50\bin\fp5autl.dll - this file is protected by
Windows.

I checked out this error message on Ms website, which indicated it's
connected with Windows File Protection mechanisms - it gave a workaround
which simply advised doing a silent install to avoid this error message, but
gave no information about whether this error is critical or how to actually
get the update to happen.

Does anyone know a workaround which will allow this file to be updated?

Many thanks for any help.

Jan

Did you try rebooting the server before doing the SP?

Did you know that you can build install media or a network installation
point that has the SPs and other updates integrated into the install?

Did you know you can install these via Group Policy?

http://www.workthin.com/tsai.htm

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.workthin.com

"Jan" wrote:

> I have a Windows 2003 Server setup as a Terminal Services Server. I have
> installed Office XP onto it (using Add/Remove Programs), then in Install
> mode applied SP1 - OK, then SP3 (realising SP3 is cumulative, didn't bother
> with SP2). This gave a fault as follows -
>
> Error 1931 - cannot update c:\program files\common files\microsoft
> shared\web server extensions\50\bin\fp5autl.dll - this file is protected by
> Windows.
>
> I checked out this error message on Ms website, which indicated it's
> connected with Windows File Protection mechanisms - it gave a workaround
> which simply advised doing a silent install to avoid this error message, but
> gave no information about whether this error is critical or how to actually
> get the update to happen.
>
> Does anyone know a workaround which will allow this file to be updated?
>
> Many thanks for any help.
>
> Jan
>
>
>
>

No, I didn't reboot after SP1. Tend to think that shouldn't be necessary
these days.

Yes, could build an installation point, but we only have one TS 2003 server,
so lot of effort for that.

Group Policy - don't see how that would help, it's still applying the same
patch whether you apply it direct, or via policy?

Thanks for the thoughts, but I'm still stuck!

Jan

"Patrick Rouse" <PatrickRouse@discussions.microsoft.com> wrote in message
news:F0A112FF-2AE6-449E-A7D1-E01B10095CBB@microsoft.com...
> Did you try rebooting the server before doing the SP?
>
> Did you know that you can build install media or a network installation
> point that has the SPs and other updates integrated into the install?
>
> Did you know you can install these via Group Policy?
>
> http://www.workthin.com/tsai.htm
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
> "Jan" wrote:
>
> > I have a Windows 2003 Server setup as a Terminal Services Server. I
have
> > installed Office XP onto it (using Add/Remove Programs), then in Install
> > mode applied SP1 - OK, then SP3 (realising SP3 is cumulative, didn't
bother
> > with SP2). This gave a fault as follows -
> >
> > Error 1931 - cannot update c:\program files\common files\microsoft
> > shared\web server extensions\50\bin\fp5autl.dll - this file is protected
by
> > Windows.
> >
> > I checked out this error message on Ms website, which indicated it's
> > connected with Windows File Protection mechanisms - it gave a workaround
> > which simply advised doing a silent install to avoid this error message,
but
> > gave no information about whether this error is critical or how to
actually
> > get the update to happen.
> >
> > Does anyone know a workaround which will allow this file to be updated?
> >
> > Many thanks for any help.
> >
> > Jan
> >
> >
> >
> >