Hi,
I have a lot of databases in my server, but the point
here is that I cannot see none. When Enterprise Manager
starts there's an error appearing:
snap-in failed to initialize
Name: Microsoft SQL Enterprise Manager
CLSID: 00100100-1816-11D0-8EF5-00AA0062C58F
After this error, in the Enterprise Manager my databases
have disappeared.
Is there a way to recover from this? I really need
somebody's help, please.
Thanks in advance.
Renato VizuetTry to re-register the server.
>--Original Message--
>Hi,
>I have a lot of databases in my server, but the point
>here is that I cannot see none. When Enterprise Manager
>starts there's an error appearing:
> snap-in failed to initialize
> Name: Microsoft SQL Enterprise Manager
> CLSID: 00100100-1816-11D0-8EF5-00AA0062C58F
>After this error, in the Enterprise Manager my databases
>have disappeared.
>Is there a way to recover from this? I really need
>somebody's help, please.
>Thanks in advance.
>
>Renato Vizuet
>.
>
Showing posts with label recover. Show all posts
Showing posts with label recover. Show all posts
Wednesday, March 28, 2012
I dont have any backup of my database, but I have the mdf's and ldf's files
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
=B7"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
=B7Error: 823, Severity: 24, State: 6
=B7"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
=B7Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
=B7Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?=20
Thank you very much...:DSeems that the "magic" tool didnt work, database seem to be (physical)
corrupt.
Offset 0000000000000000 failure doent sounds good to me.
Jens Suessmeyer.
"in_the_middle" <mediodia@.gmail.com> schrieb im Newsbeitrag
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||I agree with Jens. You could try to open a case with MS support, but I have
little hope that they
can help you as the database files seem to be, at least partially, overwritt
en.
(I've listed one "repair/recovery" tool in my links page on my web site, but
I wouldn't have much
hope for that either...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
files...
The content of the tables is important...But it is more important for
me recovering the Schema...(tables, stored procedures, indexes)...Do
you know any other tool which can help me to do this?
Thank you in advanced!|||I'm afraid that MSSQLRecovery is the only tool I know of. Sorry... :-(
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114004870.150171.315500@.f14g2000cwb.googlegroups.com...
> you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
> files...
> The content of the tables is important...But it is more important for
> me recovering the Schema...(tables, stored procedures, indexes)...Do
> you know any other tool which can help me to do this?
> Thank you in advanced!
>|||You've had it I'm afraid - the database is physically corrupt (i.e. the OS
can't read the file from the disk) right at the start. You may be able to
get a data recovery service to salvage raw data from the drive, but that's
your only hope in this kind of hardware failure - there's nothing Product
Support can do to help.
Good luck.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||Thank you very much for all your attentionsql
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
=B7"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
=B7Error: 823, Severity: 24, State: 6
=B7"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
=B7Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
=B7Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?=20
Thank you very much...:DSeems that the "magic" tool didnt work, database seem to be (physical)
corrupt.
Offset 0000000000000000 failure doent sounds good to me.
Jens Suessmeyer.
"in_the_middle" <mediodia@.gmail.com> schrieb im Newsbeitrag
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||I agree with Jens. You could try to open a case with MS support, but I have
little hope that they
can help you as the database files seem to be, at least partially, overwritt
en.
(I've listed one "repair/recovery" tool in my links page on my web site, but
I wouldn't have much
hope for that either...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
files...
The content of the tables is important...But it is more important for
me recovering the Schema...(tables, stored procedures, indexes)...Do
you know any other tool which can help me to do this?
Thank you in advanced!|||I'm afraid that MSSQLRecovery is the only tool I know of. Sorry... :-(
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114004870.150171.315500@.f14g2000cwb.googlegroups.com...
> you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
> files...
> The content of the tables is important...But it is more important for
> me recovering the Schema...(tables, stored procedures, indexes)...Do
> you know any other tool which can help me to do this?
> Thank you in advanced!
>|||You've had it I'm afraid - the database is physically corrupt (i.e. the OS
can't read the file from the disk) right at the start. You may be able to
get a data recovery service to salvage raw data from the drive, but that's
your only hope in this kind of hardware failure - there's nothing Product
Support can do to help.
Good luck.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||Thank you very much for all your attentionsql
I dont have any backup of my database, but I have the mdf's and ldf's files
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
=B7"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
=B7Error: 823, Severity: 24, State: 6
=B7"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
=B7Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
=B7Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas? Thank you very much...:DSeems that the "magic" tool di´dn´t work, database seem to be (physical)
corrupt.
Offset 0000000000000000 failure doen´t sounds good to me.
Jens Suessmeyer.
"in_the_middle" <mediodia@.gmail.com> schrieb im Newsbeitrag
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
·"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
·Error: 823, Severity: 24, State: 6
·"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
·Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
·Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||I agree with Jens. You could try to open a case with MS support, but I have little hope that they
can help you as the database files seem to be, at least partially, overwritten.
(I've listed one "repair/recovery" tool in my links page on my web site, but I wouldn't have much
hope for that either...)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
·"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
·Error: 823, Severity: 24, State: 6
·"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
·Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
·Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
files...:( :(
The content of the tables is important...But it is more important for
me recovering the Schema...(tables, stored procedures, indexes)...Do
you know any other tool which can help me to do this?
Thank you in advanced!|||I'm afraid that MSSQLRecovery is the only tool I know of. Sorry... :-(
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114004870.150171.315500@.f14g2000cwb.googlegroups.com...
> you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
> files...:( :(
> The content of the tables is important...But it is more important for
> me recovering the Schema...(tables, stored procedures, indexes)...Do
> you know any other tool which can help me to do this?
> Thank you in advanced!
>|||You've had it I'm afraid - the database is physically corrupt (i.e. the OS
can't read the file from the disk) right at the start. You may be able to
get a data recovery service to salvage raw data from the drive, but that's
your only hope in this kind of hardware failure - there's nothing Product
Support can do to help.
Good luck.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
·"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
·Error: 823, Severity: 24, State: 6
·"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
·Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
·Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||Thank you very much for all your attention
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
=B7"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
=B7Error: 823, Severity: 24, State: 6
=B7"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
=B7Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
=B7Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas? Thank you very much...:DSeems that the "magic" tool di´dn´t work, database seem to be (physical)
corrupt.
Offset 0000000000000000 failure doen´t sounds good to me.
Jens Suessmeyer.
"in_the_middle" <mediodia@.gmail.com> schrieb im Newsbeitrag
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
·"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
·Error: 823, Severity: 24, State: 6
·"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
·Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
·Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||I agree with Jens. You could try to open a case with MS support, but I have little hope that they
can help you as the database files seem to be, at least partially, overwritten.
(I've listed one "repair/recovery" tool in my links page on my web site, but I wouldn't have much
hope for that either...)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
·"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
·Error: 823, Severity: 24, State: 6
·"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
·Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
·Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
files...:( :(
The content of the tables is important...But it is more important for
me recovering the Schema...(tables, stored procedures, indexes)...Do
you know any other tool which can help me to do this?
Thank you in advanced!|||I'm afraid that MSSQLRecovery is the only tool I know of. Sorry... :-(
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114004870.150171.315500@.f14g2000cwb.googlegroups.com...
> you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
> files...:( :(
> The content of the tables is important...But it is more important for
> me recovering the Schema...(tables, stored procedures, indexes)...Do
> you know any other tool which can help me to do this?
> Thank you in advanced!
>|||You've had it I'm afraid - the database is physically corrupt (i.e. the OS
can't read the file from the disk) right at the start. You may be able to
get a data recovery service to salvage raw data from the drive, but that's
your only hope in this kind of hardware failure - there's nothing Product
Support can do to help.
Good luck.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegroups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
·"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
·Error: 823, Severity: 24, State: 6
·"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
·Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
·Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D|||Thank you very much for all your attention
I dont have any backup of my database, but I have the mdf's and ldf's files
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
=B7"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
=B7Error: 823, Severity: 24, State: 6
=B7"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
=B7Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
=B7Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?=20
Thank you very much...:D
Seems that the "magic" tool didnt work, database seem to be (physical)
corrupt.
Offset 0000000000000000 failure doent sounds good to me.
Jens Suessmeyer.
"in_the_middle" <mediodia@.gmail.com> schrieb im Newsbeitrag
news:1114002784.429829.178480@.f14g2000cwb.googlegr oups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D
|||I agree with Jens. You could try to open a case with MS support, but I have little hope that they
can help you as the database files seem to be, at least partially, overwritten.
(I've listed one "repair/recovery" tool in my links page on my web site, but I wouldn't have much
hope for that either...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegr oups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D
|||you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
files...
The content of the tables is important...But it is more important for
me recovering the Schema...(tables, stored procedures, indexes)...Do
you know any other tool which can help me to do this?
Thank you in advanced!
|||I'm afraid that MSSQLRecovery is the only tool I know of. Sorry... :-(
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114004870.150171.315500@.f14g2000cwb.googlegr oups.com...
> you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
> files...
> The content of the tables is important...But it is more important for
> me recovering the Schema...(tables, stored procedures, indexes)...Do
> you know any other tool which can help me to do this?
> Thank you in advanced!
>
|||You've had it I'm afraid - the database is physically corrupt (i.e. the OS
can't read the file from the disk) right at the start. You may be able to
get a data recovery service to salvage raw data from the drive, but that's
your only hope in this kind of hardware failure - there's nothing Product
Support can do to help.
Good luck.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegr oups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D
|||Thank you very much for all your attention
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
=B7"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
=B7Error: 823, Severity: 24, State: 6
=B7"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
=B7Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
=B7Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?=20
Thank you very much...:D
Seems that the "magic" tool didnt work, database seem to be (physical)
corrupt.
Offset 0000000000000000 failure doent sounds good to me.
Jens Suessmeyer.
"in_the_middle" <mediodia@.gmail.com> schrieb im Newsbeitrag
news:1114002784.429829.178480@.f14g2000cwb.googlegr oups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D
|||I agree with Jens. You could try to open a case with MS support, but I have little hope that they
can help you as the database files seem to be, at least partially, overwritten.
(I've listed one "repair/recovery" tool in my links page on my web site, but I wouldn't have much
hope for that either...)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegr oups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D
|||you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
files...
The content of the tables is important...But it is more important for
me recovering the Schema...(tables, stored procedures, indexes)...Do
you know any other tool which can help me to do this?
Thank you in advanced!
|||I'm afraid that MSSQLRecovery is the only tool I know of. Sorry... :-(
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114004870.150171.315500@.f14g2000cwb.googlegr oups.com...
> you mean MSSQLRecovery ... I have tried it... It found 0 corrupt
> files...
> The content of the tables is important...But it is more important for
> me recovering the Schema...(tables, stored procedures, indexes)...Do
> you know any other tool which can help me to do this?
> Thank you in advanced!
>
|||You've had it I'm afraid - the database is physically corrupt (i.e. the OS
can't read the file from the disk) right at the start. You may be able to
get a data recovery service to salvage raw data from the drive, but that's
your only hope in this kind of hardware failure - there's nothing Product
Support can do to help.
Good luck.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"in_the_middle" <mediodia@.gmail.com> wrote in message
news:1114002784.429829.178480@.f14g2000cwb.googlegr oups.com...
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:?
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:D
|||Thank you very much for all your attention
I dont have any backup of my database, but I have the mdfs and ldfs files
Im trying to recover my database using the mdf and ldf files.
I dont have any backup and i have recovered two of the mdf files using
a tool which "discovers" deleted files after hard drive formatting...
It sounds cool, isnt it...:? :(
Obviously, i get a "suspect" message when the server starts and the log
file says this kind of things:
"Full Path\Name.MDF is not a primary database file." (This is one of
the files repaired using the magic tool.
Error: 823, Severity: 24, State: 6
"I/O error (torn page) detected during read at offset
0000000000000000 in file 'Full Pathi\Name2.mdf'... Name2.mdf is the
second file
Device activation error. The physical file name 'Full Path\Name2.mdf'
may be incorrect.
When i try to execute the command "DBCC CHECKDB ('Database_Name') WITH
PHYSICAL_ONLY" i get the following message :
Could not open FCB for invalid file ID 0 in database 'Logs'.
Do you have any ideas?
Thank you very much...:DIt sounds like the files are probably damaged beyond repair, or at
least beyond the sort of repairs that you can do without help from
Microsoft. If the contents of the database are valuable enough, I would
call MS to see if they can help you to recover the data, otherwise
you'll probably have to recreate everything.
And (obviously) you should plan a backup/restore strategy and a source
control system for your database code, to prevent any similar problems
in the future.
Simon|||Probably, thats what i'll do (call Microsoft asking for help help
help...:D )...
I swear this is the first time i dont plan a backup/restore
strategy... The database was configured a long time ago and I didnt
realize to do it...but i promise ill do the next time...:D
Anyway, I have run the demo tool MSSQLRecovery. This program analyze a
mdf file and recovers corrupt data. It has checked the tables, stored
procedures, indexes, relationships... and says that everything is
OK...but it doesnt generate any report...
Do you know any tool which recovers tables, stored procedures using the
primary mdf file?
Thank you in advanced
Subscribe to:
Posts (Atom)