Problem with ASP, ODBC and IIS6
-
A few days ago i moved a asp-application i created to a new server. This application connects to an access-database by using odbc. Funny thing is, that is can connect to the database and read records without problems, but whenever i try to write data in to the database i get an internal server error. On the old server everything worked ok. The datase is writeenabled and there is no password on it. The difference is, on the new server runs IIS 6. So maybe some settings have to be changed to allow me to write to the database but i have no idea what to change. I have given writeaccess to every user of my application, but this didn't make any difference. Any idea would be highly appriciated, cause i am starting to get a little desperate by now!
-
A few days ago i moved a asp-application i created to a new server. This application connects to an access-database by using odbc. Funny thing is, that is can connect to the database and read records without problems, but whenever i try to write data in to the database i get an internal server error. On the old server everything worked ok. The datase is writeenabled and there is no password on it. The difference is, on the new server runs IIS 6. So maybe some settings have to be changed to allow me to write to the database but i have no idea what to change. I have given writeaccess to every user of my application, but this didn't make any difference. Any idea would be highly appriciated, cause i am starting to get a little desperate by now!
Did you check the access settings for the NETWORK_SERVICE user? I think IIS/ASP runs under that users context (I can't check my own server to verify atm, so YMMV) -- Ian Darling "The moral of the story is that with a contrived example, you can prove anything." - Joel Spolsky
-
Did you check the access settings for the NETWORK_SERVICE user? I think IIS/ASP runs under that users context (I can't check my own server to verify atm, so YMMV) -- Ian Darling "The moral of the story is that with a contrived example, you can prove anything." - Joel Spolsky
GREAT! This was the solution. I didn't even think about the "NETWORK_SERVICE" user until your mail and now everything is running fine. THANK YOU VERY MUCH FOR YOUR HELP!