I have just downloaded the files and copied them to my web folder. I modified the config file which is posted below. (I'm using Access) When I try to browse to the setup.asp file, it takes a couple of minutes and then gives me a 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed. I DO have show friendly HTTP error messages unchecked. I have tried using a physical and relative path in the config file and 'everyone' has full access to the the folder that the database is in. I am running Windows Server 2008. I do have Office 2003 (with Access) installed on the server so I'm not sure it the jet engine is waht is causing it or not. The link to the forum is: http://tlevering.homeip.net/teambuckeye/forum
File removed by ruirib - No need to post the whole code, here, not very useful. <
The database is in c:\inetpub\wwwroot\tb9145uret.mdb and the config file reads: strConnString = "Provider=Microsoft.Jet.OLEDB.4.0;Data source=c:\inetpub\wwwroot\tb9145uret.mdb" Since I've got it in the wwwroot folder (for now) I've even tried using the first line: strConnString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath("tb9145uret.mdb") I've also tried it without renaming the mdb file both ways. <
You shouldn't use the wwwroot folder for the access file. Try placing it outside the forum and making sure that the folder as adequate read and write permissions.<
Also, get your host to disable their custom 500 error message page or at least code it to provide information that's actually useful.
<
Search is your friend “I was having a mildly paranoid day, mostly due to the fact that the mad priest lady from over the river had taken to nailing weasels to my front door again.”
Ok. In IIS 7.0 you have to run the following command from a command prompt in order to see detailed error messages. %windir%\system32\inetsrv\appcmd set config -section:asp -scriptErrorSentToBrowser:true You must remember to set back to false when you are done.
Here is what the page is telling me: The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
The default setting was 120 seconds. I bumped the timeout up to 500 seconds and still get the same error.<
Topic Locked
Posted - 13 February 2009 : 07:20:01
