I am responsible for an application that uses the Borland Database Engine to connect clients to the database server - it's called SalesLogix. I am in the process of upgrading the databases in the working environment to SQL 7 from SQL 6.5 and on the whole it has been (relatively) successful, however I have a majorly inconvenient issue with a few client machines. Occasionally, after upgrading the SQL client and having upgraded the database server I cannot make a connection any longer and instead when I try through the BDE I am presented with the message 'General SQL Error' and the BDE error code for a general SQL error, and nothing more. It has only happened on a couple of machines, but with no apparent pattern. The clients can still connect to SQL 6.5 databases as long as the SQL 6.5 client utilities are still installed so I don't know what to think. Any ideas?
We are trying to setup a role based security access within our client software so that users have read only access to the database. Right now we are not able to connect to the database. This is a blocking issue for us on the project right now
Is it possible to approach a MS SQL Server using TCP/IP? I have lookedeverywhere but have not found any documentation about the protocol toconnect to MS SQL Server.I wish to connect to MS SQL Server directly through TCP/IP, without using MSlibraries (since i am not doing this on a windows system).Thanks in advance,Eddie Gieze
I am building a C# Windows app. I have a form and have also create a db. I tested the db connectivity in Server Explorer and the test came back successfully. According to my manual, I just need to drag the db item from the server explorer to my form designer to creation the connection. When I do this nothing happens... what am I doing wrong?
If I do the same thing in VS2003 the sqlConnection1 shows up, how do I accomplish the same thing with 2005?
hi, how to connect the database for first time iam working for a website in that i have a form. how to connect the form to the database. throw enterprice managment thanks
Hi: I m in new in ASP.net and can't connect sql server db with ASP.net.I write exact code.but it give error in connection string and server error some time.I found that error is in web.config file.can any one have running project of asp.net with sqlserver db.. if any one have then mail the project at this mail address.. ray_boby@hotmail.com
Hi im new to ASP.NET.. can anyopne pelase tell me how to make database connectivity with sql server 2000.i need to insert data into sqlserver2000 database from an ASP.NET Web form. please provide me with a asample code.thank you
I am using webforms for ASP .NET which has code in C#. My database is running on SQL Server 7. Whats the best way to connect to database. I have tried ODBC connection through myConnection=new SqlConnection(ConfigurationSettings.AppSettings["dsn"]);but it gives me an error that can not connect to the SQL Server 2005 or it does not allow remote connections though it is running SQL Server 7 and not SQL Server 2005. Thanks in advance.
I am using SQL SERVER 2000 and asp.net How shoul i connect using OLEDB provider?. In connection string, i am giving Provider=SQLOLEDB.1,datasource . It's giving error in conn.open() that login failed for database. i am also poroving username and password in connection string, so i want code for the same. awaiting for reply...
Hi, I have a sql server that I cannot connect to in Enterprise Manager. I can connect no problem with Query Analyzer, but EM always gives me a "timeout expired" error. I am using tcp/ip, and my network card is configured exactly the same as another server that i can connect to fine. Any ideas? I really need to figure this out. this has nothing to do with timeout intervals, or anything like that, as it's all default settings, same as the other database...thanks.
Here's my post from a few minutes ago, thanks for the answer but that's not a fix, and trying to reconnect doesn't help. it never connects. I'm posting again, as otherwise people wouldn't read the older thread once it's replied too
I have a sql server that I cannot connect to in Enterprise Manager. I can connect no problem with Query Analyzer, but EM always gives me a "timeout expired" error. I am using tcp/ip, and my network card is configured exactly the same as another server that i can connect to fine. Any ideas? I really need to figure this out. this has nothing to do with timeout intervals, or anything like that, as it's all default settings, same as the other database...thanks.
I have a few ASPs that were written to pull from an Access 97 database. Now that we have converted the data over to a SQL database, the ASPs have been changed accordingly. My problem is that I have two ASPs which use an Inner Join between three tables where the main field (in this case it is called "INDEX") is what the pull is based on. When I try to run the ASPs I recieve this error .
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'INDEX'.
The line that it identifies is where the connection is actually opened. This is only occuring on the ASPs that use the column INDEX and an inner join. The straight style number pulls (which have the same connection string) are working fine. Any ideas?
I'm currently trying to connect my ASP page with an SQL server 2000 DB. I already know, how to connect with Access, through the the cobnnection object...
I cannot (most of the time!!) get ODBC to make a connection to SQL Server 6.5 over the network. I get the following error:
Connection failed:SQLState: '01000' SQL server Error: 1326 [Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen[CreateFile()]. Connection failed:SQLState:'08001' SQLServer Error 1326 [Microsoft][ODBC SQL Server Driver][Client unable to establish connection.
I've looked in the SQL Server log and I've found:
"Error 17826, Severity:18, State:0 Unable to set up ListenOn Connection 'My Server Name'; OS Error: 10047"
I can get ODBC to connect from the same machine as SQL Server so it seems to be a network problem. I've tried using TCP/IP, Named Pipes, Multiprotocol, no joy. The network is ok i.e. I can ping and can otherwise find the server on the network. What's wierd is that on occassion I can get ODBC to connect!
I'm having a problem with a VB6 program I'm writing that posts data to a SQL server. The problem occurs when the SQL server is unavailable. When this happens it causes the program to hang for at least 30 seconds before releasing. The hang happens at the code that connects to the SQL server, because the server isn't there. I've added code found on this site to test the connectivity prior to making my actual data connection, but this causes the same hang. Is there any way to verify connectivity to an SQL server without actually trying to make the connection? I'm really trying to eliminate the hang that occurs when the server is unavailable.
This problem occurs in a Visual Basic 5 application which accesses the SQL Server 6.5 database through Jet Engine(DAO).
If a user starts a transaction and then his application terminates abnormally (before rolling back or committing), say due to power failure or if the user kills the application with Ctrl+Alt+Delete, then the transaction started by him is not terminated (rolled back) by SQL Server. Even the process cannot be killed using the "Kill" command and the user keeps holding all the locks that he has already acquired. Also nobody can use Enterprise Manager. This happens when you have lock on more than 8 tables including tables in tempdb. The only way to solve this problem is to restart the server which is never expected in a multiuser system.
One can know the threadID of the process that needs to be killed using "Sysprocesses" system table. Is it possible to kill the thread in Windows NT?
Is there any setting due to which SQL SERVER will automatically kill a process or rollback a transaction started by a disconnected client ?
Is it possible that a process or transaction will have to release lock after the specified time ?
I am trying to connect to my dev Sql server instance remotely from my developer edition and I get the following error
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
i Made sure that the following are complete
# [Link] Enable the TCP/IP protocol using the Surface Area Configuration Utility # [Link] Make sure the TCP/IP protocol is enabled in the SQL Server Configuration Utility # [Link] Make sure the SQL Server browser is started
We have a DB2 server which is linked to our SQL Server 2005 database. The link is through ODBC connection. Now, we are able to access some of the tables without any problems. But couple of tables are not accessible and we get following error::"
"com.ibm.db.DataException: A database manager error occurred. : [IBM][CLI Driver][DB2/NT] SQL1822N Unexpected error code "08S01" received from data source "TESTPROD". Associated text and tokens are "Communication link failure". SQLSTATE=560BD "
Any ideas on why this is happening and how to resolve this?
i am trying to connect to sql server remotely with native client. tcp/ip and named pipes are enabled on both sides. there is no firewall between client and server. surface config on server allows remote connections. i have been working on this for a week. i am new to sql server 2005 dont know where to go from here. thanks in advance
Im trying to access a sql200 database from a sql7 hosted storedprocedure and this is not working. I know that SQL7 is not compatiblewith the MDAC for SQL 2000. Does anyone know if this is what iscausing me my problems and if so is it possible to upgrade the SQL7MDAC without breaking it?Thanks