Overview

This article describes the error and its resolution, which occurs when starting Microsoft Outlook, and it crashes showing the following error:

Microsoft Visual C++ Runtime Library
Runtime Error! 
R6025 - pure virtual function call 

The Outlook Connector debug log logfirebirdbackend.csv lists a similar error as below:

2013-03-25,15:15:27,185,1,"#0000176c","#0000156c","error ","logfirebirdbackend","MessagesBatchOperationsHelper::InsertMessageHeaders firebird API call failed, error description *** IBPP::SQLException *** 
Context: Statement::Execute( INSERT INTO MESSAGES(MARID, PARENTID, DATABASEID, SUBJECT, CREATIONTIME, RECEIVEDDATE, SENTDATE, "Size", PRIORITY, "To", "From", HASATTACHEMENTS, CONVERSATION_TOPIC, CONVERSATION_INDEX) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ) 
Message: isc_dsql_execute2 failed 

SQL Message : -902 
Unsuccessful execution caused by a system error that precludes successful execution of subsequent statements 

Engine Code : 335544335 
Engine Message : 
database file appears corrupt (C:\Users\Username\AppData\Local\GFI\ARCHIVER\974130DA11567784-4B0C7A941F8B747C.FDB) 
wrong page type 
page 9010 is of wrong type (expected 7, found 5) 
internal gds software consistency check (error during savepoint backout (290), file: exe.cpp line: 4034) 

Environment

• GFI Archiver
• Outlook Connector

Root Cause

The Outlook Connector's cache database is corrupt.

Resolution

1. Ensure that Microsoft Outlook is closed (outlook.exe is not running).
2. Open the Outlook Connector's profile folder. For example, C:\Users\Username\AppData\Local\GFI\Archiver
3. Delete the FDB file(s) in this folder (they contain the synchronized/cached emails and their header data).
4. Start Microsoft Outlook.
5. The FDB file will be recreated, and header data and emails will be re-synchronized from the server.