Outlook 2003 (with exchange 2003 configed) installation fails with fatal error

[Brian Henry]

Hi everyone,

We just deployed (or tried to deploy) Outlook 2003 though out our corporate
domain. The domain is running on an Active Directory mixed mode setup
(Windows 2000/2003 servers). We did an administrative installation into our
network file share that has public access to all authenticated users. The
administrative installation of course has the CD-Key entered into its
installation so we can do quiet installations over the network. It was setup
as a group policy to have it install on all users in the company. It was
available to users through add/remove and the start menu like it should of
been. The problem though happened when a user tried to install it by
clicking on the outlook icon that was now available in the start menu or
using add programs in control panel. It would start installing then give
back a fatal error message. We thought at first this was just a network
problem, but when we tried to install it from the CD also it got up to the
point where it normall would start copying files, but when it got to that
point it did a rollback and cancelled the installation. We can not figure
out what is going on, but we absoutly need this fixed immediatly. Users have
no email because of the lack of outlook to connect to the exchange server,
and they refuse to use webmail for some reason... and the logs outlook
returned didn't make much sense.. at least at the point I could figure out
what was wrong from... I uploaded the logs to my website, they are available
at http://www.bhplace.com/logs/ if you could please look at them and try to
help me out it would mean a lot, because the 4 of us here working on it are
stumped currently. It either rolls back the install when you do it manually
off the CD or over a network deployment it gives a fatal error. Thanks so
much!

 

[neo [mvp outlook]]

The installer reported back a 1603 error code.

The "task" test file shows that this file could not be deleted.
C:\DOCUME~1\MARK_L~1\LOCALS~1\Temp\7b5fed.mst

The error code was 32.
Error code 32 comes up as "The process cannot access the file because it is
being used by another process".

In this case, make sure msiexec is not in the process list. Clean up the
temp folders, consider disabling antivirus, and then try running the install
again.

By the way is the software install policy tied to the user or computer part
of the gpo? (i always go with computer since it means that the system is
doing the install. to many variables when going with the user portion
because of rights.)

 

[Brian Henry]

I had it with the user part because office stated in the documentation
specifically not to do it with the computer part because it "wont work"...
so never attempted that one.