ASPRunner Professional Frequently Asked Questions

This FAQ answers ASPRunnerPro questions. If you don't have latest version of ASPRunnerPro, please download it here.

If you have question that isn't listed here, feel free to ask your question in ASPRunnerPro forum or contact technical support at http://support.xlinesoft.com.

 

2-3. Question:

I receive the following error message when trying to save changes I made to database

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC Microsoft Access Driver] Syntax error in UPDATE statement.
/tablename_edit.asp, line xxx

or

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC Microsoft Access Driver] Syntax error in INSERT INTO statement.
/tablename_edit.asp, line xxx

Answer:

This commonly occurs when you have a field name that is a reserved word. Certain words (like table, field, date, note, select, password, level etc) are reserved by either ADO, OLEDB or by Access for use as commands or system objects. You can get a list of reserved words in Access from the online help. You should never use these words as names for tables or fields, nor should you have spaces in your tablenames. It is recommended that you rename your offending tables/fields and adjust your SQL statement accordingly.

Back to top

 

4. Question:

I receive the following error message when opening pages generated by ASPRunner:

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'MACHINE_NAME\IUSR_MACHINE_NAME'.
/tablename_list.asp, line xxx

Answer:

Issue

When using an ODBC or OLE DB connection to a Microsoft SQL Server database in an ASP page, one of the following error messages may occur while attempting to view the page in a Web browser:

Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'WebServerName\IUSR_computername'.
Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'NT AUTHORITY\ANONYMOUS LOGON'.
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '\'.

Reason

These errors are generated if SQL Server does not accept the logon account and/or password being submitted. One possible reason could be that a corresponding SQL Server account has not been setup for the Windows NT account that is used to access the database. An example of an account used to access the SQL Server database could be the IUSR_computername account used by Internet Information Services (IIS) for anonymous access to ASP pages.

Solution

Verify that a SQL Server authentication login or a Windows NT authentication login exists in SQL Server for the Windows user account that IIS uses to access the ASP page. If a login does not exist, use the SQL Server Enterprise Manager to create it. Also, when creating an ODBC Data Source Name (DSN) in the ODBC Administrator, make sure to choose the appropriate authentication method when you configure the DSN, and to test the DSN in the ODBC Administrator to verify that it is working correctly.

For information on how to configure SQL Server authentication, please refer to the following Microsoft Knowledge Base article:

Q247931 INF: Authentication Methods for Connections to SQL Server in Active Server Pages

Additional information

For additional information about authentication methods and how they work, please refer to Understanding Anonymous Authentication and the IUSR Account (TechNote 15378) and WWW Authentication Methods (TechNote 15383), or the online IIS documentation.

Back to top

 

5. Question:

I receive the following error message when trying to save changes I made to database:

Microsoft OLE DB Provider for ODBC Drivers error '80040e07'
[Microsoft][ODBC Microsoft Access Driver] Data type mismatch in criteria expression.
/tablename_edit.asp, line xxx

Answer:

Issue

The SQL error 80040E07 occurs when attempting to use the "Insert Record" or the "Update Record" server behavior to set the value of a column in Microsoft Access with an empty string ("").

Reason

MS Access is characterized by strong data typing; it imposes a rigorous set of rules on given column values. The empty string value in the command text (SQL) cannot be stored in MS Access' "Date/Time" data type specified by the associated column.

Solution

Try to avoid inserting and/or updating columns of "Date/Time" data types in Access with empty strings, ("") or with any other value that does not correspond to the range of values specified for the data type.

Back to top

 

6. Question:

I receive the following error message when trying to save changes I made to database:

The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.

Answer:

  • This commonly occurs when your database file opened exclusively by another application (usually MS Access). Close all applications that use this database and try again.
  • This error may occur if the account being used by Internet Information Server (IIS), (usually IUSR), does not have the correct Windows NT permissions for a file-based database or for the folder containing the file.
  • Check the permissions on the file and the folder. Make sure that you have the ability to create and/or destroy any temporary files. Temporary files are usually created in the same folder as the database, but the file may also be created in other folders such as /Winnt.
  • If you use a network path to the database (UNC or mapped drive), check the permissions on the share, the file, and the folder.
  • Check to make sure that the file and the data source name (DSN) are not marked as Exclusive.
  • Simplify. Use a System DSN that uses a local drive letter. Move the database to the local drive if necessary to test.
  • The "other user" might be Visual InterDev. Close any Visual InterDev projects that contain a data connection to the database.
  • This error may also occur when accessing a local Microsoft Access database linked to a table where the table is in an Access database on a network server.

Back to top

 

7. Question:

I receive the following error message:

Unable to open registry key 'Temporary (volatile) Jet DSN for process ...

Answer:

This error can happen for a number of reasons. Usually it happens when path to the database is incorrect.

You need to check that the path to the database is correct. You need to make sure that database file was copied to the server.

The error is also quite common if the permissions on the server are incorrect. Check that IIS has sufficient permissions to access the registry and that the correct permissions, read and write, are set on the directory containing the database and the database itself, for the IUSR account.

Back to top

 

8. Question:

I receive the following error message:

Data provider could not be initialized

Answer:

This error can happen for a number of reasons. Usually it happens due to server components conflict. You can try one of the following things to resolve this problem:

Back to top

 

9. Question:

I receive the following error message:

Microsoft VBScript runtime error '800a005e'

Invalid use of Null: 'Replace'

YourTableName_list.asp, line xxx

Answer:

This error happens when key column value is NULL. You need to choose another column as key column.

Note: Key column is the database column which lets you query each table row individually and modify each row without altering other rows in the same table. The values that compose a key column a unique; no two values are the same.

Back to top

 

10. Question:

I receive the following error message:

Error number -2147467259

Error description Specified driver could not be loaded due to system error 5 (Oracle in OraHome92).

YourTableName_list.asp

Answer:

Oracle 9.2 Client software requires that you give the Authenticated User privilege to the Oracle Home by following these steps:

  • Log on to Windows as a user with Administrator privileges.
  • Launch Windows Explorer from the Start Menu and and navigate to the ORACLE_HOME folder. This is typically the "Ora92" folder under the "Oracle" folder (i.e. D:\Oracle\Ora92).
  • Right-click on the ORACLE_HOME folder and choose the "Properties" option from the drop down list. A "Properties" window should appear.
  • Click on the "Security" tab of the "Properties" window.
  • Click on "Authenticated Users" item in the "Name" list (on Windows XP the "Name" list is called "Group or user names").
  • Uncheck the "Read and Execute" box in the "Permissions" list under the "Allow" column (on Windows XP the "Permissions" list is called "Permissions for Authenticated Users").
  • Re-check the "Read and Execute" box under the "Allow" column (this is the box you just unchecked).
  • Click the "Advanced" button and in the "Permission Entries" list make sure you see the "Authenticated Users" listed there with:

    Permission = Read & Execute
    Apply To = This folder, subfolders and files

    If this is NOT the case, edit that line and make sure the "Apply onto" drop-down box is set to "This folder, subfolders and files". This should already be set properly but it is important that you verify this.
  • Click the "Ok" button until you close out all of the security properties windows. The cursor may present the hour glass for a few seconds as it applies the permissions you just changed to all subfolders and files.
  • Reboot your computer to assure that these changes have taken effect.

Re-execute the application and it should now work.

Back to top

 

11. Question:

I receive the following error message when trying to save changes I made to database:

Too many fields defined

Answer:

The Microsoft Jet database engine has an internal limit of 255 fields per query. As the Microsoft Jet database engine iterates through the records in an update query, it creates a field for the original value and a field for the updated value. When more than 127 fields are selected, it reaches the 255 field limit of a query.

Don't put more than 127 fields on Add/Edit pages.

For additional information about this error, please refer to the following Microsoft Knowledge Base article: 'Too Many Fields Defined' Error Message in Update Query.

Back to top