Troubleshooting

Miscellaneous:

• T7.1: Is DAF DLL loaded?
• T7.2: Were all DAF database(s) found and loaded?
• T7.3: Is one and only one DAF DLL loaded?

ODBC related:

• T8.1: Is there an ODBC problem?
• T8.2: Is your ODBC source a "System DSN?"
• T8.3: With an MS Access file as an ODBC data source, new users are not usable.
• T8.4: ODBC error while using the Web User Manager :
  [Microsoft][ODBC Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use ...

Access Denied:

• Access Denied with a valid DAF user login and password

Miscellaneous:

• T7.1: Is DAF DLL loaded?

DAF DLL (DAF35x.DLL or DAF40.DLL) is the main binary code (ISAPI filter). It handles web authentications and access permissions if DAFAUTH.INI files are used. Therefore if the DAF DLL is not loaded authentication cannot work and it is useless to search for any other problems as long as the DAF DLL reamin unloaded when IIS is running.

With DAF 4.0:

DAF filter is loaded if at least one of these is true:
- A message is displayed in the NT Event Viewer: "DAF IIS Filter Started (4.0)"
- DAF40x.DLL cannot be deleted

DAF filter is supose to be installed with the main setup program. If for some reason it seem not loaded, the installation can be checked as described below for DAF 3.5 in section "If DAF DLL is not loaded".

With DAF 3.5:

The filter is loaded if at least one of these is true:
- The "DAF Manager" window is available from the task bar
- A message is displayed in the NT Event Viewer: "DAF IIS Filter Started (3.5)"
- DAF35x.DLL cannot be deleted

Of course, if the filter is not loaded DAF will not work.

If DAF DLL is not loaded:

• With IIS 2.0, 3.0:

The only known reason for this symptom is that the path and name of DAL35x.DLL is not correctly specified in the registry. With the registry editor, check the key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters]

where the path and name of the DLL should be specified, for example:

"c:\inetserv\Server\sspifilt.dll,c:\inetserv\filters\daf30x.dll"

DLLs must be separate with a comma, not with a semicolon.

• With IIS 4.0:

With Microsoft Management Console, check in the ISAPI configuration that DAF is loaded (green up arrow).

DAF3xx.DLL must be installed global filter (set for "WWW Service"). DAF will not work if installed as a site ISAPI filter.

• T7.2: Were all DAF database(s) found and loaded?

See: T3.1

• T7.3: Is one and only one DAF DLL loaded?
  
  In some cases, when DAF 4.0 was installed over an older DAF version, the previous DAF DLL is not removed, and two ISAPI filter are installed. With such a setting, DAF cannot work correctly and the older ISAPI DLL must be removed:
  
  - Launch  the Internet Service Manager
  - Select the server
  - In the menu "Action", choose "Properties"
  - In "Master Properties", select "WWW Service"
  - Press [Edit]
  - Select Tab "ISAPI Filters"
  - If present, Select and Remove the older DAF ISAPI DLL
  - Press [Ok] twice.
  

ODBC Related:

• T8.1: Is there a ODBC problem?

The best way to check if there is an ODBC problem, is to use the DAF Configuration Tool (CONFIG.EXE):

- in "ODBC Source" press "Test connection"
- in "IP Addresses & Tables & Fields" press "Try to read ODBC source." It should report all users found in the database.

If the previous test does not report any errors, you can:

- activate the log of every SQL command sent "ODBC Source/Log SQL Requests"
- with a browser, try to access protected files
- and look for error in the live log window

• T8.2: Is you your ODBC source a "System DSN?"

DAF will only work with "System DSN" ODBC sources. If your ODBC source is a "User DSN" DAF will not find it and will report the selected source does not exist.

(However, the DAF Configuration Tool will accept it.)

• T8.3: With an MS Access file as an ODBC data source, new users are not usable.

With an MS Access file as data source new users added with an ADO, ASP or OLEDB client are not usable (sometime only) by DAF until the database is reload (ODBC connection closed and reopened).

This is an ODBC problem which occurs ONLY with an MS Access source and when new users are added with an ADO, ASP or OLEDB tool.

This problem was never reported with any other database system.

In ASP scripts, a simple solution is to use the "AddUser" method of DAFTools (ASP component available from the download software page).

• T8.4: ODBC error while using the Web User Manager :
  [Microsoft][ODBC Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use ...
  
  The full error message is :

Error : [Microsoft][ODBC Microsoft Access 97 Driver] Couldn't use '(unknown)';  file already in use. / [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr  failed / [Microsoft][ODBC Driver Manager] Connection not open / [Microsoft][ODBC Driver Manager]   Connection not open

This error message is reported when :

- when the MS Access file cannot be accessed for NT permissions reasons

- or, when the ODBC source was defined with option "Exclusive" enabled. In that case, since the DAF filter keeps a open connection with the ODBC source the Web User manager cannot access the ODBC source.

Solution : Uncheck option "Exclusive" :

- open the "Control Panel"
- choose "ODBC32"
- select your ODBC source
- press "Configure ..."
- press "Options>>"
- uncheck "Exclusive" option