My website host, NetworkSolutions, just upgraded to MS SQL2005 from SQL2000 over the weekend.
Wonderful of course, but now my ODBC connection doesn't work anymore and I've used it for over a year !
I can make a connection with SQL Server Management Studio Express without a problem.
But connecting with ODBC the error message I get is:
SQLState: '08001'
SQL Server Error: 10061
[Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
and then a "Login timeout expired".
I called NetworkSolutions about this and they said I had to change strings that were no longer supported. I had the idea that they didn't know what an ODBC connection is.
"...because the target machine actively refused it" , could that mean that they have to do something on their end to make a connection thru ODBC possible ?
I'm having trouble with odbc_fetch_array from my SQL Server 2005 db. I read about someone else having a similar problem and he followed up saying he downloaded new ODBC drivers. Well, I'm clueless where I can get these from (I did write him as well). Can anyone point me in the right direction?
First off, Devshed is a great place to find information for development. I'm on here daily looking through threads, finding answeres
I'm building a backend for a program that uses msSql 2005 and ODBC . I'm trying to insert into a table, and it is working, but i would like to find a solution to this error i get from the odbc trace:
Calc f54-5c4ENTER SQLExecute HSTMT 00924A18
Calc f54-5c4EXIT SQLExecute with return code -1 (SQL_ERROR) HSTMT 00924A18
DIAG [22018] [Microsoft][SQL Native Client]Invalid character value for cast specification (0)
when i try to insert a value of 0 (zero) into a column that is bound as a double it gives this error.
And one more thing: if(retcode != SQL_SUCCESS | SQL_SUCESS_WITH_INFO)
shouldnt that work? (if Retcode isnot success OR success_with_info)
Posted this at the tail end of another thread but that one appears to have died. Thought I'd try again since my question was a little distinct from that one anyway, but apologies if I've committed forum sacrilege.
I am having a heck of a time trying to migrate a fairly simple MySQL DB to SQL Server I am using SQL Server 2005 Standard Edition SP1.
I tried following MS' instructions in this article:
hoping that what worked for 2000 would work for 2005, since the principles seem sound. No luck. I can create the ODBC link, but SQL Management Studio, the '.NET provider for ODBC' option doesn't give me the choice to copy tables - only to write a query.
I tried making sense of the on-line help and was able to create the ODBC connection in the 'Business Intelligence Development Studio' but I have no idea what I am looking at with respect to creating control & data flow in an SSIS package. All I know is that I could do what I am trying to do in SQL Server 2000 quite easily - the MySQL database in question is quite simple (but not small). I am pretty amateurish when it comes to SQL administration, but this seems to me unnecessarily difficult.
I tried the MySQL OLE connector from sourceforge and was able to properly set up a test connection and get the 'copy tables' option, but then when I hit 'next' I get:
MYSqlProv 3.9 failed with no error message available, result code E_ABORT(0x80004004) (System.Data)
Am I missing some stupendously easy way around this, or did I torpedo this client when I promoted moving them from MySQL to MS SQL Server on account of my not being a full-time SQL Server DBA who knows how to use the Business Intelligence Development Studio?
I have a Login that I setup in SQL Server 2005. The only database roles given to the login are db_datareader and public. On SQL 2000 these permissions are sufficient to allow me to setup a read only ODBC connection using this login and creating an import table in Access. When using the login in SQL 2005 and creating an import table, I am able to edit the underlying data, something I am not able to do with a SQL 2000 ODBC connection. Is there something in SQL 2005 that I am unaware of that would allow this login to modify (update) the table?
Hi all, I'm not a db guru and probably this is a very simple question for you, but I was wondering if it was possible to connect to a SqlServer using odbc without DSN. I mean, I'm trying to connect to the db server from a linux (Fedora Core 8) workstation, using odbc drivers, but it looks like I can do that only using a DSN connection and setting properly the odbc.ini file. It doesn't work, if I use a connection like this from a PHP script: $cn = odbc_connect("Driver={SQL Server};Server=MyServer;Database=MyDatabase", "MyUser","MyPassword") Does anyone know how to connect to SqlServer with a DSN-less connection? Could you explain me where is the error?
I'm using SQLServer2005, Fedora Core 8 with the last FreeTDS installed.
Hi guys, Please can anyone show me how to connect SQL Server 2005 to ODBC Driver(Novell). The import/export wizard data source has no ODBC option.
My final goal is to extract data from an eDirectory into SQL table. I used Novell Client to create a link to eDirectory; with the ODBC driver as the data Source for the SQL Server to extract data from. Every help will be rewarded with appreciation. Thanks
Hi,I'm trying to find out if we can use bulkcopy via odbc in sql server 2005.With sql server 200 we could use the odbcbcp.dll.I can not find any info regarding this for ms sql server 2005.Thanks,Jos van der Velden
I have just installed SQL Server 2005, default settings. I have attempted to add a new ODBC driver using Control Panel - Administrative Tools - Data Sources (ODBC) - System DSN tab - Add - SQL Server - default settings, but it fails.
I did all this for MySQL some months ago, but I must have forgotten something.
Good afternoon everyone I am trying to import data from mas90ODBC DSN into my SQL2005 DB. IN 2000 I was able to connect to an ODBC DSN but it seems that this option has been deprecated in 2005. Can someone please provide me with the best step by step instructions on how to go about importing my data.
I am attempting to setup a SQL Server 2005 Express database as a backend to an Access MDB, and need to establish an ODBC data source for the backend database. On two different systems (Windows XP Pro and Windows 2003 SBS), I get an error that says I cannot connect to the SQL Server. I get a message that says:
Connection failed: SQL State 08001 SQL Server Error: 2 [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server
That is followed by a Login timeout expired and a suggestion that under the default settings SQL Server does not allow remote connections.
I have shared memory, named pipes and TCP/IP protocols enabled, and the firewall set to allow connections on port 1433. And the Express manager seems to work OK.
I see several posts about issues with ODBC, but none of the suggestions seem to help in this situation. Can anyone suggest something to try? Thanks in advance.
How do you import using integration services or what ever to import from a Citadel database? I have created an ODBC Data Source using National Instruments ODBC driver for Citadel? I have tried using Microsoft Access, but the field names are longer than 62 characters and Access won't "link" to the ODBC Data Source.
The SQL Server Management StudioTasksImport Wizard doesn't appear to have a way to specify an ODBC Data Source.
We are upgrading our server to 64 bit Server 2003 and SQL 2005 and have a problem with getting odbc connectivity for one application. We are working with a program called DataExtend for replication between sites. It is provided a part of the package from our software vendor. At present DataExtend does not have a 64 ODBC driver. Their 32 bit driver did install when the software was installed but did not setup correctly. We looked at a current 32 bit system and copied the ODBCINST.INI registry key to the new server making sure the paths were correct. When I go to create an odbc connection I receive "Setup Routines for DataXtend SQL Server ODBC Driver could not be loaded due to System Error Code 193". Does anyone know how to get these drivers to work with our 64 bit environment.
I have a server with SQL 2005 and I have second server with spesial database program on it from IBM and I have installed a spesial ODBC DRIVER from IBM so I can make a connection in system dns.
On my server 1 where I have the sql 2005 I have made a connection in system dns.
HOW CAN I TELL SQL 2005 TO CONNECT TO MY CONNECTION AND GET DATA FROM DER??????
HiI've got an Ingres database of some 200 tables which I need to importevery night into SQL Server 2005 for use by Reporting Services. Mostof the tables will come across unchanged (a few need massaging tohandle time intervals correctly), but the Import Wizard only seems towant to import one table (or more accurately query) at a time. I seemto remember the old 2000 Import Wizard handled multiple tables - isthere any way of processing multiple tables in 2005, or must I resignmyself to writing 200 import packages in SSIS.Chloe CrowderThe British Library
Hi, Am new to SQL Server 2005...actually this is my first day with it
am trrying to connect to SQL Server which resides on a 64-bit machine from a 32-bit machine using ODBC with a DSN aliasing thing it gives me error msg "login failed for user XXX" with error state indicating that password missmatch or sometimes invalid user!! i dont use the password i keep it blank and checked everything i could possibly think of...
I am trying to use SQL 2005 express as a datasource for a mailmerge with Word 2000.
I have created a ODBC link successfully. I have enabled all the protocols. When I open the ODBC link, all I see is a ODBC drop down. I cant see or select any database tables?
When I open the dsn I get a dialog caled Header Record Delimiters. I accept the defaults and then I get another Dialog called Mail Merge Recipients with a whole lot of connection info, but no sign of any database tables.
Hope one of you can help me. I've got SQL Server 2005 Express installed on a laptop. I'm trying to create an ODBC connection to it so that I can access the database from a program locally that will be writing to it. I can connect to the SQL instance by listing the server name as DSR-XXXXXXX(ComputerName)SQLEXPRESS
However... when I access that ODBC connection, it doesn't see the database DBProScout (which was created inside SQL Express on this laptop locally), and I cannot access the tables within it. The only tables that I can access are system tables associated with SQL Server Express.
I am running SQL 2005 SP1 on Win 2003 Std x64 SP2. I get an error trying to connect using an ODBC System DSN connection. The ODBC connection gets the following error:
Connection failed: SQLState:'28000' SQL Server Error: 18456 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'
The SQL Server logs the following error:
18456, Severity: 14, State: 8.
I have tried this with several SQL accounts. I am able to login to the SQL Manager with the accounts without issue. It is only when trying to connect via ODBC that I get the error. I am currently downloading SQL 2005 SP2 to see if this will help with the issue. Any other ideas would be greatly appreciated.
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
Database server: - Remote machine running SQL 2005 Standard as a named instance - Named pipes and TCP are enabled for remote connections - SQLBrowser service is running - Listening on default named pipe (\servernamepipeMSSQL$instancenamesqlquery)
Client: - Vista Business machine - Not in same domain as server, but on the same network (via Cisco VPN) - SQL 2005 Express is installed (for use with local databases) - Windows Firewall enabled - Running Symantec Antivirus, Corporate Edition
Connectivity: - I CAN connect to SQL 2005 databases on the remote server using "nperverinstancename" - I CAN connect to SQL 2005 databases on the remote server using Excel 2007
The problem is that I cannot successfully create an ODBC datasource using the "ODBC Data Source Administrator" application. I'm using the "SQL Server" driver and trying to create a System DSN. I'm also running the tool with elevated permissions.
- When I try to use "servernameinstancename" as the server and TCP as the connection type, I get this error:
Connection failed: SQL Server Error: 18452; "[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user ''. The user is not associated with a trusted SQL Server connection.
- When I try to use "npervernameinstancename" as the server and Named Pipes, I get this error:
Connection failed: SQLState: '01000'; SQL Server Error: 1326; [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()). Connection failed: SQLState: '08000'; SQL Server Error: 17; [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Help! I've really been beating my head against the wall on this one. It all works just fine with a Windows XP client machine.
I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:
[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]
Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.
any ideas ?
Regards, Waff
I found this out:
The server collation is defined to: Latin1_General_CI_AS
If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.
How do you use a id in lowercase and connecto via ODBC ?
Hi everybody I have installed SqlServer 2005 on my server but my Windows application on the client computers should connect to server via ODBC connection so what should i install on the client computers (that don't have any sql server installed) to enable them to connect? When i want to create ODBC connection on client computers through (Control panelAdministrative ToolsData Sources) i don't see SQL-Server 2005 ODBC driver in the list ....could anyone help me? Kind Regards.
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.
Does the x64 version of SQL Server 2005 June CTP contain 64-bit versions of the SQL Server ODBC Driver and the OLE DB Provider? I am not interested in the .NET Managed Provider here, just the legacy ODBC and OLE DB drivers, and only 64-bit versions of those.
Hi! I am trying to establish connection from different domain using ODBC driver with no luck! I am able to do it within my domain from any place, but it fails from outside. I have two-ways trust established between domains. Users are able to see and use resources both ways. When I create ODBC it doesn't matter if I use SQL or Windows NT authenctication, I am getting error:
Connection Failed: SQLState: '01000' SQLServer Error: 11004 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open (getbyhostname()() ) Connectio Failed: SQLState: '08001' SQL Server Error: 11
I tried to set it with TCP Static Port or Dynamic. No difference. What should I look into?
Hi, on a web application that I develop, I just upgraded to a new database server running SQL Server 2005 and Windows Server 2003 Enterprise Edition. The previous database server ran SQL Server 2000 and Windows Server 2003 Standard Edition. Since this upgrade, the application has been causing "timeout" errors all over the application. I've been stumped. Here's the error mssage:
Microsoft OLE DB Provider for ODBC Drivers error '80040e31' [Microsoft][ODBC SQL Server Driver]Timeout expired
I'm hoping there is some sort of a setting that can be modified to increase the maximum number of connections between the web server and database server. This is a fresh version of Windows Server 2003 and SQL Server 2005. Any support that can be provided will be greatly appreciated.
We have a legacy C++ application which uses ODBC to connect to SQL server. The application is a server process that opens a connection and caches it. Unfortunately on a connection drop, it does not refresh the connection. The standard installation is a 3 machine web/app/sql setup.
It has been working fine since last 4-5 years unless the SQL Server goes down. In that case, I keep seeing "Function sequence error" and "Communication link failure" errors. On one particular client installation on application server, I started getting this exception while SQL Server was up and running (on a different machine). I would see the connections randomly dropping in the activity monitor after 3-4 hrs of inactivity.
I wrote a .NET test app which uses ODBC drivers for SQL Server and makes a connection and then just waits. Out of 5 connections established by this application I saw one connection being dropped as well. Another test app used ADO.NET and it did not drop any connections. I asked the IT to check the network and they say its fine.
The servers are W2k3 SP2 and database is SQL Server 2005. IsAutoClose on all the databases is false. Nothing goes in the logs even after turning on traces using DBCC.
Since the connection drop was very random, I turned off connection pooling on "ODBC driver for SQL Server" on the application server and now it is working fine.
Can someone explain me what could be the reason? Also, is there a way to upgrade or downgrade ODBC drivers on W2K3 machines?
God morning! I 've just installed SQL Server 2005 on Windows 2003 Server 64 bit. One of my databases need to connect to seveal Oracle databases. - I tried installing 64 bit Orcale 9 on this server. Got a strange message that the application (Oracle 64 bit) could not be installed on a 32 bit server! Strange! - I installed Oracle 9 32 bit on the server, but I could not find ODBC driver in the Data sources! Neither the oledb under providers in MSS Manager Studio! - Same result efter several desintall and installation. A college copied the .dll files och run a script to register the dll files. We could then se the Oracle driver in the Database sources, but we could not create any connection. - We have even tried an 10G version of Oracle with the same result.
Is there anyone who succeeded installing Oracle on 64 bit Windows and could create odbc connection/linked server?
Hi I'm a newbie at SQL 2005 and I'm trying to create linked tables to our ERP system through ODBC. I can do this in MS Access or vb.net by using the ERP system's ODBC driver, but I am lost when it comes to SQL Server 2005. Thanks for any help
If I define a table-valued function in a SQL Server 2005 database, can I link to it from Access 2003 using ODBC?
I've defined the function successfully, and I can link from Access to tables in the database (so my ODBC link is basically functioning), but I can't see the table-valued function in the Linked Table Manager in Access.
I can define a pass-through query to grab the table, but with a pass-through query I have to provide the ODBC password every time.
I have application create by MsAccess and connect with Sql Server 2000 in x86
and now we transfer system to HP rx3600 Intel Itanium - Install Windows 2003 Server Enterprise (for Itanium) - Install Sql Server 2005 Standard Edition (IA64)
and now we try to create ODBC connection from client for testing.
But we can't not done it.
Anybody can tell us how to create connection to sqlserver 2005 (ia64)
