First, make sure ASP Classic Is Installed on Vista, good instructions here
Make sure your app is set up as a virtual directory, etc, etc.
Then, you need to set permissions and run commands and change around settings just to get anywhere. Just for kicks I made the IUSR for the directory have modify rights, but I am not sure if that did anything, oh well, I am not changing it back.
I ran the default page, and got this
An error occurred on the server when processing the URL. Please contact the system administrator
Nice huh? Well, I went and turned off Friendly HTTP Errors in IE Internet Options, that didn’t give me anymore info, so, found this:
cscript %systemdrive%inetpubadminiscriptsadsutil.vbs set w3svc/AspScriptErrorSentToBrowser true
That will send the actual errors to the browser, ok good.
Now, getting this:
Microsoft OLE DB Provider for ODBC Drivers error ‘80004005’
Found out you need to run 3 more commands to get this to work… ok
icacls %windir%serviceprofilesnetworkserviceAppDataLocalTemp /grant Users:(CI)(S,WD,AD,X)
icacls %windir%serviceprofilesnetworkserviceAppDataLocalTemp /grant “CREATOR OWNER”:(OI)(CI)(IO)(F)
%windir%system32inetsrvappcmd set config -section:applicationPools /[name=’DefaultAppPool’].processModel.loadUserProfile:false
After all that nonsense, the page/app actually worked! What a debacle…
3 replies on “Vista, IIS7, Classic ASP, and Microsoft Access – How to Get It Working!”
[…] Read the rest of this great post here […]
For a complete description of this and other classic ASP on IIS7 issues, see this blog post: http://blogs.iis.net/bills/archive/2007/05/21/tips-for-classic-asp-developers-on-iis7.aspx
Great article, finally got the error debugging to work properly- can’t believe that windows forces users to enter an arcane command just get the errors to display correctly!
Just one thing though, i think the cscript command you show has an “i” in the “adminiscripts”, i think its normally just “adminscripts”.
Thanks for the help!