Start a Conversation

Unsolved

This post is more than 5 years old

1406

June 10th, 2008 11:00

exSearch - Error processing message 1 of 1. Reason: -2147221223

I am encountering this error when trying to do an exSearch from Outlook, both 2003 and 2007. This is only happening on a few workstations, not all. Anyone know what this means?

2 Intern

 • 

600 Posts

June 11th, 2008 22:00

Are you seeing this error message while opening a messages using search plug-in or when you are trying to open a shortcut messages ?

Yo umentioned ExSearch but i did not want to make any guess., ExSearch has com add-in for shortcut retrieval too so that would stand in both situations.

If its to do with shortcut retrieval try clearing the froms you might have downloaded to user Application Data\Microsoft\Form library.

.. if it happening while opening messages from search plug-in then try to open the same message on another machine, especially from EX server, who knows its a bad message

Thanks,
Raj

80 Posts

June 12th, 2008 10:00

This error occurs when trying to run a open an email from the list when doing a query with the Outlook search plug-in. I am able to run the same query and open the email from other workstations including the EX server. The options listed when the error occurs is to Abort, Ignore, or Retry. In any case, the message never opens.

Thanks.

80 Posts

June 12th, 2008 18:00

This is normal user search...not directed search. It is weird because it is happening on my laptop and on a client's PC, but I haven't heard of it anywhere else (well, at least I haven't seen any posts in here about this).

Thanks, I'll most likely try support.

2 Intern

 • 

600 Posts

June 12th, 2008 18:00

Hi,

Are you running normal "User" search or "Directed Search" for folder ? I have seen somehting like this in directed search when UDA was not configured and someone was running directed search after adding particular user as the owner of a folder in EX.

If its nothing what we have discussed then a good idea could be to speak to support.

Thanks,
Raj

1 Message

June 25th, 2008 12:00

I had this on a couple of client last week.

They were both running Exchange Service Manager (ESM) on their desktops.

We ran fixmapi.exe (in the system32 directory).

This fixed one of the systems but not the other. On the system it did not work on the user uninstalled ESM and everything started working.

We did notice that the MAPI32.dll that was created on the second system was dated 2004 where the system it fixed was dated 2003.

The user was going to try copying the 2003 MAPI over to see if it worked with ESM. He is going to let me know if it worked but I haven't heard from them yet.

2 Intern

 • 

204 Posts

June 30th, 2008 00:00

Hi Kauanoe,

what die support say? Did you find out your specific problem?

Thanks for sharing it with us.

Regards,
Jochen.

80 Posts

June 30th, 2008 13:00

I am still trying to use the fixmapi solution that was provided in this thread. The problem is that my laptop now doesn't show any signs of this error...weird.

80 Posts

June 30th, 2008 14:00

I just tried running the EX search plugin, and I am again getting this error. I ran the fixmapi utility, and it didn't seem to fix it. I just don't know what else it maybe.

80 Posts

July 23rd, 2008 16:00

UPDATE:

I was getting ready for an EmailXtender demo, and had a client vmware machine available to do search for emails. It was a new vmware that was installed with Microsoft 2007. I launched Outlook 2007 and set the EX server settings, did a quick search, and got a hit list. I then tried to view the message, and wouldn't you know that the same error was happening. After several attempts, it continued. I then proceeded to the next steps, and viewing the messages worked:

1. Log on as a different user (Administrator)
2. Goto: C:\Documents and Settings\
3. Delete the folder
4. Log on as the user once more
5. Open Microsoft Word 2007 (going through whatever pop ups until Word was available for use)
6. Closed Microsoft Word 2007
7. Open Outlook 2007 and set exchange settings
8. Launch EX Search Plugin and set EX server settings

I don't know why, but this cured it. I hope this can help anyone else out there that may have been struggling with this issue.

36 Posts

July 24th, 2008 05:00

Interesting.
Are you saying: "....use WORD 2007 first before you use Outlook 2007..." ?

Thanks.

80 Posts

July 24th, 2008 10:00

What I meant is that perhaps in the opening of Outlook 2007 upon the very first login for the user to that workstation something may have happened that caused the error to occur. And just so happens that the method that solved it seemed to have been to open another Microsoft Office 2007 product upon first login (you are prompted to enter username and initial). Perhaps the real method to solve it was to remove the profile and then recreate it.

2 Intern

 • 

204 Posts

July 24th, 2008 10:00

Hi there,

but clearly, when deleting "C:\Documents and Settings\ " you not only created a new windows user profile, but also a new mail profile on that PC.

It would be interesting, if recreating a new mail profile would be enough (since there a lot of user settings stored in a windows user profile). - I somehow doubt that opening another application e.g. Word first, really makes a difference when a new user profile (windows and mail) is being created.

Kind regards,
Jochen.

80 Posts

July 24th, 2008 10:00

Yes...that clearly worked. Perhaps creating the new mail profile might work...I didn't try that at all. I just wanted to post my findings because it was very frustrating that this issue was happening in the first place.

April 22nd, 2009 13:00

I had been working with support on this, using Outlook 2007 against email extender 4.8.x. This has to do with Extender using the wrong mapi dll file. Uninstalling/Reinstalling plugins & such had no benefit. Creating a new mail profile had no benefit. Deleting forms cache had no benefit.
They were saying that I'd have to uninstall Exchange 2007 management programs from my local system and then re-install in a different order, but that would involve additional time that I don't currently have. You'd think they could compile the program to work with latest mapi dll's.

5 Posts

April 23rd, 2009 09:00

Try running fixmapi.exe in \windows\system32

I had similiar problems and this fixed it by simply running fixmapi.exe.

This was on admin workstations that had ESM installed and a few that had some sort of digital signing plugin.
No Events found!

Top