Error 3624 - SQL-DMO(ODBC SQLState:HY000)

My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:

> My ProjectServer database suddenly became (suspect), the log file increase
d
> like balloon 49.9GB, I don't know exactly what was the size before. The md
f
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>

Error 3624 - SQL-DMO(ODBC SQLState:HY000)

My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================ (After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>

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.
>>
>>
>.
>

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[vbcol=seagreen]
>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:
can[vbcol=seagreen]
the[vbcol=seagreen]
while
>.
>

Error 3624

I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?
|||Yes. The two errors are exactly as described. I looked at the dump file and the query was a SELECT against a table with historical data only (in this instance anyway). Basically it is a sales history table and the query sums the sales for a particular salesman month to date. The table is only updated during the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?

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:
can[vbcol=seagreen]
the[vbcol=seagreen]
while[vbcol=seagreen]
>.
>

Error 3624

I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2
136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?|||Yes. The two errors are exactly as described. I looked at the dump file and
the query was a SELECT against a table with historical data only (in this in
stance anyway). Basically it is a sales history table and the query sums the
sales for a particular salesman month to date. The table is only updated du
ring the end of day processing, when no one else is using he system.
"TJ" <tunj@.hotmail.com> wrote in message news:uzWMgSlsEHA.2196@.TK2MSFTNGP14.
phx.gbl...
Is your situation as described in the symptoms section of the KB?
Tunji
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message news:ub5LMGjsEHA.2
136@.TK2MSFTNGP11.phx.gbl...
I see in my SQL2K Server logs the following error, at least once a day if
not more often:
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
DBCC CHECKDB reports all is well with all of the databases on this server.
The fix outlined in KB317852 gives (almost) the exact same message, but it
says that was fixed in SP3 and I'm using SP3a, which was installed *before*
any of my own databases were created. I have an Access 97 Front End, with
the Default Record Locking set to No Locks. KB827714 seems to address a
similar issue. Does this sound like the problem? Is it something serious
where I should consider the 827714 hotfix? Or should I just ignore it and
wait for the next SP?