SQL Server 2005 - The Local Security Authority cannot be contacted - sql

I'm suddenly having a problem connecting to my local instance of SQL Server 2005 Database engine. I had no problem connecting to this instance a few days ago. I can however connect to Integration Services and Analysis Services. Only the Database engine is giving me this error:
A connection was successfully established with the server,
but then an error occurred during the pre-login handshake.
(provider: SSL Provider, error: 0 -
The Local Security Authority cannot be contacted) (Microsoft SQL Server)
Only thing I did was I installed Visual Studio 2017.

This is a generic error that has many reasons. Usually is things like expired password. To troubleshoot, you should enable Netlogon service logging, follow Enabling debug logging for the Netlogon service:
c:\>Nltest /DBFlag:2080FFFF
Then reproduce your problem then look into the logging file, which is going to be located at %windir%\debug\netlogon.log. Read the file, try to understand what is happening.
Don't forget to turn off the debug logging afterwards:
c:\>Nltest /DBFlag:0

Related

Extended Protection and SSL Encryption

Within two environments, where database servers with SQL Server 2008 R2 and SQL server 2012 are operated, the Extended Protection and SSL Encryption settings have been enabled. Since then, the applications (SharePoint 2010, SharePoint 2013 und ADFS) are having problems connecting to the databases. Following error message is logged in the SQL Server error logs: “SSPI handshake failed with error code 0x80090346, state 46 while establishing a connection with integrated security; the connection has been closed. Reason: The Channel Bindings from this client are missing or do not match the established Transport Layer Security (TLS) Channel. The service might be under attack, or the data provider or client operating system might need to be upgraded to support Extended Protection. Closing the connection.”.
On the client-side, following error message is logged: “Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.”
Basically, when both settings are enabled, the remote connection, even through SQL Server Management Studio, does not work anymore. This issue can be resolved by disabling one of the two settings.
If "disabling one of the two settings" still results in the connection between the two servers being encrypted, then your objective might have been achieved sufficiently by using only the other.

Unable to connect SSMS, Microsoft SQL Server, Error: 53

SQL Server Management Studio is not connecting on my database server machine at production server.
Whereas production sites accessing database. When I tried to connect database from SSMS, I get this error:
Cannot connect to 111.11.11.11.
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: 53)
I was using this SSMS last couple of years,n this SSMS is running fine since more then year on production database server n i didn't closed ever, now when i connecting this SSMS but facing this issue, whereas my sites which accessing this database is working fine.
I also tried to access database from sqlcmd but no luck n facing facing this error:
HResult 0x35, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [53].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to SQL Server.
Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
I thinks we resolved the issues.
1. Active Directory server was not behaving, so
2. SQL server couldn't run without credentials and
3. they found another SQL server issue and fixed it.
We started looking into the SQL connections that my team had found and it lead us to find that the Active Directory server had basically crashed. It was allowing us to log in however it wasn't able to access the majority of the AD functionality. We ended up rebooting the AD server which corrected the issue however we were still seeing issues with the SQL cluster manager and SQL itself was rejecting connections on a somewhat regular basis.
After the AD server was rebooted we were able to log into the SQL cluster manager but with limited capabilities, since it had been erroring due to the AD issue we restarted the cluster service to see if this would correct the issue. This caused the SQL service to fail over to the passive server and caused SQL to start rejecting even more connections than it had been. The cluster service started working with this restart however the SQL connections were getting worse. We found that the IPv6 protocol was enabled for the SQL service which causes problems, like the ones we were seeing, in SQL clusters, to disable this we had to reboot the 2 SQL servers. We rebooted them one at a time and once they were back up everything was working properly.

Unable to connect to SQL Azure remotely from SSMS 2012

I am unable to connect to my SQL Azure database instance remotely using SQL Management Studio 2012. Firewall exception is in there for my local IP. I can connect successfully and admin the database using the browser based management link in my Azure account.
I just can't seem to connect to the database via SSMS or anything else like VS2012.
Here is the format I'm for my connection in SSMS:
Server Name: myservername.database.windows.net
Authentication: SQL Server Authentication
Login: myusername#myservername
Password: my-password
Connect to: (i've tried) "master", mydatabasename, <default>
Encryption: TRUE
Once again, I DO have the firewall rule active for my local IP address on the server instance of my Azure account.
When I attempt to connect, I receive this error:
A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: SSL
Provider, error: 0 - the wait operation timed out.) (Microsoft SQL
Server, Error: 258)
When searching for that 258 error, I do not get many results related to SQL Azure. I appreciate any help.
Error 258 is generated due to some of the configuration within your machine if a secure network could be established between two endpoints and if one machine initiate secure channel. This problem could be very much machine specific and not SQL specific that why you did not find any resources on this regard.
Can you try using SQLCMD as described in the following troubleshooting guide and see if that works to isolate SSMS specific issues on the same machine:
http://social.technet.microsoft.com/wiki/contents/articles/1719.windows-azure-sql-database-connectivity-troubleshooting-guide.aspx
IF you capture and analyze network packets traffic you might be able to determine the root cause of connectivity error.

The server was not found or was not accessible - Server was lost for 6 hours

First off, I only have a very basic understanding of SQL. I can create tables etc. but configuration is beyond me. I am running my web site with MVC3 ASP.Net on a windows 2008 server using SQL Express.
Everything works fine, my connection strings are correct, I can use the website and it reads and writes to the dB, I can also view the dB with management studio on the server.
Today I got 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)
When I tried to log on to the database in management studio on the server I get a similar error. the only fix I have found is for a server restart. The database was down for 6 hours before I noticed which is not good for a start up website.
Has any one seen this issue before? Is this an express issue? Any help or advice would be great.
Troubleshoot as you would any network error. Start with the server's event logs.
As for notification of downtime, there are a lot of web services that will monitor your web site and email or send you an SMS message if it's not responding. Two that I've used are uptimerobot.com and basicstate.com. There are dozens of others.
You could also rewrite your ASP.Net app to email or text you when certain kinds of errors happen.

eCommerce desktop dry-run issue

So the situation is that I've d/l nopCommerce and a slew of other web development programs in order to save some cash on my business.
I've created a local server/database with sql anywhere 12, and then run nopCommerce with VS2010 to begin the install, but receive this error message when attempting to connect with the server:
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)
I've also ran the same db in VS and tried running it that way, while nopCommerce asks for a server name, I've tried many to no avail.
Checked spelling, I'm running everything local, so none of this makes sense.
All help is appreciated.
Have you enabled Named Pipes protocol for your SQL server?