• Cannot log in to the VMware View Manager 4.5 Administrator console
  • Logging in to the View Manager Administrator Console fails
  • You see the error:

    Server Error : java.lang.IllegalArgumentException: id == null
  • In the VMware View Connection server debug logs, you see errors similar to:

    <YYYY-MM-DD>T<time>,756 DEBUG <TP-Processor7> [ViewFlexFactory] id == null com.vmware.vdi.admin.ui.common.ViewFlexFactory$ViewProxy.invoke(SourceFile:91)</time>
    java.lang.IllegalArgumentException: id == null
    at com.vmware.vdi.adamwrapper.utilities.Utility.validateArgument(SourceFile:319)

This issue occurs when the LDAP attribute values is more than the default value of 1500. When there are more than 1500 LDAP attribute values, the search retrieval techniques must support range retrieval.
Note: Microsoft ADAM database on Windows Server 2003 and Active Directory LDS on Windows Server 2008 use the range retrieval technique that pages the search responses when an entry has a large number of values.
For View Manager 4.5 Administrator Connection Server to handle range retrieval for LDAP entries with more than 1,500 references, it must have the cn attribute. As VMware View folder entries are ou based and do not have the cn attribute, the software fails and administrators are unable to login.
This issue is resolved in VMware View Manager 4.6. You can download and install View Manager 4.6 from the VMware Download Center.
To workaround this issue when you do not want to upgrade to View Manager 4.6, before performing range retrieval, increase the maximum value of LDAP entry from 1,500 to 20,000.
To increase the maximum value of LDAP entry:

Warning: This procedure may cause issues if incorrect changes are made. If the View Connection Server is a virtual machine, VMware recommends you to take a snapshot before making the changes. Also, ensure to back up the ADAM database. For more information, see Performing an end-to-end backup and restore for View Manager (1008046).
  1. In one of the VMware View Connection servers, log in as administrator.

    • In Windows Server 2003, click Start > All Programs > ADAM > ADAM Tools Command Prompt. to launch the ADAM command prompt.
    • In Windows Server 2008, click Start > All Programs > Accessories > Command Prompt to launch the command prompt.

  2. Run ldp.
  3. Click Connection > Connect and set the server IP to and the port to 389.
  4. Click OK.
  5. Click Connection > Bind.
  6. Under Bind Type, select the Bind as currently logged on user option.
  7. Click OK.
  8. Click View > Tree.
  9. In BaseDN, click the down arrow to the right of the input field.
  10. Select the tree starting with CN=Configuration.
  11. Click OK.
  12. In the left pane of the LDAP tree, navigate to CN=Default Query Policy,CN=Query-Policies,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,CN={<GUID>}

    Where <GUID> is specific to the instance.

  13. Right-click this entry and click Modify.
  14. Under Edit Entry for the Attribute, type ldapadminlimits.
  15. Set MaxValRange=20000.
  16. Click Add.
  17. Click Enter.
  18. Click Run.

    Note: A reboot of the Connection Server is not required for the changes to take effect. The changes will automatically be replicated to other Connection Servers in the group.