I have a SQL server with mixed authentication, the user 'sa' is the password zitiz configured. And attach the database server. Locally connection not informing me about errors connection, but when I try to access from the client informs me that there is no server or SQL server has been denied access to the same.
Parameters connection are in a file. Ini contains:
DriverName=MSSQL
HostName=ST-02SQLEXPRESS
Database=MANEXKA
USER_NAME=sa
Password=zitiz
BlobSize=-1
ErrorResourceFile=
LocaleCode=0000
MSSQL TransIsolation=ReadCommited
OS Authentication=True
It has windows xp sp2, framework. Net 2.0 on the server and the client and the firewall is disabled.
How to verify the client or the need to configure the server?
On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
Hi ;I m trying to create Merge Replication. I was able to create thereplication on the same machine, however my aim is to use clientmachine and do all the neessary work on the client machine and thensynchronize to the server. Thus, I have installed client version of SQL2000, I connected to the database server, the thing is when I go offline I lose connection. Is there any way to create the subscription into the client machine as an off line user then synchronize it ?Or DO Ihave create my shopshot on the client machine?If someone can help me I would really appreciateRegardsAs
I'd like to do this:Have a SQL Server database hosted on a public facing web server.I want it to be held at an ISP/Web hosting company. Though I have ADSL hereI don't want to manage a server.I want some ASP pages accessing the database.I would also like for a very small number (probably 2) of users to accessthe database from a richer client. Perhaps Access/VB.I've tried using www.shanje.com, as a test. It seems to work, though thereare worries about security.I want to keep cost down!On 'normal' shared MS hosting, would it be possible to connect to the dbfrom a client like Access. The way most web hosts talk it doesn't look likeit.Is there any way of providing a richer client interface than plain webpages? I want things like autocomplete (beyond the first character) for dropdowns, keyboard shortcuts etc.This would be low volume. Essentially a private database held on theinternet.Yours, Jo
Our 32-bit applications connect to SQL Server 32-bit through OLEDB with Shared memory as preferred protocol. Our client applications and SQL Server generally reside on same machine. We are evaluating possible impact when SQL Server 2008 64-bit is accessed with our 32-bit client applications running on 64bit WindowsServer 2008. Can shared memory protocol will be still used by underlying SQL server OLEDB dll considering the client application is 32-bit where as SQL Server is 64-bit ? Or it will switch to Named pipes or TCP/IP automatically ?
Hi,I am seeing very slow connections from some client enterprise managersto server. Even at server level it takes 1 minute or less to open adatabase. I have adjusted some of the memory for the SQL server, butthere are only about 60 Dbs on the server, totalling about 2 GBs.CPU is very low at all times, 1 GB of ram, p3 1.4Ghz. SQL 2k.I know I should refrag the disk, but is there anything else I can doto speed up SQL operation via enterprise manager--ODBC connections is fairly fast, as well as query analyzer.Adam
I am a SQL DBA involved in accomplishing various activities using Enterprise Manager by regestering servers of various countries.
Now as the NT Team has gone for auditing implementation in all the servers in OS lever, they find Access violations from the workstation from where I connect to the server. This does not happens if I unregester the Servers from Enterprise manager and use only query analyzer.
Note: We have our own users in OS as wel as in SQL SERVER .
I have tried this on several different operating systems (VISTA and XP ) and several versions of SQL NATIVE CLIENT including 2005.90.3042.0
I have a 64 bit "SQL NATIVE CLIENT" connection that fails. The exact same connection and code succeeds on 32 bit. My customer and I prepend "oledb:" to the connection string and it starts working.
FAILS on 64 bit: Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
WORKS oledb:Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
I debugged my code to the point that I know it is happening when I call CreateAccessor for my SQL statement.
We have a database residing on a SQL Server 2012 Express system running under Windows Server 2012. I have installed the SQL 2012 Native Client on the user's workstation. I created the System DSN with the required settings and when I test the connection all tests pass. I am able to ping the server as well as connect to it via SQL Server Management Studio.
Now when the user launches the application he is presented with the dialog window as in Screenshot1 (see attached). After clicking on Ok he is next presented with the dialog window where he has to select the SQL server. See attached Screenshot2. The user selects the SQL server from the drop down list and he is then able to access the application and work normally. I cannot understand why this is happening because I have included the correct server instance in the DSN settings i.e. sqlserversqlexpress
Telling the user to select the server himself is not an option for us.
I have checked the settings on the SQL Server. TCP/IP is enabled, remote connections are allowed and there is no firewall blocking. Port 1433 has been set as the default port to use.
I have an issue with SMTP server " send mail task ". we see the following error [Send Mail Task] Error: An error occurred with the following error message: "The SMTP server requires a secure connection or the client was not authenticated.In SMTP connection manager what we should give in SMTP SERVER, if we use gmail id's in send mail task editor.
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?
we have tables with many image columns. We fill these image columns via ODBC and SQLPutData as described in MSDN etc (using SQL_LEN_DATA_AT_EXEC(...), calling SQLParamData and sending the data in chunks of 4096 bytes when receiving SQL_NEED_DATA).
The SQLPutData call fails under the following conditions with sqlstate 08S01
- The database resides on SQL Server 2000 - The driver is SQL Native Client - The table consists e.g. of one Identity column (key column) and nine image columns - The data to be inserted are nine blocks of data with the following byte size:
1: 6781262 2: 119454
3: 269 4: 7611
5: 120054
6: 269
7: 8172
8: 120054
9: 269 The content of the data does not matter, (it happens also if only zero bytes are written), nor does the data origin (file or memory).
All data blocks including no 7 are inserted. If the first chunk of data block 8 should be written with SQLPutData the function fails and the connection is broken. There are errors such as "broken pipe" or "I/O error" depending on the used network protocol.
If data no 7 consists of 8173 bytes instead of 8172 all works again. (Changing the 4096 chunk size length does not help)
Has anybody encountered this or a similar phenomenon?
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?
Attempting ODBC connection to SQL Server by MachineNameSqlServerName doesn't work. Can only connect by using IP address of server machine with name of SQL Server instance. Any help would be appreciated. thanks
I have installed SQL Server 2005 on my Domain Controller successfully and installed the SQL Server tools from the DVD including workstation components on my XP client computer (which is actually hosting the Domain controller as virtual VMWare machine). The authentication is set to mixed mode and I have created a login with all possible rights on SQL Server, but which is at the same time my Domain Admin (So the user is setup in SQL Server in the format Domainuser)
Now when I open any client program (SQL Srvr2005 Management console, or Toad for SQLSrvr) and try to connect, the client does find the server correctly, but I cannot login. The error status is actually 1, which means "unexpected internal error" as far as I have read. I have turned off Windows firwalls by default and also turned off my custom firewall to see if it makes a difference, but it doesn't.
My activated connection protocol on both the server and the client is TCP/IP and I have then changed the port on both the server and the client to a common 4665, which I then granted full passage through my firewall. Now the error has changed and says "the target machine has actively refused the connection", with status code 0... ???
So that's my current situation... Please, can anyone help me? What am I doing wrong?
yo ce folks... Anyone had any trouble using a dataset for return values in a datagridview for the client app?
trying to make this work...
' Open the Connection For SQL Compact Edition
Dim cn As New SqlServerCe.SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "ffgsCRM.sdf")
Dim cmdProduct As SqlServerCe.SqlCeCommand
' create dataset with table
cn.Open()
cmdProduct = cn.CreateCommand
cmdProduct.CommandText = "SELECT ProductDesc AS Description, ProductCost AS Cost, ProductListPrice AS [List Price] FROM Product"
Dim daProduct As New SqlServerCe.SqlCeDataAdapter(cmdProduct)
Dim dtProduct As New Data.DataTable("Product")
daProduct.Fill(dtProduct)
Dim ds As New DataSet
ds.Tables.Add(dtProduct)
'' FILL DATAGRIDVIEW
Me.dbGridProducts.DataSource = ds
I have this working:
' search product description
Dim reqProductSearch As String
reqProductSearch = tstxtSearchDescription.Text
' Open the Connection For SQL Compact Edition
Dim _conn = New SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "ffgsCRM.sdf")
Dim cmd As New SqlCeCommand()
cmd.Connection = _conn
cmd.CommandText = "select ProductDesc as Description, ProductCost as Cost, ProductListPrice as [List Price] from Product where ProductDesc like '%" & reqProductSearch & "%' ORDER BY ProductDesc"
_conn.Open()
Dim resultSet As SqlCeResultSet
resultSet = cmd.ExecuteResultSet(ResultSetOptions.Scrollable Or ResultSetOptions.Updatable)
Here are the error messages: Enterprise Manager: A connection could not be established to SERVERNAME - Client unable to establish connection ConnectionOpen (CreateFile())
Query Analyzer: Unable to connect to server ServerName Server Msg 67, Level 16, State 1 [Microsoft][ODBC SQL Server Driver]Client unable to establish connection
I can't register any other new servers, even ones in my workgroup. I'm connecting using named pipes, but have also tried using TCP/IP setting it up using Client Network Utility.
When i log on to another machine using my network login - I can connect.
There have been no problems connecting in the past and I haven't changed anything on my machine - any ideas???
We have a clustered server. When i create DTS packages in the secondary server I can get all the connection. But when i create DTS package that has connection to other servers. I am getting the follwing error. So my jobs that runs the DTS packages are failing.
Error Source: Microsoft OLE DB Provider for sql server
Error Description: Client Unable to establish connection. Connectionopen(createfile())
I deleted all the entries in the Client network utility and recreated with ip addresses and TCP/IP protocol.
Added all the ip addresses to Lmhosts and host files.
I cannot connect to my SQL2005 server using the old SQL ODBC drivers, I have to use the Native client drivers. The database I am trying to connect to is a SQL 2000 db I just attached. Its owner is a SQL user login, which works fine and can connect remotely.
I have a VB 2005 synchronization application that successfully pulls (through RDA) data to a SQL 2005 Mobile DB at my place of business, but when I try it at home on my SSL VPN Client connection, I get Hresult -2147012889 ("A request to send data to the computer running IIS has failed."). Typically, a -2147012889 error is a connection issue that relates to resolving the server name.
Here's a snippet:
Dim RemoteConn As String = "Provider=sqloledb; Data Source={company server};" _
& "Initial Catalog={companyDB}; User ID={username}; password={pass}"
Dim SourceURL As String = "http://{Company server name}/MobileConnection/sqlcesa30.dll"
Dim SqlRA As New System.Data.SqlServerCe.SqlCeRemoteDataAccess
SqlRA.LocalConnectionString = strConn
SqlRA.InternetUrl = SourceURL
SqlRA.InternetLogin = ""
SqlRA.InternetPassword = ""
SqlRA.CompressionLevel = 3
Try
(Perform Pulls...etc..)
When I pull the sourceURL string and plug it into IE, it works fine. I get the "SQL Server Mobile Server Agent 3.0" message indicating that I have a solid connection over to IIS. That works fine.
But I can't figure out anything in the program. I've rotated the IP address with the name resolution and neither works for me in the program. The difference though when I use the IP address for the server is that I get a slightly different Hresult of -2147012867 (which means you can't connect to the server).
Also, I have IIS configured for anonymous access, the SQL DB I'm trying to pull from isn't restricting access, and my company doesn't have a proxy I need to go through.
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.
I used the selfssl.exe tool to generate a certificate on my db server, successfully added to Personal Certificates in MMC, added R/W permissions for the service account to the cert, selected the new certificate in the protocols for mssql and restarted the service. So far so good, however when trying to connect from SSMS with encryption check box checked I get the following error:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
The certificate chain was issued by an authority that is not trusted.
When I look in MMC, the only intended purpose for the certificate is "Server authentication" and I'm not able to add "Client authentication". Does selfssl.exe not support client authentication?
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'm experiencing an extremely slow connection from a WXPP Sp2 client to a MSSQL2000 running on a W2k server. The client is running a VB6 application that connect with Windows authentication: every form requesting data opens with a long delay at the first launch; next attempts run normally fast.
In the same LAN there are some others identical clients, all running fine.
Every other network activity from that client is ok.
The following error message was displayed in the SQL server event log when the client application attempted to connect to sql server "The Tabular Data Stream (TDS) version 0x72020002 of the client library used to open the connection is unsupported or unknown. The connection has been closed. [CLIENT: XX.XX.XX.XX]"
I can retrieve "host" name of the current connection from "sysprocesses" system table(select host from sysprocesses). But is it possible to get the IP address of the client connection instead of host?
I could not find any stored procedures or extended procedures that would let me retrieve such information.
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 sql2005 on win2k3(sbs) platform(domain concept).my client is winxp.when i am tring to connect from client pc i am getting following error message.
connection failed sql state 01000 sql server error 233 microsoft odbc sql server driver(dbnetlib) connection open (connect) connection failed sql state 08001 sql server error 17 microsoft odbc sql server driver(dbnetlib)sql server does not exist or access denied
Error: Ole db error 0x80004005 Client unable to establish connection
This happens when trying to create a maintenance plan in sql 2005 sp 1
It has now happend with 3 installs - one fresh install and two upgrades from 2000 to 2005. The startup account for sql server is a domain user account and has not been changed. This happens on both windows 2000 and windows 2003.
This however does not happen if the sql startup account is in the local admin group for the machine
I unable to setup a linked server on sql server 2012. The destination server is on sql server 7.0. I can able to setup the same linked server on sql 2005 sp4 and sql 2008 r2 but unable to setup on 2012. I am getting the below error message. OLE DB provider "SQLNCLI11" for linked server "" returned message "Client unable to establish connection due to prelogin failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
OLE DB provider "SQLNCLI11" for linked server "" returned message "Client unable to establish connection".
Msg 26, Level 16, State 1, Line 0
Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server.
