ODBC connect styring does not work

Porting a C Db-library program to ODBC connectivity for Sql Server 2000 SP4.When SQLDriverConnect(hdbc, GetDesktopWindow(), "DSN=HOST_ODBC_DB;UIDDBMS=usercode2;PWDDBMS=password2;", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_COMPLETE) is used, a dialog window pops up. I enter the password and successfully connect to Sql Server 2000. Of course the usage of SQL_DRIVER_COMPLETE is causing the above "UIDDBMS=usercode2;PWDDBMS=password2;" to be ignored in the connect string.If instead the above connect string is used with SQL_DRIVER_NOPROMPT rather than SQL_DRIVER_COMPLETE the following errors are received:[28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (18452)[01S00] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0)What is causing this?What is the server working on, only on Windows Authentication or on Mixed Authentication, the (null) indicated that its using Windows Authentication but did not get the credentials from the client because either the client passed SQL Server credentials or the Windows account could not be passed.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de
|||

The database server is configured for both Windows and database server authentication. The original Db-library C program version can connect using either authentication type.

The ODBC ported C program version can connect using a Windows authentication connect string with: SQLDriverConnect(hdbc, GetDesktopWindow(), "DSN=host_ODBC", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT.

It cannot connect using a database server authentication connect string of "DSN=host_ODBC_DB;UIDDBMS=usercode2;PWDDBMS=password2".

The host_ODBC odbc data source was configured for Windows authentication. The host_ODBC_DB odbc data source was configured for database server authentication.

Why does database server authentication fail?|||

Which ODBC driver do you use?

Can you try using "UID" and PWD" instead of "UIDDBMS" and "UIDPWD"?

This posting is provided "AS IS" with no warranties, and confers no rights.

ODBC Connect Failed in SQL Job

I am running SQL Server 2000 sp4 in Win Server 2003. I have a DTS

packages which connects to FileMaker 6 files via the ODBC driver

installed with FielMaker.

The DTS packages work correctly when

executed directly. However, when executed from a SQL Server Agent job,

the same DTS packages fail. Always with the same message:

Error: -2147467259 (80004005);
Provider Error: 16394 (400A)
Error string: [FileMaker][ODBC FileMaker Pro driver][FileMaker Pro]Connect failed
Error source: Microsoft OLE DB Provider for ODBC Drivers

Searching

for info on the above message seems to indicate a permissions problem.

However, I am running the jobs with an full administrator account. All

connections and the FielMaker files reside on the one server.

Any help on this would be greatly appreciated.

Thank you.

The error you saw is very general, the message indicated a connection fail, so please provide your connection string, and try to connect to your sql instance by simply use osql.exe, if failed, that means the basic connection did not work on your server, otherwise, the error triggered during data operation, then you need sql profile to track which client operation cause server close connection.

Thanks!

Ming.

ObsoletedSprocException is being thrown

I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsa
geHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David

ObsoletedSprocException is being thrown

I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegroups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David

ObsoletedSprocException is being thrown

I have run into a strange problem with SQL Server 2000 (SP4). I am
calling a fairly simple stored procedure that selects a set of data
from one table based on several parameters passed in (combination of
varchar and int).
The problem is that everytime I execute this procedure, SQL server
returns with:
Server: Msg 50000, Level 16, State 1, Procedure
dl_CARDEX_GetUsageHistory, Line 11
ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
dl_CARDEX_GetUsageHistory is the name of my sproc.
I spliced out the select statement and it runs fine in Query Analyzer.
I googled for 'ObsoletedSprocException' and couldn't find a single
reference to it!
It's coming right from SQL Server as I get this message directly from
Query Analyzer when executing the sproc.
Any ideas? Very odd that no one has posted anything about this
exception before.
Thanks,
"Tom" <tdietz@.gmail.com> wrote in message
news:1166111230.919365.237940@.l12g2000cwl.googlegr oups.com...
>I have run into a strange problem with SQL Server 2000 (SP4). I am
> calling a fairly simple stored procedure that selects a set of data
> from one table based on several parameters passed in (combination of
> varchar and int).
> The problem is that everytime I execute this procedure, SQL server
> returns with:
>
> Server: Msg 50000, Level 16, State 1, Procedure
> dl_CARDEX_GetUsageHistory, Line 11
> ObsoletedSprocException:dl_CARDEX_GetUsageHistory.
> . . .
From BOL
When RAISERROR is used with the msg_id of a user-defined message in
sys.messages, msg_id is returned as the SQL Server error number, or native
error code. When RAISERROR is used with a msg_str instead of a msg_id, the
SQL Server error number and native error number returned is 50000.
http://msdn2.microsoft.com/en-us/library/ms177497.aspx
So what is on line 11 of the procedure dl_CARDEX_GetUsageHistory?
RAISERROR?
David