Knowledge Base |

# ACC: Network Problems May Cause "Segment Load Failure" Error, "System Process - Lost Delayed Write Error" Error or "Invalid Bookmark" Error

Article ID: 109730

Article Last Modified on 1/18/2007

APPLIES TO

- Microsoft Access 1.0 Standard Edition
- Microsoft Access 1.1 Standard Edition
- Microsoft Access 2.0 Standard Edition
- Microsoft Access 95 Standard Edition
- Microsoft Access 97 Standard Edition

This article was previously published under Q109730
Moderate: Requires basic macro, coding, and interoperability skills.

## SYMPTOMS

You receive a "Segment Load Failure" error message or another memory- conflict error message.
In Microsoft Access 97, you may also receive a "System Process - Lost Delayed Write Error" or an Invalid Bookmark Error message when viewing data from linked tables.

## CAUSE

A "Segment Load Failure" error message can occur if Microsoft Access is running on a network or is accessing data on a network, and the network server stops functioning correctly.
A segment load failure implies that there was a problem moving information from secondary storage, such as a network server disk, to main memory. If a network server stops functioning correctly, expected information may not be available to Microsoft Access.
A "System Process - Lost Delayed Write Error" error message implies that Microsoft Access had a problem writing data from its buffers to secondary storage. This can occur if the connection to a Network share stops functioning correctly. An "Invalid bookmark" error message will also occur numerous times for each field on each record in the current table or query that you are viewing if the share on which your data is stored becomes unavailable.

## RESOLUTION

The following suggestions may help you to diagnose the problem:

- Make a backup of all critical data and run disk diagnostic software, such as the MS-DOS CHKDSK command, to check the integrity of the workstation and server disk drives.
- If the workstation has a complete Microsoft Access installation, quit and then restart Microsoft Access on the workstation, and see if it operates correctly without using the network for any services. If the problem continues with Microsoft Access operating in isolation, begin checking the workstation for memory conflicts.
- If the database is being accessed off a network server, consider copying it to the local workstation to isolate whether the problem is workstation or server specific.
- If the server is required, just start the server and the Microsoft Access workstation to test Microsoft Access. If the problem does not occur at this point, you can start and diagnose other workstations one by one.

Keywords: kberrmsg kbprb KB109730