Knowledge Base

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

Provisioning linked clones when using the French version of Windows 2008 64bit fails with the error: Selected parent VM is not accessible (1037379)

Symptoms

After installing or upgrading to VMware View 4.5 or 4.6, you experience these symptoms:
  • Cannot provision linked clone pools
  • Provisioning linked clone pools fail
  • This issue occurs if you have installed vCenter Server on the French version of Windows 2008 64bit operating system 
  • In the Windows Event log of vCenter Server, you see the error:

    "Avertissement","104","09/20/2010 08:09:59","VMware View","9","AUTORITE NT\Système","Pool cn=7fdf9ece-ae4f-4e32-
    bc57-c3e61aa70dfc,ou=virtualcenter,ou=propeties,dc=vdi,dc=vmware,dc=int::Unable to create new VM - View Composer DiskFault:
    Selected parent VM is not accessible"

     
  • In the Composer log, you see entries similar to:

    2010-09-17 21:15:41,220 | 3 | FATAL | Sim.ServiceCore.SimServiceApiImpl - Error: fail to execute web service call: AddAdConfig
    VMware.Sim.CommonLib.Exception.SimAdsException: Échec d’ouverture de session : nom d’utilisateur inconnu ou mot de passe incorrect.
     ---> System.Security.Authentication.AuthenticationException: Échec d’ouverture de session : nom d’utilisateur inconnu ou mot de passe incorrect.
     ---> System.Runtime.InteropServices.COMException (0x8007052E): Échec d’ouverture de session : nom d’utilisateur inconnu ou mot de passe incorrect.

Cause

This issue occurs because the View Composer is unable to write to the C:\Windows\TEMP\vmware-temp\vmware-Système\vmount-temp folder. In the English version of Windows 2008, this folder is C:\Windows\TEMP\vmware-temp\vmware-System\vmount-temp

Resolution

This issue is resolved in View Composer 2.7.
 
To resolve this issue in earlier View Composer versions:
  1. Create a local administrator account with name containing ASCII characters only.
  2. Change the logon account for VMware Universal File Access service to this local account.
  3. Verify you can start and stop the UFA service with this account.

Impact/Risks

UFA log files are written to %userprofile%\AppData\Local\Temp\vmware-temp.
 
However, the log collection process does not collect logs from this location and you need to manually gather the UFA log files, if needed.

Tags

view-composer  view-pool-create-fails

Update History

01/04/2012 - Added resolution steps

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

  • 0 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)
  • 0 Ratings
Actions
KB: