This seems to correlate with this issue suggesting that the CryptProtectData Windows API is not functioning.
I attached the full error message received.
I also saw the lag in typing the password that chalfant_leaf saw. Launched Management Studio and attempted to login with the sql login again and it failed.
Logged out and back into the instance with a Domain account who is a member of the Domain Admins role. Launched SQL Management Studio and connected with the SQL login again successfully.Ħ. Logged in as the local Administrator again (just to test). Joined the instance to the Simple AD domain.ĥ. Reconnected in Management Studio using the new SQL login I just created.Ĥ. Enabled mixed Windows Auth and SQL Auth mode. Launched SQL Management Studio and connected with Windows Authentication. Connected to the instance with the local Administrator account. Created a Simple AD using AWS Directory ServiceĢ. I suspect that there is some interaction between SQL Server Management Studio and Simple AD when encrypting the password that might be failing. If I RDP into the EC2 instance as a domain user and use sqlplus to connect to the RDS database it works as expected. This lag is not present when RDP'd into the EC2 instance as Administrator. In addition, when I enter the sa password in SQL Server Management Studio, there is significant lag (1+ seconds) between typing a character and when it displays in the password field. When I RDP into the EC2 instance as a domain user, SQL Server Management Studio fails to connect to the RDS instance using SQL Server Authentication (sa account) with the following error message:Ĭannot connect to .com. When I RDP into the EC2 instance as the Administrator, SQL Server Management Studio can connect to the RDS instance using SQL Server Authentication (sa account). The Windows machine is a member of a Simple AD domain. Reason: Could not find a login matching the name provided.I'm using SQL Server Management Studio 2012 to connect to an RDS SQL Server 2012 instance from a Windows 2012 R2 EC2 instance. 12:58:04.23 Logon Login failed for user 'SD\SPAdmin'. Reason: Could not find a login matching the name provided. 12:58:00.90 Logon Login failed for user 'SD\SAdmin'.
12:57:58.16 Logon Login failed for user 'SD\Admin'.
12:49:05.23 Logon Login failed for user 'SD\Admin'. 12:44:49.57 Logon Login failed for user 'SD\Admin'. WeĬarefully follow the steps outline in the link below but no luck. "Error 18456" when trying to login to the Database Engine for the 1st time via SQL Management Studio. I am just new in SQL 2012 r2 and we are trying to provision one SQL VM but we are getting an error a"Login failed for user.