Sunday, February 26, 2012

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
>> All,
>> I have the below problem while attaching the database,
can
>> any one assist.
>> Thanks in advance.
>> --Error Details
>> Microsoft SQL-DMO(ODBC SQLState-HY000)
>> Error 3624
>> Location : recovery.C:2014
>> Expression: Curr-->log_length >0
>> SPID :53
>> ProcessorId: 1064
>> below is the last lines from Error Log
>> 2004-06-01 10:27:14.45 spid53 Stack Signature for
the
>> dump is 0x9A8706F6
>> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
>> File: <recovery.c>, line=2014
>> Failed Assertion = 'curr->log_length > 0'.
>> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
>> 20, State: 1.
>> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
>> 23, State: 7
>> 2004-06-01 10:27:15.93 spid53 An error occurred
while
>> processing the log for database 'UPSSISGR'..
>>
>> ...Mukund.R.L.
>>
>>
>.
>

No comments:

Post a Comment