David
Tue Dec 13 01:34:56 CST 2005
Can you describe what permission customizations you used on IIS5?
Otherwise, I have no idea whether it is comparable nor relevant for IIS6
because if you chose comparable process model configuration on IIS6, it
should work.
For example, what user account were you using to write to the Access MDB
file on IIS5? There can be many choices, so the answer depends on your
decision.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Bill" <btcchan@hotmail.com> wrote in message
news:%237ztoX6$FHA.1312@TK2MSFTNGP09.phx.gbl...
Hi David,
I have stayed with the same permission of IIS5 as with the IIS6. Please
advise which area I need to change the configuration. Thanks.
Bill
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:uHmhCmu$FHA.1256@TK2MSFTNGP15.phx.gbl...
> I presume that you've given read/write permission to the correct user
> identity to access the Access MDB file? It can be different than IIS5,
> depending on the mode you configured IIS6, but it is all configurable so
it
> may be a matter of configuration.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "msnews.microsoft.com" <btcchan@hotmail.com> wrote in message
> news:O5zLkeu$FHA.344@TK2MSFTNGP11.phx.gbl...
> Hi everybody,
>
> My ASP application has been running on W2Ksp4 with IIS5.0 for 4-5 years,
and
> everything works fine. The ASP application runs on a DLL file compiled by
> VB6SP5, and it calls for the API GetObjectContext() via the COM+ Services
> Type Library. The database at the backend is a Microsoft Access 2000 SP3,
> and it is connected by ODBC and JET engine. A few days ago, I have moved
> the ASP application to a Windows 2003 Server SP1 and IIS6.0. When the
> application needed to read and write some data from/to the Access
database,
> an error was experienced and the browser showed "HTTP 500 -Internal server
> error". I checked that the DLL file was successfully registered, and it
> worked OK as long as it did not need to access the Access database.
>
> Could someone point me to the right direction to tackle this problem?
> Thanks.
>
> Bill
>
>
>
>
>