Outlook 2016 Email not Indexing (The protocol handler Mapi16 cannot be loaded)
up vote
3
down vote
favorite
There are epic threads on the internet of users upgrading to Office 2016 and finding that Outlook 2016 email is no longer indexing. Windows Search logs the following error in Event Viewer:
The protocol handler Mapi16 cannot be loaded. Error description: (HRESULT : 0x80004005).
I've tried ALL the common suspects:
- Rebuild Index
- Reinstall Office
- Remove and Re-add Outlook from Index Sources
- Remove and Re-add Outlook Profile
- We're already running Office 2016 x32
Removing Outlook from the index and using Unindexed search is acceptable as a very short term fix, but I need the "The protocol handler Mapi16 cannot be loaded." error fixed permanently.
At present this is happening on approx 50% of the workstations we upgrade to Office 2016 (Click-to-Run) and they're all running Win10 with all patches.
windows-10 microsoft-outlook microsoft-office windows-search microsoft-outlook-2016
add a comment |
up vote
3
down vote
favorite
There are epic threads on the internet of users upgrading to Office 2016 and finding that Outlook 2016 email is no longer indexing. Windows Search logs the following error in Event Viewer:
The protocol handler Mapi16 cannot be loaded. Error description: (HRESULT : 0x80004005).
I've tried ALL the common suspects:
- Rebuild Index
- Reinstall Office
- Remove and Re-add Outlook from Index Sources
- Remove and Re-add Outlook Profile
- We're already running Office 2016 x32
Removing Outlook from the index and using Unindexed search is acceptable as a very short term fix, but I need the "The protocol handler Mapi16 cannot be loaded." error fixed permanently.
At present this is happening on approx 50% of the workstations we upgrade to Office 2016 (Click-to-Run) and they're all running Win10 with all patches.
windows-10 microsoft-outlook microsoft-office windows-search microsoft-outlook-2016
Possible answer here answers.microsoft.com/en-us/office/forum/office_2016-outlook/… "1. right click windows icon on the lower left 2.click "command prompt administrator" 3.type sfc /scannow then press enter 4.after the sfc type dism.exe /online /cleanup-image /restorehealth 5. Restart computer and test."
– DavidPostill♦
Feb 23 '16 at 12:02
From the same link another possible answer" In Outlook 2016 Open File - Open Options - Open Search. Select "Indexing Options". Select "Advanced". Select "File Types". Scroll down to "pst" and highlight it by left clicking on it. Using the radio buttons change "how should this file be indexed" to "Index Properties and File Contents". Repeat for "ost". Filter descriptions should now read "Plain Text Filter". OK and Close out back to Outlook and after a while search should start to return proper results."
– DavidPostill♦
Feb 23 '16 at 12:04
@DavidPostill There's nothing wrong with Windows, these computers have just been reimaged from scratch and search works on identical computers. Also, Indexing is not set to index PST files as text on the computers that search works on. I'd really rather fix the MAPI16 cannot be loaded error rather than a hacky fix.
– Dom
Feb 24 '16 at 3:41
@DavidPostill That smacks of the standard Microsoft forums approach to everything which is running SFC and if that doesn't work, reinstalling.
– Alan B
Aug 3 '17 at 11:10
@AlanB {shrug} It's also true that the repair approach fixes many obscure Windows problems
– DavidPostill♦
Aug 3 '17 at 12:19
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
There are epic threads on the internet of users upgrading to Office 2016 and finding that Outlook 2016 email is no longer indexing. Windows Search logs the following error in Event Viewer:
The protocol handler Mapi16 cannot be loaded. Error description: (HRESULT : 0x80004005).
I've tried ALL the common suspects:
- Rebuild Index
- Reinstall Office
- Remove and Re-add Outlook from Index Sources
- Remove and Re-add Outlook Profile
- We're already running Office 2016 x32
Removing Outlook from the index and using Unindexed search is acceptable as a very short term fix, but I need the "The protocol handler Mapi16 cannot be loaded." error fixed permanently.
At present this is happening on approx 50% of the workstations we upgrade to Office 2016 (Click-to-Run) and they're all running Win10 with all patches.
windows-10 microsoft-outlook microsoft-office windows-search microsoft-outlook-2016
There are epic threads on the internet of users upgrading to Office 2016 and finding that Outlook 2016 email is no longer indexing. Windows Search logs the following error in Event Viewer:
The protocol handler Mapi16 cannot be loaded. Error description: (HRESULT : 0x80004005).
I've tried ALL the common suspects:
- Rebuild Index
- Reinstall Office
- Remove and Re-add Outlook from Index Sources
- Remove and Re-add Outlook Profile
- We're already running Office 2016 x32
Removing Outlook from the index and using Unindexed search is acceptable as a very short term fix, but I need the "The protocol handler Mapi16 cannot be loaded." error fixed permanently.
At present this is happening on approx 50% of the workstations we upgrade to Office 2016 (Click-to-Run) and they're all running Win10 with all patches.
windows-10 microsoft-outlook microsoft-office windows-search microsoft-outlook-2016
windows-10 microsoft-outlook microsoft-office windows-search microsoft-outlook-2016
edited Nov 1 '16 at 6:43
MJH
1,02441017
1,02441017
asked Feb 23 '16 at 6:49
Dom
2974513
2974513
Possible answer here answers.microsoft.com/en-us/office/forum/office_2016-outlook/… "1. right click windows icon on the lower left 2.click "command prompt administrator" 3.type sfc /scannow then press enter 4.after the sfc type dism.exe /online /cleanup-image /restorehealth 5. Restart computer and test."
– DavidPostill♦
Feb 23 '16 at 12:02
From the same link another possible answer" In Outlook 2016 Open File - Open Options - Open Search. Select "Indexing Options". Select "Advanced". Select "File Types". Scroll down to "pst" and highlight it by left clicking on it. Using the radio buttons change "how should this file be indexed" to "Index Properties and File Contents". Repeat for "ost". Filter descriptions should now read "Plain Text Filter". OK and Close out back to Outlook and after a while search should start to return proper results."
– DavidPostill♦
Feb 23 '16 at 12:04
@DavidPostill There's nothing wrong with Windows, these computers have just been reimaged from scratch and search works on identical computers. Also, Indexing is not set to index PST files as text on the computers that search works on. I'd really rather fix the MAPI16 cannot be loaded error rather than a hacky fix.
– Dom
Feb 24 '16 at 3:41
@DavidPostill That smacks of the standard Microsoft forums approach to everything which is running SFC and if that doesn't work, reinstalling.
– Alan B
Aug 3 '17 at 11:10
@AlanB {shrug} It's also true that the repair approach fixes many obscure Windows problems
– DavidPostill♦
Aug 3 '17 at 12:19
add a comment |
Possible answer here answers.microsoft.com/en-us/office/forum/office_2016-outlook/… "1. right click windows icon on the lower left 2.click "command prompt administrator" 3.type sfc /scannow then press enter 4.after the sfc type dism.exe /online /cleanup-image /restorehealth 5. Restart computer and test."
– DavidPostill♦
Feb 23 '16 at 12:02
From the same link another possible answer" In Outlook 2016 Open File - Open Options - Open Search. Select "Indexing Options". Select "Advanced". Select "File Types". Scroll down to "pst" and highlight it by left clicking on it. Using the radio buttons change "how should this file be indexed" to "Index Properties and File Contents". Repeat for "ost". Filter descriptions should now read "Plain Text Filter". OK and Close out back to Outlook and after a while search should start to return proper results."
– DavidPostill♦
Feb 23 '16 at 12:04
@DavidPostill There's nothing wrong with Windows, these computers have just been reimaged from scratch and search works on identical computers. Also, Indexing is not set to index PST files as text on the computers that search works on. I'd really rather fix the MAPI16 cannot be loaded error rather than a hacky fix.
– Dom
Feb 24 '16 at 3:41
@DavidPostill That smacks of the standard Microsoft forums approach to everything which is running SFC and if that doesn't work, reinstalling.
– Alan B
Aug 3 '17 at 11:10
@AlanB {shrug} It's also true that the repair approach fixes many obscure Windows problems
– DavidPostill♦
Aug 3 '17 at 12:19
Possible answer here answers.microsoft.com/en-us/office/forum/office_2016-outlook/… "1. right click windows icon on the lower left 2.click "command prompt administrator" 3.type sfc /scannow then press enter 4.after the sfc type dism.exe /online /cleanup-image /restorehealth 5. Restart computer and test."
– DavidPostill♦
Feb 23 '16 at 12:02
Possible answer here answers.microsoft.com/en-us/office/forum/office_2016-outlook/… "1. right click windows icon on the lower left 2.click "command prompt administrator" 3.type sfc /scannow then press enter 4.after the sfc type dism.exe /online /cleanup-image /restorehealth 5. Restart computer and test."
– DavidPostill♦
Feb 23 '16 at 12:02
From the same link another possible answer" In Outlook 2016 Open File - Open Options - Open Search. Select "Indexing Options". Select "Advanced". Select "File Types". Scroll down to "pst" and highlight it by left clicking on it. Using the radio buttons change "how should this file be indexed" to "Index Properties and File Contents". Repeat for "ost". Filter descriptions should now read "Plain Text Filter". OK and Close out back to Outlook and after a while search should start to return proper results."
– DavidPostill♦
Feb 23 '16 at 12:04
From the same link another possible answer" In Outlook 2016 Open File - Open Options - Open Search. Select "Indexing Options". Select "Advanced". Select "File Types". Scroll down to "pst" and highlight it by left clicking on it. Using the radio buttons change "how should this file be indexed" to "Index Properties and File Contents". Repeat for "ost". Filter descriptions should now read "Plain Text Filter". OK and Close out back to Outlook and after a while search should start to return proper results."
– DavidPostill♦
Feb 23 '16 at 12:04
@DavidPostill There's nothing wrong with Windows, these computers have just been reimaged from scratch and search works on identical computers. Also, Indexing is not set to index PST files as text on the computers that search works on. I'd really rather fix the MAPI16 cannot be loaded error rather than a hacky fix.
– Dom
Feb 24 '16 at 3:41
@DavidPostill There's nothing wrong with Windows, these computers have just been reimaged from scratch and search works on identical computers. Also, Indexing is not set to index PST files as text on the computers that search works on. I'd really rather fix the MAPI16 cannot be loaded error rather than a hacky fix.
– Dom
Feb 24 '16 at 3:41
@DavidPostill That smacks of the standard Microsoft forums approach to everything which is running SFC and if that doesn't work, reinstalling.
– Alan B
Aug 3 '17 at 11:10
@DavidPostill That smacks of the standard Microsoft forums approach to everything which is running SFC and if that doesn't work, reinstalling.
– Alan B
Aug 3 '17 at 11:10
@AlanB {shrug} It's also true that the repair approach fixes many obscure Windows problems
– DavidPostill♦
Aug 3 '17 at 12:19
@AlanB {shrug} It's also true that the repair approach fixes many obscure Windows problems
– DavidPostill♦
Aug 3 '17 at 12:19
add a comment |
5 Answers
5
active
oldest
votes
up vote
0
down vote
Tentative Fix (just waiting for reproducibility).
Open Indexing Options and note the number of items in the index. Edit Environment Variables and add to the path:
x32 - C:Program FilesMicrosoft OfficerootOffice16
or x64 - C:Program Files (x86)Microsoft OfficerootOffice16
Reboot, Open Indexing Options, note the items in the index, Open Outlook, Indexer starts working on items.
Seems Indexer needs Office in the %Path% in order to open the required files for MAPI16.
Note: On machines where Office 2016 installs correctly, the above path variable is not required, so it doesn't really fix the issue properly, but it does solve the problem in a reasonable manner.
add a comment |
up vote
0
down vote
I had this same issue and turns out the cause was adobe pdf pro add in. The add in does not install with office 2016 however it was inherited with office 2013. Disabling the add in then unchecking outlook from advanced. close outlook. rebuild index, checking then allowed indexing to occur again.
add a comment |
up vote
0
down vote
I had the same problem and I was using Office 2016 Small Business that was preinstalled on my Dell laptop. I removed Office entirely via the control panel and after that I used the removal tool from support.office.com. After that, I renamed all folders named 'Outlook' or 'Office' in the AppData subfolder of my profile to make sure the new installation did not reuse them. I reinstalled Office 2016 x64 by downloading it from Office.com. Now all my e-mail is indexed.
add a comment |
up vote
0
down vote
This is what I got from a case from Microsoft; Adding the path (#4) was what worked for me. Win 10/64; Office 2016 Pro Plus /32
Open file explorer -> C:WindowsProgramFiles
- look for
scanpst.exe. - Close outlook and run the tool
- look for
https://support.office.com/en-us/article/Outlook-search-stops-working-after-updating-to-build-7870-2020-and-higher-0bcf0b06-320d-40c3-8cf0-7e3df90793ed?ui=en-US&rs=en-US&ad=US
Check for Windows Updates
On the affected machine
- Go to Start > System
- Click Advanced System Settings
- Go to Advanced tab > Environment Variables > System Variables
- From the list, select Path
- Click Edit
- Check to see if the location of the MAPI protocol handler (mapiph.dll) is there. By default, it will be C:Program FilesMicrosoft OfficeRootOffice16, as shown below. Notice that you can find mapiph.dll in this folder. REBOOT.
- If not, add the path to the value, with a semicolon separated. And click OK to save the change.
If only 1 users affected, please try to recreate the profile.
Follow steps from this link
https://blogs.technet.microsoft.com/csstwplatform/2010/07/29/desktop-search-event-3083-window-search-mapi2handler-1-cannot-be-loaded
Also, a tech had added Reg. Key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSearch DisableServerAssistedSearch DWORD value =1
I do not believe this was necessary, it seemed to be the path of the MAPI protocol handler (mapiph.dll) that resolved it. After a REBOOT.
add a comment |
up vote
-1
down vote
installing 64 bit office solved this issue for me, i think it has to do with the windows search data file going above 2 GB which 32 bit office cannot handle.
[update 2017-04-06] just to clarify the issue seems to be with the windows search file in ProgramDataMicrosoftSearchDataApplicationsWindows, it seems that when this reaches 2 GB the indexing of emails on 32 bit office stops working. this also explains why when the search files are deleted search starts working again for a short period of time.
1
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
add a comment |
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Tentative Fix (just waiting for reproducibility).
Open Indexing Options and note the number of items in the index. Edit Environment Variables and add to the path:
x32 - C:Program FilesMicrosoft OfficerootOffice16
or x64 - C:Program Files (x86)Microsoft OfficerootOffice16
Reboot, Open Indexing Options, note the items in the index, Open Outlook, Indexer starts working on items.
Seems Indexer needs Office in the %Path% in order to open the required files for MAPI16.
Note: On machines where Office 2016 installs correctly, the above path variable is not required, so it doesn't really fix the issue properly, but it does solve the problem in a reasonable manner.
add a comment |
up vote
0
down vote
Tentative Fix (just waiting for reproducibility).
Open Indexing Options and note the number of items in the index. Edit Environment Variables and add to the path:
x32 - C:Program FilesMicrosoft OfficerootOffice16
or x64 - C:Program Files (x86)Microsoft OfficerootOffice16
Reboot, Open Indexing Options, note the items in the index, Open Outlook, Indexer starts working on items.
Seems Indexer needs Office in the %Path% in order to open the required files for MAPI16.
Note: On machines where Office 2016 installs correctly, the above path variable is not required, so it doesn't really fix the issue properly, but it does solve the problem in a reasonable manner.
add a comment |
up vote
0
down vote
up vote
0
down vote
Tentative Fix (just waiting for reproducibility).
Open Indexing Options and note the number of items in the index. Edit Environment Variables and add to the path:
x32 - C:Program FilesMicrosoft OfficerootOffice16
or x64 - C:Program Files (x86)Microsoft OfficerootOffice16
Reboot, Open Indexing Options, note the items in the index, Open Outlook, Indexer starts working on items.
Seems Indexer needs Office in the %Path% in order to open the required files for MAPI16.
Note: On machines where Office 2016 installs correctly, the above path variable is not required, so it doesn't really fix the issue properly, but it does solve the problem in a reasonable manner.
Tentative Fix (just waiting for reproducibility).
Open Indexing Options and note the number of items in the index. Edit Environment Variables and add to the path:
x32 - C:Program FilesMicrosoft OfficerootOffice16
or x64 - C:Program Files (x86)Microsoft OfficerootOffice16
Reboot, Open Indexing Options, note the items in the index, Open Outlook, Indexer starts working on items.
Seems Indexer needs Office in the %Path% in order to open the required files for MAPI16.
Note: On machines where Office 2016 installs correctly, the above path variable is not required, so it doesn't really fix the issue properly, but it does solve the problem in a reasonable manner.
answered Feb 24 '16 at 11:28
Dom
2974513
2974513
add a comment |
add a comment |
up vote
0
down vote
I had this same issue and turns out the cause was adobe pdf pro add in. The add in does not install with office 2016 however it was inherited with office 2013. Disabling the add in then unchecking outlook from advanced. close outlook. rebuild index, checking then allowed indexing to occur again.
add a comment |
up vote
0
down vote
I had this same issue and turns out the cause was adobe pdf pro add in. The add in does not install with office 2016 however it was inherited with office 2013. Disabling the add in then unchecking outlook from advanced. close outlook. rebuild index, checking then allowed indexing to occur again.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had this same issue and turns out the cause was adobe pdf pro add in. The add in does not install with office 2016 however it was inherited with office 2013. Disabling the add in then unchecking outlook from advanced. close outlook. rebuild index, checking then allowed indexing to occur again.
I had this same issue and turns out the cause was adobe pdf pro add in. The add in does not install with office 2016 however it was inherited with office 2013. Disabling the add in then unchecking outlook from advanced. close outlook. rebuild index, checking then allowed indexing to occur again.
answered May 12 '16 at 16:13
nemy
1
1
add a comment |
add a comment |
up vote
0
down vote
I had the same problem and I was using Office 2016 Small Business that was preinstalled on my Dell laptop. I removed Office entirely via the control panel and after that I used the removal tool from support.office.com. After that, I renamed all folders named 'Outlook' or 'Office' in the AppData subfolder of my profile to make sure the new installation did not reuse them. I reinstalled Office 2016 x64 by downloading it from Office.com. Now all my e-mail is indexed.
add a comment |
up vote
0
down vote
I had the same problem and I was using Office 2016 Small Business that was preinstalled on my Dell laptop. I removed Office entirely via the control panel and after that I used the removal tool from support.office.com. After that, I renamed all folders named 'Outlook' or 'Office' in the AppData subfolder of my profile to make sure the new installation did not reuse them. I reinstalled Office 2016 x64 by downloading it from Office.com. Now all my e-mail is indexed.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the same problem and I was using Office 2016 Small Business that was preinstalled on my Dell laptop. I removed Office entirely via the control panel and after that I used the removal tool from support.office.com. After that, I renamed all folders named 'Outlook' or 'Office' in the AppData subfolder of my profile to make sure the new installation did not reuse them. I reinstalled Office 2016 x64 by downloading it from Office.com. Now all my e-mail is indexed.
I had the same problem and I was using Office 2016 Small Business that was preinstalled on my Dell laptop. I removed Office entirely via the control panel and after that I used the removal tool from support.office.com. After that, I renamed all folders named 'Outlook' or 'Office' in the AppData subfolder of my profile to make sure the new installation did not reuse them. I reinstalled Office 2016 x64 by downloading it from Office.com. Now all my e-mail is indexed.
answered Dec 24 '16 at 19:24
Jorrit Schippers
1114
1114
add a comment |
add a comment |
up vote
0
down vote
This is what I got from a case from Microsoft; Adding the path (#4) was what worked for me. Win 10/64; Office 2016 Pro Plus /32
Open file explorer -> C:WindowsProgramFiles
- look for
scanpst.exe. - Close outlook and run the tool
- look for
https://support.office.com/en-us/article/Outlook-search-stops-working-after-updating-to-build-7870-2020-and-higher-0bcf0b06-320d-40c3-8cf0-7e3df90793ed?ui=en-US&rs=en-US&ad=US
Check for Windows Updates
On the affected machine
- Go to Start > System
- Click Advanced System Settings
- Go to Advanced tab > Environment Variables > System Variables
- From the list, select Path
- Click Edit
- Check to see if the location of the MAPI protocol handler (mapiph.dll) is there. By default, it will be C:Program FilesMicrosoft OfficeRootOffice16, as shown below. Notice that you can find mapiph.dll in this folder. REBOOT.
- If not, add the path to the value, with a semicolon separated. And click OK to save the change.
If only 1 users affected, please try to recreate the profile.
Follow steps from this link
https://blogs.technet.microsoft.com/csstwplatform/2010/07/29/desktop-search-event-3083-window-search-mapi2handler-1-cannot-be-loaded
Also, a tech had added Reg. Key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSearch DisableServerAssistedSearch DWORD value =1
I do not believe this was necessary, it seemed to be the path of the MAPI protocol handler (mapiph.dll) that resolved it. After a REBOOT.
add a comment |
up vote
0
down vote
This is what I got from a case from Microsoft; Adding the path (#4) was what worked for me. Win 10/64; Office 2016 Pro Plus /32
Open file explorer -> C:WindowsProgramFiles
- look for
scanpst.exe. - Close outlook and run the tool
- look for
https://support.office.com/en-us/article/Outlook-search-stops-working-after-updating-to-build-7870-2020-and-higher-0bcf0b06-320d-40c3-8cf0-7e3df90793ed?ui=en-US&rs=en-US&ad=US
Check for Windows Updates
On the affected machine
- Go to Start > System
- Click Advanced System Settings
- Go to Advanced tab > Environment Variables > System Variables
- From the list, select Path
- Click Edit
- Check to see if the location of the MAPI protocol handler (mapiph.dll) is there. By default, it will be C:Program FilesMicrosoft OfficeRootOffice16, as shown below. Notice that you can find mapiph.dll in this folder. REBOOT.
- If not, add the path to the value, with a semicolon separated. And click OK to save the change.
If only 1 users affected, please try to recreate the profile.
Follow steps from this link
https://blogs.technet.microsoft.com/csstwplatform/2010/07/29/desktop-search-event-3083-window-search-mapi2handler-1-cannot-be-loaded
Also, a tech had added Reg. Key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSearch DisableServerAssistedSearch DWORD value =1
I do not believe this was necessary, it seemed to be the path of the MAPI protocol handler (mapiph.dll) that resolved it. After a REBOOT.
add a comment |
up vote
0
down vote
up vote
0
down vote
This is what I got from a case from Microsoft; Adding the path (#4) was what worked for me. Win 10/64; Office 2016 Pro Plus /32
Open file explorer -> C:WindowsProgramFiles
- look for
scanpst.exe. - Close outlook and run the tool
- look for
https://support.office.com/en-us/article/Outlook-search-stops-working-after-updating-to-build-7870-2020-and-higher-0bcf0b06-320d-40c3-8cf0-7e3df90793ed?ui=en-US&rs=en-US&ad=US
Check for Windows Updates
On the affected machine
- Go to Start > System
- Click Advanced System Settings
- Go to Advanced tab > Environment Variables > System Variables
- From the list, select Path
- Click Edit
- Check to see if the location of the MAPI protocol handler (mapiph.dll) is there. By default, it will be C:Program FilesMicrosoft OfficeRootOffice16, as shown below. Notice that you can find mapiph.dll in this folder. REBOOT.
- If not, add the path to the value, with a semicolon separated. And click OK to save the change.
If only 1 users affected, please try to recreate the profile.
Follow steps from this link
https://blogs.technet.microsoft.com/csstwplatform/2010/07/29/desktop-search-event-3083-window-search-mapi2handler-1-cannot-be-loaded
Also, a tech had added Reg. Key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSearch DisableServerAssistedSearch DWORD value =1
I do not believe this was necessary, it seemed to be the path of the MAPI protocol handler (mapiph.dll) that resolved it. After a REBOOT.
This is what I got from a case from Microsoft; Adding the path (#4) was what worked for me. Win 10/64; Office 2016 Pro Plus /32
Open file explorer -> C:WindowsProgramFiles
- look for
scanpst.exe. - Close outlook and run the tool
- look for
https://support.office.com/en-us/article/Outlook-search-stops-working-after-updating-to-build-7870-2020-and-higher-0bcf0b06-320d-40c3-8cf0-7e3df90793ed?ui=en-US&rs=en-US&ad=US
Check for Windows Updates
On the affected machine
- Go to Start > System
- Click Advanced System Settings
- Go to Advanced tab > Environment Variables > System Variables
- From the list, select Path
- Click Edit
- Check to see if the location of the MAPI protocol handler (mapiph.dll) is there. By default, it will be C:Program FilesMicrosoft OfficeRootOffice16, as shown below. Notice that you can find mapiph.dll in this folder. REBOOT.
- If not, add the path to the value, with a semicolon separated. And click OK to save the change.
If only 1 users affected, please try to recreate the profile.
Follow steps from this link
https://blogs.technet.microsoft.com/csstwplatform/2010/07/29/desktop-search-event-3083-window-search-mapi2handler-1-cannot-be-loaded
Also, a tech had added Reg. Key: ComputerHKEY_CURRENT_USERSoftwareMicrosoftOffice16.0OutlookSearch DisableServerAssistedSearch DWORD value =1
I do not believe this was necessary, it seemed to be the path of the MAPI protocol handler (mapiph.dll) that resolved it. After a REBOOT.
edited Jan 27 at 9:23
Arjan
26.8k1065107
26.8k1065107
answered Jan 27 at 4:55
Gary P
11
11
add a comment |
add a comment |
up vote
-1
down vote
installing 64 bit office solved this issue for me, i think it has to do with the windows search data file going above 2 GB which 32 bit office cannot handle.
[update 2017-04-06] just to clarify the issue seems to be with the windows search file in ProgramDataMicrosoftSearchDataApplicationsWindows, it seems that when this reaches 2 GB the indexing of emails on 32 bit office stops working. this also explains why when the search files are deleted search starts working again for a short period of time.
1
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
add a comment |
up vote
-1
down vote
installing 64 bit office solved this issue for me, i think it has to do with the windows search data file going above 2 GB which 32 bit office cannot handle.
[update 2017-04-06] just to clarify the issue seems to be with the windows search file in ProgramDataMicrosoftSearchDataApplicationsWindows, it seems that when this reaches 2 GB the indexing of emails on 32 bit office stops working. this also explains why when the search files are deleted search starts working again for a short period of time.
1
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
add a comment |
up vote
-1
down vote
up vote
-1
down vote
installing 64 bit office solved this issue for me, i think it has to do with the windows search data file going above 2 GB which 32 bit office cannot handle.
[update 2017-04-06] just to clarify the issue seems to be with the windows search file in ProgramDataMicrosoftSearchDataApplicationsWindows, it seems that when this reaches 2 GB the indexing of emails on 32 bit office stops working. this also explains why when the search files are deleted search starts working again for a short period of time.
installing 64 bit office solved this issue for me, i think it has to do with the windows search data file going above 2 GB which 32 bit office cannot handle.
[update 2017-04-06] just to clarify the issue seems to be with the windows search file in ProgramDataMicrosoftSearchDataApplicationsWindows, it seems that when this reaches 2 GB the indexing of emails on 32 bit office stops working. this also explains why when the search files are deleted search starts working again for a short period of time.
edited Apr 6 '17 at 12:24
answered Apr 5 '17 at 13:23
Mo_AB
11
11
1
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
add a comment |
1
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
1
1
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
Except Outlook 2016 32-bit doesn't have a 2GB file limit.
– Ramhound
Apr 5 '17 at 13:39
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1044318%2foutlook-2016-email-not-indexing-the-protocol-handler-mapi16-cannot-be-loaded%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible answer here answers.microsoft.com/en-us/office/forum/office_2016-outlook/… "1. right click windows icon on the lower left 2.click "command prompt administrator" 3.type sfc /scannow then press enter 4.after the sfc type dism.exe /online /cleanup-image /restorehealth 5. Restart computer and test."
– DavidPostill♦
Feb 23 '16 at 12:02
From the same link another possible answer" In Outlook 2016 Open File - Open Options - Open Search. Select "Indexing Options". Select "Advanced". Select "File Types". Scroll down to "pst" and highlight it by left clicking on it. Using the radio buttons change "how should this file be indexed" to "Index Properties and File Contents". Repeat for "ost". Filter descriptions should now read "Plain Text Filter". OK and Close out back to Outlook and after a while search should start to return proper results."
– DavidPostill♦
Feb 23 '16 at 12:04
@DavidPostill There's nothing wrong with Windows, these computers have just been reimaged from scratch and search works on identical computers. Also, Indexing is not set to index PST files as text on the computers that search works on. I'd really rather fix the MAPI16 cannot be loaded error rather than a hacky fix.
– Dom
Feb 24 '16 at 3:41
@DavidPostill That smacks of the standard Microsoft forums approach to everything which is running SFC and if that doesn't work, reinstalling.
– Alan B
Aug 3 '17 at 11:10
@AlanB {shrug} It's also true that the repair approach fixes many obscure Windows problems
– DavidPostill♦
Aug 3 '17 at 12:19