Forum Discussion
Lampadinha
Apr 10, 2025Copper Contributor
Unable to receive or send emails throughout the day
Greetings,
Started the day like any other when I noticed midday that I hadn`t received any emails not even newsletters, proceed to troubleshoot the problem and all services seem just fine. But while trying to log into my accounts through the browser I`m confronted with this error:
UTC Date: 2025-04-10T15:41:48.144Z
Client Id: 147966D6CD5243FFB400ECA71E4270B0
Session Id: 348e1df0-f5b3-4b8a-b5bc-39ff1ce2f50a
Client Version: 20250328005.22
BootResult: configuration
Back Filled Errors: Unhandled Rejection: Error: 500:undefined|undefined:undefined
err: Microsoft.Exchange.Clients.Owa2.Server.Core.OwaUserHasNoMailboxAndNoLicenseAssignedException
esrc: StartupData
et: ServerError
estack: Error: 500
at Object.s [as createStatusErrorMessage] (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.fb94a6a8.js:1:144085)
at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.fb94a6a8.js:1:157003
st: 500
ehk: X-OWA-Error
efe: VI1PR09CA0140, PR1P264CA0136, CT2P275CA0049
emsg: UserHasNoMailboxAndNoLicenseAssignedError
Any suggestions would be much appreciated.
Hi Kidd_Ip ,
Much obliged for replying. That`s why I found the error to not make any sense at all, as that is not the case. All the accounts are fully licensed.
But then last night I recalled having been working on our website and making some alterations on the previous web host`s name servers. Since my DNS records do point to Microsoft it must have caused some service disruption and affected the mailing service as well, because as soon as I reverted the changes the service was restored.
Thanks and have a good oneđź––.
2 Replies
Sort By
The error message "UserHasNoMailboxAndNoLicenseAssignedError" typically indicates that the affected account does not have a mailbox or an appropriate license assigned:
Please try the following
Step 1: Verify License Assignment
- Log in to the Microsoft 365 Admin Center.
- Navigate to Users > Active Users.
- Select the affected user and check if they have an Exchange Online license assigned. If not, assign the appropriate license.
Step 2: Confirm Mailbox Creation
- After assigning the license, ensure that the mailbox has been provisioned.
- You can check this by navigating to Exchange Admin Center > Recipients > Mailboxes and searching for the user.
Step 3: Reassign Licenses (if necessary)
If the mailbox still doesn't appear, try removing the license, waiting for a few minutes, and then reassigning it. This can trigger mailbox creation.
Step 4: Check for Sync Issues
If the user is part of a hybrid environment, ensure that their on-premises mailbox is properly synced with Exchange Online. Use the Azure AD Connect tool to verify synchronization.
Step 5: Clear Browser Cache
Sometimes, browser cache issues can cause login problems. Clear the cache and cookies of the browser and try logging in again.
Step 6: Use PowerShell for Advanced Troubleshooting
Connect-MsolService Get-MsolUser -UserPrincipalName <UserEmail> | Select-Object DisplayName, Licenses
- LampadinhaCopper Contributor
Hi Kidd_Ip ,
Much obliged for replying. That`s why I found the error to not make any sense at all, as that is not the case. All the accounts are fully licensed.
But then last night I recalled having been working on our website and making some alterations on the previous web host`s name servers. Since my DNS records do point to Microsoft it must have caused some service disruption and affected the mailing service as well, because as soon as I reverted the changes the service was restored.
Thanks and have a good oneđź––.