Error: 823

Hi,

I am I notice this message on the event logs.

Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x000003182da000 in file 'e:\sqlData\FSDocsOnline.mdf'.

If I was to run:

DBCC CHECKDB
( 'database_name'
[ , NOINDEX
| { REPAIR_ALLOW_DATA_LOSS
| REPAIR_FAST
| REPAIR_REBUILD
} ]
) [ WITH { [ ALL_ERRORMSGS ]
[ , [ NO_INFOMSGS ] ]
[ , [ TABLOCK ] ]
[ , [ ESTIMATEONLY ] ]
[ , [ PHYSICAL_ONLY ] ]
}
]

Will it fix my problem or will I need to restore the database. Which have no backup.

LystraYou might be able to fix the database, but I'd be more comfortable with either restoring a backup, or better yet trying to copy the data out one table at a time (saving the backup for a last resort).

A lot depends on just what is broken and how it broke. I don't have a good way to guess what caused the problem, so I'd assume that it will be tough to fix.

-PatP|||Well there is no Backup for this database. The last time it was backup was in 10/03. And the files have since been deleted.

In order to copy the time out one at a time what would this accomplish. And to do this should I use the bCP out method?

Thanking you in advance.

Lystra|||Brett would say yes to the BCP part.|||The method you use for the copy isn't really significant. You can BCP to flat files, or you can just use an INSERT if both databases are on the same server, or DTS if they are on different servers.

The trick is to copy data until the copy fails (due to the problem with the disk), then find a way to resume the copy just past the problem. The easiest way to do this is using PK values to copy what you can, then move a few PK values higher and start again. If there was only one flaw, then you can copy from the low PK values up, then from the high PK values down and you will have all of the recoverable data. If you have more than one flaw, then you'll have to fuss with the copy a bit, trying to "jump" the flaws.

-PatPsql

Error: 7105, Severity: 22, State: 6

it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.
Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Oops.
Wrong group.
"ME" <ME@.mail.com> wrote in message
news:e7fZBsT$GHA.4800@.TK2MSFTNGP05.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this? Thanks.
>
>sql

Error: 7105, Severity: 22, State: 6

it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
>
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
>
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
>The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.Make the call, they will tell you up front if it will be a covered (free)
call.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>|||Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Error: 3624 - SQL Server Assertion

Ok, I keep getting SQL Server assertions in the event log, with the
following stack dump message in the SQL Server logs. Any ideas?
DBCC CHECKDB reveals no problems.
* ----
2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is 0x2EF0EDAD
2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
line=573
Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
*Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
*Stack Dump being sent to I:\Microsoft SQL Server\MSSQL\log\SQLDump0033.txt
*
************************************************** **************************
***
Thanks in advance,
Jerry Dennany
Jerry,
If you search MS site for error 3624, which is mentioned in the stack dump,
you will find plenty of articles
(http://search.microsoft.com/search/r...1&s=0&c=3&st=b
&qu=3624&na=32). There are many possible reasons for this error. Just by
reading the article titles I guess you will be able to narrow the search to
your problem.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jerry Dennany" <jerry@.dennany.org> wrote in message
news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
> Ok, I keep getting SQL Server assertions in the event log, with the
> following stack dump message in the SQL Server logs. Any ideas?
> DBCC CHECKDB reveals no problems.
>
>
* ----
> --
> 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
0x2EF0EDAD
> 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> line=573
> Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> *Stack Dump being sent to I:\Microsoft SQL
Server\MSSQL\log\SQLDump0033.txt
> *
>
************************************************** **************************
> ***
>
> Thanks in advance,
> Jerry Dennany
>
|||I suppose that I should have mentioned that I've already performed the
typical google and support.microsoft.com searches, without finding anything
applicable. Any other ideas?
Thanks,
Jerry Dennany
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in
message news:OTZriQGJEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Jerry,
> If you search MS site for error 3624, which is mentioned in the stack
dump,
> you will find plenty of articles
>
(http://search.microsoft.com/search/r...1&s=0&c=3&st=b
> &qu=3624&na=32). There are many possible reasons for this error. Just by
> reading the article titles I guess you will be able to narrow the search
to
> your problem.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Jerry Dennany" <jerry@.dennany.org> wrote in message
> news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
* ----
> 0x2EF0EDAD
> Server\MSSQL\log\SQLDump0033.txt
>
************************************************** **************************
>
|||> I suppose that I should have mentioned that I've already performed the
> typical google and support.microsoft.com searches, without finding
anything
> applicable. Any other ideas?
Sorry, not directly. Maybe you can track down what happens before this
error, which command makes the problem? It would be nice if the problem
would be reproducable.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
|||The following is the SqlException our code got when that happens. What Jerry and I don't understand is that the error message "Duplicate key was ignored" should be associated with SQL error 3604, which is only on severity level 16 that will not throw the exception, (while error 3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) with "Ignore duplicate key", and a composit cluster index (QueuedTime, Odometer). The Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual processors.
Error: 3624
General message:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient .SqlException:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$all ocator@.PAU_PARAM@.@.@.std@.@.@.std@.@.W4COMMANDTYPE@.@.@.Z(In t32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> anything
> Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the problem
> would be reproducable.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
>
|||Can you send me the code directly to my e-mail (just take out the "_please_reply..." part out of the address and I will try to reproduce the error? BTW, which versions of SQL Server and .NET Framework are you using?
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Yang Cao" <yang@.yangcao88.com> wrote in message news:uu3i%23lUJEHA.3436@.tk2msftngp13.phx.gbl...
The following is the SqlException our code got when that happens. What Jerry and I don't understand is that the error message "Duplicate key was ignored" should be associated with SQL error 3604, which is only on severity level 16 that will not throw the exception, (while error 3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) with "Ignore duplicate key", and a composit cluster index (QueuedTime, Odometer). The Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual processors.
Error: 3624
General message:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient .SqlException:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$all ocator@.PAU_PARAM@.@.@.std@.@.@.std@.@.W4COMMANDTYPE@.@.@.Z(In t32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> anything
> Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the problem
> would be reproducable.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
>

Error: 3624 - SQL Server Assertion

Ok, I keep getting SQL Server assertions in the event log, with the
following stack dump message in the SQL Server logs. Any ideas?
DBCC CHECKDB reveals no problems.
* ----
--
2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is 0x2EF0EDAD
2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
line=573
Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
*Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
*Stack Dump being sent to I:\Microsoft SQL Server\MSSQL\log\SQLDump0033.txt
*
****************************************
************************************
***
Thanks in advance,
Jerry DennanyJerry,
If you search MS site for error 3624, which is mentioned in the stack dump,
you will find plenty of articles
(http://search.microsoft.com/search/...=1&s=0&c=3&st=b
&qu=3624&na=32). There are many possible reasons for this error. Just by
reading the article titles I guess you will be able to narrow the search to
your problem.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jerry Dennany" <jerry@.dennany.org> wrote in message
news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
> Ok, I keep getting SQL Server assertions in the event log, with the
> following stack dump message in the SQL Server logs. Any ideas?
> DBCC CHECKDB reveals no problems.
>
>
* ----
> --
> 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
0x2EF0EDAD
> 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> line=573
> Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> *Stack Dump being sent to I:\Microsoft SQL
Server\MSSQL\log\SQLDump0033.txt
> *
>
****************************************
************************************[vbc
ol=seagreen]
> ***
>
> Thanks in advance,
> Jerry Dennany
>[/vbcol]|||I suppose that I should have mentioned that I've already performed the
typical google and support.microsoft.com searches, without finding anything
applicable. Any other ideas?
Thanks,
Jerry Dennany
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OTZriQGJEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Jerry,
> If you search MS site for error 3624, which is mentioned in the stack
dump,
> you will find plenty of articles
>
(http://search.microsoft.com/search/...=1&s=0&c=3&st=b
> &qu=3624&na=32). There are many possible reasons for this error. Just by
> reading the article titles I guess you will be able to narrow the search
to
> your problem.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Jerry Dennany" <jerry@.dennany.org> wrote in message
> news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
* ----
> 0x2EF0EDAD
> Server\MSSQL\log\SQLDump0033.txt
>
****************************************
************************************[vbc
ol=seagreen]
>[/vbcol]|||> I suppose that I should have mentioned that I've already performed the
> typical google and support.microsoft.com searches, without finding
anything
> applicable. Any other ideas?
Sorry, not directly. Maybe you can track down what happens before this
error, which command makes the problem? It would be nice if the problem
would be reproducable.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||The following is the SqlException our code got when that happens. What Jerr
y and I don't understand is that the error message "Duplicate key was ignore
d" should be associated with SQL error 3604, which is only on severity level
16 that will not throw the exception, (while error 3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) with "Ign
ore duplicate key", and a composit cluster index (QueuedTime, Odometer). Th
e Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual process
ors.
Error: 3624
General message:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlExce
ption:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavio
r, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.
@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in message news:ecsL
MESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> anything
>
> Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the problem
> would be reproducable.
>
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
>
>|||Can you send me the code directly to my e-mail (just take out the "_please_r
eply..." part out of the address and I will try to reproduce the error? BTW,
which versions of SQL Server and .NET Framework are you using?
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Yang Cao" <yang@.yangcao88.com> wrote in message news:uu3i%23lUJEHA.3436@.tk2
msftngp13.phx.gbl...
The following is the SqlException our code got when that happens. What Jerr
y and I don't understand is that the error message "Duplicate key was ignore
d" should be associated with SQL error 3604, which is only on severity level
16 that will not throw the exception, (while error 3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) with "Ign
ore duplicate key", and a composit cluster index (QueuedTime, Odometer). Th
e Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual process
ors.
Error: 3624
General message:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlExce
ption:
Location: insert.c:573
Expression: sdesP->m_pIndex->indindid == CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavio
r, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.
@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in message news:ecsL
MESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> anything
>
> Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the problem
> would be reproducable.
>
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
>
>

Error: 3624 - SQL Server Assertion

Ok, I keep getting SQL Server assertions in the event log, with the
following stack dump message in the SQL Server logs. Any ideas?
DBCC CHECKDB reveals no problems.
* ----
--
2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is 0x2EF0EDAD
2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
line=573
Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
*Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
*Stack Dump being sent to I:\Microsoft SQL Server\MSSQL\log\SQLDump0033.txt
*
****************************************************************************
***
Thanks in advance,
Jerry DennanyJerry,
If you search MS site for error 3624, which is mentioned in the stack dump,
you will find plenty of articles
(http://search.microsoft.com/search/results.aspx?View=en-us&p=1&s=0&c=3&st=b
&qu=3624&na=32). There are many possible reasons for this error. Just by
reading the article titles I guess you will be able to narrow the search to
your problem.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Jerry Dennany" <jerry@.dennany.org> wrote in message
news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
>
> Ok, I keep getting SQL Server assertions in the event log, with the
> following stack dump message in the SQL Server logs. Any ideas?
> DBCC CHECKDB reveals no problems.
>
>
* ----
> --
> 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
0x2EF0EDAD
> 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> line=573
> Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> *Stack Dump being sent to I:\Microsoft SQL
Server\MSSQL\log\SQLDump0033.txt
> *
>
****************************************************************************
> ***
>
> Thanks in advance,
> Jerry Dennany
>|||I suppose that I should have mentioned that I've already performed the
typical google and support.microsoft.com searches, without finding anything
applicable. Any other ideas?
Thanks,
Jerry Dennany
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in
message news:OTZriQGJEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Jerry,
> If you search MS site for error 3624, which is mentioned in the stack
dump,
> you will find plenty of articles
>
(http://search.microsoft.com/search/results.aspx?View=en-us&p=1&s=0&c=3&st=b
> &qu=3624&na=32). There are many possible reasons for this error. Just by
> reading the article titles I guess you will be able to narrow the search
to
> your problem.
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> "Jerry Dennany" <jerry@.dennany.org> wrote in message
> news:uMM$BVDJEHA.556@.TK2MSFTNGP10.phx.gbl...
> >
> >
> > Ok, I keep getting SQL Server assertions in the event log, with the
> > following stack dump message in the SQL Server logs. Any ideas?
> >
> > DBCC CHECKDB reveals no problems.
> >
> >
> >
>
* ----
> > --
> > 2004-04-02 04:03:13.39 spid234 Stack Signature for the dump is
> 0x2EF0EDAD
> > 2004-04-02 04:03:13.39 spid234 SQL Server Assertion: File: <insert.c>,
> > line=573
> > Failed Assertion = 'sdesP->m_pIndex->indindid == CLUSTIND'.
> > 2004-04-02 04:03:13.39 spid234 Error: 3624, Severity: 20, State: 1.
> > *Dump thread - spid = 84, PSS = 0x3e049238, EC = 0x3e049560
> > *Stack Dump being sent to I:\Microsoft SQL
> Server\MSSQL\log\SQLDump0033.txt
> > *
> >
>
****************************************************************************
> > ***
> >
> >
> > Thanks in advance,
> >
> > Jerry Dennany
> >
> >
>|||> I suppose that I should have mentioned that I've already performed the
> typical google and support.microsoft.com searches, without finding
anything
> applicable. Any other ideas?
Sorry, not directly. Maybe you can track down what happens before this
error, which command makes the problem? It would be nice if the problem
would be reproducable.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||This is a multi-part message in MIME format.
--=_NextPart_000_01B4_01C42527.F1365AC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The following is the SqlException our code got when that happens. What =Jerry and I don't understand is that the error message "Duplicate key =was ignored" should be associated with SQL error 3604, which is only on =severity level 16 that will not throw the exception, (while error 3624 =is on level 20).
The database table has a composit unique index (Odometer, QueueID) with ="Ignore duplicate key", and a composit cluster index (QueuedTime, =Odometer). The Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual =processors.
Error: 3624
General message: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored. Detailed message: =ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at =?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote =in message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> > I suppose that I should have mentioned that I've already performed =the
> > typical google and support.microsoft.com searches, without finding
> anything
> > applicable. Any other ideas?
> > Sorry, not directly. Maybe you can track down what happens before this
> error, which command makes the problem? It would be nice if the =problem
> would be reproducable.
> > -- > Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> >
--=_NextPart_000_01B4_01C42527.F1365AC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

The following is the SqlException our =code got when that happens. What Jerry and I don't understand is that the error =message "Duplicate key was ignored" should be associated with SQL error 3604, =which is only on severity level 16 that will not throw the exception, (while =error 3624 is on level 20). The database table has a composit unique index (Odometer, QueueID) with "Ignore duplicate key", and a composit cluster =index (QueuedTime, Odometer). The Odometer column (int) is involved in =both indexes.Also, the server has 4 physical CPUs with hypertheading =to 8 virtual processors. Error: 3624General message: Location: insert.c:573Expression: sdesP->m_pIndex->indindid =3D=3D =CLUSTINDSPID: 168Process ID: 2920Duplicate =key was ignored. Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: Location: insert.c:573Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTINDSPID: =168Process ID: 2920Duplicate key was ignored. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at ?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang CaoMCSD, =MCDBA"Dejan Sarka" wrote in =message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...> > I suppose =that I should have mentioned that I've already performed the> > =typical google and support.microsoft.com searches, without finding> anything> > applicable. Any other ideas?> => Sorry, not directly. Maybe you can track down what happens before this> =error, which command makes the problem? It would be nice if the problem> =would be reproducable.> > -- > Dejan Sarka, SQL Server MVP> Associate Mentor> Solid Quality Learning> More =than just Training> www.SolidQualityLearning.com> >

---

--=_NextPart_000_01B4_01C42527.F1365AC0--|||This is a multi-part message in MIME format.
--=_NextPart_000_003E_01C425F6.395B16F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Can you send me the code directly to my e-mail (just take out the ="_please_reply..." part out of the address and I will try to reproduce =the error? BTW, which versions of SQL Server and .NET Framework are you =using?
-- Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Yang Cao" <yang@.yangcao88.com> wrote in message =news:uu3i%23lUJEHA.3436@.tk2msftngp13.phx.gbl...
The following is the SqlException our code got when that happens. =What Jerry and I don't understand is that the error message "Duplicate =key was ignored" should be associated with SQL error 3604, which is only =on severity level 16 that will not throw the exception, (while error =3624 is on level 20).
The database table has a composit unique index (Odometer, QueueID) =with "Ignore duplicate key", and a composit cluster index (QueuedTime, =Odometer). The Odometer column (int) is involved in both indexes.
Also, the server has 4 physical CPUs with hypertheading to 8 virtual =processors.
Error: 3624
General message: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored. Detailed message: =ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: Location: insert.c:573
Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTIND
SPID: 168
Process ID: 2920
Duplicate key was ignored.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at =?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang Cao
MCSD, MCDBA
"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> =wrote in message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...
> > I suppose that I should have mentioned that I've already performed =the
> > typical google and support.microsoft.com searches, without finding
> anything
> > applicable. Any other ideas?
> > Sorry, not directly. Maybe you can track down what happens before =this
> error, which command makes the problem? It would be nice if the =problem
> would be reproducable.
> > -- > Dejan Sarka, SQL Server MVP
> Associate Mentor
> Solid Quality Learning
> More than just Training
> www.SolidQualityLearning.com
> >
--=_NextPart_000_003E_01C425F6.395B16F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Can you send me the code directly to my =e-mail (just take out the "_please_reply..." part out of the address and I will =try to reproduce the error? BTW, which versions of SQL Server and .NET =Framework are you using?
-- Dejan Sarka, SQL Server =MVPAssociate MentorSolid Quality LearningMore than just Traininghttp://www.SolidQualityLearning.com">www.SolidQualityLearning.com= "Yang Cao" wrote in =message news:uu3i%23lUJEHA.=3436@.tk2msftngp13.phx.gbl...
The following is the SqlException our =code got when that happens. What Jerry and I don't understand is that the =error message "Duplicate key was ignored" should be associated with SQL =error 3604, which is only on severity level 16 that will not throw the exception, =(while error 3624 is on level 20). The database table has a composit =unique index (Odometer, QueueID) with "Ignore duplicate key", and a composit =cluster index (QueuedTime, Odometer). The Odometer column (int) is =involved in both indexes.Also, the server has 4 physical CPUs with =hypertheading to 8 virtual processors. Error: 3624General message: Location: insert.c:573Expression: sdesP->m_pIndex->indindid ==3D=3D CLUSTINDSPID: 168Process ID: =2920Duplicate key was ignored. Detailed message: ELKUpdateStatusFromAnyStatus:System.Data.SqlClient.SqlException: = Location: insert.c:573Expression: sdesP->m_pIndex->indindid =3D=3D CLUSTINDSPID: 168Process ID: 2920Duplicate key was =ignored. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior =cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at =?RunCommand@.@.$$FYAXHPADPAV?$list@.PAU_PARAM@.@.V?$allocator@.PAU_PARAM@.@.@.std@.=@.@.std@.@.W4COMMANDTYPE@.@.@.Z(Int32
Yang CaoMCSD, =MCDBA"Dejan Sarka" wrote in =message news:ecsLMESJEHA.3068@.TK2MSFTNGP10.phx.gbl...> > I suppose =that I should have mentioned that I've already performed the> > =typical google and support.microsoft.com searches, without finding> anything> > applicable. Any other ideas?> => Sorry, not directly. Maybe you can track down what happens before =this> error, which command makes the problem? It would be nice if the problem> would be reproducable.> > -- > =Dejan Sarka, SQL Server MVP> Associate Mentor> Solid Quality Learning> More than just Training> www.SolidQualityLearning.com> >

---

--=_NextPart_000_003E_01C425F6.395B16F0--sql

Error: 15457, Severity: 0, State: 1

Hello,
I am seeing this error in my sql logs. There doesn't seem to be any info in the knowledge base about why this is occurring . Can someone explain this error to me and describe any possible fixes. Thanks !!
nupee,
Since it is severity 0, there is nothing to fix. I believe that this is
generated by sp_configure and probably includes a message about some setting
being changed.
Russell Fields
"nupee" <nupee@.discussions.microsoft.com> wrote in message
news:3B7489A3-DBD6-44B2-A9AF-19863809027C@.microsoft.com...
> Hello,
> I am seeing this error in my sql logs. There doesn't seem to be any info
in the knowledge base about why this is occurring . Can someone explain this
error to me and describe any possible fixes. Thanks !!

Error: 15457, Severity: 0, State: 1

Does anyone know the meaning of this error found in the
SQL Server Logs? Thank you in advance!While it says error, this message is not an error as testified by the
severity of 0; this is is an informational message only. More preciesly it
is the message:
Configuration option '%ls' changed from %ld to %ld. Run the RECONFIGURE
statement to install.
Someone must have changed a configuration option on the server.
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:4be001c3ffd6$6852b1c0$a501280a@.phx.gbl...
> Does anyone know the meaning of this error found in the
> SQL Server Logs? Thank you in advance!|||It's an informational message, not really an error message.
If you change your server properties or if you view the
server properties in Enterprise Manager, you will see this
message in the SQL error logs.
-Sue
On Mon, 1 Mar 2004 13:44:43 -0800, "Scott"
<anonymous@.discussions.microsoft.com> wrote:
>Does anyone know the meaning of this error found in the
>SQL Server Logs? Thank you in advance!

Error: 15457, Severity: 0, State: 1

Hello,
I am seeing this error in my sql logs. There doesn't seem to be any info in
the knowledge base about why this is occurring . Can someone explain this er
ror to me and describe any possible fixes. Thanks !!nupee,
Since it is severity 0, there is nothing to fix. I believe that this is
generated by sp_configure and probably includes a message about some setting
being changed.
Russell Fields
"nupee" <nupee@.discussions.microsoft.com> wrote in message
news:3B7489A3-DBD6-44B2-A9AF-19863809027C@.microsoft.com...
> Hello,
> I am seeing this error in my sql logs. There doesn't seem to be any info
in the knowledge base about why this is occurring . Can someone explain this
error to me and describe any possible fixes. Thanks !!

Error: 15457, Severity: 0, State: 1

Does anyone know the meaning of this error found in the
SQL Server Logs? Thank you in advance!While it says error, this message is not an error as testified by the
severity of 0; this is is an informational message only. More preciesly it
is the message:
Configuration option '%ls' changed from %ld to %ld. Run the RECONFIGURE
statement to install.
Someone must have changed a configuration option on the server.
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:4be001c3ffd6$6852b1c0$a501280a@.phx.gbl...
> Does anyone know the meaning of this error found in the
> SQL Server Logs? Thank you in advance!|||It's an informational message, not really an error message.
If you change your server properties or if you view the
server properties in Enterprise Manager, you will see this
message in the SQL error logs.
-Sue
On Mon, 1 Mar 2004 13:44:43 -0800, "Scott"
<anonymous@.discussions.microsoft.com> wrote:

>Does anyone know the meaning of this error found in the
>SQL Server Logs? Thank you in advance!

Error/Failure Audit in Event Logs (SQL 2005 Express) [Advanced Services]

Q1: Any way to control which db loads when, and perhaps stop this error from happening? Again- when all is said and done, the report server functions, and I am able to access just fine.

Q2: What kind of recovery is being referred to? Given the message type- I assume it's nothing of concern- probably more to do with a system that doesn't run all the time.

Okay- so I get these two event messages each time I boot.

Below are two error message I see daily with each system boot- the services mentioned do "actually" function, and are running- as not 10 seconds after these messages are logged, the successfully loaded messages appear. It's almost as if report services tries to connect before the databases are up and running.

Basically the sequence (today) was:

1. 05:49:01 Failure Audit (MSSQL$SQLEXPRESS)

2. 05:49:01 Error (Report Server Windows Service (SQLEXPRESS)

3. 05:49:02 Recovery is complete. (EventID 3408 MSSQL$SQLEXPRESS)

4. 05:49:06 Starting up database 'ReportServer'

5. 05:49:09 Server Resumed execution (MSSQL$SQLEXPRESS)

I'm assuming based on the events that Report Server Service attempts to connect to the ReportServer database before it's actually started. Doesn't really explain the failure audit-

1. Failure Audit:

Event Type: Failure Audit
Event Source: MSSQL$SQLEXPRESS
Event Category: (4)
Event ID: 18456
Date: 8/9/2007
Time: 05:49:01
User: <MACHINENAME>\<LOCALUSER>
Computer: <MACHINENAME>
Description:
Login failed for user '<MACHINENAME>\<LOCALUSER>'.

[CLIENT: <local machine>]

This is almost immediately followed by this (which I consider a no-brainer, considering the above):

2. Error:

Event Type: Error
Event Source: Report Server Windows Service (SQLEXPRESS)
Event Category: Management
Event ID: 107
Date: 8/9/2007
Time: 05:49:01
User: N/A
Computer: <MACHINENAME>
Description:
Report Server Windows Service (SQLEXPRESS) cannot connect to the report server database.

The master database is started first, you cannot control the order in which the database are started up. if the users tries to connect to the database he will be authenticated by SQL Server and directly tries to change the default database or if explicitly mentioned in the connection string connect to the database. if the database is not yet started he will get a login failed (although authenticated but he was not able to change the database context). if you have these problems, try to set the dependency of Report Server to the SQL Service to make sure that Reporting Server will only be started if the SQL Server Service has been. This might help you getting some additional time for the server to make a regular recovery (which is normal if the database / server was not shutdown properly)

Jens K. Suessmeyer

http://www.sqlserver2005.de

error...Run RECON....what does this mean?

I am getting this in my SQL Server logs:
spid54
Configuration option 'show advanced options' changed from 1
to 1. Run the RECON
What does this mean? I have a MS Project Server pointing
to this DB server but the data cannot be loaded. I wonder
if this is the problem?
The next line down says:
spid54
Error: 15457, Severity: 0, State:1
.Todd, you only have to post the question once...
<anonymous@.discussions.microsoft.com> wrote in message
news:fd4001c43e8f$bfbbfc30$a001280a@.phx.gbl...
> I am getting this in my SQL Server logs:
> spid54
> Configuration option 'show advanced options' changed from 1
> to 1. Run the RECON
> What does this mean? I have a MS Project Server pointing
> to this DB server but the data cannot be loaded. I wonder
> if this is the problem?
> The next line down says:
> spid54
> Error: 15457, Severity: 0, State:1
> .