Quote:
Originally posted by Memnoch1207
Is the SQL Servers security setup to use Windows Authentication of SQL Server Authentication?
If SQL Server Authentication, then it would expect a username and password in the connectionstring.
That's true. The connection string does say "integrated security=true;" which tells me WinNTAuth is to be used, - but that doesn't mean the server is set up that way. I don't know under what context the page is running. Obviously, what ever user context (if any) the code is running under, that user doesn't have permissions. Since it reported the login as (null) I have to assume that it isn't running under any user context. In which case it needs to be converted over to use SQL authentication, in which case the connection string would need to be changed, or the code needs to be forced to run under a specific user context that has the appropriate security to access the database.