Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Investigating VMware View Composer failure codes (2085204)

Symptoms

  • You are unable to provision or recompose VMware Horizon View desktops
  • Provisioning or recomposing the VMware Horizon View Desktops fail
  • You see the error:

    View composer agent initialization state error (##): ...


Resolution

To resolve the issue, locate the error code in the table below:

Error
Code
Error
Description
Additional Information
0 The policy was applied successfully.

Note: Result code 0 does not appear in View Administrator. The linked-clone machine proceeds to a Ready state, unless a View error outside the domain of View Composer occurs.

1 Failed to set the computer name.
2 Failed to redirect the user profiles to the View Composer persistent disk. Deploying or recomposing a View desktop pool fails with the error: View composer agent initialization state error (2) (1021347)

Upgrading a linked-clone desktop from View 4.0.1 to View 4.5 can fail with the following error: "View Composer agent initialization state error (2)". (1027203)
3 Failed to set the computer's domain account password.
4 Failed to back up a user's profile keys. The next time the user logs in to this linked-clone machine after the recompose operation, the OS creates a new profile directory for the user. As a new profile is created, the user cannot not see the old profile data. Pool recompose fails with the error: View Composer agent initialization state error (4): Failed to backup profiles keys (waited 0 seconds) (2001299)
5 Failed to restore a user's profile. The user should not log in to the machine in this state because the profile state is undefined.
6 Errors not covered by other error codes. The View Composer agent log files in the guest OS can provide more information about the causes of these errors. (For more information on log locations, see the QuickPrep/Sysprep Script and Composer Customization logs section in Location of VMware View log files (1027744).)

For example, a Windows Plug and Play (PnP) timeout can generate this error code. In this situation, View Composer times out after waiting for the PnP service to install new volumes for the linked-clone virtual machine. PnP mounts up to three disks, depending on how the pool was configured:
  • View Composer persistent disk
  • Non-persistent disk for redirecting guest OS temp and paging files
  • Internal disk that stores QuickPrep configuration and other OS-related data. This disk is always configured with a linked clone.
The timeout length is 10 minutes. If PnP does not finish mounting the disks within 10 minutes, View Composer fails with error code 6.
Linked clone deploy or recompose results in the error: View Composer agent initialization state error (6): Unknown failure (waited 0 seconds) (1011653)
7 Too many View Composer persistent disks are attached to the linked clone. A clone can have a maximum of three View Composer persistent disks.
8 A persistent disk could not be mounted on the datastore that was selected when the pool was created.
9 View Composer could not redirect disposable data files to the non-persistent disk. Either the paging file or the temp files folders were not redirected. Deploying or recomposing a linked clone pool fails with the error: Failed to relocate disposable (waited 0 seconds) (2020204)
10 View Composer cannot find the QuickPrep configuration policy file on the specified internal disk.
12 View Composer cannot find the internal disk that contains the QuickPrep configuration policy file and other OS related data.
13 More than one persistent disk is configured to redirect the Windows user profile.
14 View Composer failed to unmount the internal disk.
15 The computer name that View Composer read from configuration policy file does not match the current system name after the linked clone is initially powered on.
16 The View Composer agent did not start because the volume license for the guest OS was not activated. Windows 7 KMS activation fails on View virtual desktops (2009481)
17 The View Composer agent did not start. The agent timed out while waiting for Sysprep to start.
18 The View Composer agent failed to join the linked clone virtual machine to a domain during customization. Provisioning linked clone desktops fail with the error: View Composer agent initialization state error (18): Failed to join the domain (1027087)

Provisioning the View desktop pool fails with the error: View Composer agent initialization state error (18): Failed to join the domain (waited nnn seconds) (2006879)
19 The View Composer agent failed to execute a post-synchronization script. Provisioning or recomposing fails with the error: View Composer agent initialization state error (19): Failed to execute postsync script (2011315)
20 The View Composer agent failed to handle a machine password synchronization event.

This error might be transient. If the linked clone joins the domain, the password is correct.

If the clone fails to join the domain, restart the operation you performed before the error occurred. If you restarted the clone, restart it again. If you refreshed the clone, refresh it again. If the clone still fails to join the domain, recompose the clone.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: