Profile Corruption / Logins

[mvinarcik]

After a recent Office 365 update, X1 now forces me to repeatedly login to my e-mail accounts (even when I check "store credentials."

Even worse, it's corrupted my profile on two occasions (seems to mess up my @msn.com e-mail account). I've figured out that if I made a different e-mail the default I can just remove it and re-add (the first time I had to re-create my entire profile).

Is anyone else seeing this behavior?

[Kenward]

After a recent Office 365 update, X1 now forces me to repeatedly login to my e-mail accounts (even when I check "store credentials."

What is the exact message that you see?

I get constant popups from "Windows Credentials" requiring me to sign in.

It doesn't always seem to be from X1. Sometimes Outlook.

I also wonder if it was an Office update. Or maybe Windows.

I'll try to grab a screen shot when it next happens.

[Kenward]

This is what I see:

[mrwul]

Same problem here. Saving/remembering credentials, or not, it makes no difference, the prompt for credentials shows up every first time you launch X1
and only when it starts to index Outlook data.
When X1 is launched in 'all connectors paused' mode and one would only start the indexing files, then the prompt will not show up.

Just click [Cancel] - Outlook data will be indexed anyhow.

Have submitted a support ticket, they are investigating, but so far no solutions.

Am using the latest Office 365 version.
Note that I 'upgraded' from Office 2016 single user license to Office 365 last year.
Allegedly the solution might(!) be to create a new profile. I didn't do that, simply because I then need to recreate profiles for a bunch of POP3 accounts as well.
Re-Attach archive mailboxes, bla bla. Too much work.
-

[Kenward]

Thanks for confirming that it isn't just me.

I use password software that can fill in the details, but is is a nuisance.

[SimonH]

I'm also having this exact issue (the repeated log in challenge). Have not experienced the issue of it corrupting my profile (AFAIK/ yet!).
I get the same log in dialog box described by mrwul, under the same circumstances. Sometimes just once a day, sometimes it seems to pop up everytime the indexing runs.
To get it to work I seem to have to delete the prefix "MicrosoftAccount\" in front of my MS account name (email address) and then supply my password. Click on remember credentials makes no difference.
I think this has been happening since about the end of May when I returned from a holiday and presumably got the latest Office 365 updates.
Driving me crazy, I've tried deleting windows credentials, tried deleting and rebuilding my Outlook mailboxes, and tried a full X1 reinstall. No joy. PLEASE somebody solve this one.
Thanks
S

[mrwul]

The pop-up shows up when X1 starts indexing only (when X1 is analysing profiles).
Click [Cancel] solves this.
Vainly spent quite some time trying to figure out why this happens.

When running ProcMon I noticed that X1OutlookService32.exe is calling on a non existing registry key, named HKEY_CURRENT_USER\Software\Policies\Policies\Microsoft\Office\16.0\Outlook\Security.
(note the \Policies\Policies\ 2x policies)

Anyway, I let it go. Hopefully there will be a patch one day.

[hbradlow]

I have exactly the same problem.

However, even when I press cancel on the popup it won't index Outlook. It simply stops the indexing process.

I tried putting in an app password into the popup (I am using multi-factor authentication on my outlook.com accounts) but this corrupted my Outlook profile (I get a message saying "Outlook cannot log on. Verify you are connected to the network and using the proper server and mailbox name. The Microsoft Exchange information service in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service"). I also tried putting in the actual password for the account (the one which then should require a second factor authentication) but X1 ignored this and just asked me for the password again.

I had to recreate the Outlook profile in order to get Outlook working again.

What I have established is that X1 has a problem with the latest version of Outlook (I am using Microsoft Outlook for Office 365 MSO (16.0.11901.20204) 64-bit) and multi-factor authentication. I am using the latest version of X1 Search 8 (version 8.6.1 6003fa (64-b9it)

[mrwul]

Probably creating a new profile is the only way to solve this. It is really weird though and I think X1 should come up with a patch or something.
If it is only 1 account, recreating a profile isn't too much work. Outside 365 on Exchange I have multiple POP3 accounts and subsequent .pst files, archive .pst files and so on..
Those profiles need to be recreated as well , I assume.
With me, Outlook is still being indexed, even when I click on [Cancel] at the credentials pop up.
So I guess I leave it this way.
Sad to see that more people have this problem, however, X1 developers seem not to address this issue.

[SimonH]

Does anyone from X1 ever respond on these forums? Astounded that it took fully two weeks for my previous post just to be approved by a moderator!!
Or is this just the frustrating way of corralling everyone to pay $20 for paid support? My concern would be that I might pay $20 for support then still not get a resolution.

[SimonH]

To be fair to X1, I recently downloaded the update (to 8.6.2 I think) and early indications are that this problem has been fixed. Fingers crossed...!

[Kenward]

To be fair to X1, I recently downloaded the update (to 8.6.2 I think) and early indications are that this problem has been fixed. Fingers crossed...!

Yes. It has gone away.

But it may have done that a bit before the X1 update. I wonder if Windows fixed something with an update.

[mccmark]

I'm on 8.6.2 and have been getting this again in the last couple weeks.
Outlook 16.0.12209.20010 64-bit
Windows 10 Pro Workstations 19002.1002
I tried to add an X1 credential in the credential manager but I guess there's not a way to do that.
Mark

[mrwul]

Does anyone from X1 ever respond on these forums? Astounded that it took fully two weeks for my previous post just to be approved by a moderator!!
Or is this just the frustrating way of corralling everyone to pay $20 for paid support? My concern would be that I might pay $20 for support then still not get a resolution.

Not often, is my impression.

Hence I submitted a case.
This resulted in quite some exchanges via email and testing and in the end Microsoft and X1 one way or the other found the issue, fixed it, which resulted in 8.6.2.