VMware Horizon Community
prutter
Enthusiast
Enthusiast
Jump to solution

View Composer on vCenter 4.1

I recently upgraded my vCenter server to 4.1 and i'm trying to install view composer on this server.  Not quite sure about the database DSN.  I setup a 32bit DSN on that server and when i go thru the install i get an error.  I don't see the DSN i setup and when i try to create one with the istall the error i get is...Setup failed to execute teh ODBC Administrator : odbcad32.exe.  I'm guessing the error is because it's pointing to the 64 bitODBC and not the 32 bit.  This is a 64 bit server.  Just can't seem to get the install rolling.  Any thoughts??  Thanks.

Perry

Reply
0 Kudos
1 Solution

Accepted Solutions
logiboy123
Expert
Expert
Jump to solution

View Composer Server 2.5 is a 64bit application and requires a 64bit DSN.

Please see the following document for a full walkthrough;

http://terenceluk.blogspot.com/2010/10/installing-vmware-view-45-composer.html

Regards,

Paul Kelly

If you found this or any other post helpful, please consider making use of the points allocation system.

View solution in original post

Reply
0 Kudos
3 Replies
logiboy123
Expert
Expert
Jump to solution

View Composer Server 2.5 is a 64bit application and requires a 64bit DSN.

Please see the following document for a full walkthrough;

http://terenceluk.blogspot.com/2010/10/installing-vmware-view-45-composer.html

Regards,

Paul Kelly

If you found this or any other post helpful, please consider making use of the points allocation system.

Reply
0 Kudos
Bitoma
Contributor
Contributor
Jump to solution

You must create a 64bit DSN, but I've noticed that you have to enter the ODBC name manually in the wizard.

Reply
0 Kudos
mittim12
Immortal
Immortal
Jump to solution

You can also look at page 31 of the install guide for information on how to setup the DSN, http://www.vmware.com/pdf/view45_installation_guide.pdf.  

On a side note composer will work on X86 OS it's vCenter 4.1 that requires the X64.   We ran 4.5 on vCenter 4.0 update 2 X86 for at least a month before we moved over to vCenter 4.1