Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Can't access Microsoft #SSEE with error 26

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

Can't access Microsoft #SSEE with error 26

Postby guest » Wed May 07, 2008 4:03 pm

Q: on a one server with Windows Server 2003 Standard Edition SP2 we use WSS
3.0. For management of the Windows Internal Database I installed SQL Server
Management Studio Express, but today I have a problem with connecting to the
WSS 3.0 default instance named Microsoft #SSEE (I use Windows
Authentication). I receive following error:

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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)

I tried to instal SQL Native Client and SQLCMD utility for connecting
through the command line, but the result is the same. Problem is, that SQL
database is on the system drive and log of Sharepoint_Config database of the
WSS is too big and I have a problem with the free space. I need to shrink
transaction log file and restrict size to the appropriate value.
Could you help me solve this problem? Thank you.

A: SQL Server Embedded Edition is a special edition (Windows internal
database) and we can only connect to the instance using Named Pipes. You
can use the following connection string using SQL Server Management Studio


OR using OSQL:

osql -E -S osql -E -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Note: The default service account of SSEE is Network Service and the
BuiltIn\Administrators have permission to logon this edition by default.
When we use osql -E -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query to connect
to the SSEE, it will use the current logon Windows account for credential.
Thus, make sure the current logon Windows account is in the local
Administrators group.

Also, I attach the steps on how to change the database files location just
for your reference. Of cause, you can do the following steps in SQL Server
Management Studio Express instead of the OSQL tool.

How to change the database files location
1. Locate the database files location. By default, these files are located
in the following folder:

2. Click Start, click Run, type cmd , and then press ENTER.

3. Start the Osql.exe tool. To do this, type osql -E -S
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query at the command prompt, and then
press ENTER.

4. At the osql command prompt, back up the existing databases. To do this,
type the following at the osql command prompt:
BACKUP DATABASE <SharePoint> TO DISK = ' PathName '
where <SharePoint> is the name of the SSEE database, and where PathName is
the path and file name that you want, such as

5. Type GO , and then press ENTER.

6. Repeat steps 4 and 5 for each database.

7. Detach all the content databases. To do this, type EXEC sp_detach_db
<DatabaseName> at the command prompt, where <DatabaseName> is the name of
the SSEE database name, and then press ENTER.

Note If you receive a message that the database is in use and cannot be
detached, open the services console by entering services.msc in a Run
window, and find SQL Server 2005 Embedded Edition (MICROSOFT##SSEE), Pause
and then Start it.

8. Start another command prompt, or start Microsoft Windows Explorer, and
then copy both of the SSEE database files (including the .ldf files) that
you located in step 1 to the new folder that you want.

9. Attach all the database. To do this, type the following at the command
prompt where the Osql.exe tool is running
EXEC sp_attach_db @dbname = <DatabaseName>, @filename1 = 'd:\
new_database_location \DatabaseName.mdf', @filename2 = 'd:\
new_database_location \DatabaseName_log.ldf'
where new_database_location is the folder where you moved the database
files in step 8.

10. At the command prompt, type quit, and then press ENTER to quit the
Osql.exe tool.
Tablet and Smartphone Setup Guide

Troubleshooting Vista Wireless
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Return to Networking

Your Ad Here

Who is online

Users browsing this forum: No registered users and 3 guests