Article ID: 914830 - Last Review: September 25, 2007 - Revision: 1.6 Access 2003 may not start as expected after you install Office 2003 SP2On This PageSYMPTOMSAfter you install Microsoft Office 2003 Service Pack 2
(SP2), Microsoft Office Access 2003 may not start as expected. You may receive
a message that is similar to the following: The configuration appears to finish as expected, but Access 2003
does not start. When you try to start Access 2003 again, you receive the same
message. CAUSEThis problem can occur if you use Group Policy to install
Office 2003 SP2 on a per-user basis. When you use Group Policy to install
Office 2003 SP2 on a per-user basis, a registry key may not be updated
correctly. RESOLUTIONThis problem is corrected in Office 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 870924
(http://support.microsoft.com/kb/870924/
)
How to obtain the latest service pack for Office 2003 To resolve this problem, you can also use one of the following methods. Method 1: Import the registry key from a computer where Access 2003 starts as expectedTo resolve this problem, export a registry key from a computer where Access 2003 starts as expected. To do this, follow these steps.Note When you follow these steps, some settings, such as ODBC settings or time-out settings, may be overwritten on the computer where Access 2003 does not start.
Method 2: Manually change the registryTo resolve this problem, manually change the registry on the computer where Access 2003 does not start as expected. To do this, follow these steps:
WORKAROUNDTo work around this problem, use Group Policy to install
Office 2003 SP2 on each computer. For more information about how to deploy
Office 2003 SP2 on each computer, visit the following Microsoft Web site: http://www.microsoft.com/office/ork/2003/two/ch5/DepC04.htm
(http://www.microsoft.com/office/ork/2003/two/ch5/DepC04.htm)
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. This problem was first corrected in Office 2003 Service Pack 3. | Article Translations
|
Back to the top
