MSACCESS 2003 Fails After SP2 Update

[Michael]

After updating to Office 2003/SP2 from Office 2003/SP1, systems on my network
no longer run MSACCESS. All other Office applications seem to work correctly
and are running at SP2 level. The installation was made through Active
Directory in a Windows 2003 Server domain. I patched the administrative
share using msiexec /p patch /a msifile SHORTFILENAMES=1.

When you start MSACCESS, Windows Installer starts to do its work then stops
and Access never starts. You can try to run MSACCESS multiple times and each
time Windows Installer shows its progress dialog but Access never runs. You
can see the MSACCESS process run in Task Manager for a short time then it
dies. I have attached the Visual Studio .Net debugger to the MSACCESS
process and it does report a CExceptionHandler exception immediately before
termination. I don't know if the application is crashing or if this
exception is being handled in Access.

I removed Office from my Active Directory system and then reinstalled Office
from the original media to determine if I could get Access running again with
no service packs and with only service pack 1. For both cases, Access runs
on my client systems. Only with SP2 does it fail.

Does anyone have any ideas on this?

Thanks

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Bob Haussmann]

For what it's worth, we are encountering the exact same issue. It appears
to be
a bug. In addition to the troubleshooting you outlined below, we tried:

1) uninstall/reinstall Access 2003 component
2) uninstall Office 2003 completely, reinstall

In both cases, the installer complains about not PRO11.MSI not found or
being
an incorrect version.

Interestingly, if we do a custom install and change the Access component
from
"Run from network" to "run from my computer", the PRO11.MSI message does
not appear, and Access appears to run correctly (at the SP2 level). Of
course,
then we no longer have the network installation we are looking for.


Bob Haussmann
Tabor Children's Services, Inc.

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

If I take the same patched administrative image and install using the
pro11.msi on a system that is not being administered by my Active Directory
domain group policy installation, Access works as well. It only fails on my
systems administered using the AD GPO.

Michael

 

[Michael]

I called Microsoft today and they're going to look into this. I'm going to
try to repo on a new Windows 2003 Server Active Directory Domain.

Michael