SQL ERROR FILE SYSTEM VS HTTP://

Question

HI- I have developed an ASP.NET website using VS 2005 Created as an HTTP:// type project. It worked just fine. I then moved the SQL database to the production server. and made appropriate changes to the WEB.CONFIG file. I am now getting an error when trying to access the database. The Error is:Login failed for user ''. When I started trouble shooting this is what I discovered: I created a very simple website that used a gridview bound to a the data table on the remote server. Displayed on screen fine. I noticed that I accidently created the project as a File System type. I then duplicated the exact same simple test project only this time created as an HTTP type saved on the local IIS/wwwroot. The second scenario would not work and gives the same error. Could someone please explain why scenario 1 worked and scenario 2 would not? And what I need to do to correct the problem? Thanks-- Mike

Mike Sportsman · Answer

Thank you for you suggestion. I checked the IIS set as you suggested. The settings were set to Form authentication. Changing to windows authentication made no difference! its like the IIS on my local machine is nulling the username before it makes its connection to the SQLEXPRESS instance that is located on the Server which is the location where this web app will live once it has been duly tested. Thanks once again for your help but I am still very puzzeled as to why this is not working

Roei Bar · Answer

is the website in IIS set as an application with Windows authentication

Mike Sportsman · Answer

Thanks for the reply: If I am using the same connection string in both cases.... Why? If I run the website from HTTP://localserver/WEB_SITE_NAME Genreates Error AND Run from C:\mydocs\vs2005\projects\WEB_SITE_NAME Works fine Can you explain please? Also I forgot to mention I am using Windows Authenication...... This app is running on an intranet..... where users are already loged into the domain.

Roei Bar · Answer

the error you state is an error on login to the SQL Server make sure that your login Credentials are OK