locked
speech server SQL Integrated Security RRS feed

  • Question

  • We are building a speech server using windows integrated security to access sql server database. however, it seems like the speech server doesn't pick up the local window account to connect the sql server. I got error of "Login failed for user ''. The user is not associated with a trusted SQL Server connection", please notice the user account here is totally empty ''.
    Does the speech server running on a different user account other than the local windows account?
    Friday, November 13, 2009 8:22 PM

All replies

  • Yes it does - http://msdn.microsoft.com/en-us/library/bb801633.aspx

    These postings are provided "AS IS" with no warranties, and confer no rights.
    Saturday, November 14, 2009 5:11 PM
  • Thanks for the reply, after a little researching into this issue, here is my understanding to summarize this:

    It seems like the speech server is only designed to run under iis 6.1 or higher. According to this reference: It "Setup program creates an application pool called Speech Server under which Speech Server applications are intended to run". and by default "The Speech Server processes run as the NETWORK SERVICE account". It should use this default account when accessing local resource and use current windows account to access network resource (such as database and shared file server).
    However, the IIS 5.1 doesn't have application pool and web app running under 5.1 is using [machinename]/ASPNET user account by default. It's uncertain if speech server has issue to use this account to access local resource, but it definitively failed to use local windows account when accessing network resource under IIS 5.1. The error developer will see is like: Login failed for user ''. The user is not associated with a trusted SQL Server connection. Please note the user account here is a empty string.
    Solution is to update to force impersonation in the machine.config under the currently used .NET framework folder. An example would be like this:
    <processmodel password="[password]" username="[domain]\[username]">

    Monday, November 16, 2009 3:42 PM