Unexpected termination when running a report

Article ID: 0412101708329 - Last Review: 18 May 2006 by jasonl - Revision: 1 - Views: 3891

When you run a report, Service Accent can terminate unexpectedly; no error message is displayed. However, when checking the Application Event log on the computer, an event similar to the following is found:

The application, "C:\Program Files\Service Accent", generated an application error. The error occurred on 12/06/2004 @ 09:23:59.696
The exception generated was c0000005 at address 67D05125

In the event text, if you see the text W3MIF or similar, the fault is in the Pervasive.SQL components.

You can download updates for the Pervasive.SQL components from [a href="http://www.pervasive.com/support/updates/?product=psql" target=_blank]www.pervasive.com[/a] or contact your support representative who will be able to advise you further.

For Pervasive.SQL 2000i
Download Pervasive.SQL 2000i Client Requesters for your client workstation if you run Pervasive.SQL Server. Download Pervasive.SQL 2000i Workgroup & NT/2000 Server for your workstations or server if your run any other edition of Pervasive.SQL.

For Pervasive.SQL V8
Download Pervasive.SQL V8 Service Pack 2 for your server and workstations.

 Related articles

Attempting to run a report returns status 525
Can not find database dll error 532 message when running a report
How to save your reports after applying an update
How to update your own reports to the latest version of Service Accent
Message 'Could not start the Crystal Reports engine'
Reports run very slowly under Windows Vista with Pervasive.SQL V9
Running a report returns error 507 or 709
Running a report terminates Service Accent unexpectedly

 Additional articles from the white papers

Service Accent - Report reference
Service Accent - Adding client reports

For additional resources and information, you can go to the Service Accent Support Centre

Click here to go to the Service Accent Support Centre

Copyright © 2003-2023 Vantage Computing Ltd. All rights reserved. The information contained on this web site is correct as of its publication date.