If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
MSACCESS 2003 Fails After SP2 Update
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 |
#2
|
|||
|
|||
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" wrote in message ... 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 |
#3
|
|||
|
|||
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 "Bob Haussmann" wrote: 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" wrote in message ... 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 |
#4
|
|||
|
|||
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 "Bob Haussmann" wrote: 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" wrote in message ... 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 |
#5
|
|||
|
|||
I have a similar problem. Whenever I start access 2003 it runs the
installer for a minute, completes, then open the program. If I click on a database shortcut, it does the same thing, but first says it can't find the file the shortcut refers to, then it opens it anyway after the installer finishes. This is driving me crazy and I would love some help. We are running Server 2003 w/ terminal services and all other office 2003 programs work fine on sp2. Thanks for any help! |
#6
|
|||
|
|||
Sounds a bit like this one:
(absurdly long URL follows) http://groups.google.com/group/micro...76719351c71 a TC |
#7
|
|||
|
|||
I was able to reproduce this problem in an isolated domain without any
difficulty. Microsoft also has been able to duplicate this problem. Unfortunately, I've not been able to convince them so far that this problem is extremely serious and warrants an immediate fix---from my perspective they have disabled 100% of the MS 2003 Access copies in use with service pack 2 if deployed through an Active Directory GPO. If I were in their position, I'd be working overtime to solve this problem. Michael " wrote: I have a similar problem. Whenever I start access 2003 it runs the installer for a minute, completes, then open the program. If I click on a database shortcut, it does the same thing, but first says it can't find the file the shortcut refers to, then it opens it anyway after the installer finishes. This is driving me crazy and I would love some help. We are running Server 2003 w/ terminal services and all other office 2003 programs work fine on sp2. Thanks for any help! |
#8
|
|||
|
|||
MSACCESS 2003 Fails After SP2 Update
TC wrote: Sounds a bit like this one: (absurdly long URL follows) http://groups.google.com/group/micro...76719351c71 a TC I have the same issue. very wierd.. |
#9
|
|||
|
|||
MSACCESS 2003 Fails After SP2 Update
I don't think anyone who installs through GPO is NOT going to have it...
Michael " wrote: TC wrote: Sounds a bit like this one: (absurdly long URL follows) http://groups.google.com/group/micro...76719351c71 a TC I have the same issue. very wierd.. |
#10
|
|||
|
|||
MSACCESS 2003 Fails After SP2 Update
wrote:
I was able to reproduce this problem in an isolated domain without any difficulty. Microsoft also has been able to duplicate this problem. Unfortunately, I've not been able to convince them so far that this problem is extremely serious and warrants an immediate fix---from my perspective they have disabled 100% of the MS 2003 Access copies in use with service pack 2 if deployed through an Active Directory GPO. If I were in their position, I'd be working overtime to solve this problem. Michael I Agree, it's a major fault and it doesn't look like MS did any QA on deployment of SP2 through Admin installs. I'm going to raise a bug report on Monday and get it escalated. In the meantime, I'll see if I can figure out what's wrong with the package, to speed the process up. The problem with MS is that they only tend to fix issues when enough people complain, so if anyone else is having the same problem, log a fault with MS. Jon |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Cannot update Outlook 2003 update | DinosaurGreener | General Discussion | 4 | May 13th, 2005 10:11 PM |
Installing cumulative update for OE 6 | Vasilis | Outlook Express | 8 | May 7th, 2005 02:01 AM |
2003 update link when Source open | Ausrobbo | Worksheet Functions | 0 | January 17th, 2005 06:25 AM |
After installing Windows XP SP2 , how do I open old Excel 2003 fil | Mike D | General Discussion | 2 | September 2nd, 2004 10:21 PM |
Bug in Office Update for Office 2003 Installation | AA Smith | Setup, Installing & Configuration | 1 | September 1st, 2004 04:43 PM |