This article was previously published under Q319704
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 102195 (SQLBUG_70)
The Index Tuning Wizard may return an application error if the workload contains a query that performs an inner join between a table and a full-text search function. The following message is displayed in the Application Error dialog box:
Title: wiztrace.exe - Application ErrorText: The instruction at "0x41745b63" referenced memory at "0x00000000". The memory could not be "read". Click on OK to terminate the application Click on CANCEL to debug the application
The application error in the Index Tuning Wizard occurs because of an Access Violation in Wiztrace.exe. The application error occurs when Wiztrace.exe tries to reference a memory location that cannot be read. Wiztrace.exe is the executable file for the Index Tuning Wizard.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
This problem does not occur if you run the Index Tuning Wizard from a computer that is running SQL Server 2000 Client Tools. Therefore, to work around this behavior, run the Index Tuning Wizard from a workstation that is running SQL Server 2000 Client Tools, and then connect to the computer that is running SQL Server 7.0.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.
If Dr. Watson is configured to be your default application debugger, you may not see the error and the Index Tuning Wizard closes. However, the error is reported to the Application Event Log with the following Dr. Watson Informational event:
EventID: 4097Source: DrWatsonCategory: NoneText: The application, , generated an application error The error occurred on 'date' @ 'time' The exception generated was c0000005 at address 41745B63 (<nosymbols>)