I've been running some tests with a 3rd party application during the last few days, but the ODBC doesn´t seem to be working well.
The ODBCs are configured to go through specific ports, since there's a firewall between the server (production area) and the database (which is located in the dev area). If i press the TEST CONFIGURATION button after i configured the ODBCs, the test is successful, and the log file of the firewall monitor shows that the server is connecting through the designated ports.
But when i run the 3rd party application, the queries fail, showing an error that says "The server cannot be found or you don´t have access", after this error, another one appears, saying something like "Connection().opened..." - unfortunately I don't have the actual text, I'll try to post it as soon as i get them .
Just to make sure that the 3rd party app is doing its job, dev team wrote a simple VB6 app to query the database, and it shows the same error.
Both apps are running well in the dev environment, since dev machines don't have to go through the firewall, and both apps are using the ODBC configured in the same way as the server. I could think that the problem is the firewall, but the firewall logs show that the production server is trying to use ports 1433, 1434, 445 and 139, and there isn´t a single entry showing activity for the ports specified on the ODBCs configuration.
The database server is running SQL Server 2000, the dev pcs are running Windows 2000, and the ODBC driver version is 2000.85.1117.00.
On the Production environment the server that is trying to access the database is running Windows 2003 Server Ent Ed. SP 1 , and the ODBC driver version is 2000.86.1830.00
I hope some one outthere has any ideas to solve this problem, or at least any idea of what is causing this error, because i´m running out of them.
We have ODBC connection problems with some client installation. Some of them need to have the port number given in the client connect part of the ODBC setup while other (with the same client version) can use the "dynamically determine port" option, even when the port number is not SqlServer default (1433).
Has someone an idee why this happens and what to change so every connecition can use the dynamic option ?
Where does the "Dynamically determine port" check box come from when creating a ODBC connection using TCP/IP in the client configuration? Only shows up in the control panel/adminstrative tools/Data Sources (ODBC) when it is installed. I have 3 computers here that have it (they are for development) but I am finding my users desktops do not have the box and so I am getting errors trying to connect from their desktops.
I am using Excel and Microsoft Access 2000 to connect to the server using the ODBC connection.
I need my users to connect to SQL Server 2005 so I need the "Dynamically determine port" box checked to find the port. Tried typing in the port but that isn't solving the problem or answering my question. So far I have tried MDAC and .NET 2.0 platform installs with no luck.
So, I have 2 laptops, both with standalone SQL Server 2012 Management Studio.
laptop 1 can connect to my remote server on xxx.xxx.xxx.xxx,1433 laptop 2 cannot connect through management studio - but can connect directly from the development website on this machine.
I get error 18456, cannot connect to server and login failed for 'user'
Hi all,I'm having some trouble with connecting to SQL server instance latelywithout adding a port number. I used to be able to always connect toinstance without having to input SQLSERVER,portnumber. However nowthis is not the case. I doing this through an ADO connection object,and creating the connection string. Does anyone know if there was arecent Microsoft update or patch that would've cause this to stopallowing me to connect to a SQL instance without having to put in theport information? Thanks.
I have a SQL server database that I am trying to connect to from VS2005 in the Server Explorer. I am not using the standard port for my SQL server listening port and I don't see where I can tell the Server Explorer to use a different port? Can someone point me in the right direction for connecting to my database? Thanks.
Version: SQL SERVER 2012 enterprise edition and SP2.
Due to one of the security reason, I have changed default port 1433 to another port number in configuration manger tools->protocols for MSSQLSERVER->TCP/IP --> IP ALL section mention another port number.
After restarted service, SQL SSMS able to connect server itself and new port number also LISTENING.
But SQL client SSMS not connected to one of the PC side after changing default port.
I'm trying to configure a named instances of SQL Server 2012 SP2 to have specific IP addresses and listen to that IP on port 1433. Alongside this, I have the default instance running on a different IP and listening to that on port 1433.I've managed to get them configured so that they are reachable using the IP, and looking at the log for each they are listening correctly on that IP on port 1433; in addition, the default instance connects fine using the SERVERNAME.However, when I try and connect to the named instance using the SERVERNAME/INSTANCENAME syntax, I receive the following:-
"Cannot connect to SERVERINSTANCE. Instance failure. (System.Data)"
Configuration for the TCP/IP protocol for that instance is as follows:-
Protocol Tab
Enabled= Yes Keep Alive = 30000 Listen All = No
IP addresses Tab
IP1 Active = Yes Enabled = Yes IP Address = 10.1.1.1 TCP Dynamic Ports = 0 TCP Port = 1433
[code]...
The SQL Browser service is running and prior to switching off Listen To All, I could connect to the instance remotely using the instance name.
In Management Studio i highlight my query and then click on 'Analyse query in Database Engine Advisor' but i get the following error message: "Failed to connect to an IPC Port: The system cannot find the file specified". Seems like if I reboot my computer it works one time then get the same error on the second time.I'm running developer edition with service pack 2.
I would like to INSERT an array of integer into a table in MSSQL Server, then count the number of rows in the table with c++ using ODBC. Here you find my code to do this task:
In my code, I would like to Insert the array and then count the number of rows:
SQLTCHAR Statement[] = _T("INSERT INTO information1(Wert1,Wert2) VALUES(?,?) select count(*) as a from information1 ") ;
Problem : My expectation is, that first 9 rows are inserted into table then comes 9 as result to user (if the table is empty) but this code returns me 1 if first the table is empty. If the table is not empty, it returns 1+number of  existing rows in the table. If I take a look inside the table, the 9 rows are successfully inserted in it. Only the number of rows in the table is wrong.
Hint : If I monitor the database using SQL Profiler. It looks like this:
Hi am very new with VB.net (Visual Studio 2005) and the first time try to use the sql server 2005 express. I did create a trial.mdf (local server) and complete procedure to attach the trial1.mdf in Microsoft SQL Management Studio Express.
I try to use VB to connect /open/close it with the following codes: (but failed)
-----------------------------------------------
Imports System.Data.SqlClient
Public Class Form1 'Link database Dim DB_Location = "c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataTrial1.mdf" Dim MyConnection = "Server=localhost; DataBase= " & DB_Location & "Integrated Security=SSPI" Dim sqlConnection As New SqlConnection(MyConnection)
'Use database Dim strSQL As String = "SELECT FROM Trial1 WHERE col2 = 'trial' " Dim cmd As New SqlCommand(strSQL, MyConnection)
Win 2003 Small business server with IIS being used as a web server. Our client app can log in and run queries, but our web app when trying to log in gets the message, 'SQL server does not exsist or access denied' The system DSN's are both sql drivers and the configuration is name pipes. Our recomended specs use TCP/IP, but when I try to change it, it craps out on me. He's opened up his firewall completely to this new box and his old box, a Win2k machine can connect using TCP/IP. This machine is in a work group. Any suggestions on what it might be??? :confused:
i have an sql express db on my webserver. now from another computer I am trying to creat an odbc connection to the sql server but when I enter in just the ip and the login and password it fails. Please advise me what I can do?
what i really am trying to do is set up an access db on my home computer to be linked to an sql server express backend. I thought to do this with odbc - is this the correct way?
I'm a new comer to this APS language and hope sombody out there can help me with this I'm trying to find codes for me to connect from ASP to Sql Server using ODBC. Can anyone help me Thanx
Could someone tell me how to use a query with a "connection string" to connect to an ODBC driver and retrieve data from its tables. I am new at this and have been having a lot of trouble connecting from the SSIS manager. If someone has a tutorial on how to do this. I would really appreciate it.
Hi all I have problem with making Connection between two computer through SQLServer and ODBC.
I have two computers which are members of a WorkGroup network with WindowsXP(sp2) installed. on one computer i have installed SQL Server 2000 Enterprise edition with MIX Authentication mode enabled. Also i have created a LOGIN (Sql Server Authentication) with System Administrator ROLE (SYSADMIN).in that sql server environment .
But in another computer when i want to create an ODBC connection (ControlPanelAdministrative ToolsData Sources (ODBC)) to connect to mentioned Computer with Sql server,I receive the following Error: Access Denied...Sql Server doesn't exist.
I have disabled Windows-XP firewall on both computers but still problem persists. By the way these two computer have one Administrator Account with DEFFERENT Passwords.
Could anyone help me.? Any help greately would be appreciated.
Installed SQL2005, connect via (the new) SQL Nativ Client ODBC Vers. 2005.90.1399.00 works, just as (the old) SQL Server ODBC-Driver 2000.85.1117.00. Works fine.
I am running SQL Server 2000 sp4 in Win Server 2003. I have a DTS packages which connects to FileMaker 6 files via the ODBC driver installed with FielMaker.
The DTS packages work correctly when executed directly. However, when executed from a SQL Server Agent job, the same DTS packages fail. Always with the same message:
Error: -2147467259 (80004005); Provider Error: 16394 (400A) Error string: [FileMaker][ODBC FileMaker Pro driver][FileMaker Pro]Connect failed Error source: Microsoft OLE DB Provider for ODBC Drivers
Searching for info on the above message seems to indicate a permissions problem. However, I am running the jobs with an full administrator account. All connections and the FielMaker files reside on the one server.
I am trying out a simple ASP.NET application which includes access to an SQL Server Database. It works fine on my local machine when I connect to the SQL Server and use SQL commands (via C#) to access it. But my web hosting provider uses ODBC drivers for database access (they support the SQL database type). I would like to find out how I should connect to my SQL Server database and program the access in order for it to be ODBC compatible, so that I can deploy it to my web hosting server. I should also mention that I am using Visual Web Developer 2005 Express Edition. Thanks for any help or pointers. Kumar
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.
I wanted to know if there is a way to connect to my MSSQL without having to setup a datasource in the control panel.
Perferably I want to locate the database within my perl code instead. I don't want to have to setup a datasource each time I need a different database. Perhaps there is a way to pass the name of the database along with the username and password through the command line.
I am trying to connect to a database and run a query using vbscript. The problem I have run into currently is that I can not get the connection to open even though I know the DSN name it still says it can not find it. I am fairly new to vbscript so I am not sure exactly what it is looking for in the connection string so that it will find the database. Any ideas?
When I begin Enterprise Manager and open a connection to a Server, it fails with a timeout error. But if I do a refresh and then connect again, it immediately works. I have had similar symptoms setting up a data source for ODBC. When you initially logon to SQL Server to define the connection it times out. But then if you immediately try again it succeeds. Furthermore one of my application programs fails to work (due to the timeout) on systems that have this behavior. I have had these symptoms occur on 2 diferent workstations, but other workstations access the SQL Server with no problem. All systems are WinNT 4.0; the engine is SQL Server 7 with SP2. The timeout is defined as 15 seconds so should be long enough.
Does anyone know what is going on, or how to fix it?
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.
Using the above connection strings in SSIS design mode, the datasource test succeeds, and an sql select statement in a datasource reader returns the table structure with no error.
However, when I try to run the package, I receive the following error.
SSIS package "Sales Data Load.dtsx" starting. Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning. Error: 0xC0047062 at Data Flow Task, DataReader Source 2 [408]: System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "DataReader Source 2" (408) failed validation and returned error code 0x80131937. Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task: There were errors during task validation. SSIS package "Sales Data Load.dtsx" finished: Failure.
Furthermore, I have packages configured in SQL 2000 DTS to use the same system dsn without any errors.
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.
Using the above connection strings in SSIS design mode, the datasource test succeeds, and an sql select statement in a datasource reader returns the table structure with no error.
However, when I try to run the package, I receive the following error.
SSIS package "Sales Data Load.dtsx" starting. Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning. Error: 0xC0047062 at Data Flow Task, DataReader Source 2 [408]: System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "DataReader Source 2" (408) failed validation and returned error code 0x80131937. Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation. Error: 0xC0024107 at Data Flow Task: There were errors during task validation. SSIS package "Sales Data Load.dtsx" finished: Failure.
Furthermore, I have packages configured in SQL 2000 DTS to use the same system dsn without any errors.
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 ?
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.
How viable is it to use MS Access as a front end (via ODBC) to a SQL Server2000 database?The users would access via the internet using a netgear vpn setup.Thanks,Paul S
