I cannot finish an installation of vc 2.5.

Environment parts are:

1 x Server with OS Windows 2003 SP1 R2 , DOTNet and SQL Native Driver installed for a fresh vc 2.5 installation

The DB Admin did gave me a SQL DB Instance on their SQL 2005 SP1 Cluster. The vc database login has the db_owner fixed database role on the VirtualCenter database and on the MSDB database.

although he did the following 6 stepps. This info comes from the kb http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=6565318&sliceId=1&docTypeID=DT_KB_1_1&dialogID=20315915&stateId=0%200%2020313452

The same info can be found in the ESX Server 3 Installation Guide http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_installation_guide.pdf

To configure a fresh installation:

1. Connect to your SQL Server 2005 server with SQL Server Management Studio.
2. Create a database login (*vclogin*) for VirtualCenter Server to use.
3. Create a new database (*VCDB*) and change the owner from <default> to vclogin.
4. Observe that vclogin maps to the dbo database user for VCDB.
5. Change the default database for vclogin from master to VCDB.
6. Install VirtualCenter Server according to the product documentation.

The db admin set SQL database recovery model for vc database to simple logging(maybe he did this when he cretaed the db). That is different to an upgrade installation. (http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_upgrade_guide.pdf - mentions the requirement for enabling bulk-logging):

For me it is not clear enough , if for a fresh installition bulk-logging is needed. In this thread http://communities.vmware.com/thread/120576 although from Jasonboche it is not clear enough.

So after we configured the sql db for vc and the sql properties , we wanted to install vc 2.5

On the vc the odbc was configured and the test was sucessfull.

Then started the installation of vc 2.5 and got the error message 25003 (Error 25003.Setup Failed to create the VirtualCenter repository)

Then look at vmware kb and found http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1003960&sliceId=1&docTypeID=DT_KB_1_1&dialogID=55140794&stateId=0%200%2055136713

Vmware tells for resolution :

Ensure that your database is installed in CASE INSENSITIVE mode.
Note: You may need to contact your Database Administrator (DBA) for assistance.

Although i looked at the the vminst.log file.

So now googled and found a vmware world 2006 docu http://download3.vmware.com/vmworld/2006/mdc9694.pdf where is written on page

1. VC is a case-insensitive DB application
2. Installation will fail with a case-sensitive collation

*
Although from the vc 2.0.2 release notes , Ensure that your database is installed in CASE INSENSITIVE mode

http://www.vmware.com/support/vi3/doc/releasenotes_vc202u1.html

VirtualCenter Server Does Not Support Case-Sensitive SQL Server Installation and Case-Sensitive SQL Server Database

If the DSN provided during the VirtualCenter Server installation points to a case-sensitive SQL Server instance or a case-sensitive SQL Server database, the installation fails and an error message is displayed. This is expected behavior. Before running the installation again, ensure that you have a case-insensitive SQL Server instance and a case-insensitive SQL Server database

So there is something in sql 2005 more to configure to get vc 2.5 installed.

Some more hints :

pierre gronau writes

Installation will fail with a case-sensitive collation http://communities.vmware.com/message/714197#714197

Should be SQL_Latin1_General_CP1_CI_AS instead of*
*SQL_Latin1_General_CP1_CS_AS

http://communities.vmware.com/thread/110310?tstart=16

Is there a password case-sensitive or password length problem?

http://communities.vmware.com/message/746277#746277

thats what i expected, also why i posted the comments above. As i said SQL2005 is case sensitive and its catching everybody out at the moment. Simply resetting the SQL users password may have cured your problem

Is vmware vc 2.5 sql database a sql 2000 database ? If so is then on a sql 2005 the db to set in sql 2000 compability mode?

An example for configuration https://knowledge.mcafee.com/article/797/612983_f.SAL_Public.html

Or look at the first screenshot database properties (scroll down) http://decav.com/blogs/andre/archive/2006/04/11/10.aspx

Although it is interessting that it is seemed to be teached.

search for "VC Install Issue: Case-sensitive SQL Server" at the following url : http://www.learnit.com/default.aspx?tabid=58&a=3&cID=1254

Tomorrow i will try this sql option.

Although there seems to be a password problem.

I had a password with spaces in it and I had the same 25003 error. Changing to a password with no spaces fixed it.

just finished installing VC on sql 2005 after reading this.... yes, make everything lower case when in doubt and it will work.

http://communities.vmware.com/thread/9524

So I have no spaces in password and i use a-z and 0-9 , can the password have 12 letters with upper and lower case?