(Re)Installation or Upgrade Troubleshooting

DAF version 4.2 can be (Re)Installed or Upgraded in the same directory or a different directory. Since configuration  information is stored in the registry the choice of the destination directory for the new installation does not make a difference.

Known problems which can prevent a correct execution of the setup program are:

• Web Services cannot be Stopped
• If installing in the same directory, locked files cannot be replaced
• The old DAF filter is not removed from IIS Global ISAPI filter list

Web Services cannot be Stopped

There are many possible causes for this symptom, most of them not related to DAF. For example, it could be a component loaded by IIS (e.g., a COM component used in ASP script) which behaves strangely and corrupts internal data. Another common reason is an HTTP request which never end for some reason.

Regarding DAF, this problem may occur if a broken ODBC connection is trying to reconnect while IIS is stopping.

Restarting the World Wide Web Publishing Service is required:

• for IIS to unload a DAF filter currently running. In other words, to unlock file DAF40xx.DLL if currently running
• to load the new DAF filter after installed as a global ISAPI filter.

Restarting the IIS Admin Service is required:

• for IIS to unload DAF ASP Component. These components are not loaded by IIS by default. They are loaded ONLY if a web client loaded a script using these components. This is the case with the Web User Manger, or if the option HTML login form is enabled. In others words, to unlock files DAFTOOLS.DLL and ASPCRYPT.DLL.

If installing in the same directory, locked files connot be replaced

If some files are locked new files with a similar names will not be copied. Main cause for this symptom is that Web Services could not be stopped (see section "Web Services cannot be Stopped") or that DAF applications (DAF Configuration Tool, DAF Manager...) are currently running.

If the installation process fails because files cannot be copied, it is recommended to:

• Close all running DAF applications
• Manually stop IIS Admin Service
• restart the setup program
• restart IIS Admin Service and all dependent services

The old DAF filter is not removed from IIS Global ISAPI filter list

It some very rare cases, the setup program will not detect that a DAF filter is already installed as an ISAPI filter. When this happens, the new DAF filter is installed and the old one remains present. The result is that DAF does not function correctly. To solve this problem the old filter must be manually removed:

• Open the MMC with the Internet Information Server
• Select the physical server
• Choose properties
• Select WWW Service as the Master properties 
• Press [Edit]
• Choose Tab ISAPI Filters
• Select the old DLL in the list of installed ISAPI filters
• Press [Remove]