Article ID: 825444 - Last Review: September 25, 2006 - Revision: 5.3 How to troubleshoot fatal system errors in Access 2003 when Access 2003 is running on the Windows 2000 operating system This
article applies to a Microsoft Access database (.mdb) and to a Microsoft Access
project (.adp). Moderate: Requires basic macro, coding, and interoperability skills. For a Microsoft Access 2002 version of this article,
see
294301
(http://support.microsoft.com/kb/294301/
)
. For a Microsoft Access 97 version of this article,
see
148424
(http://support.microsoft.com/kb/148424/
)
. On This PageSUMMARYThis article discusses the Microsoft Office 2003 Application
Error Reporting tool. You can use the Application Error Reporting tool to
report to Microsoft the fatal system errors that occur in Microsoft Office
Access 2003. This article discusses the causes of fatal system errors that may occur in Access 2003 when Access 2003 is running on the Microsoft Windows 2000 operating system. This article discusses general troubleshooting steps that you can use to solve the fatal system errors. Note This is a general article. The Microsoft Knowledge Base may have a specific article that addresses the exact error that you receive. To find out if a specific article exists, search the Knowledge Base by using the exact text of the error message. For additional information about the Knowledge Base, visit the following Microsoft Web site: http://support.microsoft.com/gp/gsssearchhelp
(http://support.microsoft.com/gp/gsssearchhelp)
Use the Office Application Error Reporting toolFor most fatal errors in Access 2003, you may receive the following error message:Microsoft Office Access
has encountered a problem and needs to close. We are sorry for the
inconvenience. The information you were working on might be lost. Microsoft Office Access can try to compact and repair your open database. Repair my open database and restart Microsoft Office Access Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Office Access. We will treat this report as confidential and anonymous. What data does this error report contain? Why should I report to Microsoft? When you receive this error message, Access 2003 permits you to collect and to send the error information to Microsoft. The error report contains an error signature that records information such as the application details, the module details, and the error information or the exception information. Microsoft uses the error report to improve Microsoft products. If you have an active Internet connection when you receive the error message, you can send the error report directly to Microsoft by using the Office Application Error Reporting tool. If you report the error, the Office Application Error Reporting tool verifies whether a solution to the problem is already available. If the solution to the problem is already available, the Office Application Error Reporting tool sends the solution to you. For additional information about end user reporting and privacy, click the following article number to view the article in the Microsoft Knowledge Base: 283768
(http://support.microsoft.com/kb/283768/
)
End
User Privacy Policy in Application Error Reporting
The following sections of this article describe how
to determine the exact problem when you receive the error message and also how
to troubleshoot the problem.Recognize fatal system errorsTypically, a fatal system error (such as a page fault error, a Stop error, a fatal exception error, or an application exception error) may cause Access 2003 (Windows-based applications) to stop responding or to fail. In Windows 2000, the basic causes for the occurrences of the fatal errors follow:
Because the specified causes are general, you may have to try several troubleshooting steps to find the specific cause of the error in Access 2003. The following sections of this article describe how to troubleshoot the occurrence of a fatal system error on your system. Understand application-related problemsThis section discusses Access 2003 application-related problems and application-related causes for fatal system errors in Windows 2000.Confirmed bug in Access 2003Sometimes a fatal system error may occur if there is a bug in an application. As a result, you may receive an error message that is similar to the following error message:Microsoft Office
Access has encountered a problem and needs to close. We are sorry for the
inconvenience. To view the error details, click What data does this error report contain?. You can find the error information such as the file that is involved in the error and the memory offset where the error occurred. You can find the known Access 2003 problems that may cause fatal system errors by using the phrase page fault for your search in the Knowledge Base. Damaged database or fragmented databaseIf the fatal system error occurs only when you open a particular database file (.mdb) or when you use a particular database file, you can use the Compact and Repair Database utility in Access 2003 to correct the potential problems that may be caused by damage to the database file or by too much fragmentation of the database structure. To use the Compact and Repair Database utility, follow these steps:
After you use the Compact and Repair Database utility and your database still behaves unpredictably and you still receive a fatal system error either immediately or after continued use, try the additional troubleshooting steps that are described in this article. Another problem may be the cause of the page fault. Corrupted databaseIf the Compact and Repair Database utility does not solve the unpredictable behavior of the Access 2003 database or the Access 2003 application-related fatal system errors, create a new database. You must import objects from the old database to the new database and then you must compile all modules in the new database.Note Microsoft does not recommend this method if your database is a replica in a replica set. If your replica is corrupted, you must create a new replica from Design Master. To create a new database and to import objects from the old database, follow these steps:
To view Microsoft Visual Basic for Applications (VBA) references, follow these steps:
For additional information about repairing Access databases, click the following article number to view the article in the Microsoft Knowledge Base: 283849
(http://support.microsoft.com/kb/283849/
)
How to Troubleshoot and Repair a Damaged Access 2002 or later Database
Damaged installation of Access 2003You may also experience problems with your database if Access 2003 is not installed correctly on your computer. Incorrect installation may result in incorrect registry settings, missing dynamic link libraries (.dll files), or corrupted dynamic link libraries.You can open your Access 2003 database on another computer that has Access 2003 installed. If your database opens and your database works correctly, you must either repair or reinstall Access 2003 on your computer. To repair the Access 2003 installation, follow these steps:
Note If you have Visual Basic with Microsoft Visual SourceSafe installed, you do not have to remove the Visual Basic program. You only have to remove the Visual SourceSafe component.
Understand system-related problemsThis section discusses system-related causes for fatal system errors in Windows 2000.Memory conflictA common cause of fatal system errors is the occurrence of a memory conflict that involves a device driver, a system component, or other loaded files. To troubleshoot a memory conflict, you must restart your computer in Safe Mode.Safe Mode bypasses startup files, including the registry, the Config.sys file, the Autoexec.bat file, and the [Boot] section and the [386Enh] section of the System.ini file. Therefore, Safe Mode provides you access to the system configuration files. When you start your computer in Safe Mode, only required system files and required device drivers (such as the mouse, the keyboard, and the standard VGA) are loaded. This makes Safe Mode useful for isolating memory conflicts and for solving memory conflicts. To start Windows 2000 in Safe Mode, follow these steps:
For more information about running Windows 2000 in Safe Mode, click the following article number to view the article in the Microsoft Knowledge Base: 202485
(http://support.microsoft.com/kb/202485/
)
Description of Safe Boot Mode in
Windows 2000
Note Windows 2000 does not provide step-by-step confirmation. If you
are troubleshooting fatal system errors with Access in Windows 2000 and the
previous article does not resolve the issue, you may want to contact Microsoft
Product Support Services. For additional information about Product Support
Services, visit the following Microsoft Web site:http://support.microsoft.com/select/?target=hub
(http://support.microsoft.com/select/?target=hub)
Temporary folder issuesWhen your computer does not have sufficient disk space for temporary files, you may notice unpredictable behavior in Access 2003. You must remove the old temporary files on your system periodically. After you remove the old temporary files, make sure that there is at least 8 megabytes (MB) to 10 MB of free space on your disk. Make sure that the free space is available to your temporary (Temp) folder.You must determine the location of your Temp folder. You must verify the validity of your TMP environment variables and your TEMP environment variables. To do this, follow these steps:
Disk Cleanup utility In Windows 2000, you can delete many unused files or temporary files by using the Disk Cleanup utility. The Disk Cleanup utility searches your disk and then shows you temporary files, Internet cache files, and unnecessary program files that you can safely delete. You can control the Disk Cleanup utility so that you delete only the files that you want to delete. To start the Disk Cleanup utility, click Start, point to Programs, point to Accessories, point to System Tools, and then click Disk Cleanup. Incompatible video driver or corrupted video driverYou may also notice page faults or unpredictable screen behavior in Access 2003 because of video-driver conflict or because of incorrect graphics hardware settings on your computer.To troubleshoot a video-driver conflict, change the video adapter for your system to Standard VGA. To do this, follow these steps:
Printer driver problem or printer settings problemWhen you try to print in the Access 2003 environment, you may receive a fatal system error or you may notice printing problems. If these problems occur, use the Generic/Text Only printer driver. To do this, follow these steps:
Incorrect virtual memory settingsYou may notice unexpected behavior in Access 2003 when the virtual memory setting is too low on your computer. The Windows 2000 operating system uses a dynamic virtual memory manager to handle paging file duties. You must use the default virtual memory settings whenever possible.However, if you suspect that the unexpected behavior in Access 2003 is caused by low virtual memory, you can manually change the virtual memory settings. If the maximum setting for virtual memory is already set, you may have to select a different disk or to remove files from the current disk to increase the disk space that is reserved for extra memory. To increase the disk space that is reserved for virtual memory on your computer, follow these steps:
Disk fragmentation or disk errorsIt is a good practice to occationally check for disk errors and disk fragmentation. To find and to correct these issues, run one of the following tools:The Disk Error-Checking tool The Disk Error-Checking tool looks for file system errors and for bad sectors on your disk. To run the Disk Error-Checking tool, follow these steps:
The Disk Defragmenter tool analyzes your disk to determine the level of fragmentation. The Disk Defragmenter tool can also defragment your disk. To use the Disk Defragmenter tool, follow these steps:
REFERENCES
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824271
(http://support.microsoft.com/kb/824271/
)
Troubleshooting corruption in an Office Access 2003 database
For more information about examining error messages in Windows
2000, click the following article numbers to view the articles in the Microsoft Knowledge Base:
256004
(http://support.microsoft.com/kb/256004/
)
How to troubleshoot "STOP 0x0000003F" and "STOP 0x000000D8" error messages in Windows Server 2003, Windows XP, and Windows 2000
228753
(http://support.microsoft.com/kb/228753/
)
Troubleshooting "Stop 0x00000077" or
"KERNEL_STACK_INPAGE_ERROR"
137539
(http://support.microsoft.com/kb/137539/
)
General causes of STOP 0x0000007F errors
| Article Translations
|
Back to the top
