error 18210 severity 16 state 1 operating system error

Question

error 18210 severity 16 state 1 operating system error

JC-3113

SSCrazy Eights

Points: 8371
More actions
January 22, 2013 at 10:03 am

#393992

Hi Folks
once in a while i get this error:
error 18210 severity 16 state 1 operating system error 995
it looks like the backup file was created, but I am not sure since I get this error, if the backup is good
so I have some questions I am hoping you can help me with
1. does VSS writer have anything to do with this error if IT IS NOT RUNNING ?
2. if VSS writer is disabled would this cause an error at times, because most of the time the backups work
and i have it disabled since i do not do shadow copies
3. if VSS write is not the issue, can you point me in the right direction
Thanks
Jim

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 1

JC-3113 (1/22/2013)
once in a while i get this error:
error 18210 severity 16 state 1 operating system error 995
it looks like the backup file was created, but I am not sure since I get this error, if the backup is good
so I have some questions I am hoping you can help me with
1. does VSS writer have anything to do with this error if IT IS NOT RUNNING ?
2. if VSS writer is disabled would this cause an error at times, because most of the time the backups work
and i have it disabled since i do not do shadow copies
3. if VSS write is not the issue, can you point me in the right direction

Could you please confirm the version of SQL Server as well as the last SP applied? Also, in case a SP was applied, did the same error pop up before such a SP?

Please check http://support.microsoft.com/kb/934396

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

JC-3113 SSCrazy Eights Points: 8371 More actions · Answer 2

Hi Paul

here is the info on the sql server from 1-12-13

I am using SSMS maint plans to back up databases right now

Does that use vss writer service ?

I looked at the info on the url and that pertains to vss writer so that is why

I am asking the above question.

I see this type of error in my logs which is similar to the (Error messages) in the url:

2013-01-12 10:06:28.41 spid94 Error: 18210, Severity: 16, State: 1.

2013-01-12 10:06:28.41 spid94 BackupMedium::ReportIoError: write failure on

backup device '0a158c7d-a7a3-4d5a-8b58-124602e40a14'.

Operating system error 995(The I/O operation has been

aborted because of either a thread exit or an application

request.).

2013-01-12 10:06:28.52 spid94 Error: 18210, Severity: 16, State: 1.

2013-01-12 10:06:28.52 spid94 BackupVirtualDeviceFile::RequestDurableMedia:

Flush failure on backup device '0a158c7d-a7a3-4d5a-8b58-

124602e40a14'.

Operating system error 995(The I/O operation has been aborted

because of either a thread exit or an application request.).

SQL Server and Resource Database Version

----------------------------------------

Microsoft SQL Server 2005 - 9.00.5069.00 (X64)

Aug 22 2012 18:02:46

Developer Edition (64-bit)

Windows NT 5.2 (Build 3790: Service Pack 2)

Edition/ProductVersion/ProductLevel/ResourceLastUpdateDateTime

--------------------------------------------------------------

Developer Edition (64-bit)

9.00.5069.00

SP4

Aug 22 2012 4:59PM

What are your thoughts ?

Thanks

Jim

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 3

Hi Jim --

if you are confident the issue you are experiencing is the same one described on kb/934396 then I would carefully consider applying the resolution procedure documented in such document.

Please be sure that: a) described and experienced issue are the same, b) all pre-requisites check out, c) resolution is applied during a maintenance window where you are able to back out the changes if needed and, d) do it first on a test environment and let it run for a reasonable period of time - a week or so - before going production.

Hope this helps.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

JC-3113 SSCrazy Eights Points: 8371 More actions · Answer 4

Thanks Paul

I am never confident applying anything from Microsoft, especially hot fixes

Even they are not confidnet when they tell you to be cautious

I guess I will forego this one for now

Jim