SQL Server Transaction Log Full When Importing an Object Package (310735)
The information in this article applies to:
- Microsoft Content Management Server 2001
- NCompass Resolution 4.0
This article was previously published under Q310735 SYMPTOMS
When you import an object package (.rop file) from Content Management Server (CMS) 2001 Site Deployment Manager, 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
When you click Details, you may see the following:
Error: 4005
Description: Offending SQL: { call LockForWrite } ;The log file for database 'DATABASENAME' is full. Back up the transaction log for the database to free up some log space.
Severity: 5
Source: (ISOK File P:\NR\Server\NRSiteDeployServer\Stub\NRSiteDeployStub.cpp, Line 166) -1
Debug info:
Extra info:
Client Source: CImProgress::ProcessPackage
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.
Import of MSCMS Object Package .... Failed
The Microsoft SQL Server error log indicates that the log file for the database is full.
CAUSE
The transaction log for SQL Server is full.
RESOLUTION
To resolve this issue, back up the database or the transaction log to free transaction log space.
WORKAROUND
To work around this problem, set the Automatically grow file property in SQL Server so that the transaction log can expand as necessary. You can either govern the amount of growth or allow the transaction log to use all available disk space.
MORE INFORMATION
The CMS 2001 Site Deployment Manager allows for incremental updates to CMS 2001 systems by using an Export and Import transfer method.
REFERENCES
For more information, see the "Backup" topic in the SQL Server Books Online.
For more information on how to import an object package in CMS 2001, see the "Importing an Object Package" topic in the CMS 2001 online Help.
For additional information on why the SQL transaction logs may fill up, click the article number below
to view the article in the Microsoft Knowledge Base:
110139 INF: Causes of SQL Transaction Log Filling Up
| Modification Type: | Major | Last Reviewed: | 10/9/2003 |
|---|
| Keywords: | kbinfo KB310735 |
|---|
|