If an error occurs when View Composer provisions or recomposes linked-clone machines, an error code indicates the cause of the failure. The error code appears in the machine-status column in View Administrator.
Table 1 describes the View Composer provisioning error codes.
This table lists errors that are associated with View Composer and QuickPrep customization. Additional errors can occur in View Connection Server and other View components that can interfere with machine provisioning.
|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. This result code is included for completeness.
|1||Failed to set the computer name.|
|2||Failed to redirect the user profiles to the View Composer persistent disk.|
|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.|
|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 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:
The timeout length is 10 minutes. If PnP does not finish mounting the disks within 10 minutes, View Composer fails with error code 6.
|7||Too many View Composer persistent disks are attached to the linked clone. A clone can have at most 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 nonpersistent disk. Either the paging file or the temp-files folders were not redirected.|
|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.|
|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.|
|19||The View Composer agent failed to execute a post-synchronization script.|
|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 fine.
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.
|21||The View Composer agent failed to mount the system disposable disk.|
|22||The View Composer agent failed to mount the View Composer persistent disk.|