dflint
Enthusiast
Enthusiast

View Composer 4 Build 21930 - Database cannot be found during install

Jump to solution

Latest releases of vSphere and View. DSN's test fine connecting to a SQL 2005 ruuning in Server 2008.

vCenter DB OK. Update Manager DB OK - on same SQL server. Unable to connect to finish View Composer install.

*"The database cannot be found.or a connection cannot be established. Check the DSN name to ensure that it is correctly entered."*

It is.

0 Kudos
31 Replies
M_25
Contributor
Contributor

Although not supported, it's running in a small test environment since last x-mas. And it works.

I can deploy winXP SP3 linked clones without problems.

The installation of View Composer was done without any problems. Actually I followed the instructions from the manual and probably what trimelater (see 3-feb-2010) did. Unfortunately I can't do the installation again, because people use this environment. Here's what's running now on vSphere 4 update 1, on seperate virtual servers:

  • SQL Server 2008 on Windows Server 2008 R2 Standard x64 (not supported)

  • vCenter server + View Composer 4 build 21930 on Windows Server 2008 R2 Standard x64 (not supported)

  • View 4 Connection server on Windows Server 2003 Enterprise Edition SP2

I would not recommend this for production environments.

Greetings from M@r$
0 Kudos
s1xth
VMware Employee
VMware Employee

I am running the exact same setup as explained above with no issues at this time. It sucks that VMware is so late to the game on the SQL compatibilities but I have zero problems using SQL 2008 and Server 2008 R2 as my hosting platform for vCenter and View Composer. Is it 'supported'? no. does it work? yes.

Blog: www.virtualizationbuster.com

Twitter: s1xth

http://www.virtualizationimpact.com http://www.handsonvirtualization.com Twitter: @jfranconi
0 Kudos
dTardis
Contributor
Contributor

You must have mised the post I made on the first page of this subject. LOL

0 Kudos
dflint
Enthusiast
Enthusiast

Well it’s been 4 months so to recap this unresolved issue.

Setup System DSN

Run C:\Windows\SysWOW64\odbcad32.exe

System DSN Tab – Add

Create New Data Source - Used SQL Native Client…

Correct server, database, credentials, etc.

Connection Tests Successfully.

Run View Composer Setup.

Type in the same DSN info.

Receive message: The database cannot be found or a connection cannot be established. Check the DSN Name to ensure that it is correctly entered.

All current versions of VMware.

vCenter Server = Windows Standard Server2008 R2

SQL Server = Windows Standard Server2008 SP2

SQL Database = SQL 2005 (x86)

When I called VMware 4 months ago I was told the server versions I am running are not supported for use with View Composer.

0 Kudos
s1xth
VMware Employee
VMware Employee

I have been using View Composer and vCenter 4 on Server 2008R2 and SQL 2008 in my test lab with no problems. View 4 is installed on a W2K3 server 32 bit server not 2008.

I just came from the Philly Users Group meeting and it was mentioned that View 4.5 will be supporting 2008 R2.

Sent from my iPad

http://www.virtualizationimpact.com http://www.handsonvirtualization.com Twitter: @jfranconi
0 Kudos
dflint
Enthusiast
Enthusiast

Unfortunately I'm not experiencing the same results.

I suppose I could call VMware again to see if anything has changed since January regarding what they support.

Glad it works for you though.

0 Kudos
s1xth
VMware Employee
VMware Employee

When you are trying to connect to the DSN, what type of Native Client did you create? Also, did you use the 32bit or 64bit? I could only get Composer to work if I created a 64bit DSN. For vCenter I used a 32bit DSN. To use the 64bit one just make sure you launch the ODBC utility from the Control Panel and create the 64 bit one from there. I need to check my lab to see if I used Native Client or not....

Blog: www.virtualizationbuster.com

Twitter: s1xth

http://www.virtualizationimpact.com http://www.handsonvirtualization.com Twitter: @jfranconi
dflint
Enthusiast
Enthusiast

OK you get the prize. I swear I've tried both versions of ODBC in the past. The DSN created using the 64 bit one would not connect to the database. Who knows at this point. The bottom line is, creating the DSN using the 64 bit version of ODBC, today, worked!

Thanks very much!

0 Kudos
s1xth
VMware Employee
VMware Employee

Awesome news!! Glad its working for you! I came across this via trial and error...:-)

Blog: www.virtualizationbuster.com

Twitter: s1xth

http://www.virtualizationimpact.com http://www.handsonvirtualization.com Twitter: @jfranconi
0 Kudos
DimkaPhantom
Contributor
Contributor

I had this issue today and I tried to create 64 bit DSN and it works!

I ran c:\WINDOWS\System32\odbcad32.exe and created DSN as described in manual.

It's so strange that vSphere needs 32 bit DSN, but Composer needs 64 bit.

0 Kudos
iamxCPx
Enthusiast
Enthusiast

I had this issue today and I tried to create 64 bit DSN and it works!

I ran c:\WINDOWS\System32\odbcad32.exe and created DSN as described in manual.

It's so strange that vSphere needs 32 bit DSN, but Composer needs 64 bit.

I had this issue today and I tried to create 64 bit DSN and it works!

I ran c:\WINDOWS\System32\odbcad32.exe and created DSN as described in manual.

It's so strange that vSphere needs 32 bit DSN, but Composer needs 64 bit.

I had this issue today and I tried to create 64 bit DSN and it works!

I ran c:\WINDOWS\System32\odbcad32.exe and created DSN as described in manual.

It's so strange that vSphere needs 32 bit DSN, but Composer needs 64 bit.

I had this issue today and I tried to create 64 bit DSN and it works!

I ran c:\WINDOWS\System32\odbcad32.exe and created DSN as described in manual.

It's so strange that vSphere needs 32 bit DSN, but Composer needs 64 bit.

I second that!

But the only difference is that I created the ODBC for the Composer from the Administrative Tools which is I'm sure it's the same thing.

I hope VMware people seeing this because they need to update their VMware View 4 evaluator's guide and it should say in BOLD;

+Need to install it on a 32-bit operating systems ONLY to follow this guide.+

Because if you're using the 64-bit like me;

VMware View Connection - Windows 2003 x64 Standard

VMware Virtual Center & View Composer - Windows 2003 x64 Standard.

You'll need to read this thread to get to where you want to be. Smiley Happy

THANK YOU AGAIN!!!

0 Kudos
TheTer
Contributor
Contributor

If your Composer is on a 2008 server, then create both a 32 bit DSN and a 64 bit DSN to your SQL2008 database. 32 bit is through Start-Programs-Administrative Tools-Data Sources and the 64bit is through Windows\SysWOW64\odbcad.exe Hope this helps

Community message 1434401

0 Kudos