Backup File I/o Error

Guys,

Apologies if this is in the wrong section. I have a SQL 2000 database which I backup to a folder on the hard disk using the following command in a Server Agent:

BACKUP DATABASE [Multilog] TO DISK = N'C:\MSSQL7\BACKUP\multilog_backup' WITH INIT , NOUNLOAD , NAME = N'Multilog backup', NOSKIP , STATS = 10, NOFORMAT

Recently it has been failing with the following error message:

Nonrecoverable I/O error occurred on file 'C:\Multilog Database Files\Data\MultiLog_data.MDF'. [SQLSTATE 42000] (Error 3271) Backup or restore operation terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

Any idea what could be causing this?

Any help would be greatly appreciated.

Sean.

Try some of the method(s) in the following kb:

http://support.microsoft.com/default.aspx/kb/904804

Is this an SP4 server? Looks like it may have been upgraded from SQL 7.0, is that correct?

|||

Chad,

Just noticed the following error on the logs:

I/O error 23(Data error (cyclic redundancy check).) detected during read of BUF pointer = 0x14243d80, page ptr = 0x1607c000, pageid = (0x1:0x1ae), dbid = 5, status = 0x801, file = C:\Multilog Database Files\Data\MultiLog_data.MDF..

Would this indicate a fault with the actual database file? Any idea what could be done to check and fix?

|||

Yeah, that would indicate a data integrity issue within your DB file. Try running a DBCC CHECKDB on the database in question and see what you get for output. Depending on the output of that, you could try using the FIX options with the CHECKDB command, rebuilding indexes, etc.

Backup failure Error Log Messages

I have not been able to find any details about backup failures for
MSSQL 2000. I am researching the following:
1. when a backup fails at a certain point during the process does the
backup:
A. stop there having recorded some details?
B. quit without backing up any of the data it already processed?
C. skip the data it cannot read and move on?
2. Does the error log record any of the details above? For instance, if
there is a table that the backup could not write to .bak, does the
error log report exactly where the error was?

I need a way to obtain a Backup Exception 'Report' that when a backup
fails it can tell me what did not get into the .bak file. I would
prefer automatic notification. Our Oracle DBs have something setup
that can be run when a piece of the DB does not get backed up letting
the Oracle DBA know where there are issues.

Thank you,
StephanieHi
1. B
2. If it is a write failure, yes it will be in the SQL Log. If it is data
corruption, it is in the SQL Log.

For a backup to fail, due to internal SQL Server problems is very very rare,
and I have not seen it on a clean database before.

Most failures are caused by running out of disk space or anti virus messing
around on the file when SQL is trying to write to it.

Regards
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Stephanie" <stuttle@.centene.com> wrote in message
news:1123710578.824686.208370@.g47g2000cwa.googlegr oups.com...
>I have not been able to find any details about backup failures for
> MSSQL 2000. I am researching the following:
> 1. when a backup fails at a certain point during the process does the
> backup:
> A. stop there having recorded some details?
> B. quit without backing up any of the data it already processed?
> C. skip the data it cannot read and move on?
> 2. Does the error log record any of the details above? For instance, if
> there is a table that the backup could not write to .bak, does the
> error log report exactly where the error was?
> I need a way to obtain a Backup Exception 'Report' that when a backup
> fails it can tell me what did not get into the .bak file. I would
> prefer automatic notification. Our Oracle DBs have something setup
> that can be run when a piece of the DB does not get backed up letting
> the Oracle DBA know where there are issues.
> Thank you,
> Stephanie

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\DatabaseName. bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK =
\\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Server
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
Michael
Michael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer available.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k'. Operating system error
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\DatabaseName. bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK =
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Server
> Agent account which has full access permission to the backup network drive.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michael

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.
).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\Dat
abaseName.bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK =
\\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Serve
r
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
MichaelMichael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3
-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer availabl
e.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak'. Operating system err
or
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\Dat
abaseName.bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK =
> \\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Ser
ver
> Agent account which has full access permission to the backup network drive
.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michael

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK = \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Server
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
MichaelMichael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer available.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system error
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK => \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Server
> Agent account which has full access permission to the backup network drive.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michaelsql

Backup failure

All,
I am receiving the following error when I try to backup to tape from SQL using backup under the Management folder in Enterprise manager. Logged in as administrator. Can backup the pubs, Northwind and master databases with no problem.
The database is approx. 8.5GB and the tape can hold 40GB formatted. Using option to overwrite and initialize.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log for more details, backup database is terminating abnormally.
In the error log;
Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size: 65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000, offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536, m_actualbytes: 65536, m_errcode: 1117, b
ackupfile: \\.\Tape0
Any thought would be appreciated.
Regards,
Dave
can you back it up to disk instead of to tape?
can you backup a large file from disk to tape?
I will do it this way because backup done faster and eliminating the hassle
of dealing with the tape drive.
my 0.02
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:C1CCFEFC-AD93-4715-919F-C468273BD974@.microsoft.com...
> All,
> I am receiving the following error when I try to backup to tape from SQL
using backup under the Management folder in Enterprise manager. Logged in as
administrator. Can backup the pubs, Northwind and master databases with no
problem.
> The database is approx. 8.5GB and the tape can hold 40GB formatted. Using
option to overwrite and initialize.
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log
for more details, backup database is terminating abnormally.
> In the error log;
> Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size:
65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000,
offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536,
m_actualbytes: 65536, m_errcode: 1117, backupfile: \\.\Tape0
> Any thought would be appreciated.
> Regards,
> Dave

Backup failure

All,
I am receiving the following error when I try to backup to tape from SQL usi
ng backup under the Management folder in Enterprise manager. Logged in as ad
ministrator. Can backup the pubs, Northwind and master databases with no pro
blem.
The database is approx. 8.5GB and the tape can hold 40GB formatted. Using op
tion to overwrite and initialize.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log for
more details, backup database is terminating abnormally.
In the error log;
Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size: 65536,
position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000, offse
t: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536, m_actualbytes
: 65536, m_errcode: 1117, b
ackupfile: \\.\Tape0
Any thought would be appreciated.
Regards,
Davecan you back it up to disk instead of to tape?
can you backup a large file from disk to tape?
I will do it this way because backup done faster and eliminating the hassle
of dealing with the tape drive.
my 0.02
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:C1CCFEFC-AD93-4715-919F-C468273BD974@.microsoft.com...
> All,
> I am receiving the following error when I try to backup to tape from SQL
using backup under the Management folder in Enterprise manager. Logged in as
administrator. Can backup the pubs, Northwind and master databases with no
problem.
> The database is approx. 8.5GB and the tape can hold 40GB formatted. Using
option to overwrite and initialize.
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log
for more details, backup database is terminating abnormally.
> In the error log;
> Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size:
65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000,
offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536,
m_actualbytes: 65536, m_errcode: 1117, backupfile: \\.\Tape0
> Any thought would be appreciated.
> Regards,
> Davesql

Backup Failure

I've encountered an error while performing a database backup. I can't seem t
o
find this error anywhere:
BACKUP failed to complete the command master.dbo.sp_sqlexec;1
Does anyone have any insight into this error?
Thank You!How do you execute the backup? For troubleshooting purposes, try executing a
BACKUP command from
Query analyzer.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:6DCC9B4B-4EE8-428A-842B-7E191FFE5AB6@.microsoft.com...
> I've encountered an error while performing a database backup. I can't seem
to
> find this error anywhere:
> BACKUP failed to complete the command master.dbo.sp_sqlexec;1
> Does anyone have any insight into this error?
> Thank You!|||The backup is executed as a scheduled job. This job has been running for
months without any issues - then suddenly...
When run manually, works just fine...
"Tibor Karaszi" wrote:

> How do you execute the backup? For troubleshooting purposes, try executing
a BACKUP command from
> Query analyzer.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:6DCC9B4B-4EE8-428A-842B-7E191FFE5AB6@.microsoft.com...
>|||Is it a TSQL job? How many jobsteps does the job contain? Where did you get
the error message from?
The job output of a job step in the job?
If you are uncertain, define a different output file for each jobstep and se
e exactly which jobstep
this message is from. Then post the TSQL commands you have in that jobstep.
I'm asking because the
error you posted doesn't look like an error that the BACKUP command would pr
oduce.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:D2BB3DBC-BFC5-4581-877B-6BE65F7E0E23@.microsoft.com...
> The backup is executed as a scheduled job. This job has been running for
> months without any issues - then suddenly...
> When run manually, works just fine...
> "Tibor Karaszi" wrote:
>

backup failure

Hi
My DB backup and transaction backup of a database keep on failing with
the following error:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on
'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Any idea what it really means ?
Thanks
DavidYou can get the description of Win32 error codes with NET HELPMSG from a
command prompt:

NET HELPMSG 112

Yields:

There is not enough space on the disk.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"David Greenberg" <davidgr@.iba.org.il> wrote in message
news:444B9239.2010804@.iba.org.il...
> Hi
> My DB backup and transaction backup of a database keep on failing with the
> following error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Write on
> 'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
> SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> Any idea what it really means ?
> Thanks
> David

Backup fails: "A nonrecoverable I/O error occurred on file"

We have been having a problem with one of our backups:
A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
It's on the same external storage drive as all of our databases yet it's the
only one that errors out, so it appears that the problem is with the .mdf
file, not with the hard disk. And it only errors intermittently...sometimes
the backup succeeds.
We have:
Run dbcc checkdb and receive no errors.
Dropped the database and restored from backup thinking the .mdf file would
be recreated.
We're not sure what to try next. Again, it doesn't seem like a hardware
problem but I can't rule it out either. Please advise.
"nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
> We have been having a problem with one of our backups:
> A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft
> SQL
> Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
> It's on the same external storage drive as all of our databases yet it's
> the
> only one that errors out, so it appears that the problem is with the .mdf
> file, not with the hard disk. And it only errors
> intermittently...sometimes
> the backup succeeds.
> We have:
> Run dbcc checkdb and receive no errors.
> Dropped the database and restored from backup thinking the .mdf file would
> be recreated.
> We're not sure what to try next. Again, it doesn't seem like a hardware
> problem but I can't rule it out either. Please advise.
Is this a SAN drive per chance? Or any special SCSI drive that may be doing
something while you do a backup?
Otherwise you may need to open a ticket with MS.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hello,
Since the issue only occurs iwht one mdf file, it might be a corruption
issue. Since the issue also occurs with a restore from backup, you may try
the following steps to troubleshoot the issue:
1. Create a new, blank database with whatever name and filename you want
(we may rename it later)
2. Generate the scripts of all tables and create them in the new database;
3. Transfer all data into the new database;
4. Check if the issue occurs with the new database
If the issue does not occur any more, you may want to detach the old
database, and rename the new database to the original name to test.
If the issue persists, you may want to use hardware check tool to confirm
there is no hardware related issue.
To find out the root cause of this issue we may need to analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. I recommend that you open a Support incident with
Microsoft Product Support Services so that a dedicated Support Professional
can assist with this case. If you need any help in this regard, please let
me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
If you have any concerns or comments on this, please feel free to let's
know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Yes this a SAN drive at a remote datacenter. The backup runs in the middle
of the night so I don't think the SAN has any heavy lifting going on at the
time the backup runs. We're going to continue to investigate and open a
ticket with MS if appropriate.
"Greg D. Moore (Strider)" wrote:

>
>
> "nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
> news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
> Is this a SAN drive per chance? Or any special SCSI drive that may be doing
> something while you do a backup?
> Otherwise you may need to open a ticket with MS.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>
|||We're going to continue to investigate and open a ticket with MS if
appropriate. Thanks for the response...I'll let you know if I have further
questions.
"Peter Yang [MSFT]" wrote:

> Hello,
> Since the issue only occurs iwht one mdf file, it might be a corruption
> issue. Since the issue also occurs with a restore from backup, you may try
> the following steps to troubleshoot the issue:
> 1. Create a new, blank database with whatever name and filename you want
> (we may rename it later)
> 2. Generate the scripts of all tables and create them in the new database;
> 3. Transfer all data into the new database;
> 4. Check if the issue occurs with the new database
> If the issue does not occur any more, you may want to detach the old
> database, and rename the new database to the original name to test.
> If the issue persists, you may want to use hardware check tool to confirm
> there is no hardware related issue.
> To find out the root cause of this issue we may need to analyze memory
> dumps, this work has to be done by contacting Microsoft Product Support
> Services. Therefore, we probably will not be able to resolve the issue
> through the newsgroups. I recommend that you open a Support incident with
> Microsoft Product Support Services so that a dedicated Support Professional
> can assist with this case. If you need any help in this regard, please let
> me know.
> For a complete list of Microsoft Product Support Services phone numbers,
> please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> If you have any concerns or comments on this, please feel free to let's
> know. Thank you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||"nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
news:B86FFC11-4C68-462B-88B5-3C9B640369DF@.microsoft.com...
> Yes this a SAN drive at a remote datacenter. The backup runs in the
> middle
> of the night so I don't think the SAN has any heavy lifting going on at
> the
> time the backup runs. We're going to continue to investigate and open a
> ticket with MS if appropriate.
Was thinking more perhaps the SAN drive might be doing something like
breaking a mirror during that time to do a backup and then recreating the
mirror or some other function and not properly quiescing the database.
[vbcol=seagreen]
> "Greg D. Moore (Strider)" wrote:
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Backup fails: "A nonrecoverable I/O error occurred on file"

We have been having a problem with one of our backups:
A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
It's on the same external storage drive as all of our databases yet it's the
only one that errors out, so it appears that the problem is with the .mdf
file, not with the hard disk. And it only errors intermittently...sometimes
the backup succeeds.
We have:
Run dbcc checkdb and receive no errors.
Dropped the database and restored from backup thinking the .mdf file would
be recreated.
We're not sure what to try next. Again, it doesn't seem like a hardware
problem but I can't rule it out either. Please advise."nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
> We have been having a problem with one of our backups:
> A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft
> SQL
> Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
> It's on the same external storage drive as all of our databases yet it's
> the
> only one that errors out, so it appears that the problem is with the .mdf
> file, not with the hard disk. And it only errors
> intermittently...sometimes
> the backup succeeds.
> We have:
> Run dbcc checkdb and receive no errors.
> Dropped the database and restored from backup thinking the .mdf file would
> be recreated.
> We're not sure what to try next. Again, it doesn't seem like a hardware
> problem but I can't rule it out either. Please advise.
Is this a SAN drive per chance? Or any special SCSI drive that may be doing
something while you do a backup?
Otherwise you may need to open a ticket with MS.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hello,
Since the issue only occurs iwht one mdf file, it might be a corruption
issue. Since the issue also occurs with a restore from backup, you may try
the following steps to troubleshoot the issue:
1. Create a new, blank database with whatever name and filename you want
(we may rename it later)
2. Generate the scripts of all tables and create them in the new database;
3. Transfer all data into the new database;
4. Check if the issue occurs with the new database
If the issue does not occur any more, you may want to detach the old
database, and rename the new database to the original name to test.
If the issue persists, you may want to use hardware check tool to confirm
there is no hardware related issue.
To find out the root cause of this issue we may need to analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. I recommend that you open a Support incident with
Microsoft Product Support Services so that a dedicated Support Professional
can assist with this case. If you need any help in this regard, please let
me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
If you have any concerns or comments on this, please feel free to let's
know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yes this a SAN drive at a remote datacenter. The backup runs in the middle
of the night so I don't think the SAN has any heavy lifting going on at the
time the backup runs. We're going to continue to investigate and open a
ticket with MS if appropriate.
"Greg D. Moore (Strider)" wrote:

>
>
> "nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
> news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
> Is this a SAN drive per chance? Or any special SCSI drive that may be doi
ng
> something while you do a backup?
> Otherwise you may need to open a ticket with MS.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com [url]http://www.greenms.com/sqlserver.html[/ur
l]
>
>|||We're going to continue to investigate and open a ticket with MS if
appropriate. Thanks for the response...I'll let you know if I have further
questions.
"Peter Yang [MSFT]" wrote:

> Hello,
> Since the issue only occurs iwht one mdf file, it might be a corruption
> issue. Since the issue also occurs with a restore from backup, you may try
> the following steps to troubleshoot the issue:
> 1. Create a new, blank database with whatever name and filename you want
> (we may rename it later)
> 2. Generate the scripts of all tables and create them in the new database;
> 3. Transfer all data into the new database;
> 4. Check if the issue occurs with the new database
> If the issue does not occur any more, you may want to detach the old
> database, and rename the new database to the original name to test.
> If the issue persists, you may want to use hardware check tool to confirm
> there is no hardware related issue.
> To find out the root cause of this issue we may need to analyze memory
> dumps, this work has to be done by contacting Microsoft Product Support
> Services. Therefore, we probably will not be able to resolve the issue
> through the newsgroups. I recommend that you open a Support incident with
> Microsoft Product Support Services so that a dedicated Support Professiona
l
> can assist with this case. If you need any help in this regard, please let
> me know.
> For a complete list of Microsoft Product Support Services phone numbers,
> please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> If you have any concerns or comments on this, please feel free to let's
> know. Thank you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ========================================
==========
> Get notification to my posts through email? Please refer to
> l]
> ications
> <[url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx" target="_blank">http://msdn.microsoft.com/subscript...ps/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscript...rt/default.aspx>.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||"nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
news:B86FFC11-4C68-462B-88B5-3C9B640369DF@.microsoft.com...
> Yes this a SAN drive at a remote datacenter. The backup runs in the
> middle
> of the night so I don't think the SAN has any heavy lifting going on at
> the
> time the backup runs. We're going to continue to investigate and open a
> ticket with MS if appropriate.
Was thinking more perhaps the SAN drive might be doing something like
breaking a mirror during that time to do a backup and then recreating the
mirror or some other function and not properly quiescing the database.
[vbcol=seagreen]
> "Greg D. Moore (Strider)" wrote:
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Backup fails: "A nonrecoverable I/O error occurred on file"

We have been having a problem with one of our backups:
A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
It's on the same external storage drive as all of our databases yet it's the
only one that errors out, so it appears that the problem is with the .mdf
file, not with the hard disk. And it only errors intermittently...sometimes
the backup succeeds.
We have:
Run dbcc checkdb and receive no errors.
Dropped the database and restored from backup thinking the .mdf file would
be recreated.
We're not sure what to try next. Again, it doesn't seem like a hardware
problem but I can't rule it out either. Please advise."nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
> We have been having a problem with one of our backups:
> A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft
> SQL
> Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
> It's on the same external storage drive as all of our databases yet it's
> the
> only one that errors out, so it appears that the problem is with the .mdf
> file, not with the hard disk. And it only errors
> intermittently...sometimes
> the backup succeeds.
> We have:
> Run dbcc checkdb and receive no errors.
> Dropped the database and restored from backup thinking the .mdf file would
> be recreated.
> We're not sure what to try next. Again, it doesn't seem like a hardware
> problem but I can't rule it out either. Please advise.
Is this a SAN drive per chance? Or any special SCSI drive that may be doing
something while you do a backup?
Otherwise you may need to open a ticket with MS.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hello,
Since the issue only occurs iwht one mdf file, it might be a corruption
issue. Since the issue also occurs with a restore from backup, you may try
the following steps to troubleshoot the issue:
1. Create a new, blank database with whatever name and filename you want
(we may rename it later)
2. Generate the scripts of all tables and create them in the new database;
3. Transfer all data into the new database;
4. Check if the issue occurs with the new database
If the issue does not occur any more, you may want to detach the old
database, and rename the new database to the original name to test.
If the issue persists, you may want to use hardware check tool to confirm
there is no hardware related issue.
To find out the root cause of this issue we may need to analyze memory
dumps, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. I recommend that you open a Support incident with
Microsoft Product Support Services so that a dedicated Support Professional
can assist with this case. If you need any help in this regard, please let
me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
If you have any concerns or comments on this, please feel free to let's
know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Yes this a SAN drive at a remote datacenter. The backup runs in the middle
of the night so I don't think the SAN has any heavy lifting going on at the
time the backup runs. We're going to continue to investigate and open a
ticket with MS if appropriate.
"Greg D. Moore (Strider)" wrote:
>
>
> "nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
> news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
> > We have been having a problem with one of our backups:
> >
> > A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft
> > SQL
> > Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
> >
> > It's on the same external storage drive as all of our databases yet it's
> > the
> > only one that errors out, so it appears that the problem is with the .mdf
> > file, not with the hard disk. And it only errors
> > intermittently...sometimes
> > the backup succeeds.
> >
> > We have:
> >
> > Run dbcc checkdb and receive no errors.
> > Dropped the database and restored from backup thinking the .mdf file would
> > be recreated.
> >
> > We're not sure what to try next. Again, it doesn't seem like a hardware
> > problem but I can't rule it out either. Please advise.
> Is this a SAN drive per chance? Or any special SCSI drive that may be doing
> something while you do a backup?
> Otherwise you may need to open a ticket with MS.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>
>|||We're going to continue to investigate and open a ticket with MS if
appropriate. Thanks for the response...I'll let you know if I have further
questions.
"Peter Yang [MSFT]" wrote:
> Hello,
> Since the issue only occurs iwht one mdf file, it might be a corruption
> issue. Since the issue also occurs with a restore from backup, you may try
> the following steps to troubleshoot the issue:
> 1. Create a new, blank database with whatever name and filename you want
> (we may rename it later)
> 2. Generate the scripts of all tables and create them in the new database;
> 3. Transfer all data into the new database;
> 4. Check if the issue occurs with the new database
> If the issue does not occur any more, you may want to detach the old
> database, and rename the new database to the original name to test.
> If the issue persists, you may want to use hardware check tool to confirm
> there is no hardware related issue.
> To find out the root cause of this issue we may need to analyze memory
> dumps, this work has to be done by contacting Microsoft Product Support
> Services. Therefore, we probably will not be able to resolve the issue
> through the newsgroups. I recommend that you open a Support incident with
> Microsoft Product Support Services so that a dedicated Support Professional
> can assist with this case. If you need any help in this regard, please let
> me know.
> For a complete list of Microsoft Product Support Services phone numbers,
> please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> If you have any concerns or comments on this, please feel free to let's
> know. Thank you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||"nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
news:B86FFC11-4C68-462B-88B5-3C9B640369DF@.microsoft.com...
> Yes this a SAN drive at a remote datacenter. The backup runs in the
> middle
> of the night so I don't think the SAN has any heavy lifting going on at
> the
> time the backup runs. We're going to continue to investigate and open a
> ticket with MS if appropriate.
Was thinking more perhaps the SAN drive might be doing something like
breaking a mirror during that time to do a backup and then recreating the
mirror or some other function and not properly quiescing the database.
> "Greg D. Moore (Strider)" wrote:
>>
>>
>> "nexdeveloper" <nexdeveloper@.community.nospam> wrote in message
>> news:E0948BFC-C002-4EBF-9E00-B0EAF6A8E850@.microsoft.com...
>> > We have been having a problem with one of our backups:
>> >
>> > A nonrecoverable I/O error occurred on file "D:\Program Files\Microsoft
>> > SQL
>> > Server\MSSQL.1\MSSQL\Data\SOMEDB_Data.mdf"
>> >
>> > It's on the same external storage drive as all of our databases yet
>> > it's
>> > the
>> > only one that errors out, so it appears that the problem is with the
>> > .mdf
>> > file, not with the hard disk. And it only errors
>> > intermittently...sometimes
>> > the backup succeeds.
>> >
>> > We have:
>> >
>> > Run dbcc checkdb and receive no errors.
>> > Dropped the database and restored from backup thinking the .mdf file
>> > would
>> > be recreated.
>> >
>> > We're not sure what to try next. Again, it doesn't seem like a
>> > hardware
>> > problem but I can't rule it out either. Please advise.
>> Is this a SAN drive per chance? Or any special SCSI drive that may be
>> doing
>> something while you do a backup?
>> Otherwise you may need to open a ticket with MS.
>>
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com
>> http://www.greenms.com/sqlserver.html
>>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.htmlsql

Backup fails WriteFileEx error !

I had a normal SQL backup fail (one of hundreds that happen every day) with
this error
Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:BACKUP DATABASE is terminating abnormally. (Microsoft
OLE DB Provider for SQL Server (80040e14): The WriteFileEx system function
executed on file 'F:\MSSQL\BACKUP\Mocom\RB_Mocom_db_FULL_99.BAK' only wrote
235008 bytes, expected 983040.)
Step Error code: 80040E14
Step Error Help File:
Step Error Help Context ID:0
I can't find any hints on microsoft.com for WriteFileEx or the error numbers.
I suspect its a simple out of space condition, but I can't be sure.
Anyone seen one of these ?
TIA
From oledberr.h file, which ships with the OLEDB SDK:
0x80040E14 The command contained one or more errors
Backup failed for some other reason, but SEM reported a generic error. You
should check your SQL errorlogs for backup errors and post them here.
Adrian
"Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
news:DF3297D4-F0E1-4348-9D3A-44E539995F9D@.microsoft.com...
>I had a normal SQL backup fail (one of hundreds that happen every day) with
> this error
> Step Error Source: Microsoft OLE DB Provider for SQL Server
> Step Error Description:BACKUP DATABASE is terminating abnormally.
> (Microsoft
> OLE DB Provider for SQL Server (80040e14): The WriteFileEx system function
> executed on file 'F:\MSSQL\BACKUP\Mocom\RB_Mocom_db_FULL_99.BAK' only
> wrote
> 235008 bytes, expected 983040.)
> Step Error code: 80040E14
> Step Error Help File:
> Step Error Help Context ID:0
> I can't find any hints on microsoft.com for WriteFileEx or the error
> numbers.
> I suspect its a simple out of space condition, but I can't be sure.
> Anyone seen one of these ?
> TIA
>

Backup fails WriteFileEx error !

I had a normal SQL backup fail (one of hundreds that happen every day) with
this error
Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:BACKUP DATABASE is terminating abnormally. (Microsoft
OLE DB Provider for SQL Server (80040e14): The WriteFileEx system function
executed on file 'F:\MSSQL\BACKUP\Mocom\RB_Mocom_db_FULL_
99.BAK' only wrote
235008 bytes, expected 983040.)
Step Error code: 80040E14
Step Error Help File:
Step Error Help Context ID:0
I can't find any hints on microsoft.com for WriteFileEx or the error numbers
.
I suspect its a simple out of space condition, but I can't be sure.
Anyone seen one of these ?
TIAFrom oledberr.h file, which ships with the OLEDB SDK:
0x80040E14 The command contained one or more errors
Backup failed for some other reason, but SEM reported a generic error. You
should check your SQL errorlogs for backup errors and post them here.
Adrian
"Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
news:DF3297D4-F0E1-4348-9D3A-44E539995F9D@.microsoft.com...
>I had a normal SQL backup fail (one of hundreds that happen every day) with
> this error
> Step Error Source: Microsoft OLE DB Provider for SQL Server
> Step Error Description:BACKUP DATABASE is terminating abnormally.
> (Microsoft
> OLE DB Provider for SQL Server (80040e14): The WriteFileEx system function
> executed on file 'F:\MSSQL\BACKUP\Mocom\RB_Mocom_db_FULL_
99.BAK' only
> wrote
> 235008 bytes, expected 983040.)
> Step Error code: 80040E14
> Step Error Help File:
> Step Error Help Context ID:0
> I can't find any hints on microsoft.com for WriteFileEx or the error
> numbers.
> I suspect its a simple out of space condition, but I can't be sure.
> Anyone seen one of these ?
> TIA
>

Backup fails WriteFileEx error !

I had a normal SQL backup fail (one of hundreds that happen every day) with
this error
Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:BACKUP DATABASE is terminating abnormally. (Microsoft
OLE DB Provider for SQL Server (80040e14): The WriteFileEx system function
executed on file 'F:\MSSQL\BACKUP\Mocom\RB_Mocom_db_FULL_99.BAK' only wrote
235008 bytes, expected 983040.)
Step Error code: 80040E14
Step Error Help File:
Step Error Help Context ID:0
I can't find any hints on microsoft.com for WriteFileEx or the error numbers.
I suspect its a simple out of space condition, but I can't be sure.
Anyone seen one of these ?
TIAFrom oledberr.h file, which ships with the OLEDB SDK:
0x80040E14 The command contained one or more errors
Backup failed for some other reason, but SEM reported a generic error. You
should check your SQL errorlogs for backup errors and post them here.
Adrian
"Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
news:DF3297D4-F0E1-4348-9D3A-44E539995F9D@.microsoft.com...
>I had a normal SQL backup fail (one of hundreds that happen every day) with
> this error
> Step Error Source: Microsoft OLE DB Provider for SQL Server
> Step Error Description:BACKUP DATABASE is terminating abnormally.
> (Microsoft
> OLE DB Provider for SQL Server (80040e14): The WriteFileEx system function
> executed on file 'F:\MSSQL\BACKUP\Mocom\RB_Mocom_db_FULL_99.BAK' only
> wrote
> 235008 bytes, expected 983040.)
> Step Error code: 80040E14
> Step Error Help File:
> Step Error Help Context ID:0
> I can't find any hints on microsoft.com for WriteFileEx or the error
> numbers.
> I suspect its a simple out of space condition, but I can't be sure.
> Anyone seen one of these ?
> TIA
>

Backup fails with Operating system error 33

Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...
> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.sql

Backup fails with Operating system error 33

Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...

quote:

---

> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.

---

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
DaveIn order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
Dave
In order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =
10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =
10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
DaveIn order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =
10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =
10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave