csa86
Contributor
Contributor

Error saving vCenter entry

Jump to solution

Hi

I am trying to add my vCenter Server with Composer enabled into VMWare View. When enabling the "Enable View Composer" checkbox it finds the proper domain but it does not let me save it. I get the error "Error saving vCenter entry". I can save it, if I disable the composer settings.

VMWare View Server:

  • Windows 2008 64-bit
  • VMWare View 4.5

VMWare vCenter Server:

  • Windows 2008 64-bit
  • VMWare vCenter Server 4.1.0
  • VMWare View Composer 2.0.0
  • Microsoft SQL 2005

I have created a new Database for viewComposer and added the System-DSN. The View Composer is running on port 4141

Any hints on what this could be?

Screen shot 2010-12-24 at 8.30.43 AM.png

0 Kudos
1 Solution

Accepted Solutions
kermic
Expert
Expert

Can you double check composer version?

Composer 2.0 will not be fully functional with View 4.5, you need to upgrade to Composer 2.5.

quote from KB http://kb.vmware.com/kb/1027095 : Until both View Connection Server and View Composer are upgraded, View Composer operations do not work. If you have View Connection Server 4.5 and View Composer 1.0 or 2.0, you can connect to the desktops, but no new linked-clone desktops can be created. Also, recompose, rebalance, and refresh operations do not work and you cannot edit the settings for linked-clone pools

WBR

Imants

View solution in original post

0 Kudos
12 Replies
pcerda
Virtuoso
Virtuoso
Hi,
Remember the account you are using for Composer must have some permissions on Active Directory and vCenter.
On Active Directory:
The following list shows all the required permissions for the user account, including permissions that are assigned by default:
  • List Contents
  • Read All Properties
  • Write All Properties
  • Read Permissions
  • Create Computer Objects
  • Delete Computer Objects
On vCenter, the account must have this permissions:

  • Folder
    • Create Folder
    • Delete Folder
  • Virtual Machine
    • Configuracion
      • Add or remove device
      • Advanced
      • Modify device settings
    • Interaction
      • Power Off
      • Power On
      • Reset
      • Suspend
    • Inventory
      • Create New
      • Remove
    • Provisioning
      • Customize
      • Deploy Template
      • Read Customization specifications
  • Resource
    • Assign virtual machine to resource Pool
  • Datastore
    • Allocate Space
    • Browse datastore
    • Low level file operations
  • Virtual Machine
    • Inventory (all)
    • Configuration (all)
    • State (all)
    • Provisioning
      • Clone Virtual Machine
      • Allow disk access

  • Resource
    • Assign virtual machine to resource pool
  • Global
    • Enable Methods
    • Disable Methods
    • System Tag
  • Network
    • All
Regards / Saludos - Patricio Cerda - vExpert 2011 / 2012 / 2013
0 Kudos
kermic
Expert
Expert

Can you double check composer version?

Composer 2.0 will not be fully functional with View 4.5, you need to upgrade to Composer 2.5.

quote from KB http://kb.vmware.com/kb/1027095 : Until both View Connection Server and View Composer are upgraded, View Composer operations do not work. If you have View Connection Server 4.5 and View Composer 1.0 or 2.0, you can connect to the desktops, but no new linked-clone desktops can be created. Also, recompose, rebalance, and refresh operations do not work and you cannot edit the settings for linked-clone pools

WBR

Imants

0 Kudos
csa86
Contributor
Contributor

Thanks! That solved the issue

0 Kudos
meltingpot24
Contributor
Contributor

Hi

I am trying to add my vCenter Server with Composer enabled into VMWare View. When enabling the "Enable View Composer" checkbox it finds the proper domain but it does not let me save it. I get the error "Error saving vCenter entry".

VMware vCenter Server:

  • Windows Server 2008 R2 Standard 64-bit
  • Microsoft SQL Server 2005
  • VMWare vCenter Server 4.1.0 (build 258902)
  • VMWare View Composer 2.6.0-349155
  • I have created a new Database for View: view_composer_db

VMware View Connection Server:

  • Windows Server 2003 Enterprise Ed SP2
  • VMware-view_connection server-4.6.0-366101

Active Directory VM

  • Windows Server 2008 R2 Standard 64-bit
  • domain: vmviewcsdc.vmlab.com

The user has "administrator" role for vCenter, View Manager and Active Directory and can login correctly as VMVIEWCSDC\buonam on View Admin Console.

Is anyone getting into the same error?

Thanks for your support

0 Kudos
Linjo
Leadership
Leadership

Do you have any vShield Trial Licenses registred on the vCenter? If so, try to remove the licence and try to add the vCenter again.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
meltingpot24
Contributor
Contributor

Thanks for the quick reply Linjo.

No trial licenses installed!

screenshot attached

Thanks

0 Kudos
Linjo
Leadership
Leadership

In the screenshot there are several vShield Licenses installed.

Remove them and try again...

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
meltingpot24
Contributor
Contributor

Hi,

I've removed the three vShield components and disabled UAC on vCenter 2008 VM.

Same error 😞

0 Kudos
meltingpot24
Contributor
Contributor

Server Address: WIN-1C4DHD8BSM7

VMVIEWCSDC\buonam failed to add VC server https://WIN-1C4DHD8BSM7:443/sdk

What /sdk means?

Server Address: WIN-1C4DHD8BSM7.vmviewcsdc.vmlab.com

VMVIEWCSDC\buonam failed to add VC server https://WIN-1C4DHD8BSM7.vmviewcsdc.vmlab.com:443/

Thanks

0 Kudos
Linjo
Leadership
Leadership

Is name-resolution working? Is it a supported VC version?

Try FQDN:s.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
meltingpot24
Contributor
Contributor

Yes, name-resolution is working

screenshot attached

Try FQDN:s.

VMVIEWCSDC\buonam failed to add VC server https://WIN-1C4DHD8BSM7.vmviewcsdc.vmlab.com:s:44

It seems adding 5 characters at the end of the FQDN

:s:44 instead of :443/

crazy!!!

0 Kudos
jaffanz
Enthusiast
Enthusiast

Kia Ora.

Same issue here; name not vcenter. dns resolving fine across/between boxes. changed to domain admin and administrator role ad account. removed the vshield edge license i had and rebooted the vc. Problem is with latest view 4.6 against vsphere 4.1update1.

any thoughts?

0 Kudos