saw one of my database went suspect, I tried to load a restore from the backup, but this was going on for ever. I cancelled out, deleted the suspect database. Created a new database and tried to restore from the old backup, but this was going on for ever. It will not restore. I cannot stop and start mssql service on this server as it is production. what else can I do.Q1 On trying to restore from the old backup, this goes on forever. I cannot stop and start mssql service on this server as it is production. What else can I do?
A1 If the issue amounts to the Db remaining in 'Loading' status "forever"; it may simply be that the DB has not been recovered following the restore.
To test this possibility, one would execute a statement similar to the following:
Restore DataBase [DBName] With Recovery
Question I
Can the DB be restored to a development server successfully using the "old backup"?sql
Showing posts with label severity. Show all posts
Showing posts with label severity. Show all posts
Tuesday, March 27, 2012
Monday, March 26, 2012
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
Thanks
SalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default...b;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB)42147483647470470
min server memory (MB)02147483647256256
set working set size0111
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/default...b;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you should
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
Thanks
SalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default...b;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB)42147483647470470
min server memory (MB)02147483647256256
set working set size0111
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/default...b;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you should
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
error 823, severity 24, state2
The following messages seems happen every two weeks. it may cause by hardwar
e
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
e
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
error 823, severity 24, state2
The following messages seems happen every two weeks. it may cause by hardware
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.
Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
|||Generally the first thing you do is look up the error number in Books On
line... Here is the info from BOL
Error 823
Severity Level 24
Message Text
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
Explanation
Microsoft SQL ServerT encountered an I/O error on a read or write request
made to a device. This error usually indicates disk problems. However,
additional kernel messages in the error log, recorded before error 823,
should indicate which device is involved.
Action
Check the accessibility and condition of the device in question.
Run hardware diagnostics and correct problems, if possible.
Restore damaged files from the latest database backup. Restoring from a
database backup should always be considered the primary means of fixing a
damaged database.
If you don't have a backup or if the errors detected are very isolated, the
repair functionality of DBCC CHECKDB may be useful. However, using DBCC
CHECKDB can be more time consuming than restoring the damaged files from a
backup, and you may not be able to recover all your data .
Caution If running DBCC CHECKDB with one of the repair clauses does not
correct the problem or if you are unsure how this process may affect your
data, contact your primary support provider.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
1000,
> the database is on SAN disks.
begin 666 caution.gif
M1TE&.#EA# `+`/<``````#,``&8``)D``,P``/\````S`#,S`&8S`)DS`,PS
M`/\S``!F`#-F`&9F`)EF`,QF`/]F``"9`#.9`&:9`)F9`,R9`/^9``#,`#/,
M`&;,`)G,`,S,`/_,``#_`#/_`&;_`)G_`,S_`/__````,S,`,V8`,YD`,\P`
M,_\`,P`S,S,S,V8S,YDS,\PS,_\S,P!F,S-F,V9F,YEF,\QF,_]F,P"9,S.9
M,V:9,YF9,\R9,_^9,P#,,S/,,V;,,YG,,\S,,__,,P#_,S/_,V;_,YG_,\S_
M,___,P``9C,`9F8`9ID`9LP`9O\`9@.`S9C,S9F8S9IDS9LPS9 O\S9@.!F9C-F
M9F9F9IEF9LQF9O]F9@."99C.99F:99IF99LR99O^99@.#,9C/,9F;,9IG,9LS,
M9O_,9@.#_9C/_9F;_9IG_9LS_9O__9@.``F3,`F68`F9D`F<P`F?\`F0`SF3,S
MF68SF9DSF<PSF?\SF0!FF3-FF69FF9EFF<QFF?]FF0"9F3.9F6:9F9F9F<R9
MF?^9F0#,F3/,F6;,F9G,F<S,F?_,F0#_F3/_F6;_F9G_F<S_F?__F0``S#,`
MS&8`S)D`S,P`S/\`S `SS#,SS&8SS)DSS,PSS/\SS !FS#-FS&9FS)EFS,QF
MS/]FS "9S#.9S&:9S)F9S,R9S/^9S #,S#/,S&;,S)G,S,S,S/_,S #_S#/_
MS&;_S)G_S,S_S/__S ``_S,`_V8`_YD`_\P`__\`_P`S_S,S_V8S_YDS_\PS
M__\S_P!F_S-F_V9F_YEF_\QF__]F_P"9_S.9_V:9_YF9_\R9__^9_P#,_S/,
M_V;,_YG,_\S,___,_P#__S/__V;__YG__\S______P``````````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M`````````````````````"'Y! $``*P`+ `````,``L`0 @.B`%D)'$BPH,&#
;K HH1)AP(4*%!1A"9$A1X,2'#BMBC#@.P( `[
`
end
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.
Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
|||Generally the first thing you do is look up the error number in Books On
line... Here is the info from BOL
Error 823
Severity Level 24
Message Text
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.
Explanation
Microsoft SQL ServerT encountered an I/O error on a read or write request
made to a device. This error usually indicates disk problems. However,
additional kernel messages in the error log, recorded before error 823,
should indicate which device is involved.
Action
Check the accessibility and condition of the device in question.
Run hardware diagnostics and correct problems, if possible.
Restore damaged files from the latest database backup. Restoring from a
database backup should always be considered the primary means of fixing a
damaged database.
If you don't have a backup or if the errors detected are very isolated, the
repair functionality of DBCC CHECKDB may be useful. However, using DBCC
CHECKDB can be more time consuming than restoring the damaged files from a
backup, and you may not be able to recover all your data .
Caution If running DBCC CHECKDB with one of the repair clauses does not
correct the problem or if you are unsure how this process may affect your
data, contact your primary support provider.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
1000,
> the database is on SAN disks.
begin 666 caution.gif
M1TE&.#EA# `+`/<``````#,``&8``)D``,P``/\````S`#,S`&8S`)DS`,PS
M`/\S``!F`#-F`&9F`)EF`,QF`/]F``"9`#.9`&:9`)F9`,R9`/^9``#,`#/,
M`&;,`)G,`,S,`/_,``#_`#/_`&;_`)G_`,S_`/__````,S,`,V8`,YD`,\P`
M,_\`,P`S,S,S,V8S,YDS,\PS,_\S,P!F,S-F,V9F,YEF,\QF,_]F,P"9,S.9
M,V:9,YF9,\R9,_^9,P#,,S/,,V;,,YG,,\S,,__,,P#_,S/_,V;_,YG_,\S_
M,___,P``9C,`9F8`9ID`9LP`9O\`9@.`S9C,S9F8S9IDS9LPS9 O\S9@.!F9C-F
M9F9F9IEF9LQF9O]F9@."99C.99F:99IF99LR99O^99@.#,9C/,9F;,9IG,9LS,
M9O_,9@.#_9C/_9F;_9IG_9LS_9O__9@.``F3,`F68`F9D`F<P`F?\`F0`SF3,S
MF68SF9DSF<PSF?\SF0!FF3-FF69FF9EFF<QFF?]FF0"9F3.9F6:9F9F9F<R9
MF?^9F0#,F3/,F6;,F9G,F<S,F?_,F0#_F3/_F6;_F9G_F<S_F?__F0``S#,`
MS&8`S)D`S,P`S/\`S `SS#,SS&8SS)DSS,PSS/\SS !FS#-FS&9FS)EFS,QF
MS/]FS "9S#.9S&:9S)F9S,R9S/^9S #,S#/,S&;,S)G,S,S,S/_,S #_S#/_
MS&;_S)G_S,S_S/__S ``_S,`_V8`_YD`_\P`__\`_P`S_S,S_V8S_YDS_\PS
M__\S_P!F_S-F_V9F_YEF_\QF__]F_P"9_S.9_V:9_YF9_\R9__^9_P#,_S/,
M_V;,_YG,_\S,___,_P#__S/__V;__YG__\S______P``````````````````
M````````````````````````````````````````````````` ```````````
M````````````````````````````````````````````````` ```````````
M`````````````````````"'Y! $``*P`+ `````,``L`0 @.B`%D)'$BPH,&#
;K HH1)AP(4*%!1A"9$A1X,2'#BMBC#@.P( `[
`
end
error 823, severity 24, state2
The following messages seems happen every two weeks. it may cause by hardware
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
error, but HP Array Utility hasn't detected any error. Any ideas, does it
make sense to move database to the local hard drive?
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
Data:Words
0000: 00000337 00000018 00000009 00550053
0010: 0044004e 00540041 00310041 00070000
0020: 00530000 004e0055 00440035 00000042
SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA 1000,
the database is on SAN disks.Sounds like you may have some corruption in the database.
Try running the DBCC CHECKCATALOG and see what you get back. BOL has some
great suggestions on the usage as well as some others like DBCC CHECKTABLE
and DBCC CHECKxxxxxx
Rick Sawtell
MCT, MCSD, MCDBA
"Joshua" <Joshua@.discussions.microsoft.com> wrote in message
news:A1DF380C-CB99-4125-A713-7E14303C6125@.microsoft.com...
> The following messages seems happen every two weeks. it may cause by
> hardware
> error, but HP Array Utility hasn't detected any error. Any ideas, does it
> make sense to move database to the local hard drive?
> Error: 823, Severity: 24, State: 2
> I/O error (bad page ID) detected during read at offset 0x0000016d7fa000 in
> file 'E:\SQLDATA\MSSQL\Data\SUN5DB_data.mdf'.
> Data:Words
> 0000: 00000337 00000018 00000009 00550053
> 0010: 0044004e 00540041 00310041 00070000
> 0020: 00530000 004e0055 00440035 00000042
> SQL Enterprise 2000 Server, Windows 2000 Enterprise Server, Compaq MSA
> 1000,
> the database is on SAN disks.
Error 823, Severity 24, State 2 (Again)
I synch 4 databases everyday and on one of them I get the Error 823, Severity 24, State 2 error (Yes I know you have heard this before but I am a new, LOL). I have tried detaching the database and copying it, renaming that database and then copying back to the original name with the same error; therefore, I think the error is somewhere in the database structure. If it is the database structure would it still give the error above or is that simply a hardware error? I have been searching for solution and I am at a loss. Any help would be appreciated.
Thanks.
N. AdkinsAn 823 error usually indicates a disk i/o problem. You say that you are synchronizing databases. How? replication ... log shipping ... home grown method?
Have you run DBCC checkdb against the database that throws the error?
And ... what OS and SP. What version SQL Server and SP. RAID ... 5 ... 0 ... 1 ... 1+0?
Have you checked with HW vendor for possible reported problems with your array controller (if you have them)?
Lots of opportunity to troubleshoot and many things can cause an 823 error.
No rest for the weary on this one! :(|||Raid 0
I have ran dbcc checkdb and shows no errors.
It is running on Win 2K Server
I am running MS SQL Server 2000
It is a Gateway 980 Server with Adaptec SCSI card (dual channel)
The remote database connects with the main database within the software itself (I.E. SmartClinic) and does the actual synch. I would assume it is using log shipping as method.
N. Adkins|||Raid 0 ... flying without a net! Striped diskset with no redundancy! I don't see the service pack levels in your response, but based on the info you have provided here is what I would start with.
1. Contact HW vendors for known disk controller problems (i.e. read / write caching, delayed writes, etc ) ... see if they have any firmware / patches. This could be a delayed write situation.
2. Check with Berdy Medical Systems regarding Smart Clinic. It was developed for Access ... are they tring to port it to SQL Server? Do they have any records or reports of disk transfer errors, or are you charting unsailed waters?
3. Start checking the transmission hardware. How is your network performing. Are you using hubs (bad), routers (good), dial-up (bad), fractional T1, etc. Copy a small file from good server to server that throws 823 error. Compare files. Was it copied in a timely manner? Are the files the same. Copy a backup of the database (if size allows) and restore to a differently named database. Run checkdb. Is it clean.
5. Check the microsoft.public forums under google groups. Check other support sites (M$ KnowledgeBase, SQLServer Central, SQL Team, etc (google 'em)).
6. Time to get the big boys involved. Micro$oft Support - not just for breakfast anymore!
HTH
Tom
Thanks.
N. AdkinsAn 823 error usually indicates a disk i/o problem. You say that you are synchronizing databases. How? replication ... log shipping ... home grown method?
Have you run DBCC checkdb against the database that throws the error?
And ... what OS and SP. What version SQL Server and SP. RAID ... 5 ... 0 ... 1 ... 1+0?
Have you checked with HW vendor for possible reported problems with your array controller (if you have them)?
Lots of opportunity to troubleshoot and many things can cause an 823 error.
No rest for the weary on this one! :(|||Raid 0
I have ran dbcc checkdb and shows no errors.
It is running on Win 2K Server
I am running MS SQL Server 2000
It is a Gateway 980 Server with Adaptec SCSI card (dual channel)
The remote database connects with the main database within the software itself (I.E. SmartClinic) and does the actual synch. I would assume it is using log shipping as method.
N. Adkins|||Raid 0 ... flying without a net! Striped diskset with no redundancy! I don't see the service pack levels in your response, but based on the info you have provided here is what I would start with.
1. Contact HW vendors for known disk controller problems (i.e. read / write caching, delayed writes, etc ) ... see if they have any firmware / patches. This could be a delayed write situation.
2. Check with Berdy Medical Systems regarding Smart Clinic. It was developed for Access ... are they tring to port it to SQL Server? Do they have any records or reports of disk transfer errors, or are you charting unsailed waters?
3. Start checking the transmission hardware. How is your network performing. Are you using hubs (bad), routers (good), dial-up (bad), fractional T1, etc. Copy a small file from good server to server that throws 823 error. Compare files. Was it copied in a timely manner? Are the files the same. Copy a backup of the database (if size allows) and restore to a differently named database. Run checkdb. Is it clean.
5. Check the microsoft.public forums under google groups. Check other support sites (M$ KnowledgeBase, SQLServer Central, SQL Team, etc (google 'em)).
6. Time to get the big boys involved. Micro$oft Support - not just for breakfast anymore!
HTH
Tom
Error 823, Severity 24, State 2
Here is my problem:
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
..
..
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
Chuck
You should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/default...b;en-us;828339
http://support.microsoft.com/default...b;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/default...b;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
http://support.microsoft.com/default...22120121120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
sql
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
..
..
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
Chuck
You should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/default...b;en-us;828339
http://support.microsoft.com/default...b;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/default...b;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
http://support.microsoft.com/default...22120121120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
sql
Error 823, Severity 24, State 2
Here is my problem:
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
.
.
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
ChuckYou should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
http://support.microsoft.com/default.aspx?scid=kb;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;231619#XSLTH4300121122120121120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
.
.
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
ChuckYou should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
http://support.microsoft.com/default.aspx?scid=kb;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;231619#XSLTH4300121122120121120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
Error 823, Severity 24, State 2
Here is my problem:
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
.
.
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
ChuckYou should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/defaul...kb;en-us;828339
http://support.microsoft.com/defaul...kb;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/defaul...kb;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
21120120" target="_blank">http://support.microsoft.com/defaul...br />
21120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
.
.
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
ChuckYou should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/defaul...kb;en-us;828339
http://support.microsoft.com/defaul...kb;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/defaul...kb;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
21120120" target="_blank">http://support.microsoft.com/defaul...br />
21120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
Error 823 with msdb
When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the followin
g
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should no
t
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msd
b
> is fixed, I am dead in the water (the existing plans still run fine). And
I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the followin
g
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage
But if you arethinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should no
t
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msd
b
> is fixed, I am dead in the water (the existing plans still run fine). And
I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
Error 823 with msdb
When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install?
Any suggestions are greatly appreciated.
Thanks
Russ Stevens
I just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens
|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens
|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install?
Any suggestions are greatly appreciated.
Thanks
Russ Stevens
I just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens
|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens
|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage
But if you arethinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
Error 823 with msdb
When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup :)
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage :) But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevenssql
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup :)
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage :) But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevenssql
Error 823
I'm running W2000 server with SQL 7.0 SP2. we get the following error
Error 823, severity 24, state 1 , i/o error (bad page 10) detected
during read of BUF pointer= 0x11959fc80, page ptr=0x45724000, page id=
(0x3:0x777f), dbid=7, status= 0x 801, file=D:\masdata\monitordb.ndf
We continued restoring a backup, but after a few day, the database crash again.Microsoft has reported to fix this error in service pack 3,
FIX: Error 823 or 8966 Reported by SQL Server with Insufficient System Resources
Knowledge base article Q274310sql
Error 823, severity 24, state 1 , i/o error (bad page 10) detected
during read of BUF pointer= 0x11959fc80, page ptr=0x45724000, page id=
(0x3:0x777f), dbid=7, status= 0x 801, file=D:\masdata\monitordb.ndf
We continued restoring a backup, but after a few day, the database crash again.Microsoft has reported to fix this error in service pack 3,
FIX: Error 823 or 8966 Reported by SQL Server with Insufficient System Resources
Knowledge base article Q274310sql
Monday, March 19, 2012
Error 7105, how to fix it?
Hi
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 7105, how to fix it?
Hi
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
I am getting error 7105 Severity: 22 on one of my tables (about 1000
record), It seems 2 of the records has been corrupted. I can select other
records and edit the records as long as these 2 records are not part of
select query.
I have read microsoft support and they say that service pack2 should solve
this problem but my server already has service pack 3.
I can not choose these records to delete it, what is the solution, any idea?> I am getting error 7105 Severity: 22 on one of my tables (about 1000
> record), It seems 2 of the records has been corrupted. I can select other
> records and edit the records as long as these 2 records are not part of
> select query.
> I have read microsoft support and they say that service pack2 should solve
> this problem but my server already has service pack 3.
> I can not choose these records to delete it, what is the solution, any
idea?
What does DBCC CHECKDB report?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 7102, Severity Level 20, State 7
We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.
Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegr oups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>
|||Thnx for the post.
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.
Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegr oups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.?^E^@.?^F^@.?^G^@.?^@.?.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransi tionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExec ute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.post ImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdat eInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>
|||Thnx for the post.
Error 7102, Severity Level 20, State 7
We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.
Error 7102, Severity Level 20, State 7
We have received the following error in the production. It is a SQL
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknow
n
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unkn
own
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.
Server Issue.
The details of the error are listed below. We also looked through a
few forums to understand more about the issue.
I am also enclosing the details along with the email.
Error in SQL Server
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
[SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
Note the error and time, and contact your system administrator.
at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknow
n
Source)
at
com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at
com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
at
com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
Source)
Forum Details
Error 7102, Severity Level 20, State 7
Message Text
SQL Server Internal Error. Text manager cannot continue with current
statement.Hi
Follow the instructions as listed in
http://msdn2.microsoft.com/en-us/library/aa226414(sql.80).aspx
You may need to contact Customer Support.
--
Regards
Michel Epprecht [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lcuky" <sachindiwaker@.gmail.com> wrote in message
news:1170963494.231090.148340@.p10g2000cwp.googlegroups.com...
> We have received the following error in the production. It is a SQL
> Server Issue.
>
> The details of the error are listed below. We also looked through a
> few forums to understand more about the issue.
> I am also enclosing the details along with the email.
>
> Error in SQL Server
>
> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]
> [SQLServer]Warning: Fatal error 7102 occurred at Feb 5 2007
> 7:10AM^@.'^E^@.'^F^@.'^G^@.?^@.'.
> Note the error and time, and contact your system administrator.
> at
> com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unkn
own
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
> at
> com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
> Source)
> at
> com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown
> Source)
>
> Forum Details
>
> Error 7102, Severity Level 20, State 7
> Message Text
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
>|||Thnx for the post.
Subscribe to:
Posts (Atom)