\\.\Tape0 is not a vaild Microsoft Tape format backup set

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,
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

\\.\Tape0 is not a vaild Microsoft Tape format backup set

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 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:
>

[SQLSTATE 42000] (Error 8198)).

Running SQL 2000 & Win 2000.
My main server was upgraded/replaced today. We stopped
SQL on the ond server and copied the dBs to the new
server, which has the same name as old server. I receive
the following message on all my subscriptions from my
remote locations.
The job failed. Unable to determine if the owner
(domain.COM\user) of job sqlname-StoreMain-
vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
4A0A-96D3-E33335441348 has server access (reason: Could
not obtain information about Windows NT
group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
8198)).
I have done some research and found I need to change the
owner of the job.
How do I do that?
HELP!!!!
Larry...
locate the job in the jobs subfolder of the management folder. Right click
on it, select properties and modify it there.
You can also use sp_update_job to make this change.
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:515a01c42cb9$00956860$a401280a@.phx.gbl...
> Running SQL 2000 & Win 2000.
> My main server was upgraded/replaced today. We stopped
> SQL on the ond server and copied the dBs to the new
> server, which has the same name as old server. I receive
> the following message on all my subscriptions from my
> remote locations.
> The job failed. Unable to determine if the owner
> (domain.COM\user) of job sqlname-StoreMain-
> vCost,vItem,PLU-remotesqlSERVER-StoreMain-D80E140D-1D56-
> 4A0A-96D3-E33335441348 has server access (reason: Could
> not obtain information about Windows NT
> group/user 'domain.COM\user'. [SQLSTATE 42000] (Error
> 8198)).
> I have done some research and found I need to change the
> owner of the job.
> How do I do that?
>
> HELP!!!!
> Larry...
|||Larry,
the job owner is only validated in AD and not actually used as the job runs
as SQL Agent. With that in mind, you can change the job owner to sa to fix
this type of problem.
Regards,
Paul Ibison

[S0001][unixODBC][Easysoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'test1'

Hello,

I am new to SQL Server, sorry for my ignorance !!!

I have installed SQL Server 2005 Express on my desktop (Win 2000 Pro.)

I have created a new database.

I just created a new login/user (SQL Authentication) and when I try to login, it

errors out:

[S0001][unixODBC][Easysoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'test1'

I believe the error is from SQL Server and not from ODBC driver.

I am also only able to connect by using my own userid (the one that I am connected to my desktop): domain\userid, and then I am only able to connect to 'master' db:

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

/usr/local/etc>isql SQLSERVER_POS -v
++
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
++
SQL> use pcspos
[S0001][unixODBC][Easysoft][ODBC SQL Server Driver][SQL Server]Could not locate entry in sysdatabases for database 'pcspos'. No entry found with that name. Make sure that the name is entered correctly.
[ISQL]ERROR: Could not SQLExecute
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Hello,

While I browse the SSMSE (SQL Server Management Studion Express) , I see that the database state (from the

Database Properties Windows) is NORMAL | SHUTDOWN !!!!!!

Is this OK ?

In the meantime when I login via SSMSE, I can see all the tables and data in the database !!!!!!!!!

Thanks,

Tom

|||

Hello, I was able to change the Database State to NORMAL (I changed the 'Auto Close' option to False).

BUT I am still not able to connect:

/usr/local/etc>isql SQLSERVER_POS -v
[S0001][unixODBC][Easysoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'test1'.
[ISQL]ERROR: Could not SQLConnect

|||If you are using Windows Authentication only, you cannot use SQL Server logins to connect to the server. (see how to switch the authentication mode on my website under the Screencasts). If you want to use WIndows authentication you will have to be aware that you cannot explicitly pass a user name within the connectionstring, the username is passed implicitly through Windows. If you have enabled Mixed authentication already, make sure that you are using the right password.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Jens, thank you for your reply.

I am using the SQL Authentication mode, see below I am able to connect from the DOS prompt (localy),

but I can NOT connect from a Linux server by using the ODBC driver:

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

C:\>isql -S (local)\SQLEXPRESS -U pos_sql05 -P passwd
1> select db_name()
2> go

--

--

--
POS

(1 row affected)
1> select * from pcs_lookup_active_status;
2> go
ACTIVE_STATUS_KEY ACTIVE_STATUS_DESC
-- --
1 Active
2 Inactive
3 Deleted

(3 rows affected)

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

|||I don′t know how the tool for Linux works but if you do not pass a username using SQL Server authentication there has to be somewhere a setting file where these information is stored.
|||

I am using a config file by the name odbc.ini.

It looks like the following:

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

[SQLSERVER_POS]
Driver = /usr/local/easysoft/sqlserver/lib/libessqlsrv.so
Description = Easysoft SQL Server ODBC driver (unixODBC 2.2.12)
Server = 10.20.30.40\SQLEXPRESS
Port = 1433
Database = POS
User = pos_sql05
Password = passwd
Mars_Connection = No
Logging = 31
LogFile = /tmp/sqlserver.log
QuotedId = Yes
AnsiNPW = Yes
Language =
Version7 = No
ClientLB = No
Failover_Partner =
VarMaxAsLong = No

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

As you cann tell, the user id and password are there.

Thanks again.

Regards,

Tom

|||

Make sure that you are using the right password for the mentioned user. In addition make sure taht the user is priviledged for the POS database, cause authentication or the connection will also fail if the initial database is not one of the allowed ones. if you are not sure, try to connect to the master database. A user which is granted access to the server should have access to the master database.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Jens, thanks again.

The userid and password are correct (I am able to connect via isql from the DOS prompt).

I think the problem relies on the fact that I am coming remotetly (from a Linux server), BUT I have

enabled the TCP/IP protocol connection properties. What else can I look for ?

Thank you.

Tom

|||

How are you authenticating? Is your server set to authenticate using Windows authentication only or integrated authentication? Perhaps this unix driver is trying to use SQL authentication and your SQL installation only accepts windows authenticated connections. That would explain this problem.

Hope this helps!

John (MSFT)

|||

Hi John & Jens, the issue has been resolved. I contacted the ODBC driver's vendor and they provided me with an updated copy of it.

Thank you for your help and suggestions.

Keep up the GREAT job.

Best regards,

Tom

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov
|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that much of traffic hitting our web pages other than the developers themselves (for now-and-then testing). This error seems to pop up sometimes early in the morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I think it might not be due to load on the system.
And changing the time out value to something more or making it unlimited would really be a temporary solution at best for us. I am trying to figure out the real problem, so that the freeze up never happens...Oddly enough, when I run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e r"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem disappears...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov|||Thanks Bojidar.
The only thing is, this is our development server and there isn't all that m
uch of traffic hitting our web pages other than the developers themselves (f
or now-and-then testing). This error seems to pop up sometimes early in the
morning when there is no on
e on our server, and sometimes never even when we have heavy usage...So, I t
hink it might not be due to load on the system.
And changing the time out value to something more or making it unlimited wou
ld really be a temporary solution at best for us. I am trying to figure out
the real problem, so that the freeze up never happens...Oddly enough, when I
run the 'EXEC sp_recompile
' with a table name, the problem seems to disappear...
Thanks for your insight Bojidar.
- A l p e r
-- Bojidar Alexandrov wrote: --
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied)
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expire
If anyone has any ideas as to possible reasons, it would be immensely appreciated
Any help would be greatly appreciated
Thank you
- A l p e"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[2.0] deploy of a Report Model ?

Hello,

I use a Report Model Project to build a Report Model and I'd like to deploy it on my production server (Win 2003 server).

I can't use Visual Studio to deploy since I don't have web access to the server (only Remote Desktop access)

The command line tool RS seems to work for a simple report (rdlc) but I have a model (smdl)...

Hi

Did you find a solution to this problem?

Cheers

|||

Not sure this is exactly what you arelooking for, I tried this tool and it solved my problem,

Reporting Services Scripter -http://www.sqldbatips.com/showarticle.asp?ID=62

Overview

Reporting Services Scripter is a .NET Windows Forms application that enables scripting and transfer of all Microsoft SQL Server Reporting Services catalog items to aid in transferring them from one server to another. It can also be used to easily move items on mass from one Reporting Services folder to another on the same server. Depending on the scripting options chosen, Reporting Services Scripter can also transfer all catalog item properties such as Descriptions, History options, Execution options (including report specific and shared schedules), Subscriptions (normal and data driven) and server side report parameters.