This article describes how to attempt to resolve a specific error in the Microsoft Windows Application log on a Neverfail for SQL Server.
If the following error is present in the Microsoft Windows Application log, the procedure below may resolve the problem.
Event Type: Error Event
Source: Application Error Event
Event ID: 1000
Description: Faulting application discoverFilterSQLServer2000.exe, version 0.0.0.0, faulting module discoverFilterSQLServer2000.exe, version 0.0.0.0, fault address 0x00005da1.
In order to start troubleshooting this issue it is necessary to first create a backup list of the systems current Neverfail for SQL Server file filters.
1. From a command line type %installdir%\Neverfail\R2\bin discoverFilterSQLServer2000 myfilters.txt.
This will create the file myfilters.txt and within this file there should now be a complete set of current Neverfail Heartbeat SQL server file filters. This should be kept as a backup copy of the file filters currently in place on your system.
At installation time Neverfail Heartbeat will use the credentials of the current user to connect to the database/s, and if it succeeds, it will write these to a file with the extension .dsn to %installdir%\Neverfail\R2\bin.
These file filters will then be written to a file called SQLServer2000.nfd in %installdir%\Neverfail\R2\bin
The following step details how to force Neverfail for SQL Server into rediscovering the correct file filters for replication automatically.
2. Delete the current SQLServer2000.nfd file and the *.dsn file both located in %installdir%\Neverfail\R2\Bin. By deleting this file we force the "discoverFilter2000.exe" to recreate the files mentioned previousy the next time it runs. If these files are not re-created please contact Neverfail Support.
If the Filter Discovery process cannot connect to SQL Server the ODBC driver software will display a dialog box where the user can fill in connection information. For example: SQL Server Username and Password. This will then be written to the DSN file.
If the errors persist in the Microsoft Windows Application log please contact Neverfail Support.