Share via


Event ID 6457 (Windows SharePoint Services health model)

Applies To: Windows SharePoint Services 3.0

 

Warning

The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

Event Details

Product:

Windows SharePoint Services

ID:

6457

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_6457

Message:

Not enough free disk space available. The tracing service has temporary stopped outputting trace messages to the log file. Tracing will resume when more than %1 MB of disk space becomes available.

Resolve

Free up disk space or relocate the trace log

Windows SharePoint Services 3.0 could not write to the trace log. This trace log contains information that is useful in troubleshooting issues.

Free up drive space

You can free up space on the drive containing the trace log by removing unneeded files. To perform this procedure, you must be a member of the Administrators group on the local computer.

Relocate the log file

You can change the location of the trace log to a partition that has more drive space.

To change the location of the trace log file

  1. In Central Administration, on the left navigation pane, click Operations.

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, type the new location for the trace log file in the Path box.

  4. Click OK.

Verify

Ensure that Windows SharePoint Services 3.0 can create, and write to, the trace log file.

To check if Windows SharePoint Services 3.0 can create, and write to, the trace log file

  1. In the SharePoint Central Administration Web site, on the left navigation pane, click Operations.

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, copy the path to the trace log file from the Path box.

  4. In Windows Explorer, navigate to the trace log file by using the copied path and open the file in Notepad, or another text editor.

    You should see log entries in the log file for events after the time that logging failed.

Diagnostic system (Health model)

Windows SharePoint Services 3.0 health model