I am using 2 machines.
Windows server 2003 with SQL Server 2005 (default instance) MySrvName" and with SQL Server 2000 (named instance) MySrvName\SQL2000
Windows 7 with VS 2010
LAN (works fine)
When I connect to SQL Server 2005 it works fine from win7 and win 2003 but when I try to connect to SQL Server 2000 via win7 it says
The server was not found or was not accessible
This instance (SQL2000) is working fine from Windows server machine. I have tried disabling all firewalls (default of windows).
In 2002-3 I used to have same issue which I used to resolve by installing MSDE/connectivity tools. Is there a way to resolve without installing anything? Or any single file to install these connectivity tools from?
Related
I've installed SQL Server 2008 R2 in my system but i'm not able to connect to the same from my colleague's machine which is on the same network.
Firewall is off on both systems.
Edited:
I've installed SQL Server 2008 R2 in my system the same installation is present in my colleague's system. While trying to connect to my machine from his machine using SQL Server Management studio it was showing an error as follows..
(I've used the server name for SQL management studio of my system for login)
The server was not found or was not accessible
I found a solution to this problem after posting the question but not sure if this is the correct way.
The SQL Server Browser service was stopped when i tried to connect initially. Now when i start this service from Sql server configuration Manager i'm able to connect to my machine from his machine.
1-Install SQL Server (Management Studio) on both machines
2-On your machine, run SQL Server
3-Make sure the server name is your colleague's machine IP address
4-enjoy!
Currently I am developing the Node.js web app on my local Mint linux machine, and connect to a local SQL Server 2008 (express) via SQL Server Authentication by using this node module mssql. Everything is fine now.
But now I need to deploy the app to a Red Hat 6.4 (64bit) machine and SQL Server 2008 R2. I was given a Windows Authentication way to access the SQL Server. I can use the Windows Authentication via the Microsoft SQL Server Management Studio to see the database and create tables. But how I can connect the app on Red Hat to the SQL server via Node.js?
I have installed this MS ODBC Driver 11 for SQL Server on the Red Hat server. What should the next move be? or best practise.
I just successfully connected to the SQL Server from Ubuntu 14.04.
I use FreeTDS as the driver, and unxiODBC as the driver manager, node odbc as the Node.js module to connect.
More information can see this link.
But I need to do more research, wondering if I can use the node module mssql to connect. mssql uses tds or tedious as drivers.
I am trying to set up an ODBC connection to our SQL 2008 server.
So far i have set up 4 windows XP machines and 3 windows 7 machines.
However, the last XP machine isnt playing ball. I use all the same settings as i did on the other computers but i keep getting "SQL Server does not exist or access is denied".
Also, i cannot telnet to the SQL server on 1433. The windows firewall on the computer is OFF and there are no other security products.
Any ideas?
I have a VB6.0 application running at a client's site on Vista SP2. When attempting to connect to a SQL 2005 Express database on a named instance ([edit]running in Mixed Mode - not Windows Authentication Only), on a SBS2008 server, from THREE OF THE FOUR Vista workstations in the office I receive the following errors:
"SQL Server does not exist or access denied"
(Using either the sqloledb provider or SQL-DMO)
Of course, the fourth Vista Workstation connects without a problem.
I've tried;
1) Creating a UDL (data link) file in order to "triple" check my connect strings and even when attempting to connect here (selecting the Microsoft OLE DB Provider) I receive the same error when it attempt to refresh the list of available databases
2) I have checked firewall exceptions on the server and even tried the tests, with the firewall turned off.
3) I have added outbound exceptions for my application to the firewall on the Vista machines.
4) I have installed the SQL2005 Backwards compatibility objects.
5) I have installed SQL Server Management Studio on one of the offending Vista machines and this errors in the same way.
6) I have also simulated the test environment in our offices on virtual machines and of course, no problems...
I guess my question is, how to I find out what is different about the one Vista PC that does connect, as opposed to the three that do not?
(Update) Also:
A Virtual Server has been added to the SBS 2008 Server, running SBS 2003 and all those offending Vista Workstations connect without a hitch??
Can you telnet from the offending workstations to the TCP port that the SQL Server is listening on? (Check the ERRORLOG file to get the dynamic port number.)
Is the SQL Browser service on the server running (required that it is).
I maintain a couple of older sites running SQL Server 2000 and 2005. On my old XP box I was using SQL Server Enterprise Manager to access them.
I'm now on a Windows 7 box. Is that product still available for download/install and will it run on Windows 7? I can't seem to find a download for that specific component.
Or is there an alternative for Windows 7? I tried install SQL Server 2008 Manager Express, but the fails halfway through on Windows 7. I do have XP running in Virtual Box so could get by with Enterprise Manager if I could figure out where to install it from.
Enterprise Manager only supports up to sql server 2000. You can't use it to access sql server 2005. Instead, you need Sql Server Management Studio. You can download the express edition here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796
I'm running both management studio and windows 7 just fine.
As for enterprise manager, it was never available for download. You had to install it from the media that came with sql server. Similarly, if you want a non-express edition of management studio you need to install it when running setup for sql server.