Thursday, March 22, 2012
\\.\Tape0 is not a vaild Microsoft Tape format backup set
I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
sql server backups have started failing. Here is the error message I get with
it
The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
set. Backup Database is terminating abnormally.
I am using HP dds-4 cartridges (40 GB)
How can I fix that?
Also how do I format my tapes?
regards,
AndreHi
Have you tried dropping the backup device and re-creating it? Will the NT
Backup recognise this tape device?
John
"Andre Gibson" wrote:
> hi all
> I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> sql server backups have started failing. Here is the error message I get with
> it
> The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> set. Backup Database is terminating abnormally.
> I am using HP dds-4 cartridges (40 GB)
> How can I fix that?
> Also how do I format my tapes?
> regards,
> Andre|||No NT Backup doesn't recognize the tape. How do I drop and re-create the
device?
"John Bell" wrote:
> Hi
> Have you tried dropping the backup device and re-creating it? Will the NT
> Backup recognise this tape device?
> John
> "Andre Gibson" wrote:
> > hi all
> >
> > I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> > sql server backups have started failing. Here is the error message I get with
> > it
> >
> > The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> > set. Backup Database is terminating abnormally.
> >
> > I am using HP dds-4 cartridges (40 GB)
> >
> > How can I fix that?
> > Also how do I format my tapes?
> >
> > regards,
> >
> > Andre|||Hi Andre
If the NT backup does not recognise the tape, then it may not be SQL Server
that is the problem. Have you tried different tapes or re-installing the tape
drive?
John
"Andre Gibson" wrote:
> No NT Backup doesn't recognize the tape. How do I drop and re-create the
> device?
> "John Bell" wrote:
> > Hi
> >
> > Have you tried dropping the backup device and re-creating it? Will the NT
> > Backup recognise this tape device?
> >
> > John
> >
> > "Andre Gibson" wrote:
> >
> > > hi all
> > >
> > > I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> > > sql server backups have started failing. Here is the error message I get with
> > > it
> > >
> > > The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> > > set. Backup Database is terminating abnormally.
> > >
> > > I am using HP dds-4 cartridges (40 GB)
> > >
> > > How can I fix that?
> > > Also how do I format my tapes?
> > >
> > > regards,
> > >
> > > Andre|||John,
You were correct. It was my tapes.
Thanks so much for your assistance.
regards,
Andre
"John Bell" wrote:
> Hi Andre
> If the NT backup does not recognise the tape, then it may not be SQL Server
> that is the problem. Have you tried different tapes or re-installing the tape
> drive?
> John
> "Andre Gibson" wrote:
> > No NT Backup doesn't recognize the tape. How do I drop and re-create the
> > device?
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Have you tried dropping the backup device and re-creating it? Will the NT
> > > Backup recognise this tape device?
> > >
> > > John
> > >
> > > "Andre Gibson" wrote:
> > >
> > > > hi all
> > > >
> > > > I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
> > > > sql server backups have started failing. Here is the error message I get with
> > > > it
> > > >
> > > > The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> > > > set. Backup Database is terminating abnormally.
> > > >
> > > > I am using HP dds-4 cartridges (40 GB)
> > > >
> > > > How can I fix that?
> > > > Also how do I format my tapes?
> > > >
> > > > regards,
> > > >
> > > > Andre
Tuesday, March 20, 2012
\\.\Tape0 is not a vaild Microsoft Tape format backup set
I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightly
sql server backups have started failing. Here is the error message I get wit
h
it
The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
set. Backup Database is terminating abnormally.
I am using HP dds-4 cartridges (40 GB)
How can I fix that?
Also how do I format my tapes?
regards,
AndreHi
Have you tried dropping the backup device and re-creating it? Will the NT
Backup recognise this tape device?
John
"Andre Gibson" wrote:
> hi all
> I am using Sql server 2000 with sp3 on Win 2003. Recently all of my nightl
y
> sql server backups have started failing. Here is the error message I get w
ith
> it
> The file on device '\\.\Tape0' is not a vaild Microsoft Tape format backup
> set. Backup Database is terminating abnormally.
> I am using HP dds-4 cartridges (40 GB)
> How can I fix that?
> Also how do I format my tapes?
> regards,
> Andre|||No NT Backup doesn't recognize the tape. How do I drop and re-create the
device?
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried dropping the backup device and re-creating it? Will the NT
> Backup recognise this tape device?
> John
> "Andre Gibson" wrote:
>|||Hi Andre
If the NT backup does not recognise the tape, then it may not be SQL Server
that is the problem. Have you tried different tapes or re-installing the tap
e
drive?
John
"Andre Gibson" wrote:
[vbcol=seagreen]
> No NT Backup doesn't recognize the tape. How do I drop and re-create the
> device?
> "John Bell" wrote:
>|||John,
You were correct. It was my tapes.
Thanks so much for your assistance.
regards,
Andre
"John Bell" wrote:
[vbcol=seagreen]
> Hi Andre
> If the NT backup does not recognise the tape, then it may not be SQL Serve
r
> that is the problem. Have you tried different tapes or re-installing the t
ape
> drive?
> John
> "Andre Gibson" wrote:
>
[URGENT] Problem to Restore Database from backup
Mrs,
I'm having a serious problem in SQL 2000 SP3 Database which is used Business Applications.
Today, I tryied to take backup in service time by the Enterprize Manager, the following
error occured and could not take backup.
--
Error 926 : Database '[database name]' cannot opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information.
--
After that, we tried same operation 3 times. But result is same.
After sometime, end-user report us that they can not log-in to database.
So we tried to dettach this database and attached it.
We success to dettach, but we can not attached it.
Also we tried to restore this database from Yesterday's backup file by using Enterprize Manager,
but the following error occured, and could not complete.
This backup file was generated daily backup task in Maintenance Plan in Enterprize Manager.
--
Microsoft SQl-DMO(ODBC SQLState:42000)
The media family on device "E:\ccd\......xxx.bak" is incorrectly formed.
SQL Server cannot process this media family.
RESTORE DATABASE is terminating abnormally.
We need to recover the database immediately not to stop the end-user business process.
Please help us.
Yamagury.
refer , http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1977204&SiteID=1 try as suggested and get back.... also you need to apply SP4 or go to sql 2005 as sql 2000 sp3 has ended its life cycle in july 10th 2007 itself....
refer
http://support.microsoft.com/gp/lifesupsps
|||Thank you for your support.Yes, We already tried to apply SP4.
But this problem was not solved.
Now I'm trying to do as your instruction.|||(you had to back up the transaction log before you perform any restore operations and hadn't detach it before.
You had to verify your backup with RESTORE VERIFYONLY statement .)
use RESTORE HEADERONLY and see if you have multiple backup files in the the same backup file. If yes then
try using FILE= option while restoring.
File is from :
RESTORE DATABASE { database_name | @.database_name_var }
< file_or_filegroup > [ ,...n ]
[ FROM < backup_device > [ ,...n ] ]
[ WITH
[ RESTRICTED_USER ]
[ [ , ] FILE = { file_number | @.file_number } ] .....
see Books Online
(Why do you have not SP4?
Read this.)
|||Dear Deepak
I tried to create database and swap mdf/ldf file.
and go into single user mode, and then run DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS,
but, DBCC command return error. Database could not be repaired.
How can I do after this?|||
Ok you can try as follows,
Alter database DBname set emergency
this will bring your db into emergency mode so that you can access your db and then subsequently export the datas alone from this db to another db so that you can minimize the dataloss.....if you have a full backup then drop this suspect database and restore it from full backup but there will be dataloss to minimize it set the db as emergency mode and export the tables,sps etc which you feel is required to another db in UAT server and script those and rerun the script in the restored db
[TCP/IP Sockets] Specified SQL Server not found
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOpen
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Server
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipes
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.com
On the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon
[TCP/IP Sockets] Specified SQL Server not found
f
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOp
en
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Se
rver
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipe
s
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.comOn the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon
Sunday, March 11, 2012
[Shared Memory]ConnectionCheckForData error on delete command.
I ave a strange error with SQLServer 2000 SP3.
I made a table that contains over 62'000 records. When I delete over
300 records, I have this error:
[Microsoft][ODBC SQL Server Driver][Shared
Memory]ConnectionCheckForData (CheckforData()).
Serveur : Msg 11, Niveau 16, État 1, Ligne 0
Structure of my table:
create table ActiveTimeForProcessing (
ACTIVETIMEFORPROCESSING_PK int identity,
InstanciedClassName int not null,
ActiveTime int not null,
DateFrom datetime not null,
DateTo datetime not null,
constraint PK_ACTIVETIMEFORPROCESSING primary key
(ACTIVETIMEFORPROCESSING_PK)
)
go
alter table ActiveTimeForProcessing
add constraint ActiveTimeForProcessingHasActiveTime foreign key
(ActiveTime)
references ActiveTime (ACTIVETIME_PK)
go
CREATE INDEX [IX_ActiveTimeForProcessing_DateFrom] ON
[dbo].[ActiveTimeForProcessing]([DateFrom]) ON [PRIMARY]
GO
CREATE INDEX [IX_ActiveTimeForProcessing_DateTo] ON
[dbo].[ActiveTimeForProcessing]([DateTo]) ON [PRIMARY]
GO
Something very strange is that on an other server, it work fine...
Thanks to help me.
PascalHi,
Try
1. Run DBCC CHECKDB against the database to make sure it is clean.
2. Check the errorlog for any error that match the time that you get the
error.
Sincerely,
Yih-Yoon Lee
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Thanks a lot, but I tryed you purpose...
Finally I found sollution... Service Pack 3a......... ... ...
Thanks one more.
Pascal
""Jinxin"" <yihyoonl@.online.microsoft.com> a écrit dans le message de news:
ZRYO4j$PDHA.2696@.cpmsftngxa09.phx.gbl...
> Hi,
> Try
> 1. Run DBCC CHECKDB against the database to make sure it is clean.
> 2. Check the errorlog for any error that match the time that you get the
> error.
> Sincerely,
> Yih-Yoon Lee
> Microsoft, SQL Server
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
Friday, February 24, 2012
[help] SQL Error - I/O Error 2 (The system cannot find the file specified)
the windows event log give the following error information:
I/O error 2(The system cannot find the file specified) detected during write at offset 0x0000010c6c4000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\GJSZBANK_Data.MDF'.
I have searched microsoft knowledge base and got this article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;828339
but don't understand some contents in the topic:
For example, if you encounter the following error message in the SQL Server Errorlog file, SQL Server encountered operating system error 2 when it uses a Windows API call to write to the tempdb primary database file:
Error: 823, Severity: 24, State: 4
I/O error 2(The system cannot find the file specified.) detected during write at offset 0x00000000284000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'
Because SQL Server has already successfully opened the file and did not receive an Invalid Handle error, the error is likely being raised in a lower-level kernel software component, such as the file system or a device driver. This problem does not indicate a problem in SQL Server, and it must be investigated as an issue with the file system or a device driver that is associated with the file.
Does that mean this is not a SQL Server error?
Does that mean something wrong with my operating system? or something wrong with my hard disk?Are there any errors in the SQL errorlog? Or is it only in the NT Event log?
Sunday, February 19, 2012
[Fail] Could not add ASPNET user to SQL Server.
1. Installed msde 2000 with sp3.
2. started the SQL Server and SQL Server Agent.
3. Ran IBuySpy Store Installation, when I ran the configuration I get error on bottum.
10:51:55 PM Tuesday, September 23, 2003: [Checking system requirements]
10:51:55 PM Tuesday, September 23, 2003: [Pass] Detected a local instance of SQL Server.
10:51:55 PM Tuesday, September 23, 2003: [Pass] Determined SQL Server version (8.00.194).
10:51:55 PM Tuesday, September 23, 2003: [Pass] Detected .NET Framework.
10:51:55 PM Tuesday, September 23, 2003: [Pass] Detected Internet Information Server (IIS).
10:52:03 PM Tuesday, September 23, 2003: [Begin Sample Configuration]
10:52:05 PM Tuesday, September 23, 2003: [Pass] Created IIS virtual directory.: StoreVBVS
10:52:05 PM Tuesday, September 23, 2003: [Pass] Determined SQL Server version (8.00.194).
10:52:22 PM Tuesday, September 23, 2003: [Fail] Could not add ASPNET user to SQL Server.
SQL Server does not exist or access denied.
10:52:22 PM Tuesday, September 23, 2003: [Done]
Can someone please tell me step by step on what I need to do and where to do it to get this working, thanks !!!did you add it via users in your db? when you xpand our db in sql server xplorer, you can add users using "users"...
HTH
[DBNETLIB]ConnectionCheckForData (CheckforData())
SQL SERVER 2000 SP3, WINDOWS 2K SERVER...
If i run this command on a remote server
select replicate(' ',190)
i have the following error
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
if i run select replicate(' ',60) on the same server it completes
succesfully...
any ideas?...
thanks...Sangines (javier.sangines@.gruposenda.com) writes:
> SQL SERVER 2000 SP3, WINDOWS 2K SERVER...
> If i run this command on a remote server
> select replicate(' ',190)
> i have the following error
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> if i run select replicate(' ',60) on the same server it completes
> succesfully...
Interesting...
Often such events are accompnied by messages in the SQL Server errorlog
with a stack dump, indicating that there was an execution error in
SQL Server. However, given the statement you submit this sounds
unlikely. I assume that you run it from Query Analyzer?
So in this case, I would say that it smells a network problem of
some sort. Do you still get the message if you run the query locally
on the SQL Server machine? Do you get the message if you talk to
other SQL Servers?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||> Interesting...
> Often such events are accompnied by messages in the SQL Server errorlog
> with a stack dump, indicating that there was an execution error in
> SQL Server. However, given the statement you submit this sounds
> unlikely. I assume that you run it from Query Analyzer?
> So in this case, I would say that it smells a network problem of
> some sort. Do you still get the message if you run the query locally
> on the SQL Server machine? Do you get the message if you talk to
> other SQL Servers?
Thanks for quick response Erland...
Yes...it was a network problem, caused by misconfiguration in network device...
problem solved...
thanks again...