Client ODBC Errors

Jul 20, 1999

As a SQL adminstrator any maintenance I perform including performing full database backups against the sql server with users connected to a certain database, causes the odbc connection to fail between the web server and the sql database. This causes all clients to experience an odbc failure. The only resolution is to reboot the webserver. There is ODBC driver incompatibilites that exist between the servers. Does anyone have any suggestions? I am in the process of a change control request to upgrade the ODBC on the production SQL server to 3.70.0623 the same as the web server but am not sure that this is the issue. Can there be something in the application itself that would be causing it to break and not reestablish the ODBC connection?

Thanks
David

View 1 Replies


ADVERTISEMENT

Can't Find SQL Native Client In ODBC Connection Manager In SQL Server Open Database Connectivity (ODBC)

Feb 13, 2007

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?

View 4 Replies View Related

ODBC Errors

Oct 8, 1999

We have recently upsized several Access databases to SQL 7.0. I created the ODBC datasource to an Access frontend. The tables open but I get the following error when I try to update any of the tables:

ODBC update on a linked table "tablename" failed.

Followed by:

[Microsoft][ODBC SQL Server Driver][SQL Server]The text, ntext and image data types cannot be used in the WHERE, HAVING, or ON clause except with the LIKE or IS NULL predicates [#306].

I have downloaded the latest MDAC. Any ideas?

View 1 Replies View Related

SQL ODBC Errors

Apr 18, 2007

Hi,



I've Got SQL 2005 installed on SBS2003. I'm trying to connect to it from XP using User/System/File DSN connections. The error it returns when I try to test the connection is 'SQL server could not be found or access is denied. The Error Codes are SQL Server Error: 2 and SQL server error: 17.



All help is appreciated.



Thanks,



Rizwan

View 7 Replies View Related

Odbc Errors

Nov 16, 2006

Hi All,
I have a database using Access 2003 as a front end and SQL as a backend. I set up all permissions in SQL and linked all tables to the Access frontend. After putting the front end on the network for other users, they receive the following error: ODBC €” connection to <name> failed. (Error 3151) What do I need to do please

View 1 Replies View Related

Getting ODBC Timout Errors.

Feb 8, 2001

Hi Folks,

I'm getting a ODBC timout error when i try to login to SQL server. After the initial error i try connecting again, and it works. Why is it giving me an error in the first place and then when i try reconnecting it'll work? Does anyone know. Could it be i need to update my ODBC drivers. This error all of a sudden just started happening.

View 1 Replies View Related

Client EM Produce OS Failed Login Errors

Jul 23, 2005

hi all, have anyone else met with the following problem.we've got a SQL2000SP3a on a 2 active-active node clusters of W2K3,this cluster in using AD.I've found that whenever I use Enterprise Manager on my local computerto register the above instance, it will constantly produce "Failedlogin for <Domain><DomainUser>" errors in the Windows Security Log ofthe database server machine. There's no failed login in the SQL errorlog and I can work normally with the Enterprise Manager. The OS failedlogins error are gone once I un-register the instance from myEnterprise Manager.Does anyone know or met with this before?

View 1 Replies View Related

Client/server ODBC Problem

Nov 6, 2004

I have an application on:

W2K client
Sql 2000 + No SP
MS ODBC V3.8
C++

The application, running on the client, connects to SQL server for many simultaneous queries involving select, insert and update. Application creats a thread for each query. Each thread connects to the sql server via ODBC using sqlconnect.

However I find that the individual thread do not close properly and stay open even after sqldisconnect has been issued on the client. At one point I have over 1200 threads on client application trying simultaneously to connect to the server and the sqlserver is holding with 276 threads open.

I do not understand why the ODBC connection stays open even after sqldisconnect is issued. I have even tried disabling connection pooling, to no effect. The performance is very poor.

How can I issue a large number of queries to same sql server via ODBC while guaranteeing performance?

View 2 Replies View Related

ODBC And SQLServer : Does I Need The Client Installed On ?

Jul 20, 2005

Hi,Does I need to install the mssql client binaries to use ODBC toconnect to a mssql database ?TYIArjp

View 2 Replies View Related

Odbc Using Native Client Fail

Aug 26, 2007

I installed sql2005 on server, created odbc connection , sucess connection.
I installed native client on pc. pc ping server sucessfully. I created odbc using sa with valid password (as i do in server), when completing give error " sql server does not exist or access denied" , and can not connect with server.
how can i resolve the problem.

View 1 Replies View Related

Odbc Errors On Terminal Server

Jul 23, 2005

We connect via terminal services to an excel spreadsheet that has anODBC link to an access database using a pivot table, when we try torefresh the data within the excel spreadsheet we receive the followingerror "the microsoft jet database engine cannot find the input table orquery....."this works ok if the user connects to terminal services as theadministrator however if they connect as any other issue it won't workAnyone got any ideas?(have tried 2000 ts and 2003 ts)

View 3 Replies View Related

ODBC Connection Not Terminating After Client Diconnects

Jan 9, 2001

Hi,

We have SQLSERVER 7.0 in one of the production.
The clients r connected thru ODBC.
The clients doesn't gets disconnected after a task result in
increase in sqlserver log.

Can anyone advice me .

Thanks in advance
Anu

View 2 Replies View Related

ODBC Connection Issue On Client Site

Jun 7, 2007

Hi,
I am not sure if I select right Froum:)
It might be a basic question but could you please help me on that?



Working Environment:



I have developed application on SQL Server 2005 and now wants to Run on Client Site, I am using access as a front end and SQL server 2005 back end through ODBC (System Dsn) which is working good. (user has been added on SQL Server and on Database)



Question:

1) Do I need to create new System Dsn Or other DSN (Keep in mind I have already create System DSN in Server) at each client site to access application from Server?

(If yes then I am trying to do that, it allow me to create (with required database which is on Server) and verify but doesn’t save on ODBC list so I can’t use that name to run appliation on client site)



I am using windows authentication.



Thanks for help in advance



AA

View 4 Replies View Related

ODBC Connection Issue On Client Site

Jun 7, 2007

Hi,


It might be a basic question but could you please help me on that?

Working Environment:

I have developed application on SQL Server 2005 and now wants to Run on Client Site, I am using access as a front end and SQL server 2005 back end through ODBC (System Dsn) which is working good. (user has been added on SQL Server and on Database)

Question:
1) Do I need to create new System Dsn Or other DSN (Keep in mind I have already create System DSN in Server) at each client site to access application from Server?
(If yes then I am trying to do that, it allow me to create (with required database which is on Server) and verify but doesn€™t save on ODBC list so I can€™t use that name to run appliation on client site)

I am using windows authentication.

Thanks for help in advance





View 1 Replies View Related

SQL Server 2005 Communcations Errors Through ODBC

Aug 10, 2006

I am the DBA for a product development company with an application currently connected to and running fine on SQL Server 2000. I have recently installed our product on 2005 sql server with compatability version of 90 and some folks have begun testing. Apparently, there are a lot of strange things happening and ODBC errors are frequent. The more they move around in the app, the more errors appear. Sometimes, they appear, sometimes they don't. The most common occurence is an error such as, x table is missing the following columns. Then the user does it again and does not receive the error. Another issues is "Application Terminating Due to Severe Database Error" and when we look at the logs our app generates:

08/10/2006 08:57:09
(01000/10054), [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
SQLColAttributes
08/10/2006 08:57:09
Table x.TS_X is missing the following columns:


The user has database role membership db_data_read and db_data_write access to the database.
MDAC version - 2.81.1117
ODBC version - 2000.85.1117

Could this be a permissions issue or possibly more of an ODBC issue? Any thoughts would be greatly appreciated

Thanks

View 7 Replies View Related

Odbc Errors After Joining New Domain With New User

Jun 14, 2007

Hi



I am new to this forum so I hope I have got the right one.



The problem I am having is I installed a new server into an office with 25 users. I joined the users to the new domain with new logins.



The server process then installed outlook 2003 onto each machine. Most machines are windows 2000



Problems arose in sage I have tied this down to the report designer and odbc.



On every machine bar 1 the report designer crashed when running a report. The problem like I said was that you cannot now connect to the odbc driver for sage and when you go into odbcad and try to look at the driver you get an error saying



The setup routines for the sage line 50 odbc driver could not be loaded due to system error 127



Then after that comes



Could not load the setup or translator library



I have looked on the net for this error and it tells you to look in the registry to make sure that the odbcinst is pointing to the correct location, I have checked this and it is. I ahve also checked the security and this seems ok aswell.



The next step was I loaded a fresh copy of windows 2000 into a new folder and tried to load the odbc driver again. This failed with the same as above.



This points to the software settings but I cannot find out where.



Iwas wondering if anyone has had the same problem and they could point me in the right direction.

View 4 Replies View Related

Girl In Need! Anyone Do This: Unix Client -&> ODBC -&> MSSQL Server

Jul 28, 2004

Anyone support a config where you have an unix/linux (AIX here) ODBC client connection to SQL Server database? I am looking for a simple, supportable configuration that does not require me to learn perl or instal a bunch of crap gnu shareware on enterprise class machines.

Please help!

View 2 Replies View Related

Cannot Connect To Sql Server 2005 From Xp Client When Trying To Create ODBC Dsn

Mar 2, 2007

Newbie here,

I am trying to link tables from an access 2003 frontend to sql server 2005 backend.

I am doing this in a vmware test environment. I am using vmware server and running sbs 2003 and xp sp2 client. Both virtaul machine can talk to each other(using local host connection).

I have tried to create a dsn to the sql server but i cannot connect. I can ping the sbs server through the command interface but the error i get when i try to connect is :

Connection failed:
Sql state: hyt00
sqlserver error: 0
microsoft odbc sql server driver timeout expired.

spent a day trying various combinations - still no joy.

Any help would be much appreciated

View 3 Replies View Related

SQL Native Client ODBC On Ia64 And SQLGetStmtAttr(SQL_ATTR_CONCURRENCY)

Dec 12, 2006

We've run into an issue running against the SQL Native Client ODBC driver (version 2005.90.2047.0) on Windows 2003 Server (Itanium). The "INFO: ODBC 64-Bit API Changes in MDAC 2.7" article (http://support.microsoft.com/kb/298678) doesn't say that the returned value for SQL_ATTR_CONCURRENCY changed to a 64-bit value, but if you request this attribute from the SQL Native Client driver, a 64-bit value is returned. The ODBC spec still indicates that SQL_ATTR_CONCURRENCY is a SQLUINTEGER value, which is 32-bit, even on a 64-bit platform.

This is easy to see by using the ODBC Test utility in the Windows SDK for ia64, "C:Program FilesMicrosoft SDKBinWin64ia64odbcte32.exe". If you connect to the SQL Server driver and then simply call SQLGetStmtAttr(SQL_ATTR_CONCURRENCY), you'll see that the *StringLengthPtr argument returns 8 bytes, when it should only return 4.

Note that we've also seen the same behavior with SQL_ATTR_ROW_BIND_TYPE as well as other statement attributes defined to return SQLUINTEGER values.

Has anyone else run into this?

Thanks,

Chris

View 3 Replies View Related

ODBC To SQL Express - SQL Driver Versus SQL Native Client

Aug 2, 2007



I have a SQL express database which I need to access from a shared hosting plan. I can create an ODBC connection through the hosting provider's control panel for SQL Server, but it won't connect. I tested this locally and discovered that the SQL Native Client connects fine, but the previous SQL Server driver does not. This seems to only happen with SQL 2005 Express edition; it works with the Developer Edition. Does SQL Express only use the Native SQL Client??

Thanks in advance for your help!

View 3 Replies View Related

Getting ODBC Connection Errors With SQL Server 2000 On Windows XP

Apr 21, 2008

Hi all-

I setup a new ODBC connection to MS SQL Server 2000 on Windows XP and keep getting the following errors when I try to
either register a new SQL Server 2000 group within Enterprise Manager or test the new ODBC connection:

Current configuration

- MS SQL Server 2000
-Windows XP
-ODBC 3.85.1117


Errors:

I. Within SQL Server 2000 Enterprise Manager

Error: SQL Server connection open

II. When I test the ODBC connection:

Microsoft SQL Server ODBC Driver Version 03.85.1117

Running connectivity tests...

Attempting connection
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not found.

TESTS FAILED!

Now here is what has me totally confused:

I can use the command line ISQL to access the database on the server and IP is all correct and port is available.

Any tips how to get this ODBC working?

Thanks
Ben Prusinski

View 1 Replies View Related

Queries Against Linked Server To Informix Via ODBC Errors

Oct 9, 2007

What can be the reason(s) why I can't get data from a linked server using an ODBC datasource that works fast & fine from MS Access?


I have an ODBC connection (System DSN) configured for an Informix ODBC driver.
The Test button (belonging to this driver-setup) reports a successfull connection test.
Getting data from this database by linking tables in MS Access works fast and easy.
But I have tried for many days now to setup a linked server from SQL Server (2005)
Creation goes fine, but as soon as I issue a query, (e.g. 'select * from infrem723...remotetable' or using 'openquery')
I get the following error:
---

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "MSDASQL" for linked server "infrem723" reported an error. The provider did not give any information about the error.

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "infrem723".

---

Why is Access able to read what "MSDASQL" cannot?
I am desperate - can anybody help?Thanks a lot!

View 8 Replies View Related

Help Usign GetDate() On A SQL DTS With IBM ISeries Client Access ODBC Driver

Oct 21, 2004

I have created a DTS package in SQL 2000 that connects to AS/400 via IBM iSeries Client Access ODBC drivers version R52. I got an error everytime I tried to use the GETDATE() function as follow:

Error Source : Microsoft OLE DB Provider for ODBC Drivers
Error Description : [IBM][iSeries ODBC Driver][DB@ UDB]SQL0204 - GETDATE in *LIBL Type *N not found

Can someone help?

Victor

View 1 Replies View Related

Is It Possible To Use A Simple ODBC Config On A Unix Client To Connect To MS-SQL Server?

Jul 20, 2005

Anyone support a config where you have an unix/linux (AIX here) ODBCclient connection to SQL Server database? I am looking for a simple,supportable configuration that does not require me to learn perl orinstal a bunch of crap gnu shareware on enterprise class machines.Please help!

View 3 Replies View Related

Database Mirroring, Client Connections All ODBC So What Methods Are Recommended?

Jun 5, 2006

As stated in the subject I have a situation where if database mirroring is employed for either manual or automatic failover, all the client (including web connections) connections use ODBC not ADO, or OLEDB etc... so what methods are recommended? Client side redirect is not available so I could not employe the "Data Source =A; Failover Partner=B..." option.

Right now the method employed (pre database mirroring and basically employing log shipping on SQL 2000) is to have a DNS alias for the ODBC connection so that if the server were to change in a failover situation the DNS record would have to be altered, so that all the client connections would not have to be reconfigured.

Regards,

Dominic Baines

View 5 Replies View Related

SQL Native Client ( ODBC ) Convert Function Unicode/SQL_DOUBLE

May 15, 2007

SQL Native Client 2005.90.3042.00 ODBC driver does not return SQL_CVT_DOUBLE as part of the mask from SQLGetInfo for SQL_CONVERT_WCHAR, SQL_CONVERT_WVARCHAR even though driver actually supports converting nchar and nvarchar to SQL_DOUBLE. For example,

select
{ fn convert(N'1.23', SQL_DOUBLE) }

works, but



SQLUSMALLINT nInfoType = SQL_CONVERT_WCHAR;

SQLUINTEGER nInfoValue = 0;

SQLRETURN rc = SQLGetInfo( hdbc, nInfoType, &nInfoValue, sizeof( nInfoValue ), NULL );



ASSERT( nInfoValue & SQL_CVT_DOUBLE ); // fails

View 3 Replies View Related

Connect SQL Server 2005 With ODBC Drive “SQL Native Client

Sep 13, 2007



Hi,



When I'm using SQL server 2005, and ODBC drive €œSQL Native Client€? I get an error when executing the below given code. Error Message: €œTransaction cannot start because more than one ODBC connection is in use.€?



But this works well with SQL Server 2000 with ODBC drive "SQL Native Client" and in SQL server 2005 also when I used ODBC drive €œSQL Server€?.



I used aTrgConn.Execute(€œBegin Transaction€?) and it's working properly. But unfortunately I cannot use this method, because I want to run the same code with Oracle ODBC as well.
Is this a known issue in SQL Native client drive with SQL server 2005? Do you know a solution for this?


Please Help..............



Thanks in advance.




Code:

Dim aTrgConn As New ADODB.connection
Dim aCmdIns As New ADODB.Command
Dim aCmdUpd As New ADODB.Command



aTrgConn.Open sConnStr



Set aCmdIns.ActiveConnection = aTrgConn
Set aCmdUpd.ActiveConnection = aTrgConn

aTrgConn.BeginTrans

View 6 Replies View Related

ODBC Connection For Client Application To SQL Server 2005 Express Installed On Network Computer

May 5, 2006

Hi All,

I've developed an application that connects to a SQL Server 2005 Express database. I created a DSN to connect to the database through ODBC. Currently, I am testing locally and everything works fine.

I would now like to install my application on another workstation and connect remotely to the database located on my development machine.

The client workstation does not have SQL Server 2005 Express installed on it because I would just like my application to connect remotely by creating the DSN and using ODBC. What I'm missing here are the database drivers. The "SQL Natice Client" is not available on this client workstation. How can I deploy the necessary drivers with my installation file so that I may create the required DSN name using the SQL Native Client driver?

Thanks!

View 6 Replies View Related

SQL Server VARCHAR(MAX) Column Returns Error While Inserting Records Into Table(ODBC Driver: SQL Native Client)

Aug 15, 2007

I created very simple table with 3 columns and one is varchar(max) datatype

When i insert records thru VC++ ADO code i am getting this error



Exception Description Multiple-step OLE DB operation generated errors. Check e
ach OLE DB status value, if available. No work was done. and Error Number:: -2147217887



ODBC Driver: SQL Native Client

SQL server 2005



Table

CREATE TABLE [dbo].[RAVI_TEMP](

[ID] [int] NULL,

[Name] [varchar](max) NULL,

[CITY] [varchar](50) NULL

)



VC++ code

#include "stdafx.h"
#include <string>
#include <strstream>
#include <iomanip>


int main(int argc, char* argv[])
{
try
{
HRESULT hr = CoInitialize(NULL);
_RecordsetPtr pExtRst = NULL;
_bstr_t bstrtDSN, bstrtSQL;
bstrtDSN = L"DSN=espinfo;UID=opsuser;PWD=opsuser;";
bstrtSQL = L"SELECT * FROM RAVI_TEMP";

_variant_t vartValueID,vartValueNAME,vartValueCITY;
_bstr_t bstrtValueID,bstrtValueNAME,bstrtValueCITY;

pExtRst.CreateInstance(__uuidof(Recordset));
hr = pExtRst->Open(bstrtSQL, bstrtDSN, adOpenDynamic, adLockOptimistic, adCmdText);

hr = pExtRst->AddNew();

bstrtValueID = L"1";
vartValueID = bstrtValueID.copy();

bstrtValueNAME = L"RAVIBABUBANDARU";
vartValueNAME = bstrtValueNAME.copy();

bstrtValueCITY = L"Santa Clara";
vartValueCITY = bstrtValueCITY.copy();

pExtRst->GetFields()->GetItem(L"ID")->Value = vartValueID;
pExtRst->GetFields()->GetItem(L"NAME")->Value = vartValueNAME;
pExtRst->GetFields()->GetItem(L"CITY")->Value = vartValueCITY;
pExtRst->Update();
pExtRst->Close();

}
catch(_com_error e)
{
printf("Exception Description %s and Error Number:: %d",(LPTSTR)e.Description(),e.Error());
return e.Error();
}
return 0;
CoUninitialize();
}


if i use regular SQL ODBC driver, no error but its truncating the data



Adv Thanks for your help

View 1 Replies View Related

ERROR [HY000] Or ERROR [23000] At Random Times When Using Sql Native Client Via ODBC

Apr 16, 2008

The following (VB.Net) code causes exceptions at seemingly random times.
Any suggestions?
Not sure if the problem is in .Net's ODBC support or in Sql Native Client.

If MARS is off, usually after less than 100 loops:



Code Snippet

System.Data.Odbc.OdbcException was unhandled
ErrorCode=-2146232009
Message="ERROR [HY000] [Microsoft][SQL Native Client]Connection is busy with results for another command"
Source="SQLNCLI.DLL"
Turning MARS is on bypasses that error, so it will sometimes survive a thousand or so runs before hitting:




Code Snippet

System.Data.Odbc.OdbcException was unhandled
ErrorCode=-2146232009
Message="ERROR [23000] [Microsoft][SQL Native Client][SQL Server]Cannot insert the value NULL into column 'Number', table 'tempdb.dbo.#TempTable___..(shortened to fit).. _________000000002F3F'; column does not allow nulls. INSERT fails.
Source="SQLNCLI.DLL"
Code here:
(Console Application, empty database,
Visual Studio 2005, .Net 2.0, Windows XP,SQL Server 2005 or SQL Express 2005, Local or Remote)





Code Snippet

Module Module1

Sub Main()

'Dim connection As New SqlClient.SqlConnection("database=TestDB;server=.sqlexpress;Integrated Security=SSPI;") 'Doesn't crash
'Dim connection As New OleDb.OleDbConnection("Provider=SQLNCLI;database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;") 'Doesn't crash

'Dim connection As New Odbc.OdbcConnection("Driver={SQL Native Client};Database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;") 'Crashes
Dim connection As New Odbc.OdbcConnection("Driver={SQL Native Client};Database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;MARS_Connection=yes") 'Crashes

VBMath.Randomize()

Dim run_count As Integer = 1
connection.Open()
Console.WriteLine("Connected!!")

While True
'connection.Open()

Dim testcmd As New Odbc.OdbcCommand("CREATE TABLE [#TempTable] (Number int PRIMARY KEY)", connection)
testcmd.ExecuteNonQuery()
testcmd.Dispose()
testcmd = Nothing

Dim dtTemp As New DataTable
Dim daTemp As New Odbc.OdbcDataAdapter("SELECT * FROM [#TempTable]", connection)
daTemp.MissingSchemaAction = MissingSchemaAction.AddWithKey
daTemp.Fill(dtTemp)
Dim cbTemp As New Odbc.OdbcCommandBuilder(daTemp)
Dim viewTemp As New DataView(dtTemp, Nothing, "Number", DataViewRowState.CurrentRows)

Dim i As Integer
For i = 1 To 1000
Dim test_number As Integer = CInt(Rnd() * 2000)
If viewTemp.Find(test_number) = -1 Then 'Keep it unique
Dim new_temp_row As DataRowView = viewTemp.AddNew()
new_temp_row("Number") = test_number
new_temp_row.EndEdit()
End If
Next

daTemp.Update(dtTemp)

'daTemp.Dispose()
'daTemp = Nothing

'cbTemp.Dispose()
'cbTemp = Nothing

'dtTemp.Dispose()
'dtTemp = Nothing

'viewTemp.Dispose()
'viewTemp = Nothing


Dim testcmd2 As New Odbc.OdbcCommand("DROP TABLE [#TempTable]", connection)
testcmd2.ExecuteNonQuery()
testcmd2.Dispose()
testcmd2 = Nothing

'connection.Close()
'GC.Collect()

'Console.Write(".")
run_count += 1
End While

End Sub

End Module

Usually the ".Update" triggers the exception, but sometimes the other sql commands do it.
Have tried various experiments with disposing of objects immediately when finished, but no effect.
Opening and closing the connection each loop seems to delay the errors, but it still happens eventually.

View 7 Replies View Related

No Failover And Client Crashes ODBC DSN Setting For Failover In Connection String

Mar 3, 2007

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

View 1 Replies View Related

Client With Tcp/ip Produce &#34;time Out Error&#34; While Same Client While Switced To Named Pipes

May 28, 2001

We have 15 clients running our applicaton
14 of then conected to SQL server using TCP/IP and it runs fine

1 of 15 when connected using TCP/IP produce "..Time out error "
but runs fine when swiched from TCP/IP to Named pipes

1.What area should we look to correct problem with Time out using TCP/IP ?
2. Where to get information about using TCP/IP via Named pipes ?

View 1 Replies View Related

Install SQL Server2005 Error:[Native Client]Encryption Not Supported On The Client

May 10, 2006

Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

View 78 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved