Link to home
Create AccountLog in
Avatar of Garry Shape
Garry ShapeFlag for United States of America

asked on

Outlook 2010 - Sending flagged-for-follow-up e-mail returns Operation Failed error

On an Exchange account in the Outlook 2010 client, when a flagged for follow-up (either tomorrow, custom, whichever) e-mail is sent, this error is thrown:

User generated image
It doesn't seem to happen to anyone else.

The only way I have found to resolve this is to create a duplicate email and send it, usually after closing and restarting Outlook.  
ASKER CERTIFIED SOLUTION
Avatar of Kamalasekar Parthasarathy
Kamalasekar Parthasarathy
Flag of India image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of Garry Shape

ASKER

I did reset the profile in question (roaming profile in a Citrix environment).

I checked the event log on the server at the time this error came up and here are the details:

Faulting application OUTLOOK.EXE, version 14.0.5130.5000, time stamp 0x4ce5a4ad, faulting module OLEAUT32.dll, version 6.0.6002.18357, time stamp 0x4d0f85d3, exception code 0xc0000005, fault offset 0x00004722, process id 0x3eb0, application start time 0x01cc9a35bd5aead7.

Faulting application OUTLOOK.EXE, version 14.0.5130.5000, time stamp 0x4ce5a4ad, faulting module OLEAUT32.dll, version 6.0.6002.18357, time stamp 0x4d0f85d3, exception code 0xc0000005, fault offset 0x00004722, process id 0x%9, application start time 0x%10.

Faulting application OUTLOOK.EXE, version 14.0.5130.5000, time stamp 0x4ce5a4ad, faulting module OLEAUT32.dll, version 6.0.6002.18357, time stamp 0x4d0f85d3, exception code 0xc0000005, fault offset 0x00004722, process id 0x3eb0, application start time 0x01cc9a35bd5aead7.


oleaut32.dll C:\Windows\System32\oleaut32.dll
System Process


Windows Process Description:

The DLL oleaut32.dll is described as Object Linking and Embedding Automation on 32-bit platform. The OLE Automation is a formal inter-process communication mechanism based on Component Object Model (COM).

The oleaut32.dll module contains core OLE Automation functions and provides an infrastructure whereby applications can access and manipulate shared automation objects that are exported by other applications. Microsoft has a continuing effort to come out with more versatile OLE-related technologies. OLE has been in development for several years, and almost every new technology authored by Microsoft somehow incorporates elements of OLE.

Microsoft developed OLE Automation to find solutions to practical problems experienced in operating systems and applications. The automation of the file oleaut32.dll provides the necessary specifications and the key services to component software, which is ultimately a significant gain for the entire computing industry.

The developer must know the object model that is employed by an application for which the automation is intended. Development of automation controllers without knowledge of the target application's object model is practically impossible. Because of these difficulties, automation components are usually provided with type libraries such as the oleaut32.dll module which contains the metadata, mostly about classes, interfaces and other features, needed by the application.

Significantly, DLL oleaut32.dll links are tapped to generate Proxy pattern or stub code for interoperation between OLE and other platforms. OLE Automation is featured in the next version of Microsoft Scheduler+. This program to add sophisticated scheduling functions to the user's custom applications links the oleaut32.dll file.

The file oleaut32.dll and the OLE Automation are existing components of Microsoft Visual C++, Microsoft Visual Basic, Microsoft Access, Microsoft Excel, and Microsoft Project.

Author: Microsoft Corporation

Author URL: http://www.microsoft.com

Part Of: Microsoft OLE Automation

Memory Usage: Medium

Associated Applications: Microsoft Visual C++, Microsoft Visual Basic, Microsoft Access, Microsoft Excel, Microsoft Project, olepro32.dll, stdole2.dll

Background DLL: No

Uses Network: No

Hardware Related: No

Common Path: C:\ Windows\ system32\ oleaut32.dll

DLL Version: 5.1.2600.2180

I've deleted the "Outlook" folder in "C:\Users\UserName\AppData\Roaming\Microsoft\" and opened Outlook so far it's running better.
I think the first step here worked, but I should note, it wasn't a new Outlook Profile specifically, but a new Windows profile would correct it since the new folder "Outlook" in C:\Users\UserName\AppData\Roaming\Microsoft\ had to be re-created.