Error Example:An error occurred while executing connection '<connectionName>': Error reading from entity '<entityName>': Login failed for user '<DOMAIN\userAccount>'. An error occurred while executing connection '<connectionName>': Error reading from entity '<entityName>: <connectionnNme>: Cannot open database "<DBname>" requested by the login. The login failed.Login failed for user '<userAccount>'. Cause:There are a couple of known reasons for this error. The first is that the given account is incorrect or has insufficient permissions. It may also be that the account that was meant to be a SQL account to Windows instead in the creation of the account. The second is that you are trying to use a Windows account as the credentials. The username/password in a connection string is always assumed to be a SQL authentication account by MS SQL Server Provider. You cannot use AD/Windows accounts to log into the SQL server when using the provider unless using integrated security. Third, is that you are using integrated security. The Layer2 Cloud Connector will log in as the service's account, by default the local system account, which likely doesn't have access. Usually, you will see an account with the server's own name in the error, like 'DOMAIN\ServerName$', which is the local system account. Fourth, though rare, is that the SQL instance was deployed allowing only for Windows integration for login. This can be adjusted though. Resolution/Workaround:There are two options to deal with this, assuming it's not a general wrong :
Caveat for Cloud Connector - If you are using integrated security for your connection to SQL you MUST set the account attached to the Layer2 Cloud Connector Service to be one that has access to that Table in SQL (else the sync will fail). Otherwise, you will need to add SQL Account to the connection string which is what we recommend doing.
|
Login Failed for User 'X' -SQL
