December 13, 2007 at 6:16 pm
I can't seem to connect to the SQL Server 2005 database engine using SSMS. I'm running SSMS on the same server, I'm not even trying to connect remotely. I know the database is up and running because Sharepoint is using it. I can connect to everything else with SSMS, just not the database engine. I'm using Windows Authentication because I don't know of any other userIDs and passwords that would be associated with the database. I'm logged in with a domain administrator account.
I have also enabled remote connections using the Surface Area Configuration utility.
The error message reads:
An error has occured 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)
I have not idea what I'm doing wrong. Can anyone shed some light?
Darryl Allen
Aurora, CO
December 13, 2007 at 9:28 pm
Are you connecting with TCP/IP? It's possible that SQL was installed without TCPIP. You can check the beginning of the SQL Server error log to see which IPs it's listening on, if any. Try connecting in SSMS to the IP directly.
December 13, 2007 at 11:17 pm
Hi
since you are trying SSMS on the same server is the Sharedmemory protocol enabled.
"Keep Trying"
December 14, 2007 at 1:12 am
December 14, 2007 at 7:02 am
Go the SQL configuration manager. Confirm that SQL Server and SQL Server Browser are running. From here you can also click on the Network configuration tab and enable all the required protocols, like shared memory, tcp/ip, named pipes.
Note: you can also get the port the instance is listening on by going to the tcp/ip protocol. You can then try to login using server\instance,portnbr.
December 14, 2007 at 10:31 am
I'm not sure where to find the installation log, however all of the protocols except VIA are running and enabled.
December 14, 2007 at 11:11 am
To check the port go to SQL Configuration Manager and click on SQL 2005 network configuration.
Select the instance --> right click tcp/ip --> properties --> ipaddresses tab then scroll down to the bottom it will say port number.
try to connect to the instance witht he port, e.g. server\instance,portnumber.
Steve was saying that you could find the same information in the sql error logs (not installation logs). You can get to that in SSMS by expanding mangement then expand sql server logs and choosing current. The error logs may be able to help you better understand where the conflict may be.
December 14, 2007 at 11:21 am
I don't know if I have Error Reporting enabled, and I can't connect to it in SSMS, that's the problem.
When I look under my TCP/IP protocol settings in the Configuration Manager, I have two IP addresses and the localhost IP address. All three of the IP address are set as follows:
Active: Yes
Enabled: Yes
IP Address: ip_address
TPC Dynamic Ports: 0
TCP Port:
Notice no port is specified. I figured that meant use the default of 1433. But, just to make sure, I actually put 1433 in the port field, restarted the services, but still had the same results.
My firewall isn't running. I did notice that when I did a Netstat -an command that I don't see anything listening on port 1433 (TCP or UDP). It's almost as if there's something missing.
December 14, 2007 at 1:22 pm
Yeah the default is 1433. You did say the browser service was running, right? Is this a default instance? If yes, the instance name is MSSQLSERVER. Try getting in with serverip\instancename,1433 for a named instance or MSSQLSERVER,1433 or local for a default instance.
December 14, 2007 at 1:42 pm
Yes, the browser service is running. I'm pretty new to SQL Server, so I don't know if my terminology is correct.
When I browse for a Database Engine to open there's only one choice, so I'm assuming that's the default database. The name is servername/MICROSOFT##SSEE. That's the one that I can't open.
I'm running SharePoint on this server, but it's database doesn't show up as a database engine, it shows up as a an Analisys Service. I'm not sure what the difference is. I can connect to the Analisys Service instance name of servername/SHAREPOINT using SSMS.
I have only 4 services that are running. They are as follows:
SQL Server Integrations Services
SQL Server Analisys Services (SHAREPOINT)
SQL Server 2005 Embedded Edition (MICROSOFT##SSEE)
SQL Server Browser
Am I missing something?
I've tried to connect using ther servername/instancename,1433, and it still fails. However, the fail message is different. It reads:
An error has occured 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.) (Microsoft SQL Server, Error: 10061)
Does this help?
December 14, 2007 at 3:57 pm
You cant connect to embeded editon via SSMS. There is no other instance on the server. So you will have to install an instance of SQL server. This means you are going to have to install the full version from disk or msi package.
more info here
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=949426&SiteID=1
December 14, 2007 at 4:18 pm
I'm not sure what Embedded Edition is. Is it possible it's because I installed Sharepoint before I installed SQL Server? I did this, then realized my mistake. I then uninstalled Sharepoint, installed SQL Server 2005, then re-installed Sharepoint. Sharepoint is working, and shows as an instance.
I did install SQL Server 2005 from disk. Is there something I did wrong during the install?
December 14, 2007 at 6:55 pm
You cant connect to the embeded version in a traditional way because the way it functions. Try connecting to the instance using the named pipe, as the server name. e.g.
\\.\pipe\mssql$microsoft##ssee\sql\query
December 14, 2007 at 7:06 pm
When you look under the services in the control panel, do you have SQL services listed? Since there seems to be a SSEE instance loaded, and that it's loaded as the default instance, you might need to run the SQL 2005 install again, and create a named instance (that's under the advanced settings a few screens after having picked advanced).
There's only one default instance per machine, even if they're different versions, editions, etc... You can have lots of NAMED versions but each of the names also have to be unique.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
December 15, 2007 at 7:53 am
No, SQL Services is not listed. Only the SQL Server Embedded Services. What is the difference, and how did the Embedded version get installed? Was it because I installed Sharepoint before I installed SQL Server 2005? I can certainly try to reinstall SQL Server 2005 if that will work.
At this point I'm trying to figure out the cleanest way to get out of this mess. If I have to uninstall Sharepoint as well, I need a way to back up the database so I can restore it once Sharepoint is reinstalled.
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply