Apixel COMET - Learning Record Store

Help

Trouble Shooting

 

Connection Strings

Comet was written specifically for classic ASP 3, and it uses many intrinsic ASP objects such as Request. Classic ASP is different from ASP.NET and must usually be specifically enabled on your web server.

Here's an MSDN blog post on enabling ASP and here's a link on deploying a classic ASP server.

A web site that we use as a reference for connection strings is http://www.connectionstrings.com/.

Generally, if you have "special characters" in your Server, User, Password or Database parameters then they must be changed to a URL form (via URI hex encodings). For example:

 

Operation must use an updateable query

Comet was written specifically for classic ASP 3, and it uses many intrinsic ASP objects such as Request. Classic ASP is different from ASP.NET and must usually be specifically enabled on your web server.

If you encounter the following error, Operation must use an updateable query then this Microsoft article should help.

 

Data source name not found and no default driver specified

This error occurs when you attempt to sign in (the error message may vary depending on your database and web server.) Commonly this occurs beause the connection string is incorrect.

 

Could not find installable ISAM

One of a number of things may cause this error:

 

Active Server Pages error "ASP 0131"

If you get the error Active Server Pages error "ASP 0131" or Server.MapPath() error "ASP 0175 : 80004005" it means that IIS has disallowed the ".." characters in paths. Comet uses ".." in various paths it so you will need to enabled them.

The following image shows where you can enable parent paths for ASP in the IIS Manager (Select to enlarge):

Select to enlarge

 

Why can't I access an MS Access database on the web server?"

The most common reason is because the database has not been given anonymous access. Under IIS you need to set access permissions for the IUSR and IIS_IUSRS accounts for the database.

The other reason may be because you have not installed the MS Access Database provider. One can be downloaded from Microsoft Access Database Engine 2010 Redistributable. Do not use the JET.OLEDB 4.0 provider in a 64bit environment.

 

Debugging

If you having trouble resolving a database setup issue you may find it worthwhile to:

 

Error Messages in Internet Explorer

To get errors that are more meaningful i.e. technical, in Internet Explorer it may help if you:

 

Making detailed ASP error messages display in the browser

In IIS the default settings may prevent detailed ASP error messages from being displayed to the user. This is good in a production/live web site but detailed error messages may be necessary during debugging. To switch on detailed error messages:

Note sending detailed error messages is never advisable for a production website. The setting should be changed back when debugging is complete.

 

The server says that .accdb is not a supported format

You are using Microsoft access and your server does not support the newer (Microsoft Access 2007) format. Your server may instead support the older Microsoft Access format of .mdb. In which case you should open the database file in Microsoft Access and do a "save as..." to an .mdb and then use the new file in place of the existing one. You may have to manually edit the .asp files in the config folder to point to the new file name.

 

IIS Section Locked

If you receive the following error:
"This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault='Deny'), or set explicitly by a location tag with overrideMode='Deny' or the legacy allowOverride='false'."
then you will probably need to unlock the relevant section.

More information on locking in IIS is available here.

 

 

© Copyright 2016 Apixel Pty Ltd, All rights reserved