I’ve exported my contacts from Windows Live Mail on my old computer and now I want to import them into Outlook on my new computer.
The file is in csv-format but when I try to import it into Outlook, I’m being prompted to Map Custom Fields but everything is just on a single line.
How can I import my contacts into Outlook?
I’m not sure whether I should call this a bug or a feature but luckily the solution is quite easy.
For a change, let’s start with the solution and then I’ll explain my dilemma of whether to call this a bug or a feature.
Solution
The issue is that instead of commas ( , ) being used as a separator, you probably see semi-colons ( ; ) being used instead. So replace the semi-colons for commas and you’re done. The easiest is to do this in Notepad;
Turning a semi-colon separated file into a proper comma separated file can be done easily via Notepad. The bug or feature dilemma
The reason why Windows Live Mail (WLM), and also Outlook Express (OE) and Windows Mail (WM), used a semi-colon as a separator instead of a comma is because that is what is specified in your Region Settings in Windows to be used as the list separator. If this was set to a comma, you probably wouldn’t have been reading this
Outlook however expects a comma as a separator in a csv-file as that is what the file format stands for; comma separated value. Should WLM, OE or WM look at your configured list separator instead and use that? Skyrim best restoration spells. Should Outlook? It would break interoperability between systems if the format of a file is depended on end-user configuration. Are WLM, OE and WM to blame here for not respecting the meaning of csv? In essence, WLM, OE and WM export to the dsv-format; delimiter separated value. In this format the choice of the delimiter is not restricted to a comma.
However, as I said, you can configure the delimiter in your Regional Settings in Windows which would make it a feature again and will enable to WLM, OE and WM to create a proper csv-file again.
To change your list separator value in Windows;
Selecting the default List Separator in the Region settings of Windows.
So, would you call it a bug or a feature? Should WLM, OE and WM always use the comma and not look at your list separator value or should they rename the file format to dsv instead?
I think I’d prefer the first solution as that is what Outlook expects as well when importing and that is simply what the csv-format stands for. The thing is, files with another delimiter than a comma usually are named *.csv as well so the confusion remains when getting another file for import.
My advise
Always double check the delimiter being used before importing anything.
If the delimiter is not what is being expected and you cannot configure the delimiter upon importing (like Excel exports), then fire up Notepad and use its Replace function.
The dilemma might be complex, but at least the workaround is easy
Last Updated: February 14, 2019 ISSUE When you click Rules > Manage Rules & Alerts.., the following error occurs:
Error: 'The operation failed because of a registry or installation problem. Restart Outlook and try again. If the problem persists, reinstall.'
The issue may occur after installing the following perpetual updates:
The issue may occur after installing the following subscription updates and subsequent versions:
Warning: We do not recommend removing security updates as a workaround for this issue.
STATUS: FIXED If you have an Office 365 subscription (C2R) version installed: This issue is fixed in the following Channel versions:
To get the latest update immediately, open Outlook and choose File > Office Account > Update Options > Update Now. Failed To Get The Crawl Scope Manager Outlook 2016 Windows 10For more information about the latest updates, go to this article: Update history for Office 365 ProPlus
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:
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.
MJH
1,01544 gold badges1010 silver badges1818 bronze badges
Failed To Get The Crawl Scope Manager Outlook 2016 DownloadDomDom
31544 gold badges55 silver badges1515 bronze badges
7 Answers
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.
DomDom
31544 gold badges55 silver badges1515 bronze badges
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.
nemynemy
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.
Jorrit SchippersJorrit Schippers
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
Also, a tech had added Reg. Key: Arjan
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.
27.2k1010 gold badges6565 silver badges107107 bronze badges
Gary PGary P
Problem was Dixed December 2018 and occured again in January 2019 with Outlook 2016 version 1812. in Cache Mode
Extending path seems not to work for me, happend on Dell Image of Windows 10 updated to 1809 current Patchlevel as of 24.1.2019
What we figured out so far:Problem seems to happen in the Bridge between Windows Search x64 and Outlook mapi x32.
Quick Work Arround:Set Outlok Cache mode to not load all data, then you can search via Server by clicking on the search more line.
Michael MösslerMichael Mössler
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.
In addition to this, they can also be intimidated into surrendering, which gives the player full access to their inventory. Forcefully taking a few items from a caravan can be regarded as relatively unimportant, whereas outright attacking it will be considered as a major provocation.Consequences for Hostile ActionsIf you are not at war with the kingdom of the target, hostile actions are considered to be criminal acts and thus increase your criminal rating in the region. Just like with hostile actions against settlements, the severity of the hostile action is taken into account to determine consequences. Caravans and villager parties moving on the campaign map can also be attacked, coerced to join the player or forced to hand over a portion of their items and gold. Mount and blade warband siege tower. However, if your criminal rating exceeds a certain point, the other kingdom will be provoked to declare war.
[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.
Mo_ABMo_AB
I've been struggling with the very same problem for the past few days.
It turns out it was related to the 'HKCUSoftwareClassesVirtualStore' branch of the registry. It contained a few entries in the 'MACHINESOFTWAREMicrosoftOfficeClickToRun' subtree, so it was hiding the real 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftOfficeClickToRun' subtree.
After removing the whole 'HKCUSoftwareClassesVirtualStoreMACHINE' subtree and restarting the 'Windows Search' service, the error disappeared and the indexing started working again.
This is the site that helped me in finding the solution : https://www.win-10-forum.de/office/87414-outlook-2016-office-365-betriebssystem-momentan-ausfuehren-anwendung-konfi.html
SdrikSdrik
Not the answer you're looking for? Browse other questions tagged windows-10microsoft-outlookmicrosoft-officewindows-searchmicrosoft-outlook-2016 or ask your own question.
Posted by1 year ago
Archived
FIX THAT WORKED FOR ME :
[HKEY_CURRENT_USERSoftwareMicrosoftOffice16.0CommonIdentity] 'DisableADALatopWAMOverride'=dword:00000001
Thank you /u/teh_kyle .
Original post :
Hi,
Since i’ve tried to get an answer from the support i have access to (i don’t know if i can name it, but it’s an international provider of computers and services related to IT), and didn’t have any useful information, i’m asking this here. I really hope that you guys can provide me some details, the issue has been running since september…
TL ;DR : We have an Autodiscover-related issue ; it happens randomly to users ; it fixes itself randomly ; i have found a fix for one which doesn’t work for another ; i’m desperately trying to UNDERSTAND the mechanism of Autodiscover and what settings can be culprit on the client-side, and why it seems to happen randomly across different users.
In-depth details : Users in our organization, whom uses Office 2016 (OEM H&B or O365 Premium Business ) have, or used to have, a connection problem with their Outlook. Everything works fine with Skype for Business, Onedrive, office online, OWA,… it’s only related to Outlook 2016. When i say connection problem, i mean that in the Outlook 2016 interface, in the bottom-right, we see a button : Password Required. We click on it, we have a blank window which appears, and disappears quickly. Nothing else.
I have a perfect example of a user whom the problem happened to : Freshly created Active Directory account, Brand new Laptop with Windows 10 Installed with an ISO obtained with the Microsoft Media Creation Toolkit, Office365 Premium License, no fancy tweak, windows update ran in the first place, drivers updated from manufacturer website (including Bios). I’ll reference this user by UserA, with the computer CompA.
When i do the Autodiscover diag (Ctrl + rightclick on Outlook in the notification zone) :
ON OUTLOOK 2013 H&B OEM, this report comes from a working outlook profile on another computer : test with the mail account UserA@domain.com
Autodiscover to https://autodiscover.domain.com/autodiscover/autodiscover.xml starting
Getlasterror=2147954429; httpstatus=0.
Autodiscover to https://autodiscover.domain.com/autodiscover/autodiscover.xml Failed (0x80004005)
Local autodiscover for domain.com starting
Local autodiscover for domain.com Failed (0x8004010F)
Redirect Check to http://autodiscover.domain.com/autodiscover/autodiscover.xml Starting
Autodiscover URL redirection to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml
Autodiscover to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml Starting
Getlasterror=0; httpStatus=401.
GetLastError=0; httpStatus=401.
GetLastError=0; httpStatus=200.
Autodiscover to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml Succeeded (0x00000000)
Redirect Check to http://autodiscover.domain.com/autodiscover/autodiscover.xml Succeeded (0 x 00000000)
ON OUTLOOK 2016, FROM A PREMIUM O365 OFFICE 2016 SETUP. this report comes from CompA, with credentials of UserA. Outlook does NOT connect at this point :
Autodiscover to https://domain.com/autodiscover/autodiscover.xml starting
Failed To Get The Crawl Scope Manager Outlook 2016 Pdf
GetLastError=16;httpStatus=0.
Autodiscover to https://domain.com/autodiscover/autodiscover.xml Failed (0x80070057)
Autodiscover to https://autodiscover.domain.com/autodiscover/autodiscover.xml starting
GetLastError=2147954429;httpStatus=0.
Autodiscover to https://autodiscover.domain.com/autodiscover/autodiscover.xml Failed (0x80070057)
Local Autodiscover for domain.com starting
local autodiscover for domain.com Failed (0x8004010F)
Redirect Check to http://autodiscover.domain.com/autodiscover/autodiscover.xml Starting
Autodiscover Url redirection to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml
Autodiscover to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml Starting
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
[..]
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
Autodiscover to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml Failed (0x800C820E)
redirect check to http://autodiscover.domain.com/autodiscover/autodiscover.xml Failed (0x800C820E)
Srv Record lookup for domain.com starting
Srv Record lookup for domain.com failed (0 x 8004010F)
autodiscover to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml Starting
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
[..]
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
GetLastError=0;httpStatus=401.
Autodiscover to https://autodiscover-s.outlook.com/autodiscover/autodiscover.xml Failed (0x800C820E)
Alright, so at this point, i take CompA, i log in with my own credentials, i set myself an O365 Premium License, i launch Outlook 2016. It works perfectly. I go back in UserA’s environment, it doesn’t work. Conclusion : it’s related to user’s session. Yay, at least i can isolate the scope of the problem !
Some google-fu later, i stumble across this page :
https://newsignature.com/articles/bug-alert-exterminate-autodiscover-bug-windows-10-microsoft-office/ Which presents 3 Workarounds :
[HKEY_CURRENT_USERSoftwareMicrosoftOfficex.0OutlookAutoDiscover] 'ExcludeHttpsRootDomain'= dword:00000001 And restart the computer Doesn’t work.
[HKEY_CURRENT_USERSoftwareMicrosoftExchange] 'MSOAuthDisabled'=dword:00000001 It Works !!!
Revert Outlook 2013 to the May 2015 Public Update version 15.0.4719.1002. This issue appears to have been introduced in the June Public Update. Doesn’t apply here, it’s Office 2016.
Alright, so the fix worked for UserA ! awesome ! let’s try it with someone else experiencing the problem ! Well, i wouldn’t post on Reddit if it worked obviously…
Since about a week, it works well for UserA.
When it happened to several users back in september, my team and I thought it was related to some maintenance going on Exchange services. We had around 10 users who had the issue, and we had 40 users in Premium O365 License at the time. The issue is still happening, but we don’t have an exact count. I know for sure that there is an user which is affected right now, and waiting for a fix.
Basically, i just want to have answers to these questions :
I hope i’ve explained correctly the problem, and that you will be able to help me !
Thanks.
EDIT : Formatting. EDIT2 : Solution Added on top.
8 comments
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |