Problem:

When you run WinSpool/400 Web Report Server on a Windows NT PC with IIS 4.0 (Microsoft Internet Information Server) and the report files and settings database files WSPBCH32.MDB or WSPINDEX.MDB are on network drives instead of the C: drive, you get the error:
 
Server Settings Database File WSPBCH32.MDB or WSPINDEX.MDB was not found
 

Solution:

In IIS Administrator, for Default Web Site, go to Anonymous Access and Authentication Control and edit the authentication information for anonymous access to the web server:
  1. Enable Allow anonymous access.
  2. Type a valid NT Domain User name and Password for the anonymous access. Usually you will use the IUSR_[Machine Name] user. The anonymous user name must be registered as a DOMAIN USER in Windows NT so the user can access files on other servers, if authorized.

    Note: If the reports will be stored on a file server with secured directories, the user must also have Windows NT permission to access the data directory.

  3. Disable Enable Automatic Password Synchronization.

    Note: This setting can cause problems when the web server and CGI process are running on a Windows NT web server PC, and the report files or MDB files are on another Windows NT PC or server. This problem can also occur when the report files or MDB files are on the local drive, so you will need to test after changing this setting.

  4. Disable Basic Authentication and Windows NT Challenge/Response.
Note: Alternatively, you can force user authentication, although RJS Software recommends using the settings above instead. When you access WinSpool/400 Web Report Server, IIS asks for a user name and password before passing control to the WinSpool/400 Web Report Server CGI program.
 
This option is only recommended when WinSpool/400 Web Report Server is running on an intranet, because the user ID and password are sent in plain text over the internet connection. However, WinSpool/400 Web Report Server does its own user name and password encryption before sending data over the web, so the risk of password exposure is minimized.
  1. Disable Windows NT Challenge/Response and Allow anonymous access.
  2. Enable Basic Authentication.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: December 10, 2016