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 ?
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.
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.
I am using SSIS 2014 with the below .net framework version and installed in Windows server 2012 R2 . I have installed my client's odbc drivers (both 32 bit and 64 bit) in my production server and created ODBC system DSNs for 32 bit and 64 bit.
When i open SSIS 2014 and tried to create the odbc connection but i can able to see only the 32 bit system DSN connection ,i can't able to see my 64 bit odbc system dsn connection.
Microsoft Visual Studio 2012 Shell (Integrated) Version 11.0.50727.1 RTMREL Microsoft .NET Framework Version 4.5.51650
SQL Server Integration Services   Microsoft SQL Server Integration Services Designer Version 12.0.1524.0
And i installed my client odbc drivers(32,64 bit) and created ODBC system DSNs in my local system and when i open ssis 2014 and i can able to see both the ODBC system DSNS(32,64) connections from SSIS ODBC connection.
I am using below version of .net framework in my local system which was installed in windows 7 and i have SSIS 2012 also installed in my system and i can able to see both ODBC connections using 2012 as well in my local system.
Microsoft Visual Studio 2012 Shell (Integrated) Version 11.0.50727.1 RTMREL Microsoft .NET Framework Version 4.5.50938
SQL Server Integration Services   Microsoft SQL Server Integration Services Designer Version 12.0.1524.0
why i can not see the ODBC 64 bit system DSN connection from SSIS in my production server ?
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?
Witam!Mam problem z polaczeniem sie z baza danych po TCP/IP przez port domyslny1433, nie mozna sie telnetowac ani nic z nim zrobic, poprostu niezyje. Portjest zamkniety i nijak nie moge go zmusic do jakiejkolwiek komunikacji nawetpo localhoscie. Skaner portów wykrywa go jako zamkniety. Czy wiecie moze jakten port otworzyc i zmusic go do komunikacji z baza danych? OS win2k3,MSSQL2000 Server.PozdrawiamHello!I have a problem with a TCP/IP connection to Data Base through the 1433port. I cannot telnet on this port even on localhost. My firewalls aredisabled but port scanner see the port as closed. Protocol TCP/IP on theMSSQL Server is enabled and it's not hidden, so I don't know what I shouldto do. My configurations: Win2k3 Server, MSSQL Server 2000Thx for answers.
my application connect a sql server which was name instanced. And the sql server browser was stopped, so i need to specify the port in connection manually .
i try this:
server=xx.xx.xx.xx,1433mssqlserver2;database=master;uid=xxx;pwd=xxx; it always return a error message:
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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)
I've mapped a sqlserver machine within vs2005, but when I attempt to set the database connection, I dont see place to stick the port number (even in the advanced area)... it continues to fail when I test the connection.. I can telnet into the machine on the sql server port, so I know its open to me... Also - when I publish this to an IIS server, what is the syntax for placing the connection and port number in web.config? I've tried various settings, cant get it to work. <appSettings><add key="con" value="Server=12.123.123.123;PORT=1234;UID=*****;PWD=*****;database=mydb" /></appSettings>
In our(my company) current design we want to switch from failover clustering to Always On as high availibility solution.
I am currently testing the availiblity Group Listener function and have two questions regarding this.
First of all, is it possible to connect to a a listener by just using its "name" instead of "name,port", it is for our users very inconvenient to start using ports. If this is possible, where can I find information on how to configure this?
Second, is it possible to use the Availiblity Group Listener as loadbalancer or in combination with a loadbalancer to split the users over two or more nodes?*note we don't use azure.
connecting to a SQL Server Instance. I have a SQL server DB on a server having an Instance not running on the default port. Let's say ServerAInstanceA has the services exposed on Port 12345. When I'm trying to connect to ServerAInstanceA without specifying the port number, while I can connect from one client machine (ClientA), I am unable to connect from a different client machine (ClientB).On a side note, when I provide the port number, I can connect both from clients A and B. My question is, when I do not provide the port number, why is one client machine able to connect while the other isn't?
We have an SSIS job that runs once a day and sends emails. For security reasons, IT switched the send-mail porton the smtp server from 25 to a different number (let's say 1234).
So, I changed the SSIS SMTP Connection Manager's smtpServer string to smptserver:1234
However, this does not seem to be working. I keep getting 'Send Mail Failure' error.
Any ideas how to set the port number for sending emails using SSIS?
Has anyone had an issue with the ODBC data source that when you set it up for SQL, it does not retain the username and password you entered and keeps defaulting back to the NT windows verification instead of using the SQL verification that you choose?
I add a datasource, select validation based off of SQL profile/password assigned, enter the user and password I assigned on SQL, go through the setup and test successfully. Then I try to connect using that datasource with my VB application and it says connection failure. When I go back to the datasource, it has changed back to NT verification and removes the user/password I entered for SQL verification. Maybe there is an service pack from MS on this?
any help is appreciated. At the very least, I can just hard code into my VB app, but that is my last resort. Thanks!
I installed the MS SQL server 7.0 on a Windows NT 4.0 SP 4 server. The network runs with TCP/IP. I want to connect the SQL server by a ODBC-connection. Only a connection on the server (local) was successful.
The odbcping-utility reports following: COULD NOT CONNECT TO SQL SERVER
SQLState: 08001 Native Error: 6 Info. Message: [Microsoft][ODBC SQL Server Driver][DBNMPNTW]Selected SQL server not found.
I am currently running a application and a database server they are connected via ethernet. Only the application is connected to our network. Is there a way to connect MS Access to the database server without connecting the database server to the network? I've tried several different approaches and it still dosent work. Any help would be greatly appreciated. Dale
Would someone provide a code snip example of a T-SQL script using an ODCB connection against a non-SQL2K database. I can hit the outside database using DTS (so I know it is possible) but I'm having trouble with the parameters using a script.
Hello - I'm trying to creat an ODBC connection and the db I created is not showing up in the dropdown for 'Change the default database to:' option. I'm logged into SQL using Windows Authentication, create the db, restored it w/ a backup and then added a user w/ no problems. Any ideas?
I am trying to connect to SQL Server using a 3rd party report generating software (dbextra). Everything is located on my local box. I am trying to establish connection through ODBC. Is this installed during setup or is this a function I have to manually set up and configure?
I have front-end visual basic program that use an ODBC connection to connect with SQL server, and my questions is there any automated procedure to configure this ODBC connection instead of configure it manually specially of the user profiles was changed I have to configure it again.
We have three users that access a particular sqlserver database via microsoft access, two of the users have no problem, the third user used to be able to use the access database but is now getting a sql server error 18452 followed by an error message 'login failed for user '(null)' reason: not associated with a trusted sql server connection. When reviewing the odbc setup that the user that is having problems has, we find two sqlserver entries when it asks 'which sqlserver do you want'. How do i go about finding out where that entry comes from so i can look into removing one of them. None of the other users have two sqlserver entries. The othere users have no problem accessing this sqlserver database via ms access, I'm trying to find out why all of a sudden this one user is having problems
First of all i apologise if this is in the wrong area. My problem is as follows. I had set up a couple of aspx pages on our webserver which accessed a sql database on another server. These pages were set up using frontpage 2003 and everything worked fine. A week ago the pages stopped working giving the error "Server Error in '/' Application". As far as I know nothing has been changed on the servers. On top of this frontpage has started having connection problems. Frontpage will connect to the database but is unable to access the fields giving the following error. Server error: Unable to retrieve schema information from the record source ' NAME' in a database using the connection string: 'DRIVER={SQL Server};SERVER=servername;DATABASE=live;UID=********;PWD=********'. The following error message comes from the database driver software; it may appear in a different language depending on how the driver is configured.-------------------------------------------------------[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'NAME'. Source: Microsoft OLE DB Provider for ODBC DriversNumber: -2147467259 (0x80004005)
I have been trying for the past few days to solve this one, but am reasonable new to SQL, so this may be an easy one. Hope someone can help me
In my project, I have added a database called aspnetdb.mdf and I store all the required information here. Now I want to write a seperate Cryatl Report for my manager, that accesses this database and display required data. This report is not a part of the asp.net project. This is only for my manager. My database is not attached to any server. I just use the attachdb in the coonection string of my project to attach this database. no I want my crystal report to access this database. If I can create an ODBC connection to this database, it will solve my problem. Dows any body know how to access this database from Crystal with or without ODBC? Any help is greatly appreciated.
We have a helpdesk built with Sql7 and it has an frontend built with access. We had two machines that would connect to it. Now only one machine connects and is able to see all tables. The other machine cannot see the tables now. All permissions are the same, The other operator can log into the good one and it work and log into the bad one and it not work. All connections are the same. Any ideas on the problem(s)?
Has anyone had any problems connecting to SQL server 7.0 using ODBC connection? When I create a dsn within odbc to connect to my sql server the test connection is good. But when I go into access to link the table I get an odbc error message, reading something like, the stored procedure need to complete this task could not be found on this server.
I have a web site that provides sport news and I am using SQL Server 7.0 as my back end. The ASP page connect to SQL Server through ODBC(3.70) connection using DSN configured using TCP/IP protocol. This site has been running for 8 months with no problems.
Today, the website page was showing network errror when it was trying to get the infomation from the SQL Server. So, when tried to reconfigure the DSN using TCP/IP prtocol I got the following error.
Connection failed: SQLState: '08001' SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][DBMSSOCN] General Network error. Check your documentation. Connection failed: SQLState: '01000' SQL Server Error: 10061 [Microsoft][ODBC SQL Server Driver][DBMSSOCN]ConnectionOpen(connect()) Connection failed: SQLState: 08001 SQL Server Error: 11 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation. Connection failed: SQLState: 01000 SQL Server Error: 10061 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (connect())
Dear All, When trying to connect to the server outside the firewall through an ODBC connection string, we get the following error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database requested in login '[database name]'. Login fails.
When trying to uncover some more information pertaining to this problem, we get the associated error number, 4060. When researching this number, we see that the number has an associated error severity code of 11. Thus Microsoft is saying that it is a problem that could be corrected at the user level. Ok, I am missing something. I give. Does anyone have a new idea or an approach on which I can begin to uncover new information? We have also checked the database login and the login for the MTSServices is in fact able to access the database through an integrated login with NT Security. Also the Domain Administrator for User Rights does not have the specific NT Group enabled to log onto the computer from the network but the 'Everyone' field is still on the server. If anyone has specific questions, email me directly. Thanks for your help in advance. Daimon
We recently install SQL Server 7 and we are testing things to get it up to speed so we can use it for our clients. We are having difficulty calling the database from a ASP page. Here is the error it gives in the browser:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''.
/asptest.asp, line 11
Now here is the ASP code:
<% set conntemp=server.createobject("adodb.connection") conntemp.open "DSN=Northwind;uid=dbuser;pwd=dbuser" set rstemp=conntemp.execute("select * from customers") howmanyfields=rstemp.fields.count -1 %>
I have created a System DSN name Northwind, and a user 'dbuser' on the PDC (running IIS as well). I have gone into SQL Server and added the user dbuser and specified to authenticate it from the PDC. What am I missing? What am I doing wrong? Could someone please point it out to me.
I am using MS Access to link to an SQL table via ODBC. The DSN was setup to "use SQL authentication" with login "username", password "pwd".
After I link to the table and try opening it, I am getting an error, after which a login screen comes up with "Use Trusted Connection" checkbox turned ON. There is the user's NT username in the login textbox. I have to check "Use Trusted Connection" OFF and enter SQL login/SQL password ("user"/"pwd")before I am able to view the table contents.
It just started happening recently. Earlier, I would get a login screen with "Use Trusted connection" OFF prompting me for my SQL username/password. And no errors, of course...
What is making the system use "Trusted connection" (and, I guess, NT authentication)???
I am explicitly asking for "SQL authentication" when creating the DSN...
One of my user is having trouble connecting to the database,i have already reset his pwd bt when she is trying to connect trhough application , he keeps getting this error
"Unable to connect to database
Sytem Error codes:[microsoft][ODBC SQL Server driver] SQL Server Log in failed for user 'Username'. [microsoft]ODBC SQL Driver] Invalid connection string attribute Data provider could not be initialized. please try again or contact adminstrator!
i am sure it is not psw issue because i have reset his psw Please help me out.
Hi, I'm new to SQL Server, but regularly connect to Oracle via ODBC. I'm trying to a) connect to our SQL Server over an ISP and b) Run Enterprise Manager over the ISP. Both actions work fine over our campus network but fail across an ISP.
The first returns the message: 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
The second returns the message: Unable to connect to server [reason:[DB-Library]Unable to connect. SQL Server is unavailable or does not exist. Register anyway.
I had previously received a different error (in case 1) and, through the knowledge Base discovered I needed MDAC drivers for named pipes. I installed them but get a new error. I can find nothing in the KB or previous SWYNK messages.