Windows NT Server reboots when SQL does a Transaction Log Backup and the Backup fails.I get the following Error message: --------------- Microsoft SQL-DMO (ODBC SQLState: 42000) The Microsoft Tape Format (MTF) soft filemark database on backup device 'N:\NewClient\NewClient_tlog_200405171516.TRN' cannot be read, inhibiting random access. Backup or restore operation terminating abnormally. ---------------- Any information on this would be greatly appreciated.

Have you looked at the stored backup procedure to make sure reboot the server is not enabled? You're doing a transaction log backup to tape?? That is a bit odd. Should be to file. You can always backup the logs with regular tape backup.

As far as I know I am not using a Stored Procedure for backup purposes. I am using a Database Maintainance Plan, the jobs are under SQL Server Agent and I can not see anywhere where you can enable or disable reboot the server. The server is rebooting on its own whenever I try to do a Full Database Backup, a Differential Backup or a Transaction Log Backup and the backup fails with the Error Message: ---------------- SQL-DMO (ODBC SQLState: 42000) --------------- The Microsoft Tape Format (MTF) soft filemark database on backup device 'N:\NewClient\NewClient_tlog_200405171516.TRN' cannot be read, inhibiting random access. Backup or restore operation terminating abnormally. ---------------- No I am not doing a transaction log backup to tape it is to file: 'N:\NewClient\NewClient_tlog_200405171516.TRN'. But I do a Full Backup ever night to tape. Any information on this would be greatly appreciated.

Let's start with some basics. When was the last time the drives were defragged? It is the first place to look when you have file writing issues. In the maintenance plan are you running optimization? Are you backing up master, msdb and your database? You need all three to restore your database. I did find this http://support.microsoft.com/default.aspx?scid=kb;en-us;290622&Product=sql One of the first things I do is reapply the service pack for SQL. I have had it correct issues.

Thank you everybody for your responses to my problem. The problem has been corrected, it ended up being a BAD MOTHERBOARD. Some of the capacitors were leaking and corroded. Thanks again.