Troubleshooting
We have described some general and frequent errors below:
Answer:
There is something wrong with the path to your databases. Make sure you specify the virtual directory in web_config.asp if there is one!
Answer:
Your database is marked 'Read-only' or the IUSR does not have enough permissions to edit your database(s)! I recommend to give IUSR "Full Control" on the folder containing the database.
Answer:
A connection to your database(s) could not be established. Most likely there is an error in the path to your database. Check these paths in asp/config/web_config.asp.
Answer:
Check Microsoft's KB at http://support.microsoft.com/kb/315122/en-us?spid=3198&sid=205
Answer:
Your database is marked 'Read-only' or the IUSR does not have enough permissions to edit your database(s)! I recommend to give IUSR "Full Control" on the folder containing the database.
Answer:
The above error occurs when your website is having a lot of visitors (>500 visitors/day). MS Access is not made for busy sites. You may want to upgrade QuickerSite to use MS SQL Server if this problems occures on a regular base.
QS v168 is compatible with MS SQL Server 2005.
QS v168 is compatible with MS SQL Server 2005.
Answer:
Windows 2003 servers running IIS6.0 prevent the upload of files more than +200Kb.
If you are running QuickerSite on a web host, please contact the host and ask them to increase the file size limit in IIS.
If you are running your own server, you will need to make some changes in IIS.
1: Stop the IIS service.
2: Open the file metabase.xml in the c:\Windows\System32\Inetsrv folder.
3. Find the line " AspMaxRequestEntityAllowed "
4. Change it to whatever size you need in bytes (eg. "1073741824" is 1GB).
5. Save the file.
6. Restart IIS.
If you are running QuickerSite on a web host, please contact the host and ask them to increase the file size limit in IIS.
If you are running your own server, you will need to make some changes in IIS.
1: Stop the IIS service.
2: Open the file metabase.xml in the c:\Windows\System32\Inetsrv folder.
3. Find the line " AspMaxRequestEntityAllowed "
4. Change it to whatever size you need in bytes (eg. "1073741824" is 1GB).
5. Save the file.
6. Restart IIS.
Answer:
This problem occurs when using an external mail-service (<> localhost) together with the CDO.MESSAGE component.
The solution is to add 1 line to asp/includes/mail_message.asp, around line 70:
myMail.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/sendusing")=2
Be careful: only add this line in case you experience problems when sending emails using CDO.MESSAGE, and in case you use an external mail server, like smtp.mydomain.com!
The solution is to add 1 line to asp/includes/mail_message.asp, around line 70:
myMail.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/sendusing")=2
Be careful: only add this line in case you experience problems when sending emails using CDO.MESSAGE, and in case you use an external mail server, like smtp.mydomain.com!
Answer:
To properly install ASP.NET in IIS, please check the appropriate forums/sites. In short, you need to 'allow' ASP.NET in IIS 6.0 (under Web Service Extensions). The latest version of showThumb.aspx works for ASP.NET 1.1 & 2.0.
Answer:
In IIS 5.0 (Windows 2000 only), passwords (for the backsite, the intranet & items with passwords) should be limited to ascii-characters only (a-z, 0-9). IIS 5.0 does not support the use of UTF-8 characters in cookies! This issue is solved as from IIS 5.1 (Windows XP Pro).
Support > Installation Guide > Troubleshooting / Step by step... / System Requirements / Multiple QuickerSites