![]() Error 18452 will be generated along with SSPI handshake errors because same database is set as default database for your login that has become inaccessible now because of acting secondary database in AOAG. If failover will happen then you would not be able to access the database because it will become secondary. As I described above that one of the probable reason to get this error 18452 is because you might use AOAG replica server name to connect to the database with the login for which default database is set as the AOAG availability database. If your SQL Server Instance is already set with SQL Server and Windows Authentication mode then you should fix this issue in separate way. Restart SQL Server services to apply the changes. You can see that I have selected above mode to apply the changes. Select the radio button for SQL Server and Windows Authentication mode option and click ok button to proceed. Now we will change it to SQL Server and Windows Authentication mode. You can see current Server Authentication configuration is set to Windows Authentication mode in below screenshot. Click at Security option from left side pane. Once you will click at Properties option, you will be getting below SQL Server instance property window. Right click at the instance node and click at the properties option as shown in below screenshot. To check the configured authentication mode for your SQL Server Instance, we need to launch SQL Server Instance property window. If your SQL Server instance is running with windows authentication mode then you must change it to Mixed mode so that windows and SQL both type of logins can be authenticated. ![]() ![]() To fix this issue first we need to check the authentication mode set for your SQL Server Instance. SSPI handshake errors comes because of Kerberos failure, which would most likely be related to non-existent SPN or bad SPN for SQL Server. The Windows error code indicates the cause of failure. SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security the connection has been closed. ![]()
0 Comments
Leave a Reply. |