[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][SQL Server]Transaction (Process ID X) was deadlocked

I am not concerned about seeing an occasional deadlock. I am wondering
why I am seeing unprintable characters now when SQL is trying to tell
me what it deadlocked with. This did not happen in our old environment
and our SQL DBA was unable to explain.
Thanks.
-Jeff-Hi
Check that sysmessages is not corrupted and that the languages installed are
ok (both OS and SQL Server). You may also want to see what the sessions
language is.
John
"kludge" <jeff.schuler@.53.com> wrote in message
news:1130674174.697516.35360@.g43g2000cwa.googlegroups.com...
>I am not concerned about seeing an occasional deadlock. I am wondering
> why I am seeing unprintable characters now when SQL is trying to tell
> me what it deadlocked with. This did not happen in our old environment
> and our SQL DBA was unable to explain.
> Thanks.
> -Jeff-
>

[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID X) was deadloc

My company recently upgraded from SQL 7 to SQL 2000. We also updated
our application servers from Windows NT to Windows 2003. Now when we
get the error [Microsoft][ODBC SQL Server Driver][SQL
Server]Transaction (Process ID X) was deadlocked, the part that comes
next "on {unprintable" shows up as unprintable characters. The rest of
the error message seems fine. Only the part between the braces is
garbage. Does anyone have any suggestions as to why this is? It
seems to be happening from both C++ and Java apps. We are using ODBC
with the C++ apps and JDBC with the Java apps.
Thanks.
-Jeff-Hi
You may want to run SQL profiler to see what is being sent to the server,
and look at the query plans to see if you are missing indexes or statistics.
You may need to change the order of the SQL in your code/stored procedures
and if you have carried over any hints from the SQL 7 upgrade you may want
to evaluate if they are still necessary.
For ways ways to find blocking check out
http://support.microsoft.com/kb/271509/EN-US/ and general tips on
http://www.sql-server-performance.com/
John
"kludge" <jeff.schuler@.53.com> wrote in message
news:1130515027.782023.128220@.g43g2000cwa.googlegroups.com...
> My company recently upgraded from SQL 7 to SQL 2000. We also updated
> our application servers from Windows NT to Windows 2003. Now when we
> get the error [Microsoft][ODBC SQL Server Driver][SQL
> Server]Transaction (Process ID X) was deadlocked, the part that comes
> next "on {unprintable" shows up as unprintable characters. The rest of
> the error message seems fine. Only the part between the braces is
> garbage. Does anyone have any suggestions as to why this is? It
> seems to be happening from both C++ and Java apps. We are using ODBC
> with the C++ apps and JDBC with the Java apps.
> Thanks.
> -Jeff-
>

[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.

I am using PowerDesigner to reverse engineer a SQL 2000 database. I am getting the following error. I can't find out what this error means. Does anyone know?

Unable to list the users. [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared. SQLSTATE =37000

This error is caused when the client is asking the server to prepare a statement which has errors. For example if there is a syntax error in the statement that is being attempted to be executed and SQLPrepare ODBC API is called on it, you will hit this problem. Do you know if the T-SQL you are trying to execute valid or not. To find out the exact problem try using SQL Profiler to see which statement failed to execute.

Thanks

Waseem Basheer

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for us

We changed from sql 7 to 2000, crissis mode.
One use with a laptop keeps getting the error when connecting to the sql
server.
SQL 2000 latest, mixed mode.
Laptop xp pro latest, mdac is latest.
I looked up sql server 26000 and 18452. I was not able to resolve the
problem. Still an untrusted connection.
I do know it is in the user profile but what?
Hi Brian,
Just to be sure, you have some machines working and one particular machine
(the laptop) is not working, right? Are you using Named Pipes or TCP-IP? Is
the laptop using a trusted connection or SQL Server security mode? What was
the exact text of the error message? What things have you tried that did not
resolve the problem?
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@.msn.com www.cindywinegarden.com
"BrianMultiLanguage" <BrianMultiLanguage@.discussions.microsoft.com> wrote in
message news:3D81F886-58B5-4C09-AA8A-1529B54CE72B@.microsoft.com...
> We changed from sql 7 to 2000, crissis mode.
> One use with a laptop keeps getting the error when connecting to the sql
> server.
> SQL 2000 latest, mixed mode.
> Laptop xp pro latest, mdac is latest.
> I looked up sql server 26000 and 18452. I was not able to resolve the
> problem. Still an untrusted connection.
> I do know it is in the user profile but what?

[Microsoft][ODBC Sql Server Driver][Sql Server]Line1: Incorrect Sy

Hi,
I am using SQL server 2000. One of the tables in it has become really large
so i tried to use a sql query to view only a certain rows. I used the
following query:
SELECT * FROM TABLE WHERE Company= X
When i verified the syntax , it verified correctly. Buy when i tried to run
the query i got the error msg box :: [Microsoft][ODBC Sql Server Driver][Sql
Server]Line1: Invalid column name X .
But a column with the company value as X exists!
Also when i tried to use a little different query:: SELECT * FROM TABLE
WHERE Company LIKE s % , then i get the same error but the end part of the
error message says Incorrect Syntax Near %
Why is this happening?
pmud
It's a string, you need string delimiters.
WHERE Company='X'
http://www.aspfaq.com/
(Reverse address to reply.)
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> Hi,
> I am using SQL server 2000. One of the tables in it has become really
large
> so i tried to use a sql query to view only a certain rows. I used the
> following query:
> SELECT * FROM TABLE WHERE Company= X
> When i verified the syntax , it verified correctly. Buy when i tried to
run
> the query i got the error msg box :: [Microsoft][ODBC Sql Server
Driver][Sql
> Server]Line1: Invalid column name X .
> But a column with the company value as X exists!
> Also when i tried to use a little different query:: SELECT * FROM TABLE
> WHERE Company LIKE s % , then i get the same error but the end part of
the
> error message says Incorrect Syntax Near %
> Why is this happening?
> --
> pmud
|||you need single quotes around all character fields
SELECT * FROM TABLE WHERE Company= 'X'
SELECT * FROM TABLE WHERE Company LIKE 's %'
-Andre
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> Hi,
> I am using SQL server 2000. One of the tables in it has become really
> large
> so i tried to use a sql query to view only a certain rows. I used the
> following query:
> SELECT * FROM TABLE WHERE Company= X
> When i verified the syntax , it verified correctly. Buy when i tried to
> run
> the query i got the error msg box :: [Microsoft][ODBC Sql Server
> Driver][Sql
> Server]Line1: Invalid column name X .
> But a column with the company value as X exists!
> Also when i tried to use a little different query:: SELECT * FROM TABLE
> WHERE Company LIKE s % , then i get the same error but the end part of
> the
> error message says Incorrect Syntax Near %
> Why is this happening?
> --
> pmud

[Microsoft][ODBC Sql Server Driver][Sql Server]Line1: Incorrect Sy

Hi,
I am using SQL server 2000. One of the tables in it has become really large
so i tried to use a sql query to view only a certain rows. I used the
following query:
SELECT * FROM TABLE WHERE Company= X
When i verified the syntax , it verified correctly. Buy when i tried to run
the query i got the error msg box :: [Microsoft][ODBC Sql Server Driver][Sql
Server]Line1: Invalid column name X .
But a column with the company value as X exists!
Also when i tried to use a little different query:: SELECT * FROM TABLE
WHERE Company LIKE s % , then i get the same error but the end part of the
error message says Incorrect Syntax Near %
Why is this happening?
--
pmudIt's a string, you need string delimiters.
WHERE Company='X'
--
http://www.aspfaq.com/
(Reverse address to reply.)
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> Hi,
> I am using SQL server 2000. One of the tables in it has become really
large
> so i tried to use a sql query to view only a certain rows. I used the
> following query:
> SELECT * FROM TABLE WHERE Company= X
> When i verified the syntax , it verified correctly. Buy when i tried to
run
> the query i got the error msg box :: [Microsoft][ODBC Sql Server
Driver][Sql
> Server]Line1: Invalid column name X .
> But a column with the company value as X exists!
> Also when i tried to use a little different query:: SELECT * FROM TABLE
> WHERE Company LIKE s % , then i get the same error but the end part of
the
> error message says Incorrect Syntax Near %
> Why is this happening?
> --
> pmud|||you need single quotes around all character fields
SELECT * FROM TABLE WHERE Company= 'X'
SELECT * FROM TABLE WHERE Company LIKE 's %'
-Andre
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> Hi,
> I am using SQL server 2000. One of the tables in it has become really
> large
> so i tried to use a sql query to view only a certain rows. I used the
> following query:
> SELECT * FROM TABLE WHERE Company= X
> When i verified the syntax , it verified correctly. Buy when i tried to
> run
> the query i got the error msg box :: [Microsoft][ODBC Sql Server
> Driver][Sql
> Server]Line1: Invalid column name X .
> But a column with the company value as X exists!
> Also when i tried to use a little different query:: SELECT * FROM TABLE
> WHERE Company LIKE s % , then i get the same error but the end part of
> the
> error message says Incorrect Syntax Near %
> Why is this happening?
> --
> pmud|||Thanks I was trying to use double quotes instead of single...
Thanks :))
"Andre Chan" wrote:
> you need single quotes around all character fields
> SELECT * FROM TABLE WHERE Company= 'X'
> SELECT * FROM TABLE WHERE Company LIKE 's %'
> -Andre
> "pmud" <pmud@.discussions.microsoft.com> wrote in message
> news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> > Hi,
> >
> > I am using SQL server 2000. One of the tables in it has become really
> > large
> > so i tried to use a sql query to view only a certain rows. I used the
> > following query:
> >
> > SELECT * FROM TABLE WHERE Company= X
> >
> > When i verified the syntax , it verified correctly. Buy when i tried to
> > run
> > the query i got the error msg box :: [Microsoft][ODBC Sql Server
> > Driver][Sql
> > Server]Line1: Invalid column name X .
> >
> > But a column with the company value as X exists!
> >
> > Also when i tried to use a little different query:: SELECT * FROM TABLE
> > WHERE Company LIKE s % , then i get the same error but the end part of
> > the
> > error message says Incorrect Syntax Near %
> >
> > Why is this happening?
> > --
> > pmud
>
>

[Microsoft][ODBC Sql Server Driver][Sql Server]Line1: Incorrect Sy

Hi,
I am using SQL server 2000. One of the tables in it has become really large
so i tried to use a sql query to view only a certain rows. I used the
following query:
SELECT * FROM TABLE WHERE Company= X
When i verified the syntax , it verified correctly. Buy when i tried to run
the query i got the error msg box :: [Microsoft][ODBC Sql Server Dr
iver][Sql
Server]Line1: Invalid column name X .
But a column with the company value as X exists!
Also when i tried to use a little different query:: SELECT * FROM TABLE
WHERE Company LIKE s % , then i get the same error but the end part of the
error message says Incorrect Syntax Near %
Why is this happening?
--
pmudIt's a string, you need string delimiters.
WHERE Company='X'
http://www.aspfaq.com/
(Reverse address to reply.)
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> Hi,
> I am using SQL server 2000. One of the tables in it has become really
large
> so i tried to use a sql query to view only a certain rows. I used the
> following query:
> SELECT * FROM TABLE WHERE Company= X
> When i verified the syntax , it verified correctly. Buy when i tried to
run
> the query i got the error msg box :: [Microsoft][ODBC Sql Server
Driver][Sql
> Server]Line1: Invalid column name X .
> But a column with the company value as X exists!
> Also when i tried to use a little different query:: SELECT * FROM TABLE
> WHERE Company LIKE s % , then i get the same error but the end part of
the
> error message says Incorrect Syntax Near %
> Why is this happening?
> --
> pmud|||you need single quotes around all character fields
SELECT * FROM TABLE WHERE Company= 'X'
SELECT * FROM TABLE WHERE Company LIKE 's %'
-Andre
"pmud" <pmud@.discussions.microsoft.com> wrote in message
news:A17DE491-DF25-47D0-BBA4-F84A2FE6602A@.microsoft.com...
> Hi,
> I am using SQL server 2000. One of the tables in it has become really
> large
> so i tried to use a sql query to view only a certain rows. I used the
> following query:
> SELECT * FROM TABLE WHERE Company= X
> When i verified the syntax , it verified correctly. Buy when i tried to
> run
> the query i got the error msg box :: [Microsoft][ODBC Sql Server
> Driver][Sql
> Server]Line1: Invalid column name X .
> But a column with the company value as X exists!
> Also when i tried to use a little different query:: SELECT * FROM TABLE
> WHERE Company LIKE s % , then i get the same error but the end part of
> the
> error message says Incorrect Syntax Near %
> Why is this happening?
> --
> pmud

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name on Linked Server

Hi Folks,
I'm having a strange situation here between 2 Linked MS SQL 2K servers.
One of the servers died recently and I rebuilt it.
All seems to be working fine, except that when I create views that access tables on the other (linked) server, I can not modify any data, because I get the [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name server.database.dbo.TableName error.
The View does work fine otherwise, ie displays the data in it, I just can't modify.
The Linked Servers are done with the sa user between these 2 servers.

Any ideas what could be causing this error?
Thanks!-- bump --
no one ideas on this?|||I'm also having problems with this - mine is in relation to a labeler printer, it is present in my ODBC and the test is successful. However, when I go to print I get the following error: [microsoft][ODBC SQL Server Driver][SQL SERVER] Invalid object name 'table name' ODBC -- call failed

I can't seem to see what the problem is as my project server works from this client.

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

Quote:

Originally Posted by daxter

hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

Try using

\Control Panel\Administrative Tools\Data Sources (ODBC)

And System DNS tab up the top of that window

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

From Enterpise Manager I create a user, giving all available rights. I have created a DB and set this user to be everything for it (except deny). I create tables as this user on the above DB. When I try to access these tables with an app using ODBC, the specific error appears.
Please assist fellas - situation critical.
Thanx.Refer to this KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q218/9/95.asp&NoWebContent=1) to resolve the issue.|||Thanx for the info but it didn't work.|||If you created the objects as the user, then they are owned by the user, and will be named [ownername].[objectname].

If your sql code does not specify a ownername sqlserver assumes dbo ownership, and your objects don't exists as dbo.[objectname].

Either specify the owner name when you reference the objects,
or instead of granting all individual rights to the user just grant it dbo access to the database. Then any objects it creates will be dbo owned and will not need to be fully referenced.

blindman

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

I have a ms sqlserver 2000 database installed on my Windows NT4 PC.

I want to access this database from a java program using JDBC - ODBC

Here are the relavent lines of code from my java source code file.

Note : I am attempting to access the sample database "Northwind Traders" that came with the installation.

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver").newInstance();
datasource = "NORTHDS";
url = "jdbc:odbc:" + datasource;
con = DriverManager.getConnection(url,username,password) ;
query = "SELECT * from " + datasource + "." + username + "." + tablename;
ResultSet rs = stmt.executeQuery(query);

The connection succeeds but the query fails with :
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'NORTHDS.username.Customers'.

Using the program "Microsoft Access" I was able to verify that the "Customers" table is intact.

Any ideas ?Take a look at the following:

In your select statement there are a couple of potential problems that you need to verify.

select * from datasource.username.table ... which is returning 'NORTHDS.username.Customers'

should be

select * from Northwind.dbo.Customers ... (unless you renamed the database ...)

In other words, check to make sure your are referencing the correct database/owner/table in your select statement. It appears that the variables you are using are incorrect. tablename appears to be ok, but the username variable is returning username. Also, the datasource variable may not be your database name.

[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID)

Hi!

Im having this error when doing a query to a SQL Server 2000 Database:

Microsoft OLE DB Provider for ODBC Drivers error
'80004005'

[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error
(bad page ID) detected during read at offset
0x000000003ac000 in file 'E:\Program FIles\Microsoft SQL
Server\MSSQL\Data\sitioIAC_Data.MDF'.

It doesnt happend in some queryes trough a ASP file.

What could it be??

Thank You
JuanRun DBCC CHECKDB against that table(s) with REPAIR_ALLOW_DATA_LOSS option. Refer to BOL for more information on DBCC CHECKDB & CHECKTABLE topics.

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure

I am new to SQL Server and stored procedures and here is my problem.

I am stepping into a stored procedure ‘storedProced1’ using T-SQL debugger. ‘storedProced1’ is calling ‘storedProced2’. When I step into the following line where storedProced2’ is being executed,

exec storedProced2 @.Parameter1, @. Parameter2, @. Parameter3

I got the following message in the immediate window.

[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find stored procedure 'storedProced2’.

@.RETURN_VALUE = N/A

But “storedProced2” does exists. What am I doing wrong?

Make sure that the procedure exists within the actual database and make sure that you are using the right owner declaration for this, this calling the procedure with the Routine_Schema and Routine_Name from the following query.

SELECT Routine_schema, ROutine_name
From INFORMATION_SCHEMA.Routines
WHere Routine_Name = 'storedProced2'

--> Calling EXEC <SchemaName>.<Objectname>

HTH, jens K. Suessmeyer.

http://www.sqlserver2005.de

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241:The media family on device

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC
SQL Server Driver][SQL Server]The media family on device
'G:\WBTNVDS031\SQLBackup\I_WBTNVDS031A\MAILSUPP\MAILSUPP_db_200605110530.BAK'
is incorrectly formed. SQL Server cannot process
this media family.
[Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
terminating abnormally.Hi
It sounds like the backup may be corrupted, have you tried using RESTORE
HEADERONLY ?
John
"csesaravana@.gmail.com" wrote:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3241: [Microsoft][ODBC
> SQL Server Driver][SQL Server]The media family on device
> 'G:\WBTNVDS031\SQLBackup\I_WBTNVDS031A\MAILSUPP\MAILSUPP_db_200605110530.BAK'
> is incorrectly formed. SQL Server cannot process
> this media family.
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is
> terminating abnormally.
>
>