SQL Trusted Connection

[ble0t]

I am having an issue trying to use the 'Trusted Connection' option for establishing a SQL connection. The install I'm am attempting to create must establish a connection with a SQL server that is not local and when attempting to use the 'Trusted Connection' option, it returns an error saying that the login was denied. The error message is as follows:

SQLDriverConnect: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'DOMAIN\USER$'

(I've changed the domain and user name to be generic...)

I've triple checked the fact that the login is valid on the server and trying the install runs fine when on the actual SQL server itself (logged in as the same user). The thing that appears odd to me is the '$' that occurs after the user name.

Can anyone shed any light on this? Thanks in advance!

EDIT: I am currently using AI 4.7

[gigi]

Hi,

The install I'm am attempting to create must establish a connection with a SQL server that is not local and when attempting to use the 'Trusted Connection' option

A Trusted Connection can be established only with a SQL server that runs local. Because when using a trusted connection the credentials of the current user are used.

Best Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[ble0t]

Because when using a trusted connection the credentials of the current user are used.

True, but if the SQL server has logins that are using integrated security (i.e. using domain accounts), accessing it locally or accessing it from a remote location (if the accounts being used are the same) should not matter because the server requires the same credentials in either case. I am confused as to where the difference lies...

[gigi]

Hi,

Please make sure that:

1. The user installing your package is in the same Windows domain with the user who is configured with integrated Windows authentication on the SQL server.
2. The SQL server accepts remote administrative logins and also if it's configured to accept remote trusted connections.

You can test with "Microsoft SQL Server Enterprise Manager" or "Microsoft SQL Query Analyzer" to see if you can establish a trusted connection from the computer you are installing the package to the SQL Server machine.

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[ble0t]

I have verified these two things. I will do some more testing and try and to narrow it down further. Thank you for the quick responses!

[ble0t]

I finally got around to testing things out a bit more...if using SQL authentication (in my case, forcing the user to use the 'sa' login), everything appears to work fine. Perhaps trusted connection against a non-local machine could be a future feature?