Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=MyDBName;Data Source=MyServerName

this is the connection string, it can not be changed, it is in a dll from the dark ages. we are having to use it on a server outside of our domain. we can hit the server because we set up a host entry all we need is read access is there something on the sql server that can be configured to allow this connection?

but get the following:
Message: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Source: Microsoft OLE DB Provider for SQL Server

share|improve this question

1 Answer 1

up vote 2 down vote accepted

You need to either

  1. Configure the app to run in the context of a Windows user who has sufficient permissions to the data on the SQL Server or
  2. Create a Windows login on the SQL Server for the user(s) whose accounts the app is running under.
share|improve this answer
    
i tried enabling impersonation in asp.net but got an error that the domain could not resolved. –  Christopher Kelly Jan 21 '10 at 17:11
    
You need to make sure that the application pool in IIS that is servicing your app is running with its identity set to that of the Windows account that has access to your db. –  squillman Jan 21 '10 at 17:13

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.