Error ID: XDDS:240FCB74 - Cannot bind argument to parameter 'ADAccountName'

Error ID: XDDS:240FCB74 - Cannot bind argument to parameter 'ADAccountName'

book

Article ID: CTX200655

calendar_today

Updated On:

Description

Error ID: XDDS:240FCB74

Exception:
Citrix.Console.Models.Exceptions.ScriptException Cannot bind argument to parameter 'ADAccountName' because it is an empty string.
at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.CreateException[T](ICommonLog logger, ExecutionResults`1 results, ICmdletExecutionHost host)
at Citrix.Console.PowerShellInteraction.CmdletExecutionMethods.Execute[T](ISdkCmdlet`1 sdkCmd, ICmdletExecutionHost host, Boolean allowFailover)
at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.Scripts.RemoveAccountsScript.FinishCommand(ISdkCmdlet`1 command)
at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.Scripts.RemoveAccountsScript.RunScript()
at Citrix.Console.PowerShellInteraction.PowerShellScript`1.Run()
at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.PSCatalogService.RemoveAccounts(IdentityPoolModel identityPool, String catalogName, IEnumerable`1 accountsToRemove, AccountRemovalOption removalOptions, Boolean forceRemoval, Action`1 progressModelCreated, ScriptExecutionContext context)
at Citrix.Console.ProvisioningSchemes.UI.Dialogs.ManageADAccountsDialogViewModel.RemoveAccountsOperation.PerformOperationInternal()
at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowOperation.PerformOperation()
at Citrix.Console.CommonControls.ProgressDisplay.ProgressWindowViewModel.PerformAction(Action operationComplete)

DesktopStudio_ErrorId : UnknownError
Sdk Error Message : Cannot bind argument to parameter 'ADAccountName' because it is an empty string.
$False

Resolution

Run these power-shell commands to remove your orphaned AD accounts. 

  1. Open Citrix Studio from a Controller. 

  2. Launch powershell. 

  3. Type "Get-AcctADAccount -State Available" (without the quotes) to see your orphaned AD accounts. 

  4. Determine the Identity Pool Name your orphaned accounts are in. 

  5. Determine the AD Account SID Name of your orphaned accounts (you'll have to use the SID name, because the AD Account Name will be blank). 

  6. Type the following to remove the orphaned accounts: 
    "Remove-AcctADAccount -IdentityPoolName General -ADAccountSid S-1-5-21-2931136610-426972087-2848873238-65689" 
    "General" is my pool name, and "S-1-5-21-2931136610-426972087-2848873238-65689" is the SID of my orphaned account. 

  7. Type "Get-AcctADAccount -State Available" again to verify the orphaned account was deleted.

                       Or

    Follow the Below Steps. 

    1 - Select Machine catalog and right side of the pane select "Manage AD accounts".
    2 - Delete all Orphaned machine SID accounts / Tainted machine accounts.
    3 - Now try adding machines to the catalog. 
    4 - Machines were added successfully. 

     


Problem Cause

Orphaned machine accounts or Tainted machine accounts caused the issue.

Issue/Introduction

When trying to add VDI using MCS, they get error: "Cannot bind to parameter."