SOLVED

"No mailbox with such guid" error

%3CLINGO-SUB%20id%3D%22lingo-sub-304257%22%20slang%3D%22en-US%22%3E%22No%20mailbox%20with%20such%20guid%22%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304257%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3ELast%20week%20we're%20suffering%20from%20many%20office%20365%20errors%2C%20that%20started%20to%20happen%20out%20of%20the%20blue.%3C%2FP%3E%3CP%3ENow%2C%20it's%20a%20new%20one%2C%20we're%20using%20EWS%20to%20access%20office%20365%20%2C%20using%20account%20with%20impersonation%20rights%20to%20access%20another%20mailboxes.%3C%2FP%3E%3CP%3ESince%20yesterday%20we%20see%20high%20rate%20of%20error%20%22No%20mailbox%20with%20such%20guid%22%20on%20the%20mailbox%20that%20are%20really%20exists%20and%20valid%20mailboxes.%3C%2FP%3E%3CP%3EHave%20no%20idea%20what%20is%20going%20on%20there%20in%20Office%20365%2C%20but%20last%20week%20it's%20a%20worst%20ever%2C%203%20different%20issue%20for%20one%20week%2C%20MS%20support%20team%20is%20totally%20non-professional%20and%20response%20with%20%22it's%20a%20connectivity%20issue%22%20or%20%22it's%20a%203'rd%20party%20issue%2C%20we%20don't%20solve%20this%22%2C%20even%2C%20even%20when%20we%20send%20them%20request%20%2F%20response%20trace%2C%20clearly%20showing%20what%20was%20request%20and%20what%20is%20response%2C%20and%20where's%20the%20problem.%20And%20they%20constantly%20asking%20for%20the%20screenshot%20for%20EWS%20!!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVery%20sad%2C%20it%20was%20stable%20product%2C%20but%20last%20weeks%20dangerous%20degradation%2C%20affecting%20many%20tenants%2C%20without%20any%20one%20from%20Microsoft%20is%20taking%20responsibility%20on%20that.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-304257%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304535%22%20slang%3D%22en-US%22%3ERe%3A%20%22No%20mailbox%20with%20such%20guid%22%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304535%22%20slang%3D%22en-US%22%3E%3CP%3EStrange%2C%20while%20we%20tried%20to%20check%20the%20flag%2C%20with%20the%20customer%2C%20seems%20that%20mailboxes%20that%20failed%20with%20that%20error%2C%20found%20that%20lost%20their%20licenses.%20They%20were%20licensed%20and%20somethow%20license%20was%20vanished%20from%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304411%22%20slang%3D%22en-US%22%3ERe%3A%20%22No%20mailbox%20with%20such%20guid%22%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304411%22%20slang%3D%22en-US%22%3EHave%20you%20checked%20%22%20non-Null%20value%20in%20the%20%22msExchMailboxGuid%22%20attribute%20of%20the%20mailbox%20account.%22%3CBR%20%2F%3E-------------------------------------------------------------------------------%3CBR%20%2F%3EPlease%20mark%20as%20%22Answer%22%20and%20give%20a%20%22like%22%20if%20you%20are%20satisfied%20with%20the%20reply%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304400%22%20slang%3D%22en-US%22%3ERe%3A%20%22No%20mailbox%20with%20such%20guid%22%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304400%22%20slang%3D%22en-US%22%3EWell%2C%3CBR%20%2F%3EIt's%20not%20our%20tenant%2C%20but%20customer's%20that%3CBR%20%2F%3Esaying%20that%20mailbox%20are%20licensed%2C%20and%20even%20more%20up%20to%202%20days%20ago%2C%20those%20accounts%20were%20working%20fine.%20So%2C%20I%20assume%20it's%20something%20else%2C%20it's%20just%20started%20to%20return%20errors%20on%20those%20valid%2C%20licensed%20and%20previousky%20working%20mailboxes%2C%202%20days%20ago.%20Last%20week%2C%20we%20see%20strange%20bug%20from%20office%20365%2C%20so%20I%20guess%20it's%20another%20one%20in%20the%20bugs%20pipeline%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E.Thanks%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304390%22%20slang%3D%22en-US%22%3ERe%3A%20%22No%20mailbox%20with%20such%20guid%22%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304390%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20sorry%20to%20here%20%2C%20that%20you%20guys%20are%20going%20thorough%20a%20lot%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20error%20is%20commonly%20caused%20by%20an%20unlicensed%20mailbox%20account.%20Check%20that%20all%20of%20the%20migrating%20mailboxes%20are%20licensed%20in%20Office%20365%20first.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20a%20mailbox%20account%20has%20been%20assigned%20a%20license%20and%20the%20error%20persists%2C%20it%20is%20usually%20caused%20by%20a%20non-Null%20value%20in%20the%20%22msExchMailboxGuid%22%20attribute%20of%20the%20mailbox%20account.%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20refer%20the%20below%20link%20for%20more%20info%20and%20let%20me%20know%20how%20it%20goes.%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fhelp.bittitan.com%2Fhc%2Fen-us%2Farticles%2F115008114287-No-mailbox-with-such-GUID-ErrorNonExistentMailbox%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fhelp.bittitan.com%2Fhc%2Fen-us%2Farticles%2F115008114287-No-mailbox-with-such-GUID-ErrorNonExistentMailbox%3C%2FA%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

Last week we're suffering from many office 365 errors, that started to happen out of the blue.

Now, it's a new one, we're using EWS to access office 365 , using account with impersonation rights to access another mailboxes.

Since yesterday we see high rate of error "No mailbox with such guid" on the mailbox that are really exists and valid mailboxes.

Have no idea what is going on there in Office 365, but last week it's a worst ever, 3 different issue for one week, MS support team is totally non-professional and response with "it's a connectivity issue" or "it's a 3'rd party issue, we don't solve this", even, even when we send them request / response trace, clearly showing what was request and what is response, and where's the problem. And they constantly asking for the screenshot for EWS !!!

 

Very sad, it was stable product, but last weeks dangerous degradation, affecting many tenants, without any one from Microsoft is taking responsibility on that. 

 

 

4 Replies
Highlighted
Best Response confirmed by Devagnanam Jayaseelan (DEVA) (Microsoft)
Solution
Hi,

I am sorry to here , that you guys are going thorough a lot

This error is commonly caused by an unlicensed mailbox account. Check that all of the migrating mailboxes are licensed in Office 365 first.

If a mailbox account has been assigned a license and the error persists, it is usually caused by a non-Null value in the "msExchMailboxGuid" attribute of the mailbox account.

Please refer the below link for more info and let me know how it goes.
https://help.bittitan.com/hc/en-us/articles/115008114287-No-mailbox-with-such-GUID-ErrorNonExistentM...
Highlighted
Well,
It's not our tenant, but customer's that
saying that mailbox are licensed, and even more up to 2 days ago, those accounts were working fine. So, I assume it's something else, it's just started to return errors on those valid, licensed and previousky working mailboxes, 2 days ago. Last week, we see strange bug from office 365, so I guess it's another one in the bugs pipeline :).
Thanks

Highlighted
Have you checked " non-Null value in the "msExchMailboxGuid" attribute of the mailbox account."
-------------------------------------------------------------------------------
Please mark as "Answer" and give a "like" if you are satisfied with the reply
Highlighted

Strange, while we tried to check the flag, with the customer, seems that mailboxes that failed with that error, found that lost their licenses. They were licensed and somethow license was vanished from them.