Error Message "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"

I deployed an 2.0 app in March that was running properly until a few days ago.  I didn't have time to examine it much, I was simply told to move it to a new server and that it was no longer working.

Since the move, I've encountered several problems.  The app is accessible and runs locally by referencing both the localhost and the server name.  However, an attempt to access it accross the network results in either one or two error messages depending on how I had the web app configured:

                       "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
                        [this occurs when I have the app set for Integrated Windows authentication only]

                       "You are not authorized to view this page.
                        HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
                        Internet Information Services (IIS)"
                        [this occurs when the app is set to allow Anonymous Access]

No matter what domain user account I use for anonymous access in the Window Event View I always get a logon failure for the NT AUTHORITY\SYSTEM account using the designated domain user account for anonymous access.  The domain user accounts are added as SQL logins with access to the applicable database.

Anyone have any ideas what's going on with this?  The new server is using Sharepoint, application pools, IIS 6 on a Win 2003 box.  SQL Server 2000 is on a separate box.


Who is Participating?
aim4fameConnect With a Mentor Commented:
Perhaps this link will help:
Leon FesterConnect With a Mentor Senior Solutions ArchitectCommented:
Are you missing any DSN entries?
Anandhi KConnect With a Mentor Commented:
Just add this in your connection string and try again

MariyamAuthor Commented:
db 1110, I can't put the credentials in the connection string for security reasons.  I checked the link posted by aim4fame and there isn't a missing DSN entry.  It appears to be a configuration issue involving the application pool(s) in Sharepoint/IIS.

I think I'll post a link to this question on the IIS board.  Thanks for your suggestions anyway.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.