Hi!

When I try Attach a DB I have this error:

Error: 3624
Location: recovery.c:2440
Expression: seenCKptEnd
SPID: 51
Process ID: 1344


Any idea ?


Excuse my English.
Thanks in advance.

Joao Pinto

Which version and Service Pack level are you on?

And has the DB been detached using sp_detach_db or Enterprise Manager (which
uses sp_detach_db behind the scenes)? If you try to attach a database that
has not been explicitly detached, it might not work.

--
Jacco Schalkwijk
SQL Server MVP

"Joao Pinto" <joao.pi (AT) mail (DOT) telepac.pt> wrote

I'm getting the same error. I've tried the suggested steps for
recovering a database, but the problem seems to be a real bug. Any
updates on this issue?

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

So, did you detach the database first? Are you on the same version and service pack? Attach should work if you
are on the same version (and service pack for system databases) and you first detached the database. If not,
you should open a case with MS PSS.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/


"David Rairigh" <drairigh (AT) allinview (DOT) com> wrote

Actually, the order of events was:
<OL>
<LI>Was working on db in evening
<LI>Following morning, system drive was full from another transfer
process when the system re-booted.
<LI>When SQL Server started, <database> was marked as suspect.
<LI>Error was same as reported above.
<LI>Tried to reset the status using sp_ResetStatus
<LI>Even after resetting status and re-starting system, continued
received the subject error.
<LI>Tried detaching. Database detached, with error (don't remember
specific error)
<LI>Couldn't re-attach db, received the subject error
<LI>Tried updating to sp3, tried different machine, same error.
</OL>
Finally, gave up and re-scripted the database. Haven't got time to do
research on it. Now I'm simply insuring that I have backups of the dbs
in development <i>and</i> production.<br>
I don't know that the low disk space caused the problem, but it seems
the most like culprit as the <i>start</i> of the problem.



*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!