Event ID: 17052

First, to say I am a SQL admin is a BIG stretch. Having said that, I am
seeing this event during a DTS import of external data into the DB "cab2002"
Anyone?
Thanks
Bob
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 4/15/2006
Time: 5:01:34 AM
User: N/A
Computer: ACCOUNTING
Description:
Error: 823, Severity: 24, State: 7
I/O error (bad page ID) detected during read at offset 0x00000000582000 in
file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 37 03 00 00 18 00 00 00 7......
0008: 0b 00 00 00 41 00 43 00 ...A.C.
0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
0020: 00 00 08 00 00 00 43 00 .....C.
0028: 61 00 62 00 32 00 30 00 a.b.2.0.
0030: 30 00 32 00 00 00 0.2...Hi Bob
I would guess at disc corruption causing this, have you tried doing a
chkdsk?
Look up 823 in the index of Books Online for more information.
John
"Bob Williamson" <Osm3um@.news.postalias> wrote in message
news:%23FfnIrjYGHA.5004@.TK2MSFTNGP02.phx.gbl...
> First, to say I am a SQL admin is a BIG stretch. Having said that, I am
> seeing this event during a DTS import of external data into the DB
> "cab2002"
> Anyone?
> Thanks
> Bob
>
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 4/15/2006
> Time: 5:01:34 AM
> User: N/A
> Computer: ACCOUNTING
> Description:
> Error: 823, Severity: 24, State: 7
> I/O error (bad page ID) detected during read at offset 0x00000000582000 in
> file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 37 03 00 00 18 00 00 00 7......
> 0008: 0b 00 00 00 41 00 43 00 ...A.C.
> 0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
> 0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
> 0020: 00 00 08 00 00 00 43 00 .....C.
> 0028: 61 00 62 00 32 00 30 00 a.b.2.0.
> 0030: 30 00 32 00 00 00 0.2...
>|||http://support.microsoft.com/kb/826433
--
Thomas
"Bob Williamson" wrote:
> First, to say I am a SQL admin is a BIG stretch. Having said that, I am
> seeing this event during a DTS import of external data into the DB "cab2002"
> Anyone?
> Thanks
> Bob
>
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 4/15/2006
> Time: 5:01:34 AM
> User: N/A
> Computer: ACCOUNTING
> Description:
> Error: 823, Severity: 24, State: 7
> I/O error (bad page ID) detected during read at offset 0x00000000582000 in
> file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 37 03 00 00 18 00 00 00 7......
> 0008: 0b 00 00 00 41 00 43 00 ...A.C.
> 0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
> 0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
> 0020: 00 00 08 00 00 00 43 00 .....C.
> 0028: 61 00 62 00 32 00 30 00 a.b.2.0.
> 0030: 30 00 32 00 00 00 0.2...
>
>|||Thanks for your reply, but all patches are up to date and read caching is
disabled.
I am going to try and recreate this evening.
Bob
"Thomas" <Thomas@.discussions.microsoft.com> wrote in message
news:B55D9D4F-2B01-4974-8159-FD0D6B4991FC@.microsoft.com...
> http://support.microsoft.com/kb/826433
> --
> Thomas
>
> "Bob Williamson" wrote:
>> First, to say I am a SQL admin is a BIG stretch. Having said that, I am
>> seeing this event during a DTS import of external data into the DB
>> "cab2002"
>> Anyone?
>> Thanks
>> Bob
>>
>>
>> Event Type: Error
>> Event Source: MSSQLSERVER
>> Event Category: (2)
>> Event ID: 17052
>> Date: 4/15/2006
>> Time: 5:01:34 AM
>> User: N/A
>> Computer: ACCOUNTING
>> Description:
>> Error: 823, Severity: 24, State: 7
>> I/O error (bad page ID) detected during read at offset 0x00000000582000
>> in
>> file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 37 03 00 00 18 00 00 00 7......
>> 0008: 0b 00 00 00 41 00 43 00 ...A.C.
>> 0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
>> 0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
>> 0020: 00 00 08 00 00 00 43 00 .....C.
>> 0028: 61 00 62 00 32 00 30 00 a.b.2.0.
>> 0030: 30 00 32 00 00 00 0.2...
>>|||Tahnks for the suggestion but the harddrive checks out,
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%23qT0oolYGHA.2208@.TK2MSFTNGP03.phx.gbl...
> Hi Bob
> I would guess at disc corruption causing this, have you tried doing a
> chkdsk?
> Look up 823 in the index of Books Online for more information.
> John
> "Bob Williamson" <Osm3um@.news.postalias> wrote in message
> news:%23FfnIrjYGHA.5004@.TK2MSFTNGP02.phx.gbl...
>> First, to say I am a SQL admin is a BIG stretch. Having said that, I am
>> seeing this event during a DTS import of external data into the DB
>> "cab2002"
>> Anyone?
>> Thanks
>> Bob
>>
>>
>> Event Type: Error
>> Event Source: MSSQLSERVER
>> Event Category: (2)
>> Event ID: 17052
>> Date: 4/15/2006
>> Time: 5:01:34 AM
>> User: N/A
>> Computer: ACCOUNTING
>> Description:
>> Error: 823, Severity: 24, State: 7
>> I/O error (bad page ID) detected during read at offset 0x00000000582000
>> in file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 37 03 00 00 18 00 00 00 7......
>> 0008: 0b 00 00 00 41 00 43 00 ...A.C.
>> 0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
>> 0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
>> 0020: 00 00 08 00 00 00 43 00 .....C.
>> 0028: 61 00 62 00 32 00 30 00 a.b.2.0.
>> 0030: 30 00 32 00 00 00 0.2...
>>
>|||Hi
You could try moving tempdb to a different drive and seeing if it still
occurs http://support.microsoft.com//kb/224071#EOACAAA This would rule out
tempdb totally. It could be corruption/faulty memory although I would expect
this to be more widespread if that was the case.
Has this data been imported before? Can you import this in stages and verify
that it is correct at each stage?
John
"Bob Williamson" <Osm3um@.news.postalias> wrote in message
news:e8kL86lYGHA.3848@.TK2MSFTNGP05.phx.gbl...
> Tahnks for the suggestion but the harddrive checks out,
> Bob
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:%23qT0oolYGHA.2208@.TK2MSFTNGP03.phx.gbl...
>> Hi Bob
>> I would guess at disc corruption causing this, have you tried doing a
>> chkdsk?
>> Look up 823 in the index of Books Online for more information.
>> John
>> "Bob Williamson" <Osm3um@.news.postalias> wrote in message
>> news:%23FfnIrjYGHA.5004@.TK2MSFTNGP02.phx.gbl...
>> First, to say I am a SQL admin is a BIG stretch. Having said that, I am
>> seeing this event during a DTS import of external data into the DB
>> "cab2002"
>> Anyone?
>> Thanks
>> Bob
>>
>>
>> Event Type: Error
>> Event Source: MSSQLSERVER
>> Event Category: (2)
>> Event ID: 17052
>> Date: 4/15/2006
>> Time: 5:01:34 AM
>> User: N/A
>> Computer: ACCOUNTING
>> Description:
>> Error: 823, Severity: 24, State: 7
>> I/O error (bad page ID) detected during read at offset 0x00000000582000
>> in file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 37 03 00 00 18 00 00 00 7......
>> 0008: 0b 00 00 00 41 00 43 00 ...A.C.
>> 0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
>> 0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
>> 0020: 00 00 08 00 00 00 43 00 .....C.
>> 0028: 61 00 62 00 32 00 30 00 a.b.2.0.
>> 0030: 30 00 32 00 00 00 0.2...
>>
>>
>|||This DTS first everynight and last friday was the first time I have seen the
issue. I come to find out that my users had some trouble accessing the DB
over the weekend.
Interestingly enough, the backup process for the SQL server (simply a DB
backup via the server agent) is when the issue APPEARS to have been fixed as
I have not had a single complaint of access problems all day.
I wil mess with it a bit more this evening, verify the DTS is completing
etc.
Thanks again,
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:ONoL6WmYGHA.3516@.TK2MSFTNGP03.phx.gbl...
> Hi
> You could try moving tempdb to a different drive and seeing if it still
> occurs http://support.microsoft.com//kb/224071#EOACAAA This would rule out
> tempdb totally. It could be corruption/faulty memory although I would
> expect this to be more widespread if that was the case.
> Has this data been imported before? Can you import this in stages and
> verify that it is correct at each stage?
> John|||Hi Bob ,
From the error event, it appears to be the hardware failue. To verify this,
I'd like to suggest you send me the SQL log and whole System event log to
v-xuwen@.microsoft.com
Have a good day.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================Get Secure! - www.microsoft.com/security
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================>>Reply-To: "Bob Williamson" <Osm3um@.news.postalias>
>>From: "Bob Williamson" <Osm3um@.news.postalias>
>>Subject: Event ID: 17052
>>Date: Mon, 17 Apr 2006 09:20:01 -0700
>>Lines: 36
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>X-RFC2646: Format=Flowed; Original
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>Message-ID: <#FfnIrjYGHA.5004@.TK2MSFTNGP02.phx.gbl>
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: mail.eisenhowerlaw.com 66.224.12.186
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:428231
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>First, to say I am a SQL admin is a BIG stretch. Having said that, I am
>>seeing this event during a DTS import of external data into the DB
"cab2002"
>>Anyone?
>>Thanks
>>Bob
>>
>>
>>Event Type: Error
>>Event Source: MSSQLSERVER
>>Event Category: (2)
>>Event ID: 17052
>>Date: 4/15/2006
>>Time: 5:01:34 AM
>>User: N/A
>>Computer: ACCOUNTING
>>Description:
>>Error: 823, Severity: 24, State: 7
>>I/O error (bad page ID) detected during read at offset 0x00000000582000
in
>>file 'C:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'.
>>For more information, see Help and Support Center at
>>http://go.microsoft.com/fwlink/events.asp.
>>Data:
>>0000: 37 03 00 00 18 00 00 00 7......
>>0008: 0b 00 00 00 41 00 43 00 ...A.C.
>>0010: 43 00 4f 00 55 00 4e 00 C.O.U.N.
>>0018: 54 00 49 00 4e 00 47 00 T.I.N.G.
>>0020: 00 00 08 00 00 00 43 00 .....C.
>>0028: 61 00 62 00 32 00 30 00 a.b.2.0.
>>0030: 30 00 32 00 00 00 0.2...
>>|||Hi Bob
The error message is pointing to tempdb as being the problem, and I would
not expect that to be backed up. If the server has stopped/started then
tempdb would have been re-created. If you have any lower level tools to
check the status of the disc then you may want to try running them (make
sure everything is backed up first though!).
You don't say what the external source is or how the data is loaded! The
error may somehow be possibly be related to connectivity to this, check the
Windows Event Log as well as the SQL Server event log for errors.
If you are backing up to disc you may want to see if this is on the same
spindles as tempdb and check to see if there is a bottleneck on the disc. If
there is a backup agent being run by the backup software, try and schedule
it for a different time to make sure it is not interferring with the loading
process.
John
"Bob Williamson" <Osm3um@.news.postalias> wrote in message
news:u17coJnYGHA.4168@.TK2MSFTNGP05.phx.gbl...
> This DTS first everynight and last friday was the first time I have seen
> the issue. I come to find out that my users had some trouble accessing
> the DB over the weekend.
> Interestingly enough, the backup process for the SQL server (simply a DB
> backup via the server agent) is when the issue APPEARS to have been fixed
> as I have not had a single complaint of access problems all day.
> I wil mess with it a bit more this evening, verify the DTS is completing
> etc.
> Thanks again,
> Bob
>
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:ONoL6WmYGHA.3516@.TK2MSFTNGP03.phx.gbl...
>> Hi
>> You could try moving tempdb to a different drive and seeing if it still
>> occurs http://support.microsoft.com//kb/224071#EOACAAA This would rule
>> out tempdb totally. It could be corruption/faulty memory although I would
>> expect this to be more widespread if that was the case.
>> Has this data been imported before? Can you import this in stages and
>> verify that it is correct at each stage?
>> John
>