Error 1225 In Sql Server
Environment : AlwaysOn HA group, 2 nodes, 1 database, SQL2012, Server2012R2.
Active Directory Apple AWS Browser CentOS Chromebook cloud command line Debian eBook Fedora Free Tools Google Apps Google Chrome Google Chromebook Google Drive GP10 Great Plains How-To How To Linux Mac MS Office MS Outlook Outlook 2010 PowerShell Red Hat SBS2008 Scripting Security Server 2008 Server 2012 Small Business Server 2008 Tools. See the major causes of Microsoft SQL Server Login Failed Error 18456 and also get the simple solution of this error.
Here is my .NET C# code :
It works perfectly. 'ecouteuralwayso.xppocsql.local' accepts connections on TCP1435, I can read my database, no matter which node is the primary.
I want to use Read-Only redirection (http://msdn.microsoft.com/en-us/library/hh710054.aspx), so I configured read-only urls as described in the KB. Here are the results:
Which gives:
Then, I add
To my connection string .. But it doesn't work :
[Win32Exception (0x80004005): The remote computer refused the network connection]
[SqlException (0x80131904): 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: TCP Provider, error: 0 - The remote computer refused the network connection.)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +6564850
Without the MultiSubnetFailover, the error is :
Nothing logged in SQLServer..Any ideas?
madoxav1 Answer
Ok, got it. I had to force the TCP1433 port in SQL Configuration manager.. That was only that.I found it when trying to connect with a wrong password : SQLServer denied connection because of this wrong pass.So, the mistake was between the listener and the server supposed to accept the connection.. which was the second one, because of the read-only intent.
And this second one, even if it was listening on TCP1433, wasn't responding without explicitely configuring it in Configuration Manager.
Sorry!
madoxavmadoxav