BackupIoRequest::WaitForIoCompletion - Unable to find ryme or reason!

Event Type: Error
Event Source: MSSQLServer
Event Category: (6)
Event ID: 17055
Date: 8/11/2002
Time: 8:00:08 PM
User: xxxxxxxxxx
Computer: xxxxxxxxxx
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup
device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453
(Insufficient quota to complete the requested service.).

This is the event log view from a SQL7 No service pack server on a W2k server SP2.

The D: drive where the backup file is going has over 13GB free !

Has any one else had this error ? M$ have no information :(

Cheers

DaveRE:
read failure on backup device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453 (Insufficient quota to complete the requested service.).
This is the event log view from a SQL7 No service pack server on a W2k server SP2.
The D: drive where the backup file is going has over 13GB free !
Has any one else had this error ? M$ have no information

Q1 Has any one else had this error ?
A1 This looks like it may be a disk quota related error.

Q2 The D: drive where the backup file is going has over 13GB free!
A2 Fine, but if disk quotas are enabled, how much is available on the D:\ drive for the service account under which sql server is running?

S1 Are you able to complete any (small) backup dumps? (If not, some DB may have already grown to meet an existing quota limit.)

S2 Try deleteing all existing backup files and then attempt a (very small) backup dump, say for master.|||Hi,

No Quota's are enabled

The 'Job' ran successfully the following morning after the initial error.

This morning (Tuesday) the Job ran successfully.

I am thinking that the Quota reference is 'system resources' rather than disk quota.

I think that even though the source is MSSQLSERVICE i believe its a W2K issue.

OS W2K SP2
1x 1Ghz CPU
Memory 2GB
Hardware RAID
2x Database.
Cataloging 3,2xx,xxx records (manual incremental population)

I have read where people have Service Packed there OS to SP3 but this still doesnt fix [there] problem

Dave|||RE:
Hi, No Quota's are enabled
The 'Job' ran successfully the following morning after the initial error.
This morning (Tuesday) the Job ran successfully.
I am thinking that the Quota reference is 'system resources' rather than disk quota. I think that even though the source is MSSQLSERVICE i believe its a W2K issue.

OS W2K SP2
1x 1Ghz CPU
Memory 2GB
Hardware RAID
2x Database.
Cataloging 3,2xx,xxx records (manual incremental population)

I have read where people have Service Packed there OS to SP3 but this still doesnt fix [there] problem Dave

Q1 [No Quota's are enabled]
A1 That's too bad it would have been an easy fix.

Q2 [I am thinking that the Quota reference is 'system resources' rather than disk quota. I think that even though the source is MSSQLSERVICE i believe its a W2K issue.]
A2 Well yes, kind of (probably); the API likely ends up calling the same lower level drivers in any case.

S1 The issue may also be related to driver corruption, driver coding issues / bugs and / or authentication and / or ACL issues. If you happen to have also very recently updated any disk / array drivers, you might consider either attempting to refresh the driver update(s) and / or undoing them?
As far as I understood there (were / are in 99 / 00?) some issues having to do with "IO set completion" that had / have something to do with switches between different levels of kernel drivers that array controller drivers initiate (maybe related, maybe not?).
As to authentication, I've seen (and experienced) problems with some network domains wherein every now and then the (domain controller?) decides the Sql Server / service account doesn't have the neccessary rights to dump wherever (usually, but not always, also accompanied by logon failures in the event log), which causes similar issues.|||Event Type: Error
Event Source: MSSQLServer
Event Category: (6)
Event ID: 17055
Date: 8/11/2002
Time: 8:00:08 PM
User: xxxxxxxxxx
Computer: xxxxxxxxxx
Description:
18210 :
BackupIoRequest::WaitForIoCompletion: read failure on backup
device 'd:\mssql7\data\Debtors_Data.MDF'. Operating system error 1453
(Insufficient quota to complete the requested service.).

This is the event log view from a SQL7 No service pack server on a W2k server SP2.

The D: drive where the backup file is going has over 13GB free !

Has any one else had this error ? M$ have no information :(

Cheers

Dave

Q1 This is the event log view from a SQL7 No service pack server?
A1 I missed that detail previously. If I read that correctly why is that? You may want to check out MS Q274310 (or "Why you may consider applying Service Pack 3 for Microsoft SQL Server 7.0")?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;274310

Backup yielding Operatin System Error 33?

A little help please?
I have a 14.2 GB database that has stopped backing up and yields the
following errors in the Event log and SQL Server Log respectively:
Application Event Log
18210 :
BackupMedium::ReportIoError: write failure on backup device 'C:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
Operating system error 33(The process cannot access the file because another
process has locked a portion of the file.).
SQL Server Error Log:
Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
Is there any reasonable way to fix this?
Thanks in advance for your help.I've seen that message when trying to backup to a compressed volume.
If that's the case, this may help :-
http://support.microsoft.com/?id=231347
--
HTH. Ryan
"Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> Operating system error 33(The process cannot access the file because
> another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft
> SQL
> Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>|||Dave,
You can try to identify the process that has locked the file. It is
possible that a third party software like tape backup has acquired a read
lock on the file.
1) use "net file " command to see open files
"net file id /close " to close a open file
2) Use third party tools like filemon from sysinternals to do the same
You can also see if there are no active sql server processes or agent jobs
that may be accessing the file.
Another workaround is to rename the existing file and try the backup again
assuming that you are able to rename and there is space for additional backup.
"Dave Smith" wrote:
> A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> Operating system error 33(The process cannot access the file because another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>|||Way to go Ryan!!
That was exactly the problem. Out MSSQL\BACKUP folder was set to be
compressed.
FYI, the job does a DBCC CHECKDB, Full Backup, and Verify. It used to fail
after 38 to 44 minutes. it just succeeded in 18:03!!
YOU are the man!
Thanks a bunch,
Dave Smith
"Ryan" wrote:
> I've seen that message when trying to backup to a compressed volume.
> If that's the case, this may help :-
> http://support.microsoft.com/?id=231347
> --
> HTH. Ryan
>
> "Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
> news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
> >A little help please?
> >
> > I have a 14.2 GB database that has stopped backing up and yields the
> > following errors in the Event log and SQL Server Log respectively:
> >
> > Application Event Log
> > 18210 :
> > BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> > Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> > Operating system error 33(The process cannot access the file because
> > another
> > process has locked a portion of the file.).
> >
> > SQL Server Error Log:
> > Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> > 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> > Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> > m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft
> > SQL
> > Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> >
> > Is there any reasonable way to fix this?
> >
> > Thanks in advance for your help.
> >
> >
>
>

Backup yielding Operatin System Error 33?

A little help please?
I have a 14.2 GB database that has stopped backing up and yields the
following errors in the Event log and SQL Server Log respectively:
Application Event Log
18210 :
BackupMedium::ReportIoError: write failure on backup device 'C:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Ma
nual.bak'.
Operating system error 33(The process cannot access the file because another
process has locked a portion of the file.).
SQL Server Error Log:
Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\enDataWH_db_20060104
2204.BAK
Is there any reasonable way to fix this?
Thanks in advance for your help.I've seen that message when trying to backup to a compressed volume.
If that's the case, this may help :-
http://support.microsoft.com/?id=231347
HTH. Ryan
"Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Ma
nual.bak'.
> Operating system error 33(The process cannot access the file because
> another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft
> SQL
> Server\MSSQL\BACKUP\enDataWH_db_20060104
2204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>|||Dave,
You can try to identify the process that has locked the file. It is
possible that a third party software like tape backup has acquired a read
lock on the file.
1) use "net file " command to see open files
"net file id /close " to close a open file
2) Use third party tools like filemon from sysinternals to do the same
You can also see if there are no active sql server processes or agent jobs
that may be accessing the file.
Another workaround is to rename the existing file and try the backup again
assuming that you are able to rename and there is space for additional backu
p.
"Dave Smith" wrote:

> A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Ma
nual.bak'.
> Operating system error 33(The process cannot access the file because anoth
er
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQ
L
> Server\MSSQL\BACKUP\enDataWH_db_20060104
2204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>|||Way to go Ryan!!
That was exactly the problem. Out MSSQL\BACKUP folder was set to be
compressed.
FYI, the job does a DBCC CHECKDB, Full Backup, and Verify. It used to fail
after 38 to 44 minutes. it just succeeded in 18:03!!
YOU are the man!
Thanks a bunch,
Dave Smith
"Ryan" wrote:

> I've seen that message when trying to backup to a compressed volume.
> If that's the case, this may help :-
> http://support.microsoft.com/?id=231347
> --
> HTH. Ryan
>
> "Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
> news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>
>

Backup yielding Operatin System Error 33?

A little help please?
I have a 14.2 GB database that has stopped backing up and yields the
following errors in the Event log and SQL Server Log respectively:
Application Event Log
18210 :
BackupMedium::ReportIoError: write failure on backup device 'C:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
Operating system error 33(The process cannot access the file because another
process has locked a portion of the file.).
SQL Server Error Log:
Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
Is there any reasonable way to fix this?
Thanks in advance for your help.
I've seen that message when trying to backup to a compressed volume.
If that's the case, this may help :-
http://support.microsoft.com/?id=231347
HTH. Ryan
"Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> Operating system error 33(The process cannot access the file because
> another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft
> SQL
> Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>
|||Dave,
You can try to identify the process that has locked the file. It is
possible that a third party software like tape backup has acquired a read
lock on the file.
1) use "net file " command to see open files
"net file id /close " to close a open file
2) Use third party tools like filemon from sysinternals to do the same
You can also see if there are no active sql server processes or agent jobs
that may be accessing the file.
Another workaround is to rename the existing file and try the backup again
assuming that you are able to rename and there is space for additional backup.
"Dave Smith" wrote:

> A little help please?
> I have a 14.2 GB database that has stopped backing up and yields the
> following errors in the Event log and SQL Server Log respectively:
> Application Event Log
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device 'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\enDataWH_20060401_Manual.bak'.
> Operating system error 33(The process cannot access the file because another
> process has locked a portion of the file.).
> SQL Server Error Log:
> Internal I/O request 0x2775DCF8: Op: Write, pBuffer: 0x062E0000, Size:
> 983040, Position: 10592131584, UMS: Internal: 0x103, InternalHigh: 0x0,
> Offset: 0x77571A00, OffsetHigh: 0x2, m_buf: 0x062E0000, m_len: 983040,
> m_actualBytes: 0, m_errcode: 33, BackupFile: C:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\enDataWH_db_200601042204.BAK
> Is there any reasonable way to fix this?
> Thanks in advance for your help.
>
|||Way to go Ryan!!
That was exactly the problem. Out MSSQL\BACKUP folder was set to be
compressed.
FYI, the job does a DBCC CHECKDB, Full Backup, and Verify. It used to fail
after 38 to 44 minutes. it just succeeded in 18:03!!
YOU are the man!
Thanks a bunch,
Dave Smith
"Ryan" wrote:

> I've seen that message when trying to backup to a compressed volume.
> If that's the case, this may help :-
> http://support.microsoft.com/?id=231347
> --
> HTH. Ryan
>
> "Dave Smith" <DaveSmith@.discussions.microsoft.com> wrote in message
> news:255EB00C-6217-4471-BC1B-ECAC8E935F03@.microsoft.com...
>
>

Backup Transaction Log - Event ID 17055

I recently changed the recovery model from simple to full on a specific SQL
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts'?
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:
> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts'?
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.|||Yes, that has been completed.
"Hari Prasad" wrote:
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote:
> > I recently changed the recovery model from simple to full on a specific SQL
> > Server 2000 database. I am backing up the transaction log every two hours
> > via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> > full recovery model and do not receive these messages. The following error,
> > not a warning, appears in the application event log when the log backup
> > completes also in the database log. Are these backups valid? Found KB
> > 818202 on this, but I cannot determine what action needs to be taken, if any.
> > Thoughts'?
> >
> > Source: MSSQLSERVER
> > Category: (6)
> > Event ID: 17055
> > Description: 18278 Database log truncated: Database: dbname.|||It looks like someone is running a Backup LOG command with
NO_LOG or TRUNCATE_ONLY option. Investigate if anyone or
any job is scheduled to run this command. Also, check your
own backup log command to see if it includes this option.
Lll the Log backups after a truncate will be invalid till
you take a FULL backup.
>--Original Message--
>I recently changed the recovery model from simple to full
on a specific SQL
>Server 2000 database. I am backing up the transaction
log every two hours
>via a maintenance plan. I have other SQL Server 2000 DB's
defined with the
>full recovery model and do not receive these messages.
The following error,
>not a warning, appears in the application event log when
the log backup
>completes also in the database log. Are these backups
valid? Found KB
>818202 on this, but I cannot determine what action needs
to be taken, if any.
> Thoughts'?
>Source: MSSQLSERVER
>Category: (6)
>Event ID: 17055
>Description: 18278 Database log truncated: Database:
dbname.
>.
>

Backup Transaction Log - Event ID 17055

I recently changed the recovery model from simple to full on a specific SQL
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts??
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.
Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:

> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts??
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.
|||Yes, that has been completed.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote: