Error in adding new shared mailbox

%3CLINGO-SUB%20id%3D%22lingo-sub-123821%22%20slang%3D%22en-US%22%3EError%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123821%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3ECan%20anyone%20send%20me%20why%20I%20get%20this%20error%20%22%3CSPAN%3ENumber%20of%20databases%20available%200%20are%20not%20enough%20to%20allow%20meaningful%20database%20selection%3C%2FSPAN%3E%22%20while%20trying%20to%20add%20new%20shared%20mailbox%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20a%20lot!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-123821%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%20center%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%20Administration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125051%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125051%22%20slang%3D%22en-US%22%3E%3CP%3EI%20pinged%20the%20Exchange%20Online%20team.%20Maybe%20they%20can%20relieve%20the%20road%20block%20internally.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125049%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125049%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20morning%20the%20issue%20was%20fixed%20and%20I%20was%20able%20to%20create%20mailboxes%20and%20migrate%20from%20Exchange%202013.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20just%20one%20hour%20ago%2C%20the%20issue%20reappeared%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3EI'm%20blocked%20again%2C%20with%20the%20same%20error%20message%20saying%20that%20there%20is%20no%20available%20databases...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20feedback%20from%20Microsoft%20and%20I'm%20unable%20to%20tell%20how%20many%20time%20I'll%20have%20to%20wait%20before%20retrying%20migrations...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20you%20have%20more%20luck%20on%20your%20side.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBruno%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125007%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125007%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20unfortunate%20that%20a%20glitch%20stopped%20your%20migration.%20These%20things%20happen%2C%20even%20in%20the%20best-managed%20environments.%20What%20is%20more%20problematic%20is%20the%20lack%20of%20response%20from%20support.%20Have%20they%20acknowledged%20the%20problem%20(apart%20from%20the%20advisory)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F209%22%20target%3D%22_blank%22%3E%40Brian%20Levenson%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F210%22%20target%3D%22_blank%22%3E%40Anne%20Michels%3C%2FA%3E%26nbsp%3BMaybe%20another%20instance%20where%20support%20could%20have%20done%20better%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124985%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124985%22%20slang%3D%22en-US%22%3E%3CP%3EWell....%20a%20%22breadth%20of%20fresh%20air%22%20that%20blocked%20migration%20projects%20for%202%20days%20and%20a%20Week-end...%20That%20sort%20of%20%22breadth%22%20that%20cost%20a%20lot%20%3Ap%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124946%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124946%22%20slang%3D%22en-US%22%3E%3CP%3EWelcome%20to%20the%20cloud.%20Things%20happen%20and%20then%20disappear%20as%20quickly%20as%20a%20breadth%20of%20fresh%20air%20blows%20through%20a%20datacenter...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124904%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124904%22%20slang%3D%22en-US%22%3E%3CP%3EIts%20very%20strange%20but%20i%20don't%20have%20any%20advisories%20regarding%20this%20issue.%20I%20only%20see%201%20advisory%20regarding%20Office365%20Portal%20and%20some%20connectivity%20issues%20that%20are%20irelevant.%20All%20other%20services%20are%20healthy.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20based%20in%20South%20Europe.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124901%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124901%22%20slang%3D%22en-US%22%3EHello%2C%3CBR%20%2F%3EYes%20for%20me%20too.%20It's%20mention%20in%20the%20portal%20in%20advisories%20section%20%3A%20EX124353%20-%20Issues%20setting%20up%20new%20users%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124898%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124898%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20the%20issue%20is%20solved%20for%20us%20too.%20It%20was%20probably%20a%20temporary%20issue%20that%20is%20why%20they%20didn't%20even%20mention%20in%20the%20portal.%20tickets%20unanswered%20yet%20also.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124895%22%20slang%3D%22en-US%22%3ERE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124895%22%20slang%3D%22en-US%22%3EHi%2C%20since%20this%20morning%20everything%20works%20fine%20on%20my%20exchange%20in%20office%20365%2C%20but%20I%20can't%20tell%20you%20what%20was%20wrong%20because%20to%20this%20issue%20I%20didn't%20receive%20a%20response%20from%20Microsoft.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124565%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124565%22%20slang%3D%22en-US%22%3EIt%20seems%20that%20is%20the%20problem%20yes.%20New%20mailboxes%20cannot%20be%20created%20because%20there%20are%20no%20databases%20available.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124563%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124563%22%20slang%3D%22en-US%22%3E%3CP%3Ethese%20messages%20are%20related%20to%20the%20problem%3A%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F23619i56753533A5F373B2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Problem1.png%22%20title%3D%22Problem1.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F23620i81C4CB64BFF676C7%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Problem2.png%22%20title%3D%22Problem2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124553%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124553%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20started%20migration%20on%20Saturday%20morning.%20(Exchange%202010%20to%20O365)%3CBR%20%2F%3EIt%20worked%20well%20until%20noon%20(55%20mailboxes%20were%20completed).%20It%20is%20then%20broken%20and%20can%20not%20be%20restarted%20or%20deleted.%20Nothing%20can%20do%20with%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124526%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124526%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20reason%20why%20the%20error%20message%20is%20signaled%20is%20that%20Exchange%20Online%20cannot%20work%20out%20what%20mailbox%20database%20to%20create%20the%20new%20shared%20mailbox%20is.%20It's%20a%20bug.%20The%20only%20way%20to%20solve%20it%20is%20through%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124517%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124517%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here.%20Ticket%20open%20but%20i%20am%20sure%20Microsoft%20won't%20reply%20soon.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20update%20here%20if%20you%20have%20a%20solution%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124500%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124500%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20have%20the%20same%20problem%20here%20since%20this%20morning.%20I'll%20open%20a%20case%20at%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124483%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124483%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20the%20same%20problem%20Friday%2011%2F03%20and%20still%20have%20it%20this%20morning.%3C%2FP%3E%3CP%3EI'm%20currently%20preparing%20a%20brand%20new%20migration%20to%20Office%20365%20from%20Exchange%202013%20with%20hybrid%20mode.%3C%2FP%3E%3CP%3EOn%20Friday%20I%20tested%20my%20first%20migration%20of%20a%20test%20mailbox%20and%20had%20the%20same%20error%20message.%20I%20searched%20the%20web%20and%20found%20NOTHING.%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20morning%20I%20serached%20the%20web%20and%20found%20your%20question...%20I%20was%20wondering%20what%20was%20wrong%20in%20my%20configuration%20but%20finally%20it%20may%20be%20a%20global%20problem%20on%20the%20cloud%20!%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20successed%20in%20migrations%20before%20friday%20%3F%20For%20my%20part%20I%20experienced%20the%20problem%20on%20my%20first%20test%20migration%20so%20I'm%20uanble%20to%20tell%20if%20it%20was%20working%20before.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20any%20more%20informations%20on%20your%20side%20about%20this%20problem%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sorry%20you%20have%20this%20problem%20but%20I'm%20also%20happy%20not%20to%20be%20alone%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20a%20good%20day.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124481%22%20slang%3D%22en-US%22%3ERE%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124481%22%20slang%3D%22en-US%22%3EHi%2C%20I've%20got%20the%20same%20issue%20like%20you%20and%20waiting%20for%20a%20response%20from%20Microsoft.%20Do%20you%20have%20to%20receive%20an%20answer%20in%20between%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-124327%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124327%22%20slang%3D%22en-US%22%3EI%20also%20have%20the%20same%20problem%3A%20resources%20and%20shared%20mailbox.%3CBR%20%2F%3EMailbox%20migration%20is%20also%20interrupted%20by%20this%20error%20message.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-123916%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20in%20adding%20new%20shared%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-123916%22%20slang%3D%22en-US%22%3EUps%2C%20reading%20the%20message%20you%20get%20I%20recommend%20you%20to%20open%20a%20support%20ticket%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi,

Can anyone send me why I get this error "Number of databases available 0 are not enough to allow meaningful database selection" while trying to add new shared mailbox?

 

Thank a lot!

19 Replies
Highlighted
Ups, reading the message you get I recommend you to open a support ticket
Highlighted
I also have the same problem: resources and shared mailbox.
Mailbox migration is also interrupted by this error message.
Highlighted
Hi, I've got the same issue like you and waiting for a response from Microsoft. Do you have to receive an answer in between
Highlighted

Hi,

 

I had the same problem Friday 11/03 and still have it this morning.

I'm currently preparing a brand new migration to Office 365 from Exchange 2013 with hybrid mode.

On Friday I tested my first migration of a test mailbox and had the same error message. I searched the web and found NOTHING. 

This morning I serached the web and found your question... I was wondering what was wrong in my configuration but finally it may be a global problem on the cloud !??

 

Did you successed in migrations before friday ? For my part I experienced the problem on my first test migration so I'm uanble to tell if it was working before.

 

Do you have any more informations on your side about this problem ?

 

I'm sorry you have this problem but I'm also happy not to be alone ;)

 

Have a good day.

 

Highlighted

Hello,

I have the same problem here since this morning. I'll open a case at Microsoft.

 

 

Highlighted

Same issue here. Ticket open but i am sure Microsoft won't reply soon. 

 

Please update here if you have a solution

 

thank you

Highlighted

The reason why the error message is signaled is that Exchange Online cannot work out what mailbox database to create the new shared mailbox is. It's a bug. The only way to solve it is through support.

Highlighted

We started migration on Saturday morning. (Exchange 2010 to O365)
It worked well until noon (55 mailboxes were completed). It is then broken and can not be restarted or deleted. Nothing can do with it.

Highlighted

these messages are related to the problem:Problem1.pngProblem2.png

Highlighted
It seems that is the problem yes. New mailboxes cannot be created because there are no databases available.
Highlighted
Hi, since this morning everything works fine on my exchange in office 365, but I can't tell you what was wrong because to this issue I didn't receive a response from Microsoft.
Highlighted

Yes the issue is solved for us too. It was probably a temporary issue that is why they didn't even mention in the portal. tickets unanswered yet also.

Highlighted
Hello,
Yes for me too. It's mention in the portal in advisories section : EX124353 - Issues setting up new users
Highlighted

Its very strange but i don't have any advisories regarding this issue. I only see 1 advisory regarding Office365 Portal and some connectivity issues that are irelevant. All other services are healthy. 

 

We are based in South Europe. 

 

 

Highlighted

Welcome to the cloud. Things happen and then disappear as quickly as a breadth of fresh air blows through a datacenter...

Highlighted

Well.... a "breadth of fresh air" that blocked migration projects for 2 days and a Week-end... That sort of "breadth" that cost a lot :p

Highlighted

It's unfortunate that a glitch stopped your migration. These things happen, even in the best-managed environments. What is more problematic is the lack of response from support. Have they acknowledged the problem (apart from the advisory)?

 

@Brian Levenson @Anne Michels Maybe another instance where support could have done better?

Highlighted

Hi all,

 

This morning the issue was fixed and I was able to create mailboxes and migrate from Exchange 2013.

 

Unfortunately, just one hour ago, the issue reappeared :(

I'm blocked again, with the same error message saying that there is no available databases...

 

I have no feedback from Microsoft and I'm unable to tell how many time I'll have to wait before retrying migrations...

 

I hope you have more luck on your side.

 

Regards,

 

Bruno

 

Highlighted

I pinged the Exchange Online team. Maybe they can relieve the road block internally.