SQL Server Transaction Log Full When You Purge Revisions from Site Builder (311082)

SYMPTOMS

When you purge revisions in Content Management Server (CMS) 2001 from the Site Builder application, you may receive the following error message:

Microsoft Content Management Server
An unexpected error has occurred.
Please record and report details to the appropriate administrator

If you click Details for more information on the error, you may see the following:

Error: 4005
Description: The XML parser could not parse the tag it was given.
Severity: 5
Source: P:\NR\Shared\GrammarParserC\AEGrammarParser.cpp 313
Debug info: Extended error: [What='Offending SQL: {? = call PurgeRevisionsByDate(?)}; {call UpdateChangeTable };The log file for database 'DATABASENAME' is full. Back up the transaction log for the database to free up some log space. '] [LCID='1024'] [SourceFile=''] [SourceFileLine='-1'] [DebugInfo='
Extra info:
Client Source: AETree::evhAETree_OnEvent:Menu\ToolsPurgeRevisions
Recommended Action: The ODBC data source may be incorrectly configured, the database may not be running, or there may be incorrect data in the database.

The Microsoft SQL Server error log indicates that the log file for the database is full. The following is logged in the SQL Server error log file:

The log file for database databasename is full. Back up the transaction log for the database to free up some log space.

WORKAROUND

To work around this problem, set the Automatically grow file property in SQL Server. This property provides the transaction log with the capability to expand as needed. You can govern the amount of growth, or set it to to use all available disk space.

MORE INFORMATION

Within the Site Builder, administrators can permanently delete all object revisions that were archived before a specific time. All revisions in the site that are older than the specified date and time are purged. To purge revisions, follow these steps:

On the Tools menu, select Purge Revisions. The Purge Revision dialog box appears.
Using the drop-down lists on the calendar, select the month, date, and time that correspond to the revisions that you want to purge.
Click Purge. A confirmation message appears.
Click Yes. All revisions before the date that you specified are purged.

REFERENCES

For additional information on why the SQL Server transaction logs become full, click the article number below to view the article in the Microsoft Knowledge Base:

110139 INF: Causes of SQL Transaction Log Filling Up

For more information, see the following Knowledge Base article:

310735 SQL Server Transaction Log Full When Importing an Object Package

For more information, see the "Page versioning" topic in the Content Management Server 2001 Help.

For more information, see the "Backup" topic in the SQL Server Books Online.