Solved

Exchange 2010 SP1 update fails (Cannot bind argument to parameter 'Identity' because it is null.)

Posted on 2011-02-25
5
3,011 Views
Last Modified: 2012-05-11
When I attempted to upgrade my Exchange 2010 box to SP1, the Mailbox role fails to install. I am using an administrator account with all relevent permissions and groups.  I've tried the procedure to remove white space from my public folder names but this did not help.   The error message is below.  Any help would be appreciated.

Mailbox Role
Failed

Error:
The following error was generated when "$error.Clear(); if ($RoleCreatePublicFolderDatabase) { $publicDB = get-PublicFolderDatabase -Server:$RoleFqdnOrName -ErrorAction SilentlyContinue; $DB = get-MailboxDatabase -Server:$RoleFqdnOrName -ErrorAction SilentlyContinue; if ($publicDB -and $DB) { set-mailboxdatabase -Identity:$DB.Identity -publicFolderDatabase:$publicDB.Identity -DomainController $RoleDomainController } }" was run: "Cannot bind argument to parameter 'Identity' because it is null.".

Cannot bind argument to parameter 'Identity' because it is null.

0
Comment
Question by:caronimsguy
  • 4
5 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 34981083
Sounds like possibly a space in an alias for a user? Be worth checking.
0
 

Author Comment

by:caronimsguy
ID: 34982438
Thanks dematzer for your comment.

I checked but I didn't find any spaces in any user alias.  I did find one user that had a corrupt
mailbox.  I fixed the mailbox but the problem still exists.
0
 

Accepted Solution

by:
caronimsguy earned 0 total points
ID: 35021935
After 7 hrs. on the phone with Microsoft this case has been resolved.

The error message actually points in the wrong direction.  The problem is not with the Public Folders, mailboxes or user alias.  The issue is a missing registry key.  Please note editing the registry incorrectly can get you into trouble.  Proceed at your own risk.  In my case the following Registry value was missing

Under the key HKLM\Software\Microsoft\ExchangeServer\v14\MailboxRole, the REG_SZ  value ConfiguredVersion should be set to the current version of Exchange, in my case 14.0.639.21
0
 

Author Comment

by:caronimsguy
ID: 35021979
Accepted
0
 

Author Closing Comment

by:caronimsguy
ID: 35067690
Resolved the problem via support call to Microsoft.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now