January 15, 2010 at 5:37 pm
Hello,
I have a SQL Server 2005 server that has WSS 3.0 databases. Instance where the databases are located are <server name>\MICROSOFT##SSEE.
Yesterday, everything was fine and I was able to connect to the server and see the databases in MS SQL Server Management Studio. Now, I see the following error
“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) ”
The instance does have the local and remote connections enable. MSSQLSERVER is started. Do you have other ideas what is happening?
Thanks,
Paul
January 15, 2010 at 5:52 pm
Is the Browser service running?
Can you connect to it by IpAddress/Port?
Any additional error info from the Application Event log?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 17, 2010 at 1:50 pm
Also disable local security policy on your machine.
January 17, 2010 at 7:08 pm
rspskumar-704119 (1/17/2010)
Also disable local security policy on your machine.
Typically not. But you will need to explain what you mean here. Disabling the local security policy could leave your machine in a very vulnerable state. So, unless you mean something different - I would not disable the local security policy.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 18, 2010 at 4:22 am
This sounds like a problem with AD security that changed or maybe a group (normally the local\administrators) that was removed disabled on the SQL instance or server security.
What happens is that by default local\administrators have access to the databases and alot of the time domain controllers is also local admins. This means if you where removed form some group or if the administrators group was disabled on the server it can cause authentication problems for windows loggin.
If SQL loggin check the case(upper/lower) of the username and password.
You can also check under SQL configuration manager that your TCP/IP/named pipes is enabled depending on what you use.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Do not reinvent the wheel.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
January 18, 2010 at 6:54 am
Sounds like SQL Server Browser not started, ports being blocked (1433 / 1434) or protocols disabled. Look in configuration manage under network protocols and make sure that TCPIP and Named Pipes are enabled. When connecting via management studio, click on options and change the protocol to named pipes, see if this helps.
January 18, 2010 at 11:24 am
The SQL Server Browser service is running.
I am using Windows Authenication to try to login to the SSEE instance. My account in AD says I have full Domain Admin and Administrator rights.
I know my problem seems to be more of a SharePoint related and I may not have the appropriate forum, but I last week the Search database failed, so I created a new Search database with SharePoint Central. That seem to fix other problems, but then I could not login and connect to the SSEE instance. The account I used to create the database does have Domain Admin, Domain Users, and WSS_WPG
January 18, 2010 at 11:38 am
Windows admins and domain admins don't necessarily have permission to SQL. They do by default, but that can be removed. I'd check and be sure that isn't the case. Could someone else have modified security?
January 18, 2010 at 12:25 pm
Are you able to login with an alternative account? (A SQL Login).
What about locally from the box, are you able to login with your NT account when you have remoted to the SQL Server (in case you can't RDP, can a domain/net admin login to that server and connect to that instance)?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 18, 2010 at 1:10 pm
Well, my account is a domain admin account and I have DBA rights to other databases when I login to other servers with SQL Server. I checked my AD account and I have full admin rights.
January 18, 2010 at 1:19 pm
pbyrum (1/18/2010)
Well, my account is a domain admin account and I have DBA rights to other databases when I login to other servers with SQL Server. I checked my AD account and I have full admin rights.
When you connect, are you trying to connect to the SSEE instance from SSMS running on your desktop?
Or
Are you logging into the server and using SSMS from that server to connect?
If both, are you seeing the same results?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 18, 2010 at 1:27 pm
Both, I see the same error connecting via my Desktop with SQL Server Express.
I connect to HERMES\MICROSOFT##SSEE. HERMES is the server name. MICROSOFT##SSEE is the instance
I use Remote Desktop to view the server remotely and get the same error.
January 18, 2010 at 1:35 pm
If you error out on remote desktop, it sounds like the rights are messed up in Windows.
connections to one server, or SQL Server instance, don't necessarily mean that the rights are there in the next one. Are you sure this machine didn't get dropped from the domain?
January 18, 2010 at 1:41 pm
I can use Remote Desktop to this same server and use SSMS to connect and see other instances on the SQL Server, while having full admin rights to the database. No problems with those, except this SSEE instance.
Can I run any command line commands to access the database? I don't know what commands I would use, though.
January 18, 2010 at 1:41 pm
Do you get the same / similar error when connecting via Profiler?
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply