Thomas, thanks so much for that tip it got me one step closer to migrating a classic ASP site over to IIS 7 on 64bit vista. I still have a missing piece to my puzzle though, I cannot for the life of me get a connection to my Access database when running the code under IIS. I get the dreaded when attempting to connect:
Microsoft JET Database Engine : Unspecified error : -2147467259
However, if I take the offending code out and place it into a .vbs file (changing Response.write to MsgBox and Server.CreateObject to CreateObject), everything works just fine. I run the .vbs file from the command line using wscript from the sysWOW64 directory (otherwise you get Provider not Found).
Just to make sure it wasn't permissions, I moved the .mdb to a new folder and gave full perms to "Everyone".
Here is the code:
<%
Dim mobjConnection
Dim mobjRecordSet
Private Sub Initialize()
Dim lstrQuery
Dim rows
Set mobjConnection = Server.CreateObject("ADODB.Connection")
mobjConnection.Provider = "Microsoft.Jet.OLEDB.4.0"
Response.write("<h1>Got here</h1>")
On Error Resume Next
mobjConnection.Open "E:\\temp\\status.mdb"
If Err.number <> 0 then
Response.write("<h1>" & Err.source & ":" & Err.description & ":" & Err.number & "</h1>")
End If
Response.write("<h1>Got here</h1>")
End Sub
Call Initialize()
%>
I saw an article which stated that Windows\Temp folder needed to be permed right as well, I did that, still no luck. In my .vbs version I do infact see a temp file being created in my user account's Temp folder (Jet apparently uses the %TEMP% var from System env settings when running under IIS, but uses %TEMP% from the user's env settings when running under a user's account).
Any help would be greatly appreciated. It has to be some configuration I missed.
Thanks in advance.