[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Exchange  2010 - New Installation Mailbox Role Fails

Posted on 2011-05-02
16
Medium Priority
?
2,775 Views
Last Modified: 2012-06-27
The original environment was Windows 2003 SP2 and Exchange 2003 SP2. We have installed a Windows 2008 R2 SP1 Domain Controller and have moved All Roles to it. The new Exchange 2010 SP1 server on Windows 2008 R2 SP1.The plan is to run a Transitional migration from Exchange 2003 to Exchange 2010.  I have followed the steps set out for prerequisite’s. I have utilized the "Exchange Server Deployment Assistant" for installation. I have had good success until the "Mailbox Role" installation. I received this Application error event id 1002 pasted below and have section of the "ExchangeSetup.log" where the installation fails. I noticed the Mailbox Databases are dismounted and fail to mount when manually set to mount. Public Folder Database does mount automatically. I also noticed 3 Mailbox Databases (0058727555, 0104608875 and 0660603716) that I did not create. I did try the Mailbox Role installation 3 times. I assume each time it created a new Mailbox Database.

I have found one EE article ID 26500495 that is like my specific situation, but not sure the details are the same.

Exchange Server component Mailbox Role failed.
Error: 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.

Here is the 1st error I found in the ExchangeSetup.log on the Mailbox Role setup that failed.

04/30/2011 01:19:56.0786] [1] The following 1 error(s) occurred during task execution:
[04/30/2011 01:19:56.0786] [1] 0.  ErrorRecord: Cannot bind argument to parameter 'Identity' because it is null.
[04/30/2011 01:19:56.0786] [1] 0.  ErrorRecord: System.Management.Automation.ParameterBindingValidationException: Cannot bind argument to parameter 'Identity' because it is null.
   at System.Management.Automation.ParameterBinderBase.ValidateNullOrEmptyArgument(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, Type argumentType, Object parameterValue, Boolean recurseIntoCollections)
   at System.Management.Automation.ParameterBinderBase.BindParameter(CommandParameterInternal parameter, CompiledCommandParameter parameterMetadata, ParameterBindingFlags flags)
   at System.Management.Automation.CmdletParameterBinderController.BindParameter(CommandParameterInternal argument, MergedCompiledCommandParameter parameter, ParameterBindingFlags flags)
   at System.Management.Automation.CmdletParameterBinderController.BindParameter(UInt32 parameterSets, CommandParameterInternal argument, MergedCompiledCommandParameter parameter, ParameterBindingFlags flags)
   at System.Management.Automation.CmdletParameterBinderController.BindParameters(UInt32 parameterSets, Collection`1 arguments, CommandMetadata commandMetadata)
   at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParametersNoValidation(Collection`1 arguments)
   at System.Management.Automation.CmdletParameterBinderController.BindCommandLineParameters(Collection`1 arguments)
   at System.Management.Automation.CommandProcessor.BindCommandLineParameters(CommandParameterInternal[] parameters)
   at System.Management.Automation.CommandProcessor.Prepare(CommandParameterInternal[] parameters)
   at System.Management.Automation.CommandProcessorBase.DoPrepare(CommandParameterInternal[] parameters)
   at System.Management.Automation.Internal.PipelineProcessor.Start(Boolean incomingStream)
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
[04/30/2011 01:19:56.0832] [1] 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.".
[04/30/2011 01:19:56.0832] [1] Cannot bind argument to parameter 'Identity' because it is null.
[04/30/2011 01:19:56.0832] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___952169dbb47940388c375ba40fc0c835 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[04/30/2011 01:19:56.0832] [1] Setup is stopping now because of one or more critical errors.
[04/30/2011 01:19:56.0832] [1] Finished executing component tasks.
[04/30/2011 01:19:56.0879] [1] Ending processing Install-MailboxRole
[04/30/2011 01:21:58.0359] [0] [WARNING] Setup has made changes to operating system settings that require a reboot to take effect. Please reboot this server prior to placing it into production.
0
Comment
Question by:mark-grant
  • 11
  • 5
16 Comments
 
LVL 10

Expert Comment

by:scriven_j
ID: 35511443
0
 

Author Comment

by:mark-grant
ID: 35514783
I have reviewed the links you have sent and have found the following items needed to be corrected:

1. Disable IPv6 on E2010 server
2. Set Net.TCP sharing service to automatic & start the service
3. Set in registry the Link State Suppression to 1 and restart SMTP on E2k3

I am not clear on Step 6: Prepare New Server with Prerequisites to install Exchange Server 2010
number #2 Install Active Directory Domain Services in new Windows Server 2008. The E2010 Server is not going to be a DC. If this Role needs to be install what are the steps to configure past installing the Active Directory Domain Services Role?

I ran the Pre-Deployemt Analyzer and the only warning is for SMTP is configured to route all messages to a Smart host. Currently the E2k3 in/out bound nmessages are scanned for virus. Is this a problem? What change should I consider to amke this work with my new E2010 server.
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35688742
Step 6: Prepare New Server with Prerequisites to install Exchange Server 2010
number #2 Install Active Directory Domain Services in new Windows Server 2008.

You need to do this regardless of whether it is going to be a DC.

There is no configuration.  Just needs to be added:-

 AD DS and AD LDS Tools
With regards to the Smart host, Exchange 2010 does not have an SMTP service, but instead uses the Hub Transport role to send Email (which uses SMTP behind the scenes).  I'll have a look at the Smart Host thing and see how you would configure it...
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 10

Expert Comment

by:scriven_j
ID: 35688779
I've just checked and in Step 9 when you set up a Send Connector, it allows you to specify a Smart Host.  Should be as simple as that:-

Send Connector - Using a Smart Host
Post back here if you have problems.
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35698883
Alternatively you can install the pre-requisite roles and features using Powershell as outlined on this site:-

http://technet.microsoft.com/en-us/library/bb691354.aspx
(drill down to your OS)

** WARNING: IT MAY REBOOT THE SERVER WITHOUT WARNING **
0
 

Author Comment

by:mark-grant
ID: 35699495
I have followed your comments and Mailbox Roles still fails to complete. I have tried to uninstall and that fails as well. I have opened a call with Microsoft. We have deleted the Mailbox Role installation and DiscoverySearchMailbox from adsiedit, removed 2 system mailboxes plus the FederatedEmail from Active Directory Users and Computer. Deleted the partial directory structure created by the failed Mailbox Role installation for the non-existent .edb files. Ran Setup.com /p to add objects/values back. This allowed the installation to complete successfully. However the DiscoverySearchMailbox in adsiedit seems to be corrupt missing values. Ran EMC shell cmdlet for mailbox -arbitration and had errors. Removed again 2 system mailboxes plus the FederatedEmail from Active Directory Users and Computer and ran Setup.com /p. It fixed the arbitration problem but still the DiscoverySearchMailbox is missing values. Each time an EMC command is issued an Event Id 5000 Error is thrown. Created manually a Discovery Mailbox user and added it to the Discovery Management group under Microsoft Exchange Security Groups for purposes of logging changes to Exchange. I am now waiting for Microsoft to get back today/tomorrow on the Event ID 5000 Error. I can successfully add mailboxes, move mailboxes and connect using Outlook and OWA (the UCC Cert form Godaddy work fine). I have not been able to get Outlook AnyWhere working. Not clear if this is related.
The Exchange Remote Connectivity Analyzer reports errors on:
Attempting to test potential Autodiscover URL ttps://mydomain.com/AutoDiscover/AutoDiscover.xml
  Testing of this potential Autodiscover URL failed

Testing TCP port 443 on host mydomain.com to ensure it's listening and open.
  The specified port is either blocked, not listening, or not producing the expected response.

Certificate trust is being validated.
  The test passed with some warnings encountered. Please expand the additional details. Additional Details
  ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Testing SSL mutual authentication with the RPC proxy server.
  Verification of mutual authentication failed.
Additional Details
  The certificate common name mydomain.com doesn't validate against the mutual authentication string that was provided: msstd:webmail.mydomain.com
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35699817
You could try running:-

outlook /rpcdiag

This should give you a bit more information about what is happening with Outlook Anywhere.  Certainly the certificate needs to be correct or Outlook clients won't trust the Exchange server.

You said the certificate is working fine, but these all look like certificate errors....

Is the certificate definitely installed in the Trusted Root Certification Authority?

See if this helps at all:-

http://www.learnmsexchange.com/exchang/exchange-server-2010/configuration-a-administration/387-how-to-configure-outlook-anywhere-in-exchange-server-2010

0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35699832
Also, I haven't had a chance to go through it, but this thread looks like the same kind of errors:-

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26676269.html
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35699844
I would definitely start with Outlook /rpcdiag though, internally and externally.....
0
 

Author Comment

by:mark-grant
ID: 35707038
outlook /rpcdiag pops up "Windows Security" dialog box for password. The Password entered is not accepted. "The Microsoft Exchange Connection Status" displays "Disconnected". I noticed from Microsoft Exchange Remote Connection Analyzer for Outlook RPC/HTTP testing the following error: Attempting to test potential Autodiscover URL https://mydomain.com/AutoDiscover/AutoDiscover.xml. If I cut and pasted this in Internet Explorer it points to my www.mydomain.com (Not my CAS server webmail.mydomain.com/autodiscover.mydomain.com).

I have tried this URL in Internet Explorer and found is not correct. It should be pointed to https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml. The message I get back in Internet Explorer is “600 Invalid Request”, “Event ID=985748911
<?xml version="1.0" encoding="UTF-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"><Response><Error Id="985748911" Time="07:49:12.8331032"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>

I have run "Get-AutodiscoverVirtualDirectory | FL" to get infor on autodiscover but cannot find out where I need to correct Autodiscover URL.

RunspaceId                      : 1f116f81-a6fb-4372-882d-2bd5573ac16f
Name                            : Autodiscover (Default Web Site)
InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication      : False
WSSecurityAuthentication        : True
LiveIdBasicAuthentication       : False
BasicAuthentication             : True
DigestAuthentication            : False
WindowsAuthentication           : True
MetabasePath                    : IIS://InternalServerName.mydomain.com/W3SVC/1/ROOT/Autodiscover
Path                            : D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
Server                          : InternalServerName
InternalUrl                     : https:// InternalServerName.mydomain.com/autodiscover/autodiscover.xml
ExternalUrl                     : https://ExternalServerName.mydomain.com/autodiscover/autodiscover.xml
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
DistinguishedName               : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN= InternalServerName,CN=Servers,CN=Exchange Administrative Group
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35707288
You might find these links helpful - both have sections on setting up autodiscover correctly - second link talks about certificate problems and how to get round them:-

http://www.myexchangeworld.com/2010/08/how-autodiscover-service-in-exchange-2010-works/

http://www.wardvissers.nl/2010/08/09/exchange-2010-autodiscovery-issues/

0
 

Author Comment

by:mark-grant
ID: 35707421
In the 2nd post link it says:
You cannot set autodiscover external URL since outlook will try to access https://autodiscover.wardvissers.nl/autodiscover/autodiscover.xml, this behavior is by design and cannot be changed.

The Microsoft Exchange Connection Status" displays "Disconnected". I noticed from Microsoft Exchange Remote Connection Analyzer for Outlook RPC/HTTP testing the following error: Attempting to test potential Autodiscover URL https://mydomain.com/AutoDiscover/AutoDiscover.xml.

Why does mine not have a server/host name ( https://mydomain.com/AutoDiscover/AutoDiscover.xml.)? There is no host name in front of "mydoamain.com". It seems it is suppose to.
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35707555
Looks like you might need to add something to DNS:-

http://support.microsoft.com/kb/940881
0
 
LVL 10

Expert Comment

by:scriven_j
ID: 35707569
I would guess that if you don't have the DNS record, it just uses the MX record and appends autodiscover/autodiscover.xml to the end (this is only a guess though!)
0
 
LVL 10

Accepted Solution

by:
scriven_j earned 1500 total points
ID: 35707580
0
 

Author Closing Comment

by:mark-grant
ID: 35805688
The problem I had still required a support call to Microsoft Spport to resolve.
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

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

Stellar Exchange Toolkit: this 5 in 1 toolkit comes loaded with mega-software tool. Here’s an introduction to tools’ usage and advantages:
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this video we show how to create an Address List 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 Organization >> Ad…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses
Course of the Month18 days, 22 hours left to enroll

834 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