Event ID 851 in SQL2005 - what to do?

Hi,
when trying to shrink a transaction log file in SQL2005 we receive every few
minutes (for 4 hours now) the following Information in the event logs and the
shrink does not complete.
Type: Information
ID: 851
Source: MSSQLSERVER
Text (English translation follows): Das Betriebssystem hat den Fehler
1450(Nicht genügend Systemressourcen, um den angeforderten Dienst
auszuführen.) an SQL Server zurückgegeben. Dieser Fehler ist bei einem
Schreiben am Offset 0x000007c3ca3e00 in der Datei mit dem Handle 0x000008E4
aufgetreten. üblicherweise ist dies ein tempor?rer Zustand, und der Server
mit SQL Server versucht immer wieder, diesen Vorgang zu wiederholen. Wenn der
Zustand weiterhin besteht, muss sofort etwas unternommen werden, um das
Problem zu beheben.
In English (free translation): The operating System returned Error 1450 (not
enough system resources for executing the service) to the SQL server during
write at offset ... in file with handle ...This is mostly temporary and SQL
server tries again to repeat the operation. If this error continues to happen
you have to take actions immediately to resolve the problem.
The executed query is:
BACKUP LOG accountings TO
DISK='e:\mssql\BACKUP\accountings\transakt_2007052 10928.bak'
DBCC SHRINKFILE ('accountings_Protokoll',5120) WITH NO_INFOMSGS
go
Any ideas what action to take?
Regards
--Stefan
Hi Stefan
"Stefan Funk" wrote:

> Hi,
> when trying to shrink a transaction log file in SQL2005 we receive every few
> minutes (for 4 hours now) the following Information in the event logs and the
> shrink does not complete.
> --
> Type: Information
> ID: 851
> Source: MSSQLSERVER
> Text (English translation follows): Das Betriebssystem hat den Fehler
> 1450(Nicht genügend Systemressourcen, um den angeforderten Dienst
> auszuführen.) an SQL Server zurückgegeben. Dieser Fehler ist bei einem
> Schreiben am Offset 0x000007c3ca3e00 in der Datei mit dem Handle 0x000008E4
> aufgetreten. üblicherweise ist dies ein tempor?rer Zustand, und der Server
> mit SQL Server versucht immer wieder, diesen Vorgang zu wiederholen. Wenn der
> Zustand weiterhin besteht, muss sofort etwas unternommen werden, um das
> Problem zu beheben.
> --
> In English (free translation): The operating System returned Error 1450 (not
> enough system resources for executing the service) to the SQL server during
> write at offset ... in file with handle ...This is mostly temporary and SQL
> server tries again to repeat the operation. If this error continues to happen
> you have to take actions immediately to resolve the problem.
> --
> The executed query is:
> BACKUP LOG accountings TO
> DISK='e:\mssql\BACKUP\accountings\transakt_2007052 10928.bak'
> DBCC SHRINKFILE ('accountings_Protokoll',5120) WITH NO_INFOMSGS
> go
> Any ideas what action to take?
> Regards
> --Stefan
Have you looked at the what is in the SQL Server Error log? Can you backup
the database and then shrink the file manually as two separate batches?
John
|||"John Bell" wrote:
> Hi Stefan
> Have you looked at the what is in the SQL Server Error log? Can you backup
> the database and then shrink the file manually as two separate batches?
> John
Hi John,
the backup did not succeed but stalled at some 8MB with running endlessly
and not consuming disk space. I put the database in single user mode, run
"backup log with truncate_only", then shrinked the log file, finally
performed a full backup of course.
The database is running again now. But the eventlog entries are still not
clear to me...
Thanks anyway
--Stefan
|||Hi Stefan
"Stefan Funk" wrote:

> "John Bell" wrote:
> Hi John,
> the backup did not succeed but stalled at some 8MB with running endlessly
> and not consuming disk space. I put the database in single user mode, run
> "backup log with truncate_only", then shrinked the log file, finally
> performed a full backup of course.
> The database is running again now. But the eventlog entries are still not
> clear to me...
> Thanks anyway
> --Stefan
Have you checked that you haven't run out of resources such as memory?
Although nothing seems to relate to SQL 2005 there are some articles on this
error see http://tinyurl.com/yuwak5
Failing that you may want to call PSS if it happens again.
John