KNOWN ISSUE: Not able to execute SQL scripts with Windows NT Authentication
|Article:TECH40299|||||Created: 2005-10-04|||||Updated: 2007-07-13|||||Article URL http://www.symantec.com/docs/TECH40299|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
When running an .MSI that executes a SQL script against a remote database using Windows Authentication, this error appears:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'DOMAIN\<computer name>$
- Create an .MSI that executes a SQL script. This .MSI should contain the User Information dialog and SQL Connection Dialog
- Set up SQL Server in a domain
- Be sure to set the SQL permissions for a NT User to allow access to remote SQL Server
- On a client machine in same domain, login as the NT user above
- Execute the .MSI
- On the User Information Dialog, select 'Anyone who uses this computer'
- On the SQL Connection Dialog, select 'Windows NT Authentication'
The installation proceeds until the SQL script attempts to execute at which point the error above appears. If you perform a per-user information instead of per-machine installation, the SQL script executes successfully.
Wise for Windows Installer 6.x
Wise Installation Studio 7.0
Connect to SQL Server using NT Authentication
- Go to MSI Script > Execute Deferrred
- Find the WiseSqlCallDll Custom Action. There will be separate custom actions for each SQL Script called in the installation
- Double-click on the Call DLL from Installation custom action. The Call DLL from Installation dialog appears.
- Click the Properties tab.
- Select 'Deferred Execution - User Context' from the In-Script Options drop-down list.
|Description||Logged in Littlebuggy (Altiris - Lindon, Plymouth) database|
Article URL http://www.symantec.com/docs/TECH40299