ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on Windows XP it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
VadimIt should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on Windows XP it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on windows xp it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
Vadim
It should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on windows xp it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>
|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on windows xp it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
VadimIt should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on windows xp it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> I have a client server app that connects to sql server through ODBC, it
>> works fine when connecting to sql server 2005 32 bit, but when connecting
>> to sql server 64 bit from the client on windows xp it behaves strangely,
>> are there separate set of odbc drivers that one has to use to connect to
>> sql server 2005 64 bit, even from 32 bit machine.
>> Thank you
>> Vadim
>sql

ODBC Connection Problems

I'm having problems connecting to an MSDE database through ODBC.
The following message appears below:

Connection Failed:
SQL State: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
Connection Open (Connect())
Connection Failed:
SQL State '08001'
SQL Server Error 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL
Server does not exist or access denied

I've tried the following
1. Downloading the lastest version of MDAC.
2. Tried Pinging the server which was successful.
3. Setting up an ODBC connection to the server from another client which was successful.
4. Adding an entry in my hosts file to see the server.
5. Searching the archives for a solution.

Does anyone have any other ideas as I stumped?

Thanks.Are you sure you have declared the full server (and instance) name for the MSDE instance? Check services on the MSDE box, and look for MSSQL$___. The ___ is the instance name. Also, are you able to connect to the MSDE instance with any other tools (Query Analyzer, OSQL, etc.)?|||It's quite embarrassing but someone put the wrong IP address label on the server. Thanks for your help.|||As fate would have it, I am encountering a very similar problem. Everything was working fine and dandy up until two days ago when suddenly you were unable to connect to SQLServer.

At first, you were able to connect via EM but not Query Analyzer. Now suddenly you're unable to connect using either. This literally happened overnight. I'm gettign the same error message as referenced above. I'm able to ping the box just fine, but cannot isql into it or use Query Analyzer/EM.

I'm running SQL2K on SP3 / Windows 2000 Advanced Server.

ANY suggestions would be greatly appreciated.

P.S. - One of the boxes is a development box and one is a production machine. I have considered installing MDAC 8 on the dev machine to see if this does the trick. Has this worked for anyone else who was having a similar problem, and what - if any - were the side effects?

Thanks again!|||...also forgot to mention that I'm unable to create an ODBC connection to the servers as well.

Thanx

ODBC Connection failure

My application (written in a proprietary old 4GL) is connecting to a SQL 2000 database via ODBC

This works fine nearly all the time, but occasionally, it throws the following error when trying to connect :

Connection Failed

SQLState '01000'

SQL Server Error: 10060

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open(Connect()).

Connection Failed:

SQLState '08001'

SQL Server Error: 17

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

This error is displayed in a Windows dialog box. When the OK button on this dialog is clicked, it throws up a login/password box. When this is filled in and submitted, the connection is usually made cleanly and the application continues.

The big problem is that the application is an unattended service, and this dialog can go unnoticed for quite a while.

If these dialogs are 'Cancelled' rather than 'OK'd, the 4GL receives the error and arranges to re-try the connection itself.

Is ODBC responsible for popping up the interactive dialog, and, if so, can I do anything to force it to return an error instead ?

Hi Steve,

Interesting situation. The error 10060 means this: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. So you are probably experiencing a timeout in one of the socket-relation ops, most probably connect() (different from the SQL netlib's Connect() mentioned above).

The login popup is implemented by the SQL ODBC driver. You are probably using SQLDriverConnect in ODBC? It has a parameter "DriverCompletion", which could be:

SQL_DRIVER_PROMPT
SQL_DRIVER_COMPLETE
SQL_DRIVER_COMPLETE_REQUIRED
SQL_DRIVER_NOPROMPT

You probably have passed the first one (SQL_DRIVER_PROMPT). In order to make sure the SQLDriverConnect fails without popping up the troublesome dialog, you need to pass the SQL_DRIVER_NOPROMPT. I truly hope you are able to modify the 4GL application?

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks a lot Jivko.

Unfortunately, the only parameter the 4GL allows me to specify is the DSN name.

I'll be on to the vendor's support desk rather forcefully first thing on Monday morning - thanks for the Ammo!

ODBC Connection failed

I am having an issue connecting to a SQL server under
windows Xp and office 2003. This is the error it gives.
****
Connection Failed
SQL State : 'HY000'
SQL Server error : 0
[Microsoft][ODBC SQL server driver]Cannot generate SSPI
content
****
Connecting to the same Database on the SQL server works
perfect on a Windows 2000 machine, running Office XP.
Any Ideas?
Thanks,
AndyWinXP Pro to SQL Server 2000 on Win2000 server: I'm having this problem also
, after about an hour. It works fine for that long then fails.
Connection failed:
SQLState 'HY000
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver] Cannot generate SSPI context
Logout and back in has no effect, only rebooting clears the problem which th
en works fine for another hour or so. Not much time to get any serious codin
g and testing done.

odbc advantages?

What are the advantages / disadvantages of using odbc to connecting to a
(mysql) database?
StefanStefan,
This is a SQLServer newsgroup.You will have better luck trying a mysql one.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Stefan Richter" <spam@.spammenot.com> wrote in message
news:c6kbie$vkn$1@.otis.netspace.net.au...
> What are the advantages / disadvantages of using odbc to connecting to a
> (mysql) database?
> Stefan
>

odbc advantages?

What are the advantages / disadvantages of using odbc to connecting to a
(mysql) database?
Stefan
Stefan,
This is a SQLServer newsgroup.You will have better luck trying a mysql one.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Stefan Richter" <spam@.spammenot.com> wrote in message
news:c6kbie$vkn$1@.otis.netspace.net.au...
> What are the advantages / disadvantages of using odbc to connecting to a
> (mysql) database?
> Stefan
>

ODBC 4,099 byte record limit?

I'm connecting to an Access DB through ODBC on a windows server from a PHP
page. The problem is the text retrieved from the select (nfo) is truncated
at
4,099 bytes everytime.
How to I get around this 4k limit?
I read about SET TEXTSIZE but I don't know how to use it in the script?
The full text is in the DB field so it is being truncated somewhere in the
ODBC.
PHP Script:
--
$connect = odbc_connect("datab_nfo", "", "");
$query = "SELECT nfo FROM Titles where ID=15";
$result = odbc_exec($connect, $query);
while(odbc_fetch_row($result)){
$nfo = odbc_result($result, 1);
print("$nfo\n");
}Look for these values in php.ini
; Valid range 0 - 2147483647. Default = 4096.
;mssql.textlimit = 4096
; Valid range 0 - 2147483647. Default = 4096.
;mssql.textsize = 4096
"Repo" wrote:

> I'm connecting to an Access DB through ODBC on a windows server from a PHP
> page. The problem is the text retrieved from the select (nfo) is truncated
> at
> 4,099 bytes everytime.
> How to I get around this 4k limit?
> I read about SET TEXTSIZE but I don't know how to use it in the script?
> The full text is in the DB field so it is being truncated somewhere in the
> ODBC.
> php Script:
> --
> $connect = odbc_connect("datab_nfo", "", "");
> $query = "SELECT nfo FROM Titles where ID=15";
> $result = odbc_exec($connect, $query);
> while(odbc_fetch_row($result)){
> $nfo = odbc_result($result, 1);
> print("$nfo\n");
> }
>
>

ODBC 4,099 byte record limit?

I'm connecting to an Access DB through ODBC on a windows server from a PHP
page. The problem is the text retrieved from the select (nfo) is truncated
at
4,099 bytes everytime.
How to I get around this 4k limit?
I read about SET TEXTSIZE but I don't know how to use it in the script?
The full text is in the DB field so it is being truncated somewhere in the
ODBC.
PHP Script:
$connect = odbc_connect("datab_nfo", "", "");
$query = "SELECT nfo FROM Titles where ID=15";
$result = odbc_exec($connect, $query);
while(odbc_fetch_row($result)){
$nfo = odbc_result($result, 1);
print("$nfo\n");
}
Look for these values in php.ini
; Valid range 0 - 2147483647. Default = 4096.
;mssql.textlimit = 4096
; Valid range 0 - 2147483647. Default = 4096.
;mssql.textsize = 4096
"Repo" wrote:

> I'm connecting to an Access DB through ODBC on a windows server from a PHP
> page. The problem is the text retrieved from the select (nfo) is truncated
> at
> 4,099 bytes everytime.
> How to I get around this 4k limit?
> I read about SET TEXTSIZE but I don't know how to use it in the script?
> The full text is in the DB field so it is being truncated somewhere in the
> ODBC.
> PHP Script:
> --
> $connect = odbc_connect("datab_nfo", "", "");
> $query = "SELECT nfo FROM Titles where ID=15";
> $result = odbc_exec($connect, $query);
> while(odbc_fetch_row($result)){
> $nfo = odbc_result($result, 1);
> print("$nfo\n");
> }
>
>

odbc + sql problem

Anyone could please help me ?
I have a simple asp program connecting to sql7.0.
I have the system dsn setup already.
After I transfer everything from the old hard disk to new hard disk, I
cannot login through asp program anymore. Below is the error message but I
don't know why it has to do with the iusr account. Thanks a lot. (any image
of setup would be helpful)
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'CENTRAL\IUSR_CENTRAL'.So, the error message is that this user:
doesn't exist as a SQL login.
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'CENTRAL\IUSR_CENTRAL'.
175671 PRB: 80004005 ConnectionOpen (CreateFile()) Error Accessing SQL
http://support.microsoft.com/?id=175671
307002 PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User
http://support.microsoft.com/?id=307002
176380 How To Use ASP with a SQL Trusted Connection with Guest Account
http://support.microsoft.com/?id=176380
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.