Exchange 2007 server has reached the named properties quota and emails are being bounced

We have an Exchange 2007 server that has reached the named properties quota of 32,767 and has started bouncing emails from certain domains. Can we fix this without moving all of our mailboxes to a new mailbox database?  We have no service packs and when we tried to upgrade to Service Pack 1 it wouldn't complete with an error saying it found an Exchange 2003 Server in the domain.  We don't have any Exchange 2003 servers in our domain, however all of the mailboxes on this Exchange 2007 server were copied from the old 2003 server.
carilouAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tshearonCommented:
You can increase the quotas for named properties if you prefer. It requires taking the database offline though, which will be more disruptive. However, if you are in an emergency situation you probably don't care about that.

http://technet.microsoft.com/en-us/library/bb851493(v=exchg.80).aspx

Regarding your lingering Exchange 2003 server. It is likely a removal of one of your Exchange 2003 servers from your organization went bad. You can use ADSIEdit to remove it if you are comfortable with that process. If so your 2003 Exchange servers will be located here:

Open ADSIEdit and Navigate to:

CN=Configuration,DC=DOMAIN,DC=LOCAL
CN=Services
CN=Microsoft Exchange
CN=EXCHANGE_ORG
CN=Administrative Groups
CN=First Administrative Group
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
carilouAuthor Commented:
According to everything I am reading, I can't increase the quota past 32,767 because that is the maximum allowed quota.  Is that not the case?
0
tshearonCommented:
Taken from the artcle I posted:

Registry Name                              Default quota limits
Named Props Quota                   16K
NonMAPI Named Props Quota  8K
Replids Quota                               8K

So if you raise each registry dword value then you are essentially raising the quota to 32767 x 3.

Registry Name                              Default quota limits
Named Props Quota                   32K
NonMAPI Named Props Quota  32K
Replids Quota                               32K
0
carilouAuthor Commented:
We were able to upgrade the service pack level to SP2 as research told us that this may help.  Unfortunately that did not solve the problem, so we went ahead and created a new database (Database2) and began moving mailboxes.  We picked 12 mailboxes and kicked off the move last night to use off hours to get this completed.  After seeing 2 mailboxes complete successfully, we tested those mailboxes and the issue was resolved.  We then left the rest of the mailboxes to complete their move overnight and this morning found that only 2 more completed successfully while the other 8 had errors.  This is the error:

Error: Failed to copy messages to the destination mailbox store with error:
MAPI or an unspecified service provider.

We then attempted to move one of those mailboxes again and received this error:

Error: Failed to copy basic mailbox information with error: A duplicate mailbox was found due to problems during a Move Mailbox procedure. The duplicate mailbox has been deleted. Try again later.

So we tried again and received this error:

Error: Failed to copy basic mailbox information with error: After moving a mailbox, you must wait for cleanup operations to complete before you can move it again.

In researching this we found a solution that suggested we run the Clean-MailboxDatabase cmdlet.  Our concern is whether we should do this during the day while people are accessing email. Right now all mailboxes are currently accessible.  The ones that moved successfully are able to receive emails from the companies emails were bouncing back from.  The ones that didn't move still can't receive emails from those companies but email is working otherwise.  

Is the Clean-MailboxDatabase cmdlet the right way to go?  If we run it, how long can we expect it to take?  

Alternately, is there way to clean the mailboxes individually as opposed to the whole database?  I'd like to keep most of my users working and take them down one at a time if possible.
0
tshearonCommented:
Clean-mailboxdatabase is pretty instantaneous. You can use it whenever, it doesn't impact anything. However, I would just raise the named properties quotas as suggested.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.