Avatar of TVS-ServiceDesk
TVS-ServiceDesk
 asked on

Unable to create new Mailboxes in Exchange 2007

Hi,

We had an issue last week where the Data Stores on Exchange needed clearing out. At the same time we were unable to create new mailboxes, when we went through the wizard and the timer starts showing the new mailbox being created it wouldn't actually create the mailbox.

The time would just go on and on.
ExchangeWindows Server 2008

Avatar of undefined
Last Comment
TVS-ServiceDesk

8/22/2022 - Mon
Stelian Stan

Diwakar Sharma

Check if default / primary database status is showing mouted, if not mount that and check.

Diwakar
dsnegi_25dec

What's the error please .

Are the databases mounted.

Did you see anything on event viewer
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
TVS-ServiceDesk

ASKER
No errors, the Elapsed Time just keeps going and going. Where in Event Viewer should I be looking for errors?

The databases are mounted
Diwakar Sharma

Is Microsoft Exchange System Attendant service running?

Diwakar
TVS-ServiceDesk

ASKER
Yes that service is running
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Stelian Stan

Open Event Viewer and navigate to Windows Logs > Application
TVS-ServiceDesk

ASKER
I started to create a new Mailbox and watch Windows Logs > Application at the same time, the only entry I see is: "The Directory Service Referral interface (RFRI) received a client request on RPC protocol sequence ncacn_ip_tcp.  RFRI is returning the Domain Controller name crossbill.domain.com"
ASKER CERTIFIED SOLUTION
TVS-ServiceDesk

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Stelian Stan

Probably the Exchange server was not able to communicate to any DC.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
TVS-ServiceDesk

ASKER
Wasn't a root cause fix