Discussion Locked

Error R6025 - pure virtual function call

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When launching MS Outlook 2000, user receives an error titled "Microsoft Visual C++ Runtime Library." The message is "Runtime Error! Program ...\outlook.exe. R6025 - pure virtual function call."

Outlook starts to load and the messages are visible, then this error appears. Clicking the OK button closes outlook. I have tried starting Outlook with several command line parameter(CLP) to reset the folders and turn off preview and run it in "safe" mode.

I have uninstalled Norton Antivirus (heard it could cause this problem).

I have uninstalled and reinstalled office even with the CLP "/famu" to force all files and registry rewrites.

MS web site says the error is a code error and the code needs to be rewritten.

OS is W2K. Outlook is connecting to a GroupWise 5.5 back end and it used to work.

9 replies

by maxwell edison

C Run-Time Error R6025
pure virtual function call
No object has been instantiated to handle the pure virtual function call. This error is caused by calling a virtual function in an abstract base class through a pointer that is created by a cast tothe type of the derived class, but is actually a pointer to the base class. This can occur when casting from a void* to a pointer to a class when the void* was created during the construction of the base class.

----------

SYMPTOMS:
The C++ program fails, and reports the following run-time error:

runtime error R6025
- pure virtual function call

CAUSE:
This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time.

The error occurs when you indirectly calla pure virtual function within the context of a call to the constructor or destructor of an abstract base class. This is illustrated in the sample code below, along with some more description.

RESOLUTION:
Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.

One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls theWindows API function DebugBreak(). When using the debugger, DebugBreak() will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called.

Source:

Cause of theR6025 Run-Time Error (Q125749)

http://support.microsoft.com/default.aspx?scid=KB;EN-US;q125749

(REMOVE SPACES from the pasted URL.)

Maxwell

by maxwell edison

.
.
Another possibility:

If you get an illegal operation when you start meetingmaker under Windows 98 or a 'Runtime Error' from the 'Microsoft Visual C++ Runtime Library, R6025' - pure virtual function call is received. There is probably a conflict between a meetingmaker driver and Windows 98. Changing the extension of the proper driver will often correct the problem.

Go to the meetingmaker program folder

(usually 'C:\MM\' for version 4.x or C:\Program Files\Meeting Maker for later versions) and locate the .drv files. If none of your files has an extension (a period followed by three characters), you will need to:

Select 'Options...' from the 'View' pull down menu of the window.

Select the 'View' tab.

Remove the check mark from the 'Hide file extensions for known file types' check box.

Click the 'OK' button.

You can change the file extension on select files (look below to see which files can safely be renamed and which files should not be renamed) tostop the drivers from loading.

To rename a file:

Right click on the file.

Select 'Rename' from the menu that appears.

Change the '.drv' extension to '.drx'.

Push the 'Enter' key.

The following files can safely be renamed:DDP32.DRV -- Windows compatible meetingmaker Client AppleTalk Driver

IPX32NT.DRV -- Windows NT IPX Driver

IPXw95.DRV -- Windows 95 or 98 IPX Driver

IPXNWL.DRV -- Netware NW-Link IPX Driver

TCPOS32.DRV -- TCP/IP Winsock Driver("TCP" driver, version 5.5x only)

DO NOT rename the following file:

IPSW32.DRV -- UDP/IP Winsock Driver (the 'IP' driver)

Maxwell

by cray

Since I don't have access to outlook source code, answer number 1 doesn't help. Also, I don't have meetingmaker so the additional comments don't help either. - Thanks for the effort.

by dcosgrove

This is not a familiar error to me, but there are several known errors in outlook which are similar. It is poosibly caused by an aborted or incomplete install or upgrade of outlook express. This can occur if Internet explorer was updated recently. Sometimes it is repairable by doing a reinstall or update of IE and including outlook express. May not specifically pertain to your situation, but it is what I would try first.

by cray

I had hope for this one. I had just recently upgraded to IE 6. Not sure if that was related or not. However, going back to 5.5 and reinstalling outlook express didn't help. Thanks.

This discussion is closed to new replies.