April 30, 2010 at 9:22 am
I just found out that we have Express for some Sharepoint databases and we need to start taking backups. The Network Admin gave me admin rights to the server, but I can't find a way to connect to SQL Express to see anything. I see the .MDF files in this folder: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\
When I log onto the server directly, and try to connect to SQL using Windows Authentication, I get errors. I have just TCP\IP enabled. Do I need named pipes ? I'm not familiar with the limitations of Express so maybe I'm overlooking some obvious things ?
TITLE: Connect to Server
------------------------------
Cannot connect to SERVERNAME.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
April 30, 2010 at 9:31 am
Are you trying to connect with SSMS to that instance !?
Seems that your instance name is incorrect!!!
In Express Edition you should connect like this:
ServerName\InstanceName
or
YourComputerName\InstanceName
April 30, 2010 at 9:34 am
If your installation is default way & if you work in your local machine(PC) you can try also like :
.\sqlexpress OR
(local)\sqlexpress
April 30, 2010 at 9:37 am
I think you're right. Tried SERVER\INSTANCE and got a different error:
TITLE: Connect to Server
------------------------------
Cannot connect to SERVERNAME\MICROSOFT##SSEE.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
April 30, 2010 at 9:44 am
Ok! Are you trying to connect in local machine or remote machine !?
While you have same problem seems that you are trying to connect in remote machine so take a look if your SQL Browser Service is running...!?
Let me know ...
April 30, 2010 at 9:47 am
I'm remotely logged onto the server itself. There is no browser service. The only services related to SQL are:
SQL Server VSS Writer.
I don't know how this was setup .... I assume as part of the Sharepoint install a while back (?)... I was just handed it and hour ago.
April 30, 2010 at 9:52 am
homebrew01 (4/30/2010)
I'm remotely logged onto the server itself. There is no browser service. The only services related to SQL are:SQL Server VSS Writer.
I don't know how this was setup ... I was just handed it and hour ago.
Can you check to the services if you have SQL Server Browser service stop or running or if you have firewall let me know!?
April 30, 2010 at 9:55 am
SQL Server Browser service doesn't show at all. I'm not familiar with the firewall settings that may be in place .... not much help :ermm:
April 30, 2010 at 10:10 am
Ok! It is impossible if you have SQL Server Express edition and no SQL Server Browser ... !!!
Ok! In your machine where you are connected remotely try to find the SQL Server Browser service like:
Start >> All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager, you will see anywhere SQL Server Services then right-click SQL Server Browser, and then click Start if it is Stopped. Maybe it can be Disable so Enable it then Start it ...OR
Try to start it with cmd option like :
Start > Run ...type cmd then type net start sqlbrowser
For more info and other details :
http://msdn.microsoft.com/en-us/library/ms181087.aspx
http://msdn.microsoft.com/en-us/library/ms189093.aspx
Let me know what happened...!?!
April 30, 2010 at 10:24 am
"... Start >> All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager ..."
I just have "Windows Internal Database (MICROSOFT##SSEE)" No other services.
April 30, 2010 at 10:31 am
Ok did you check to the services area ...Control Panel > Administrative Tools > Services then search for the SQL Server Browser service!?
If you find there you should start it, every SQL Server that is required remote connection should have SQL Browser Service running to see it available in network!!!
April 30, 2010 at 10:33 am
I just found this, so I guess I don't have SS Express: Looks like I need to enable Named Pipes
http://www.mssqltips.com/tip.asp?tip=1577
Problem
Microsoft products such as Windows Server Update Services (WSUS) 3.0 and Windows Sharepoint Services (WSS) 3.0 ship with SQL Server 2005 Embedded Edition. Now called the Windows Internal Database, more and more system administrators charged with managing WSUS and WSS are faced with the challenge of managing these databases. Since most of these system administrators are not full-fledged DBAs, how do they manage the Windows Internal Database?
Solution
The Windows Internal Database is an embedded data service that can only be used by a handful of Windows Services. It is designed in such a way that you are not allowed to connect to and use this particular database service for non-Microsoft products. By default, installing either WSUS 3.0 or WSS 3.0 will create the databases on the C:\ partition and will cause administration issues such as insufficient disk space. It is quite confusing to manage this SQL Server instance as it does not appear as a SQL Server service nor are there management tools included with the products. The easiest way is to use SQL Server Management Studio Express. You can install a copy of SQL Server Management Studio Express on the server running your WSUS 3.0 or WSS 3.0. You then register this instance using Named Pipes as this is the only configuration for connectivity. Use this server name when you register this instance
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply