When I create a new storage group, I have no problem. When I create a new database, it fails. Using the command prompt, I get no indication as to why. When I do it in the GUI, the database creation indicates success and it fails to mount. However physically the database is not being created in either instance. The log files are being created when I create the database. I am not getting any errors or indication as to why its failing. File permissions are that I and the system both have full access to the file locations. I created other ones with no problem.......

which version of exch are you using 2007/2010? SP and RU? check the event log, for any errorsSukh

On Sat, 4 Jun 2011 22:30:34 +0000, Tracy Cleeton wrote: >When I create a new storage group, I have no problem. When I create a new database, it fails. Using the command prompt, I get no indication as to why. When I do it in the GUI, the database creation indicates success and it fails to mount. However physically the database is not being created in either instance. The log files are being created when I create the database. The database won't mount until the DC used by the server as its configuration DC gets the new AD object. That's true no matter what release of Exchange you're using. >I am not getting any errors or indication as to why its failing. File permissions are that I and the system both have full access to the file locations. I created other ones with no problem....... Nothing in the applications event log? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Exchange 2007

There wasn't earlier, but I tried it again and I got Failed to create the Event Registration Mailbox for Database Corporate\Corporate. Error - 0xbf6f. event code: 9546

On Sat, 4 Jun 2011 23:12:09 +0000, Tracy Cleeton wrote: > > >There wasn't earlier, but I tried it again and I got > > > >Failed to create the Event Registration Mailbox for Database Corporate\Corporate. Error - 0xbf6f. > >event code: 9546 That looks like the System Mailbox for that database already exists in the MESO container. This KB is pretty old, but it describes the situation and a way to locate the mailbox object in the AD and remove it. http://support.microsoft.com/?kbid=274534 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

The below may also be relevant, there are a few suggestions. http://technet.microsoft.com/en-us/library/bb218254(EXCHG.80).aspx Also try restarting the SA service and then try again.Sukh

Hi Tracy, This problem occurs if the Microsoft Exchange System Object (MESO) container is deleted from the Active Directory service. To resolve this issue, run Exchange 2007 Setup together with the /preparedomain switch to create the MESO container. After the MESO container is created, restart the Information Store service. To create the MESO container At a command prompt on the computer that is running Exchange 2007, type the following command, and then press ENTER: Setup /prepareDomain Click Start, click Run, type services.msc, and then click OK. In the Results pane, find the Microsoft Exchange Information Store service. Right-click the service, and then click Restart. Regards, Hakim. BHakim

I looked at the exchange objects and found that the permissions were correct. I found that this is a consistent problem..... and consistently if I wait 5-10 minutes to mount the mailbox, it is created and mounts without any problem. I am guessing that something is being flagged, created, updated in AD -- and it is taking Exchange a while to find this...... but why would Exchange update a different DC than it queries? So -- it is working, but now I am trying to figure out why the delay.

On Sun, 5 Jun 2011 16:46:53 +0000, Tracy Cleeton wrote: > > >I looked at the exchange objects and found that the permissions were correct. I found that this is a consistent problem..... and consistently if I wait 5-10 minutes to mount the mailbox, it is created and mounts without any problem. I am guessing that something is being flagged, created, updated in AD -- and it is taking Exchange a while to find this...... but why would Exchange update a different DC than it queries? It's not Exchange, it's Powershell. The situation is pretty common. Using the EMS and specifying the DC used by Exchange as it configuration DC sometimes helps. >So -- it is working, but now I am trying to figure out why the delay. The don't call them slow-main controllers for no reason. :-0 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Tracy, Per your description, do you mean that the issue always occur when you create the database and mount it? Or the issue just occur when you do it firstly after you deploy the exchange email system? Do you run the EXBPA to retrieve some issue? What is the problem at present, whether the delay still exists? Please also check the MESO is exists. If the issue still exists, please refer to below: http://technet.microsoft.com/en-us/library/bb218254(EXCHG.80).aspx Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.