Sdscompany.ru

Компьютерный журнал
2 просмотров
Рейтинг статьи
1 звезда2 звезды3 звезды4 звезды5 звезд
Загрузка...

Olmapi32 dll outlook ошибка

Outlook 2013 — OLMAPI32.dll error after latest windows updates (11/13/2013)

Have approximately 20 clients with Office 2013 (pro and standard) that are all crashing with the same error after the latest round of windows updates have been installed. (Outlook will run for about 15-20 seconds before it stops responding and crashes.)

Faulting application name: OUTLOOK.EXE, version: 15.0.4551.1004, time stamp: 0x5253ad6f

Faulting module name: olmapi32.dll, version: 15.0.4551.1003, time stamp: 0x524a7a77

Exception code: 0xc0000005

Fault offset: 0x000138c5

Faulting process id: 0x1120

Faulting application start time: 0x01cee1658be85d3e

Faulting application path: C:Program Files (x86)Microsoft OfficeOffice15OUTLOOK.EXE

Faulting module path: C:Program Files (x86)Microsoft OfficeOffice15olmapi32.dll

Report Id: e5d0721e-4d58-11e3-aabe-b4b52fc8d811

I’ve tried all the OLMAPI32 fixes I’ve been able to find, but none work. The only solution has been to uninstall and reinstall, but after the updates get applied again the error comes back. Anyone have a fix that works?

Question Info

Replies (18) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same problem. All Outlook 2013 clients on our SBS 2011/Exchange network are having the same problems.

Recreating the profile seems to have fixed things.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same problem. Ours was an upgrade from 2007 to 2013.

Re-creating the Outlook profile works.

Hope Microsoft is listening.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Like others have said, the only solution that works is to either:

Читать еще:  Работа над ошибками онлайн по русскому

1. Not install the windows update
2. Delete and recreate the profile.

starting outlook in safe mode doesn’t help.

Not sure which KB is the ultimate cause: KB2768005 or KB2837643, but after its installed uninstalling it won’t fix the problem. Only solution I’ve found is reinstall of office (which once the office updates get applied will just recreate the problem), or system restore to before the update was applied (same thing.)

For my users that are affected I’m just leaving the updates apply and recreating their outlook profile. Luckily I’ve only got about 20 copies of Office 2013 so far.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Chalk another one up for us. It was only machines that were upgraded from Office 2003. All fresh Office 2013 installs were not affected. A couple users were able to have a new profile created to fix it. Then the third one failed with that solution.

We then had to uninstall and reinstall. That fixed all of them until the next client called.

The Uninstall/reinstall fix isn’t working for them. We are trying the KB uninstall to see if that works.

UPDATE: The two latest machines that had the problem don’t have the KB2837618 installed. But we recreated the profile on those and that worked for them. Weird how some solutions work for some and not others and vice versa. Keeps us on our toes that way.

Did this solve your problem?

Sorry this didn’t help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

Заметки Лёвика

web программирование, администрирование и всякая всячина, которая может оказаться полезной

Ошибка при запуске Outlook 2003: «Файл MAPI32.DLL поврежден или имеет неправильный номер версии»

Установка и удаление поочередно Microsoft Office 2007, затем Microsoft Office 2003 (в какой последовательности — уже неизвестно) привела к тому, что 2003 “Офис” перестал отправлять почту. Если точнее вообще перестала запускаться программа Microsoft Office Outlook 2003 — при запуске выдавалось сообщение
Файл MAPI32.DLL поврежден или имеет неправильный номер версии … и предположение, что была установлена посторонняя почтовая программа.

“Причиной получения сообщения об использовании неправильной версии mapi32.dll или о том, что этот файл поврежден, может быть другое программное обеспечение для передачи сообщений, установленное после Microsoft Outlook.” — действительно, была попытка установить другой Microsoft Outlook.

Попытки скопировать файл MAPI32.DLL (находится в каталоге WINDOWSSYSTEM32) с “рабочего” компьютера (с рабочим “офисом — аутлуком”) , переустановка Office 2003 (решили остановить свой выбор на нем), удаление старых файлов, скачивание Mapi32.dll — “нужной” версии из интернета… В общем, все было безуспешно.

Читать еще:  Bluestacks 4 ошибка

Утилита fixmapi.exe (находится в системной папке WINDOWSsystem32) тоже не дала нужного результата. Возможно, кому-то достаточно будет набрать в командной строке fixmapi — и “все будет”.

До причины все-таки удалось докопаться —

“неисправность может возникнуть при установке, а затем удалении Microsoft Office Outlook 2007 (бета-версия 2) на компьютере с установленным Outlook 2003. После удаления Outlook 2007(бета-версия 2) файл MSMapi32.dll из Outlook 2007 (бета-версия 2) не удаляется из следующей папки вашего компьютера:

C:Program FilesCommon FilesSystemMsmapiLocaleID

(у меня LocaleID был 1049)

После переименования файла MSMapi32.dll, Microsoft Office 2003 (Родной!) запустился… самовосстановился (пару раз запросил исходные файлы), и все-таки “встал”…

ps. получается, что странный какой-то Uninstall у 2007 офиса… Ну не.. кривизну рук тоже никто не отрицает.

UPD. При входе в Панель управления при попытке перейти в раздел “Почта” возникает сообщение об ошибке

Нехватка памяти или системных ресурсов. Закройте часть окон или программы и повторите попытку.

При этом запуск Outlook 2003 также выдавал сообщение про MAPI32.DLL, а запуск любых других программ происходил нормально. Помогло удаление (переименование) файла MSMapi32.dll (как в последнем пункте)

Опубликовано Пятница, Август 21, 2009 в 17:02 в следующих категориях: Без рубрики. Вы можете подписаться на комментарии к этому сообщению через RSS 2.0. Вы можете добавить комментарий, или trackback со своего сайта.

Автор будет признателен, если Вы поделитесь ссылкой на статью, которая Вам помогла:
BB-код (для вставки на форум)

html-код (для вставки в ЖЖ, WP, blogger и на страницы сайта)

ссылка (для отправки по почте)

Комментарии (10) к записи “Ошибка при запуске Outlook 2003: «Файл MAPI32.DLL поврежден или имеет неправильный номер версии»”

  1. Павел сообщает Декабрь 4th, 2009 в 09:47:

спасибо за дельный совет у меня тоже самое все заработало

Спасибо. офис восстановил. на mapi32.dll больше не ругается

Спасибо, Outlook заработал, однако при экспорте возникает ошибка: Сбой операции и все.
Может подскажите как решить?

Спасибо, Sergey
(присланное сообщение от Sergey ):

проблему решил координальной переустановкой всего офиса. перед инсталяцией предварительно удалил все из реестра, связанное с outlook
2007 outlook оказался весьма живучий

Ссылка на статью техподдержки майкрософта
последний пост автора оттуда

Отличный совет.
Мучился 3 месяца.

Спасибо, стояли 2007 и 2003 офис на комьпютере, и аутлук 2003 не запускался с ошибкой, а в 2007 аутлук был недоступен помогла фикс мапи

Спасибо все заработало.

Спасибо, тоже с этим MAPI32.DLL промучался, ввел fixmapi и все стало работать, ошибка исчезла.

Resolving “OLMAPI32.dll is incompatible” Error When Upgrading from Outlook 2007 to Outlook 2010

You cannot/should not, it appears, retain Outlook 2007 installed on your PC after upgrading to Outlook 2010.

If, as I did, you do not de-install Outlook 2007 after the upgrade you may find that you cannot run Outlook 2010. In such case you may get the following error message when attempting to run it:

“The file OLMAPI32.dll is incompatible with Microsoft Outlook. Install Outlook again”

It may be possible that had I uninstalled Outlook 2007 or had I never attempted to run Outlook 2007 after upgrading to Outlook 2010, this error may never have appeared. Nonetheless, once this error appeared I was not able to run Outlook 2010 again until I uninstalled Outlook 2007 as described below.

Читать еще:  Почему выдает ошибку

Note: As always, before proceeding, I recommend creating a restore point in case something goes wrong.

According to this Microsoft Answers post, the solution did not lie in ”Installing Outlook again’ as the error message suggested. Rather, the solution required uninstalling Outlook 2007 and repairing Outlook 2010.

So, off to Add-Remove Programs from the Control Panel to Remove Outlook 2007 right? Not so easy.

You can’t directly uninstall any given Office 2007 application installed on your computer. They do not appear as individually installed items in the Add-remove programs panel. As described in this Microsoft knowledge base article (unfortunately written for XP and Vista users), in order to remove just one application from the Office suite in Windows 7, you need to ‘Change’ the features/applications installed in the Office 2007 suite.

To do this is Windows 7 you need to:

  • Go to Control Panel
  • Select “Uninstall a program” under the “Programs” heading
  • As depicted below, right click on the “Microsoft Office Standard 2007 item in the resulting “Uninstall or change a program” window and select the ‘Change’ option:

From there you’ll get the option to ‘Add or Remove’ Features’:

Click the radio button beside ‘Add or Remove Features” then click Continue.

As depicted below, X out the “Microsoft Office Outlook” application by clicking on the down arrow and selecting the ‘Not Available” option. Once X ’d out, click on the Continue button:

From there you’ll see this Configuration Process screen:

Followed by this success screen:

After which, Outlook 2007 will be removed from your PC.

Now run your previously installed Outlook 2010 and, if all has gone according to plan, you’ll see this Office 2010 repair screen instead of the OLMAPI32.dll error message:

When done the following warning screen came up:

Since I hadn’t seen this error message multiple times I selected ‘No”

From then on, My Outlook 2010 has run just fine.

May 29, 2009 Update: Well, things didn’t run so fine after that. I had the problem where Outlook 2010 couldn’t reliably connect to the Google Apps Gmail iMap server. So I went and ‘repaired’ my Office 2010 installation as follows:

  • Proceed again to the “Uninstall or change a program” window (see first image above)
  • Right click on “Microsoft Office 2010” in the list
  • Select “Change” (as you can see that I did in the picture above for Office 2007)
  • Select the ‘Repair” option as pictured below then press “Continue”

This will be followed by a ‘Configuration Process” notification screen.

When done, Office 2010 should be repaired.

So far, Outlook 2010 seems to be running without the errors I had before. I’ll update this post if more problems crop up. If there are no more edits, you can assume things are working fine again. Well, subject to known Outlook 2010 / iMap glitches that is.

Ссылка на основную публикацию
ВсеИнструменты 220 Вольт
Adblock
detector
×
×