question

SusanDodds-3538 avatar image
0 Votes"
SusanDodds-3538 asked MaxFury-8335 commented

Exchange/Outlook asking for credentials of an account that doesn't exist

Exchange 2019/2016 coexistence. Outlook 2019

All mailboxes moved to 2019. I powered off 2016 to test.

Now in Outlook, Bob (bob@domain.com) is getting a credential box for test@domain.com constantly. There is no test@domain.com. It looks like Outlook is still connected but the box constantly pops back up. The same thing happened when creating Bob's account in Outlook on another computer.

Bob is the only one with this problem as far as I know.

Turning exchange 2016 back on seems to correct the problem.

Bob's OWA works fine when 2016 is powered off.

office-outlook-itprooffice-exchange-server-connectivity
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.


Hi,
You may have defined the wrong user ID or entered it incorrectly in your e-mail program settings. Your internet connection might not be working or you might be having problems. A firewall can block your attempts to connect to your mail server. This is also common if you provide the wrong password too often.

0 Votes 0 ·
YukiSun-MSFT avatar image
0 Votes"
YukiSun-MSFT answered YukiSun-MSFT converted comment to answer

Hi @SusanDodds-3538,

Now in Outlook, Bob (bob@domain.com) is getting a credential box for test@domain.com constantly. There is no test@domain.com. It looks like Outlook is still connected but the box constantly pops back up.

So despite of the credential prompt, Bob can still use his mailbox without issue in Outlook client, right?
May I know how you confirmed that "There is no test@domain.com"? Did you check it by running "Get-Mailbox test@domain.com" and it showed it cound't be found?

When the password prompt appears, please follow the steps below to check the connection status and see if there's any clues:
1. Hold down CTRL and right-click the Outlook icon in your system tray.
2. Choose "Connection Status":
105997-1.jpeg
3. Go through the entries listed to see whether there's any suspicious item which is related to test@domain.com. If possible, you can remove all personal information like domain name, personal name, etc, and then share a screenshot similar to below:
105999-2.jpeg

Besides, After Exchange 2016 is turned back, please run the commands below to see if we are able to find any trace of test@domain.com:

 Get-User test@domain.com
 Get-Mailbox -PublicFolder test@domain.com

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


1.jpeg (21.9 KiB)
2.jpeg (41.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SusanDodds-3538 avatar image
1 Vote"
SusanDodds-3538 answered YukiSun-MSFT commented

Thanks for the reply.

It turns out it was a public folder mailbox not tied to an actual user for testing purposes but not actually implemented. It also wasn't in the list of migratable mailboxes.

However, I got an error when deleting it. 0x8004010F

I'll try shutting 2016 down again tonight and see if I get the same error.

Edit: Symptoms still persist.

Edit 2: Symptoms possibly gone. Might have been residual issue. Will leave it off again for now.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @SusanDodds-3538,

Thanks for sharing the updates and great to know that symptoms is possibly gone.

Just wondering did you manage to delete the probIematic public folder mailbox after getting the error 0x8004010F? If you still have issue removing it and the issue comes back again, I'd like to suggest trying to deteting the public folder mailbox using the following command and see if it works:

 Remove-Mailbox -PublicFolder -Identity "test" -Force

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

0 Votes 0 ·

I got the error after deleting the public mailbox in ecp and doing a get-mailbox afterwards gave me an error saying it didn't exist so as far as I know, it's gone.

The workstation that had the issue persist didn't load Bob's Outlook profile when 2016 was powered on after it was deleted so that might have been the false positive.

I'll give it a few days (or first thing in the morning since if anything goes wrong, Bob will let me know) to make sure.

0 Votes 0 ·

Thanks @SusanDodds-3538 for the clarification. Sounds like the public folder mailbox should have already been deleted. Keep monitoring it for several days and feel free to post back should there's any update or if you need further assistance on this.

0 Votes 0 ·

Hi @SusanDodds-3538,

It has been a few days and I'd like to follow up with this thread. Is everything going fine these days since the public folder mailbox was removed?


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

0 Votes 0 ·
SusanDodds-3538 avatar image
1 Vote"
SusanDodds-3538 answered YukiSun-MSFT commented

On an unrelated note, it looks like deleting the public folder mailbox cleared up a 2019 ECP error on the compliance tab that I was having and couldn't find a solution for.

Error: The underlying connection was closed: An unexpected error occurred on a send

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Cool! It seems that these two issues are not related to each other, but happy to see that both disappeared after removing the public folder mailbox. Appreciate your sharing and hopefully it can give some hints to others who enounter the same error.

0 Votes 0 ·