Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts

Thursday, March 29, 2012

ERROR 926 dATABSE msdb CANNOT OPEN

Hi paul
we are using MS SQL Server2000 when we try to take backup we are getting
this Error " Error 926 Data base MSDB cannot Open it has been marked
suspect by recovery"
Please if you solution to solve this problem let us know.
Thanks in advance
S KaliyanSeems your msdb is corrupted. Restore msdb from your mort recent backup(s).
But do investigate why
msdb went corrupt first:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"S Kaliyan" <as_kalyan@.patel-india.com> wrote in message
news:Oqi5ek3MFHA.3788@.tk2msftngp13.phx.gbl...
> Hi paul
> we are using MS SQL Server2000 when we try to take backup we are getting
> this Error " Error 926 Data base MSDB cannot Open it has been marked
> suspect by recovery"
> Please if you solution to solve this problem let us know.
> Thanks in advance
> S Kaliyan
>
>

Tuesday, March 27, 2012

error 9004, severity 21, state 10

saw one of my database went suspect, I tried to load a restore from the backup, but this was going on for ever. I cancelled out, deleted the suspect database. Created a new database and tried to restore from the old backup, but this was going on for ever. It will not restore. I cannot stop and start mssql service on this server as it is production. what else can I do.Q1 On trying to restore from the old backup, this goes on forever. I cannot stop and start mssql service on this server as it is production. What else can I do?

A1 If the issue amounts to the Db remaining in 'Loading' status "forever"; it may simply be that the DB has not been recovered following the restore.

To test this possibility, one would execute a statement similar to the following:

Restore DataBase [DBName] With Recovery

Question I
Can the DB be restored to a development server successfully using the "old backup"?sql

Error 9004 attaching a database

I've been given a database backup in the form of an .mdf file, a bunch
of .ndf files, and a .log file. When I try to attach the .mdf file in
Server Management Studio, I get error 9004, An error occurred while
processing the log.
Any suggestions?
Phil Hibbs.Phil,
Kevin Farlee's answer has helped a couple of people with your problem.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193140510.353843.250240@.y27g2000pre.googlegroups.com...
> I've been given a database backup in the form of an .mdf file, a bunch
> of .ndf files, and a .log file. When I try to attach the .mdf file in
> Server Management Studio, I get error 9004, An error occurred while
> processing the log.
> Any suggestions?
> Phil Hibbs.
>|||On 23 Oct, 13:31, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Kevin Farlee's answer has helped a couple of people with your problem.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
Hm, looked promising, but when I try to "bring online" the database
with the files replaced, I get a load of errors in this form:
E:\data\data_file_09.ndf is not a primary database file
I have a .mdf file and 26 .ndf files, it looks like the creation of
the empty database is creating these files in a different way to the
original database.
Phil Hibbs.|||Phil,
Did you first create the 26 ndf files in your database to be replaced before
trying to copy the files into place?
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193148065.531336.193770@.e34g2000pro.googlegroups.com...
> On 23 Oct, 13:31, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Kevin Farlee's answer has helped a couple of people with your problem.
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
> Hm, looked promising, but when I try to "bring online" the database
> with the files replaced, I get a load of errors in this form:
> E:\data\data_file_09.ndf is not a primary database file
> I have a .mdf file and 26 .ndf files, it looks like the creation of
> the empty database is creating these files in a different way to the
> original database.
> Phil Hibbs.
>|||On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Did you first create the 26 ndf files in your database to be replaced before
> trying to copy the files into place?
Yep. I made a big CREATE DATABASE statement with the .mdf and all
the .ndf files specified in it.
Phil Hibbs.|||On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Did you first create the 26 ndf files in your database to be replaced before
> trying to copy the files into place?
Yep. I made a big CREATE DATABASE statement with the .mdf and all
the .ndf files specified in it.
Phil Hibbs.|||Phil,
I understand that you are using SQL Server 2005, since you mention
Management Studio. I have tested and not been able to duplicate your
problem. When you use SSMS to do the attach, have you pressed the Script
command at the top of the panel. This will provide an exact script of the
commands to be run. If you do that, perhaps you will see something helpful.
Or, you can post it here for review.
Obviously something is different between our setups. I am running SQL
Server 2005 SP2. Are you also running SP2? I ask because SP2 fixed some
Management Studio problems and you should update to it (plus some hotfixes)
if you have not done so.
This describe my patch level:
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
For more recent fixes, see also: http://support.microsoft.com/kb/937137/LN/
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193222031.764752.35650@.v29g2000prd.googlegroups.com...
> On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Did you first create the 26 ndf files in your database to be replaced
>> before
>> trying to copy the files into place?
> Yep. I made a big CREATE DATABASE statement with the .mdf and all
> the .ndf files specified in it.
> Phil Hibbs.
>|||On 25 Oct, 17:34, "Russell Fields" <russellfie...@.nomail.com> wrote:
> I have tested and not been able to duplicate your
> problem.
I suspect that is because you don't have the same .mdf and .ndf
and .log files that I have.
Phil Hibbs.|||Phil, No doubt about that. Sorry this did not help. - RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193761341.010344.78000@.k79g2000hse.googlegroups.com...
> On 25 Oct, 17:34, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> I have tested and not been able to duplicate your
>> problem.
> I suspect that is because you don't have the same .mdf and .ndf
> and .log files that I have.
> Phil Hibbs.
>

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, d
atabase ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produ
ce this message.
Action
This message can usually be ignored; however, if you receive repeated messag
es where the wait time
increases, it may indicate an internal server problem. Contact your system a
dministrator. The system
administrator should check the waittype, waittime, lastwaittype, and the wai
tresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...[vb
col=seagreen]
> I have one database that I keep getting an error 845: Time out ocurred whi
le
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (othe
r
> than normal data entry) in over a year. Does anyone have any ideas of wha
t
> should be checked?
> Thanks in advance
>[/vbcol]

Monday, March 26, 2012

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advance
Did you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>
sql

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>

Thursday, March 22, 2012

Error 8198 when trying to backup database

Hello,

My network team accidentally deleted and had to recreate the WNS database on the network, which posed all sorts of problems for us. Most everything is corrected, however I get the following error message in the failure of the database backup maintenance plan:

-----------------------
The job failed. Unable to determine if the owner (ANCONY\COgnos) of job DB Backup Job for DB Maintenance Plan '6pm Nightly Production Backup' has server access (reason: Could not obtain information about Windows NT group/user 'ANCONY\COgnos'. [SQLSTATE 42000] (Error 8198)).
-----------------------

I tried even adding this user into SQL Sever with full rights and it still did not work. It worked fine before hundreds of times, and like I said only stopped working when my network team did some thing on WNS.

Does anyone know what may be causing this. Is there something that they may have to add back to the network?

Any help or direction for additional research is greatly appreciated.

Thanks.

RodneyI did find that I could change the jobs to use the "SA" owner instead and it looks like it is working, however things were running perfectly fine before under the 'ancony\Cognos' user, I can't figure out why it would stop working....

Monday, March 19, 2012

Error 64 while backup TL onto NAS

Dear All,
I have a problem that I cannot seem to find much info on. I am backing up
SQL 2000 Transaction logs onto a network share (NAS). This share is
connected to the SQL server by a gigabit switch. When backing up the
transactions logs overnight - I find that the SQL server reports errors
"Operating System error 64 (The specified network name is no longer
available). Error 15457 Severity:0, State:1 on large logs (over 1Gb) - it
seems to backup smaller logs ok.
The SQL server is up to date with the SP3a as are the servers (Windows 2K -
SP4). The Transaction logs are 1Gb or over - some are 4Gb+ (this is a
back-end DB for a large web site).
Can someone point me in the right direction please.
PS. I have applied the MS KB813130 hot fix - this has had no effect.
Thanks
Andrew.Andrew,
This suggests that you are overrunning the ability of the target machine to
keep up with your request. We had problems with this at one time (and are
sneaking back up on it again.) Here are a couple posts from Google that
might help you.
http://tinyurl.com/wtm3
http://tinyurl.com/wtmb Jasper Smith, MVP wrote this response about RAID5
drives.
Russell Fields
"andrew" <andrew_loftus@.hotmail.com> wrote in message
news:%23G2XEPRtDHA.1224@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I have a problem that I cannot seem to find much info on. I am backing up
> SQL 2000 Transaction logs onto a network share (NAS). This share is
> connected to the SQL server by a gigabit switch. When backing up the
> transactions logs overnight - I find that the SQL server reports errors
> "Operating System error 64 (The specified network name is no longer
> available). Error 15457 Severity:0, State:1 on large logs (over 1Gb) - it
> seems to backup smaller logs ok.
> The SQL server is up to date with the SP3a as are the servers (Windows
2K -
> SP4). The Transaction logs are 1Gb or over - some are 4Gb+ (this is a
> back-end DB for a large web site).
> Can someone point me in the right direction please.
> PS. I have applied the MS KB813130 hot fix - this has had no effect.
> Thanks
> Andrew.
>|||Hi Andrew,
My name is Michael and I would like to thank you for using Microsoft
newsgroup.
Before you troubleshoot the SQL Server, I would like you to check if the
network configration is correct and if the status of the network is normal
on your side when the error occurred. I would like to try excluding the
network reason for this problem so that we can narrow down this issue on
SQL Server.
Based on my research, there is a known issue that if the database size is
big, such as 20 GB, and using a network share name for the backup file, it
can fail with Operating System error 64 (The specified network name is no
longer available.) or 121 (The semaphore timeout period has expired.) when
multiple files are used. The workaround is to use the file path instead of
the network share name for the backup file(s).
Does it solve your problem? If not, I would like you to provide more
information so that I can perform further research.
1. How is the issue going on your side now? Did the problem occur before?
Does the problem occur again? Does it occur randomly?
2. Please provide the Sqldiag.txt (by default located in \Mssql\Log) using
Sqldiag utility (Sqldiag.exe by default located in C:\Program
Files\Microsoft SQL Server\MSSQL\Binn). If you are unable to find the
Sqldiag.exe, please search and run the utility. Then please search the
Sqldiag.txt file and provide it to me at v-yshao@.microsoft.com
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident to
troubleshoot this further. If you need any help in this regard, please let
me know.
I am standing by for your response.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Michael,
Thank you for the reply.
I seem to be able to backup the Tlogs to the local disk and only have the
problem when trying to backup to the N/W share. I was backing up to local
disk and have recently purchased this NAS to backup onto (over £3,000) - the
errors occured when using this NAS.
My Tlog files are no bigger than 6Gb at the moment and it is only the bigger
ones (over 1Gb) that seem to give the error. I assume MS software can handle
this kind of transfer with proper "handshaking" to ensure the share does not
get swamped with data it cannot handle. The NAS is a DELL 725n with "Windows
2000" powered software. The disks are configured in a RAID5 array. This
problem does occur on a regular daily basis.
Thanks
Andrew.
I have emailed you the SQLDIAG.TXT seperatly to your email address.
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:EX4O1RYtDHA.2072@.cpmsftngxa06.phx.gbl...
> Hi Andrew,
> My name is Michael and I would like to thank you for using Microsoft
> newsgroup.
> Before you troubleshoot the SQL Server, I would like you to check if the
> network configration is correct and if the status of the network is normal
> on your side when the error occurred. I would like to try excluding the
> network reason for this problem so that we can narrow down this issue on
> SQL Server.
> Based on my research, there is a known issue that if the database size is
> big, such as 20 GB, and using a network share name for the backup file, it
> can fail with Operating System error 64 (The specified network name is no
> longer available.) or 121 (The semaphore timeout period has expired.) when
> multiple files are used. The workaround is to use the file path instead
of
> the network share name for the backup file(s).
> Does it solve your problem? If not, I would like you to provide more
> information so that I can perform further research.
> 1. How is the issue going on your side now? Did the problem occur before?
> Does the problem occur again? Does it occur randomly?
> 2. Please provide the Sqldiag.txt (by default located in \Mssql\Log) using
> Sqldiag utility (Sqldiag.exe by default located in C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn). If you are unable to find the
> Sqldiag.exe, please search and run the utility. Then please search the
> Sqldiag.txt file and provide it to me at v-yshao@.microsoft.com
> Also, such issues tend to be complex and take up extensive research time.
> I'd like to set your expectations that it may take a while for us to help
> you narrow down the problem and we may eventually redirect you to PSS to
> continue working with a dedicated Support Professional. If this is
> critical, I'd recommend contacting PSS and opening a Support incident to
> troubleshoot this further. If you need any help in this regard, please let
> me know.
> I am standing by for your response.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Hi Andrew,
Thanks for your response. Please perform the following tests on your side
so that I can narrow down this issue.
1. Please perform the problematic backup job manually to see if the problem
also occurs.
2. Have you tried the suggestions in my previous post? Please try to use
the file path instead of the network share name for the backup file(s) on
the destination computer. Can you backup the transaction logs?
3. Please try to change the Write Policy for the RAID controller from
Writethru to Writeback. Does it solve your problem?
If not,please provide the following information so that I can perform
further research.
1. When the backup problem occurred, could you connect to the destination
server using the server name?
2. You wrote "it is only the bigger ones (over 1GB) that seem to give the
error." I am unable to find related information on this in the sqldiag.txt
file. Why do you think so, can you describe it in detail?
3.Do you mean that you are unable to backup transaction logs (over 1GB)
using the server name in any situation?
I am standing by for your response.
Thank you,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Michael,
Good morning and thanks for your last reply.
1. Yes, the error happens when a manual backup is done.
2. I backed up upto the local drive E:\ - is this what you mean by file
path - or do you mean mapping a drive letter to the share and backing up to
the drive letter?
3. I have changed the RAID system on the NAS from RAID5 to RAID1, I am
waiting for results but it looks good so far, in that a manual backup has
completed where it did not before the conversion. I will know tommorow for
good.
If this does solve the problem - it surely means that there is no
handshaking/communication between two computers on the network - so one can
easily "swamp" the other with data and get an error message. I would have
thought MS Windows was able to cope with this sinario - any comments?
I will let you know tommorow when my nightly backup has completed, I am
quietly hopeful.
Thanks again
Andrew.
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:7rULUm8tDHA.984@.cpmsftngxa06.phx.gbl...
> Hi Andrew,
> Thanks for your response. Please perform the following tests on your side
> so that I can narrow down this issue.
> 1. Please perform the problematic backup job manually to see if the
problem
> also occurs.
> 2. Have you tried the suggestions in my previous post? Please try to use
> the file path instead of the network share name for the backup file(s) on
> the destination computer. Can you backup the transaction logs?
> 3. Please try to change the Write Policy for the RAID controller from
> Writethru to Writeback. Does it solve your problem?
> If not,please provide the following information so that I can perform
> further research.
> 1. When the backup problem occurred, could you connect to the destination
> server using the server name?
> 2. You wrote "it is only the bigger ones (over 1GB) that seem to give the
> error." I am unable to find related information on this in the sqldiag.txt
> file. Why do you think so, can you describe it in detail?
> 3.Do you mean that you are unable to backup transaction logs (over 1GB)
> using the server name in any situation?
> I am standing by for your response.
> Thank you,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Hi Andrew,
Thanks for your response. I am glad to hear that the manual backup works
after the conversion. Hope the backup job also works fine.
The file path which I mentioned in my previous post indicated the local
path. Generally, it is better to backup the database to the local machine
and run some jobs to copy the backup files to the remote machine. In my
opinion, it is a safer solution.
Also, I am not quite clear your concerns about handshaking/communication on
the network. What does the handshaking/communication indicate? What do you
mean by " swamp"? Can you describe your concerns in detail?
I am standing by for the result on your side.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Michael,
Thanks for your help - all seems to work now I have changed the NAS to RAID
0 from RAID 5.
My concerns are as you mention - surely one windows computer on the network
cannot "swamp" another - surely there is communication between the
computers - like hold on a minute with that data while I just commit what I
have to disk - ok ready now please send the next chunk.
Andrew.
"Michael Shao [MSFT]" <v-yshao@.online.microsoft.com> wrote in message
news:Aq%23G2XLuDHA.1532@.cpmsftngxa06.phx.gbl...
> Hi Andrew,
> Thanks for your response. I am glad to hear that the manual backup works
> after the conversion. Hope the backup job also works fine.
> The file path which I mentioned in my previous post indicated the local
> path. Generally, it is better to backup the database to the local machine
> and run some jobs to copy the backup files to the remote machine. In my
> opinion, it is a safer solution.
> Also, I am not quite clear your concerns about handshaking/communication
on
> the network. What does the handshaking/communication indicate? What do you
> mean by " swamp"? Can you describe your concerns in detail?
> I am standing by for the result on your side.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||Hi Andrew,
Thanks for your update. It is great that the backup job also works fine.
Generally, when taking backup copy on the network, some protocol will be
used. There are certain Timout and Retry mechanism defined in the protocol.
If there is still no response from the target after using the Timout and
Retry mechanism, the error will occur.
Thanks for using MSDN newsgroup.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Sunday, March 11, 2012

Error 5171 when attaching database

I am having an issue attaching a database. I am getting Error 5171 - ls is
not a primary database file.
We did not have a backup of a database, so I am not able to restore a
backup. The reason we do not have a backup of the database is a long story.
Anyways, somehow the SQL Server installation got corrupted and I was not able
to take a backup of the database. I had the mdf and ldf files. Once I
unsinstalled and installed SQL Server 2000 SP4, I was able to restore all
databases from a backup except for one, the one that did not have a backup.
But I had the mdf and ldf files. When I tried to attach the database, I got
the error above. Any help in this matter will be greatly appreciated.
Thanks,
Bill
A full backup would be very helpful, but anyway, take a look here:
http://www.sqlservercentral.com/scri...p?scriptid=599
HTH, Jens Suessmeyer.
|||>From the BOL:
sp_attach_db should only be executed on databases that were previously
detached from the database server using an explicit sp_detach_db
operation. If more than 16 files must be specified, use CREATE DATABASE
with the FOR ATTACH clause.
The database attached must have been created using the same code page
and sort order as SQL Server.
So check your collation on the server and if it is different than the
database (hopefully you have documented somewhere), find a SQL Server
that is on the same code page and attach there, change the collation of
the database, then detach and re-attach to the intended server.
Hope it will help.
Mel

Error 5171 when attaching database

I am having an issue attaching a database. I am getting Error 5171 - ls is
not a primary database file.
We did not have a backup of a database, so I am not able to restore a
backup. The reason we do not have a backup of the database is a long story.
Anyways, somehow the SQL Server installation got corrupted and I was not abl
e
to take a backup of the database. I had the mdf and ldf files. Once I
unsinstalled and installed SQL Server 2000 SP4, I was able to restore all
databases from a backup except for one, the one that did not have a backup.
But I had the mdf and ldf files. When I tried to attach the database, I got
the error above. Any help in this matter will be greatly appreciated.
Thanks,
BillA full backup would be very helpful, but anyway, take a look here:
http://www.sqlservercentral.com/scr...sp?scriptid=599
HTH, Jens Suessmeyer.|||>From the BOL:
sp_attach_db should only be executed on databases that were previously
detached from the database server using an explicit sp_detach_db
operation. If more than 16 files must be specified, use CREATE DATABASE
with the FOR ATTACH clause.
The database attached must have been created using the same code page
and sort order as SQL Server.
So check your collation on the server and if it is different than the
database (hopefully you have documented somewhere), find a SQL Server
that is on the same code page and attach there, change the collation of
the database, then detach and re-attach to the intended server.
Hope it will help.
Mel|||Thank you guys for your help. I tried a few things and it did not work. If
one problem was fixed then another was created. Anyways, the users have sai
d
they do not need that database and they will probably recreate it if needed.
Bill
"MSLam" wrote:

> sp_attach_db should only be executed on databases that were previously
> detached from the database server using an explicit sp_detach_db
> operation. If more than 16 files must be specified, use CREATE DATABASE
> with the FOR ATTACH clause.
> The database attached must have been created using the same code page
> and sort order as SQL Server.
> So check your collation on the server and if it is different than the
> database (hopefully you have documented somewhere), find a SQL Server
> that is on the same code page and attach there, change the collation of
> the database, then detach and re-attach to the intended server.
> Hope it will help.
> Mel
>

Error 5171 when attaching database

I am having an issue attaching a database. I am getting Error 5171 - ls is
not a primary database file.
We did not have a backup of a database, so I am not able to restore a
backup. The reason we do not have a backup of the database is a long story.
Anyways, somehow the SQL Server installation got corrupted and I was not able
to take a backup of the database. I had the mdf and ldf files. Once I
unsinstalled and installed SQL Server 2000 SP4, I was able to restore all
databases from a backup except for one, the one that did not have a backup.
But I had the mdf and ldf files. When I tried to attach the database, I got
the error above. Any help in this matter will be greatly appreciated.
Thanks,
BillA full backup would be very helpful, but anyway, take a look here:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
HTH, Jens Suessmeyer.|||>From the BOL:
sp_attach_db should only be executed on databases that were previously
detached from the database server using an explicit sp_detach_db
operation. If more than 16 files must be specified, use CREATE DATABASE
with the FOR ATTACH clause.
The database attached must have been created using the same code page
and sort order as SQL Server.
So check your collation on the server and if it is different than the
database (hopefully you have documented somewhere), find a SQL Server
that is on the same code page and attach there, change the collation of
the database, then detach and re-attach to the intended server.
Hope it will help.
Mel|||Thank you guys for your help. I tried a few things and it did not work. If
one problem was fixed then another was created. Anyways, the users have said
they do not need that database and they will probably recreate it if needed.
Bill
"MSLam" wrote:
> >From the BOL:
> sp_attach_db should only be executed on databases that were previously
> detached from the database server using an explicit sp_detach_db
> operation. If more than 16 files must be specified, use CREATE DATABASE
> with the FOR ATTACH clause.
> The database attached must have been created using the same code page
> and sort order as SQL Server.
> So check your collation on the server and if it is different than the
> database (hopefully you have documented somewhere), find a SQL Server
> that is on the same code page and attach there, change the collation of
> the database, then detach and re-attach to the intended server.
> Hope it will help.
> Mel
>

Friday, March 9, 2012

Error 50007: xp_execresultset: unable to get a bound connection back to server

Hi,
I have just resinstalled my server and restored the backup of my database. I am now trying to re-setup replication and I get the above error. The server configuiration:
Win2k3
SQL Server 2000 SP4
Replication: Distributor & Publisher (intended Push Publisher)
Snapshot
Subscriber: Remote server
I have looked around the web for similar problems and resolutions but mine still does not want to work. I have completely removed the replication as per the information on this article: http://support.microsoft.com/kb/324401 but still cannot get it working.
I did not backup the distribution db, master or msdb - only the main database I want to replicate.
Any advice?
Thanx
Dave
From http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
You get this error when you have not set up your administrative link
password correctly. Either uncheck this option or ensure that when you
configure your publisher you enter the correct one.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dave" <nospam@.developmentnow.com> wrote in message
news:2ae92f81-6f29-41d1-ba10-e7841b355fbb@.developmentnow.com...
> Hi,
> I have just resinstalled my server and restored the backup of my database.
> I am now trying to re-setup replication and I get the above error. The
> server configuiration:
> Win2k3
> SQL Server 2000 SP4
> Replication: Distributor & Publisher (intended Push Publisher)
> Snapshot
> Subscriber: Remote server
> I have looked around the web for similar problems and resolutions but mine
> still does not want to work. I have completely removed the replication as
> per the information on this article:
> http://support.microsoft.com/kb/324401 but still cannot get it working.
> I did not backup the distribution db, master or msdb - only the main
> database I want to replicate.
> Any advice?
> Thanx
> Dave
> From
> http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
|||Hi,
Thanx for the information. I have managed to get it to work again by creating a new username and password for the distribution agents to use. Initially it was set to impersonate the service account (which is a domain account that the SQL Services use). I would have thought that this would be sufficient. I even gave this account sysadmin privledges.
Also, when I first setup the replication it worked without having to change any usernames and/or passwords. Was the problem because I recovered from a backup?
Thanx
Dave
From http://www.developmentnow.com/g/114_2007_7_0_0_995269/Error-50007-xp-execresultset-unable-to-get-a-bound-connection-back-to-server.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
|||Its hard to say what caused the problem, but I am glad you have solved it.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dave" <nospam@.developmentnow.com> wrote in message
news:2258406d-86c6-4c5e-87e2-1283b7f9b4e6@.developmentnow.com...
> Hi,
> Thanx for the information. I have managed to get it to work again by
> creating a new username and password for the distribution agents to use.
> Initially it was set to impersonate the service account (which is a domain
> account that the SQL Services use). I would have thought that this would
> be sufficient. I even gave this account sysadmin privledges.
> Also, when I first setup the replication it worked without having to
> change any usernames and/or passwords. Was the problem because I recovered
> from a backup?
> Thanx
> Dave
> From
> http://www.developmentnow.com/g/114_2007_7_0_0_995269/Error-50007-xp-execresultset-unable-to-get-a-bound-connection-back-to-server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com

Error 4064 after attempting restore backup?!

Hi,

We have a little problem for you:

We have 2 servers both running sqlexpress2005, both have service pack 1 installed, both have the same db (same tables etc.) both have the same users with the same passwords. Everything is identical.

What I want to do is move the db. I am attempting to do this by making a backup of the db and restoring it into the second machine. (I am not sure of a more practical way to do this without stopping the SQL server).

This is the problem, the backup process works fine, without error, but when restoring the copy to the other server ,it loses the dbowner property and all default users when attempting to connect recieve a 4064 error even though all the password for users are there. Very strange.

I tried to restore the copy to to the same server that I made the copy and everything works, this only happens when attempting to restore the copy on another machine.

Do you know if this is a possible bug? I have tried to do further test on 4 different machines now and the same happens.

The objective is to be able to send the data from sqlexpress server to another by making a backup and without the need t stop the sql server. Any suggestion would be appreciated.

Adam

Even though the usernames and passwords are the same the users will have different SIDs (SQL Server's unique identifiers for users). To get a list of the orphaned users run the following on the database you restored:

EXEC sp_change_users_login 'Report'

You can then run the following command for each orphaned user to fix their relationship to the database:

EXEC sp_change_users_login 'Auto_Fix', 'user'

|||

William, can you help me with this:

I have the same scenario as the original posting, and the orpahned user (Webuser) can be fixed with the following:

1 - EXEC sp_change_users_login 'Auto_Fix', 'webuser'

2- I must then create a table, and give webuser rights to it.

Until I do step 2 the user webuser still cannot select from any tables

How can I simplify this and allow webuser to use the db without the second step.

thanks for any help

regards

David

|||

hi David,

step 1 only fixex membership to the database users... being a database user only grants (again) membership to "public" database role, and usually public members do not have lots of permissions on database objects... acutally public members do not have read/write permissions on database tables at all.. you have to manually handle that, or make the desired/required database user member of other privileged database roles, like db_datareader/db_datawriter.. or, even better, define appropriate database roles to have the desired granularity in object's permissions...

regards

|||Hi
Sorry I did not explain adequately.

My user already has rights to all necessary tables and other objects in the db.

I am having to update a remote server with the latest version if a db, I have

no online link to that server the only possible method is manually

overwriting the mdb and ldb files

After I re-attach the updated file to the server, the user cannot select from any of those objects that they formerly had access to.

I run the sp to deal with the orphaned users issue, but then, the user still cannot select etc, even though I can look into all the object permissions and the user is shown there. So they are not an orphan, and they have explicit permissions, but they cannot see or use any of the database.

The only way I have found to resolve it is to create a new object, a table say, grant the user permissions, then hey presto suddenly they can see that, and more to the point they can see and use all the objects they are supposed to see. Then I delete the newly created table object.

The act of creating a new table and giving them rights has fixed the problem. But it cannot be the right way to do it.

regards
David

Error 4064 after attempting restore backup?!

Hi,

We have a little problem for you:

We have 2 servers both running sqlexpress2005, both have service pack 1 installed, both have the same db (same tables etc.) both have the same users with the same passwords. Everything is identical.

What I want to do is move the db. I am attempting to do this by making a backup of the db and restoring it into the second machine. (I am not sure of a more practical way to do this without stopping the SQL server).

This is the problem, the backup process works fine, without error, but when restoring the copy to the other server ,it loses the dbowner property and all default users when attempting to connect recieve a 4064 error even though all the password for users are there. Very strange.

I tried to restore the copy to to the same server that I made the copy and everything works, this only happens when attempting to restore the copy on another machine.

Do you know if this is a possible bug? I have tried to do further test on 4 different machines now and the same happens.

The objective is to be able to send the data from sqlexpress server to another by making a backup and without the need t stop the sql server. Any suggestion would be appreciated.

Adam

Even though the usernames and passwords are the same the users will have different SIDs (SQL Server's unique identifiers for users). To get a list of the orphaned users run the following on the database you restored:

EXEC sp_change_users_login 'Report'

You can then run the following command for each orphaned user to fix their relationship to the database:

EXEC sp_change_users_login 'Auto_Fix', 'user'

|||

William, can you help me with this:

I have the same scenario as the original posting, and the orpahned user (Webuser) can be fixed with the following:

1 - EXEC sp_change_users_login 'Auto_Fix', 'webuser'

2- I must then create a table, and give webuser rights to it.

Until I do step 2 the user webuser still cannot select from any tables

How can I simplify this and allow webuser to use the db without the second step.

thanks for any help

regards

David

|||

hi David,

step 1 only fixex membership to the database users... being a database user only grants (again) membership to "public" database role, and usually public members do not have lots of permissions on database objects... acutally public members do not have read/write permissions on database tables at all.. you have to manually handle that, or make the desired/required database user member of other privileged database roles, like db_datareader/db_datawriter.. or, even better, define appropriate database roles to have the desired granularity in object's permissions...

regards

|||Hi
Sorry I did not explain adequately.

My user already has rights to all necessary tables and other objects in the db.

I am having to update a remote server with the latest version if a db, I have

no online link to that server the only possible method is manually

overwriting the mdb and ldb files

After I re-attach the updated file to the server, the user cannot select from any of those objects that they formerly had access to.

I run the sp to deal with the orphaned users issue, but then, the user still cannot select etc, even though I can look into all the object permissions and the user is shown there. So they are not an orphan, and they have explicit permissions, but they cannot see or use any of the database.

The only way I have found to resolve it is to create a new object, a table say, grant the user permissions, then hey presto suddenly they can see that, and more to the point they can see and use all the objects they are supposed to see. Then I delete the newly created table object.

The act of creating a new table and giving them rights has fixed the problem. But it cannot be the right way to do it.

regards
David

Wednesday, March 7, 2012

ERROR 3628 Floating point error

Our system just started receiving an error on the
optimization phase of backup maintenance plan. This is
during index rebuild.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
This system is Sql2k SP3. I have found a couple of hits on
floating point errors, but nothing directly related to
index rebuilds.
Any ideas?The first thing I'd do is to check if the database is clean using DBCC
CHECKDB and DBCC CHECKCATALOG.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Judy" <jranson@.harris.com> wrote in message
news:015a01c3be88$b4c5afb0$a401280a@.phx.gbl...
> Our system just started receiving an error on the
> optimization phase of backup maintenance plan. This is
> during index rebuild.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
> [Microsoft][ODBC SQL Server Driver][SQL Server]A floating
> point exception occurred in the user process. Current
> transaction is canceled.
> [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
> execution completed. If DBCC printed error messages,
> contact your system administrator.
> This system is Sql2k SP3. I have found a couple of hits on
> floating point errors, but nothing directly related to
> index rebuilds.
> Any ideas?

Error 3624 doing trans log backup

I get Error 3624 sporadically when doing trans log backups,
Any clues as to why?
ThanksIt is helpful if you post the actual error message, as most of us haven't memorized all error
messages. Actually, I didn't even find 3624 in sysmessages, so that doesn't seem to be an SQL Server
error message.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Richard Buchner" <rbuchner@.hpsg.com> wrote in message
news:019001c37f99$de393200$a101280a@.phx.gbl...
> I get Error 3624 sporadically when doing trans log backups,
> Any clues as to why?
> Thanks|||Tibor,
below is the messages, this is wile doing trans log dump
of Great Plains db's, Thanks
________________________________________________________
2003-09-11 00:27:10.45 spid54 Stack Signature for the
dump is 0x21F5A243
2003-09-11 00:27:10.49 spid54 SQL Server Assertion:
File: <p:\sql\ntdbms\storeng\drs\include\record.inl>,
line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <=MAXDATAROW'.
2003-09-11 00:27:10.49 spid54 Error: 3624, Severity:
20, State: 1.
______________________________________________________
>--Original Message--
>It is helpful if you post the actual error message, as
most of us haven't memorized all error
>messages. Actually, I didn't even find 3624 in
sysmessages, so that doesn't seem to be an SQL Server
>error message.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>
>"Richard Buchner" <rbuchner@.hpsg.com> wrote in message
>news:019001c37f99$de393200$a101280a@.phx.gbl...
>> I get Error 3624 sporadically when doing trans log
backups,
>> Any clues as to why?
>> Thanks
>
>.
>

Sunday, February 26, 2012

Error 3271 while doing a backup

Hi I am trying to do a backup of a database and it gives me the following
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerTry "DBCC CHECKDB"
Thanks & Regards,
P.C Sekhar.
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:78B5EACF-9948-46D6-8D96-C99B6B286E16@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>|||Please read the entire message which i posted, i already tried dbcc checkdb
and tried dbcc checkalloc with 2 options.
Thanks
Rodger
"P.C Sekhar" wrote:

> Try "DBCC CHECKDB"
> Thanks & Regards,
> P.C Sekhar.
> "Rodger" <Rodger@.discussions.microsoft.com> wrote in message
> news:78B5EACF-9948-46D6-8D96-C99B6B286E16@.microsoft.com...
>
>

error 3271

Hi I am trying to do a backup of a database and it gives me the following
error
Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
I ran dbcc checkdb and it gives consistency errors on one of the table, i
dropped all indexes on the table but its giving me errors while dropping the
last index, i think the index is corrupted . Is there any way to fix the
table or to drop the index without losing the data. I tried dbcc checkalloc
with rebuild and fast option still the same , i am hesitant to try the first
option of dbcc checkalloc which says it will fix the problem but will loose
some of the data. I tried copying the contents of the table to a temporary
table, but it gives I/O error.
Any suggestion '
Thanks
RodgerI assume you're on sql2k; thus, it's not possible to disable a corrupted
index to rebuild it.
You can try running "dbcc checktable(tb_name,repair_rebuild)". If it still
fails, you can force a drop of the index by deleting it from sysindexes.
(all warnings/disclaimers applied about direct system modification).
Restoring from a known backup is recommended for most corruption issues!
e.g.
exec sp_configure 'allow','1'
reconfigure with override
go
use <db>
go
--create a backup of sysindexes
--in case of mistake
select *
into sysindexes_bak
from sysindexes
go
delete sysindexes
where name='your_index'
go
exec sp_configure 'allow','0'
reconfigure with override
go
-oj
"Rodger" <Rodger@.discussions.microsoft.com> wrote in message
news:7D83EAD0-94D3-4B01-9C7F-7EBAE775450A@.microsoft.com...
> Hi I am trying to do a backup of a database and it gives me the following
> error
> Nonrecoverable I/O error occurred on file 'C:\Program Files\Websense
> Reporter\wslogdb61.mdf'. [SQLSTATE 42000] (Error 3271)
> I ran dbcc checkdb and it gives consistency errors on one of the table, i
> dropped all indexes on the table but its giving me errors while dropping
> the
> last index, i think the index is corrupted . Is there any way to fix the
> table or to drop the index without losing the data. I tried dbcc
> checkalloc
> with rebuild and fast option still the same , i am hesitant to try the
> first
> option of dbcc checkalloc which says it will fix the problem but will
> loose
> some of the data. I tried copying the contents of the table to a
> temporary
> table, but it gives I/O error.
> Any suggestion '
> Thanks
> Rodger
>

Error 3271

Hi,
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel LanserHi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser

Error 3271

Hi,
during a backup of a database with the following command I get an error:
backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
BACKUP DATABASE is terminating abnormally.
What can I do to repair the database files ?
Best regards
Axel Lanser
Hi,
See SQL Server error log and Event viewer logs for more informations on this
error.
Run a DBCC CHECKDB on the database to make sure that it doesnt have any
consistency or allocation errors. It is most likely there will be errorr.
In that case you see the DBCC Checkdb with repair options in Books online.
If the database have errors and if it is difficult to solve using repair
options, Best option will be is to RESTORE from last
healthy backup or contact MS Product support.
Thanks
Hari
SQL Server MVP
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:B471FEE1-F07D-44F5-9150-ABF4C5BF630B@.microsoft.com...
> Hi,
> during a backup of a database with the following command I get an error:
> backup database TV_TOPO to disk='d:\Backup.nacher\TV_TOPO.bck'
> Server: Nachr.-Nr. 3271, Schweregrad 16, Status 1, Zeile 1
> Nonrecoverable I/O error occurred on file 'D:\Database\TV_TOPO.mdf'.
> Server: Nachr.-Nr. 3013, Schweregrad 16, Status 1, Zeile 1
> BACKUP DATABASE is terminating abnormally.
> What can I do to repair the database files ?
> Best regards
> Axel Lanser