Installing Exchange 2010 on windows 2008 server Hub Transport Role failed 'Cannot bind argument to parameter 'Identity' because it is null'

  • Thread starter Sprabhune
  • Start date Views 1,007
S

Sprabhune



While installing Exchange 2010 on windows 2008 server Hub Transport Role  getting failed with following error message.

ipv6 is disabled on windows 2008 server also i am installing Exchange with Domain Administrator Account (Default Account)
Make a note that HMC 4.0 is deployed on this setup. before Installing HMC 4.0 if I try to install Exchange 2010 fresh it  works but after installing HMC4.0 if i start the Installation  then it get failed.

Error Message as follows :-

Error:The execution of: "$error.Clear(); $user = Get-User -Identity $RoleLoggedOnUser; Set-User -Identity $user.Identity -RemotePowerShellEnabled $true;", generated the following error: "Cannot bind argument to parameter 'Identity' because it is null.".Cannot bind argument to parameter 'Identity' because it is null.

My Observation: - Exchange 14 installation does not work after deploying the HMC4.0.

HMC 4.0 setup & install Exch 14 compatible?  Dose anyone have any information ? Dose any one successfully install / tried this scenario? please help.. :(

An unexpected error has occurred and a Watson dump is being generated: The execution of: "$error.Clear(); $user = Get-User -Identity $RoleLoggedOnUser; Set-User -Identity $user.Identity -RemotePowerShellEnabled $true;", generated the following error: "Cannot bind argument to parameter 'Identity' because it is null.".

Below you can find the Exchange install Log.

[06-12-2009 09:58:38.0988] [1] RoleUpdatesDir = C:\install\Exchange 14 Beta1\Updates
[06-12-2009 09:58:38.0988] [1] ShellId = Microsoft.PowerShell
[06-12-2009 09:58:38.0988] [1] StackTrace =    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, Boolean coerceTypeIfNeeded)
   at System.Management.Automation.CmdletParameterBinderController.BindParameter(CommandParameterInternal argument, MergedCompiledCommandParameter parameter, Boolean coerceTypeIfNeeded)
   at System.Management.Automation.CmdletParameterBinderController.BindParameter(UInt32 parameterSets, CommandParameterInternal argument, MergedCompiledCommandParameter parameter, Boolean coerceTypeIfNeeded, Boolean delayBindScriptBlock)
   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)
[06-12-2009 09:58:38.0988] [1] true = True
[06-12-2009 09:58:38.0988] [1] user = testqa.lab/Users/Administrator testqa.lab/Hosting/change.450/admin@change.450 testqa.lab/Hosting/nsp.470/admin@nsp.470 testqa.lab/Hosting/470.update1/admin@470.update1
[06-12-2009 09:58:38.0988] [1] VerbosePreference = SilentlyContinue
[06-12-2009 09:58:38.0988] [1] WarningPreference = Continue
[06-12-2009 09:58:38.0988] [1] WhatIfPreference = False
[06-12-2009 09:58:38.0988] [1] WSManMaxRedirectionCount = 5
[06-12-2009 09:58:38.0988] [1] [WARNING] <<<  Variable dumping complete.  >>
[06-12-2009 09:58:38.0988] [1] Exception : Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The execution of: "$error.Clear(); $user = Get-User -Identity $RoleLoggedOnUser; Set-User -Identity $user.Identity -RemotePowerShellEnabled $true;", generated the following error: "Cannot bind argument to parameter 'Identity' because it is null.". ---> 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, Boolean coerceTypeIfNeeded)
   at System.Management.Automation.CmdletParameterBinderController.BindParameter(CommandParameterInternal argument, MergedCompiledCommandParameter parameter, Boolean coerceTypeIfNeeded)
   at System.Management.Automation.CmdletParameterBinderController.BindParameter(UInt32 parameterSets, CommandParameterInternal argument, MergedCompiledCommandParameter parameter, Boolean coerceTypeIfNeeded, Boolean delayBindScriptBlock)
   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)
   --- End of inner exception stack trace -   at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.InternalExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
   at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.ExecuteScript(String script, Boolean handleError, Int32 subSteps, LocalizedString statusDescription)
   at Microsoft.Exchange.Management.Deployment.ComponentInfoBasedTask.GenergeateAndExecuteTaskScript(InstallationCircumstances installationCircumstance)
[06-12-2009 09:58:39.0004] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: The execution of: "$error.Clear(); $user = Get-User -Identity $RoleLoggedOnUser; Set-User -Identity $user.Identity -RemotePowerShellEnabled $true;", generated the following error: "Cannot bind argument to parameter 'Identity' because it is null.".
[06-12-2009 09:58:39.0004] [1] [ERROR] The execution of: "$error.Clear(); $user = Get-User -Identity $RoleLoggedOnUser; Set-User -Identity $user.Identity -RemotePowerShellEnabled $true;", generated the following error: "Cannot bind argument to parameter 'Identity' because it is null.".
[06-12-2009 09:58:39.0004] [1] [ERROR] Cannot bind argument to parameter 'Identity' because it is null.
[06-12-2009 09:58:56.0915] [0] End of Setup
[06-12-2009 09:58:56.0915] [0] **********************************************
sameer Prabhune
 
C

Chinthaka Shameera



HI,

can you please try to install HUB by using different user account with all the possible rights of the administrator who is trying to install this HUB ?

Regards

Chinthaka
 
S

Sprabhune



ipv6 is disabled on windows 2008 server also i am installing Exchange with Domain Administrator Account (Default Account)
Make a note that HMC 4.0 is deployed on this setup. before Installing HMC 4.0 if I try to install Exchange 2010 fresh it  works but after installing HMC4.0 if i start the Installation  then it get failed.

My Observation: - Exchange 14 installation does not work after deploying the HMC4.0.

HMC 4.0 setup & install Exch 14 compatible?  Dose anyone have any information ? Dose any one successfully install / tried this scenario? please help.. :(

 

sameer Prabhune
 

Similar threads

Top