VMware Cloud Community
Petrolej
Contributor
Contributor
Jump to solution

Error 25003. Setup failed to create the vCenter Server repository.

Hello,

I am trying to install vCenter Server 4.0. When the installator tries to creator repository an error pops up:

Error 25003. Setup failed to create the vCenter Server repository.

I click OK and the installation rollups.

The last records in installation log are:

Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe"

Launch as logon user Administrator

Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe"

Process returned 3221225477

ERROR: Failed to create the VirtualCenter repository

Posting error message 25003

Description of our environment:

  • The vCenter service is running under the SYSTEM account.

  • Standalone edition in eval mode.

  • All ports are standard.

  • Using SQL2005 Express bundled in install media.

  • I have downloaded the trial version.

  • The server is VM on ESX with Win 2003 x86 SP2 CZE Standard Edition

  • The server is not in AD

  • Free disk space 7,5 GB

I also tried to create the database manully but no luck.

Thanks for any advise.

Reply
0 Kudos
1 Solution

Accepted Solutions
mmartin1977
Contributor
Contributor
Jump to solution

After install Win XP SP3 ENG everything works OK... So problem was really in language version of OS...

View solution in original post

Reply
0 Kudos
13 Replies
Troy_Clavell
Immortal
Immortal
Jump to solution

see if this offers some guidance

also, just in case

  • vCenter Server installation on Windows Server 2008 with a remote SQL Server database fails in some circumstances

If you install vCenter Server on Windows 2008, using a remote SQL Server database with Windows authentication for SQL Server, and a domain user for the DSN that is different from the vCenter Server system login, the installation does not proceed and the installer displays the following error message:

25003.Setup failed to create the vCenter repository.

</div>

Reply
0 Kudos
Petrolej
Contributor
Contributor
Jump to solution

Thanks Troy,

I have read the KB article but no luck. The article describes situation when custom DB is used. I am using bundled SQL Express DB so I cannot set case sensitivity of the DB. But I have also tried to install the DB manually - same result.

As to your another suggestion - I am on Win 2003 and I don't use remote SQL Server.

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Did you already check the requirements on KB1009080 - Installing ESX 4.0 and vCenter 4.0 best practices

Especially points 4 and 5!

André

Reply
0 Kudos
Petrolej
Contributor
Contributor
Jump to solution

Hi André,

I did check these requirements. The only thing is that the server is in a workgroup, not in a domain. But our another vCenter server is already installed without domain and it works without problem.

I tried the installation with both the SYSTEM account and the Administrator account. Same result.

I have read the compatibility matrix and on the page 17 it is said that vCenter Server 4.0 is not compatible with Windows 2003 Standard and Web Edition. Web Edition is understandable but why Standard edition?

Any tips?

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

The only thing is that the server is in a workgroup, not in a domain.

This is more a recommendation than must. vCenter Server works perfectly in a Workgroup.

I already installed vCenter Server in domains and workgroups a couple of times without any issues.

... it is said that vCenter Server 4.0 is not compatible with Windows 2003 Standard and Web Edition.

How I understand this, this refers to a Windows 2003 installation without at least SP1.

André

Reply
0 Kudos
mmartin1977
Contributor
Contributor
Jump to solution

I have same problem with installation - only difference is system on which I am installing vCenter Server - in my case is it Win XP SP3 CZE

Reply
0 Kudos
vRajan
Contributor
Contributor
Jump to solution

Try this,,

Check your DSN connection with DB.

..

I got the same issue, I created new SQL user account for vCenter and thats worked fine.

Check your SQL server authentication mode.

Thanks

Reply
0 Kudos
Petrolej
Contributor
Contributor
Jump to solution

Thanks. But as I said I used bundled SQL Express so every setttings are performed by the installer.

Anyway, I got it working. I tried to install it on Windows 2003 R2 Enterprise ENG.

God knows what did the trick - the change of edition from Standard to Enterprise or the change of language. Personally I bet on the language.

Czech: Martine, zkus to na operační systém s jiným jazykem, jestli můžeš. Rád bych pak věděl, jak jsi dopadl.

Cheers

Petr

Reply
0 Kudos
mmartin1977
Contributor
Contributor
Jump to solution

After install Win XP SP3 ENG everything works OK... So problem was really in language version of OS...

Reply
0 Kudos
smithriver
Contributor
Contributor
Jump to solution

VMware KB does not help and I am so sad to see that not much help available from Vmware.

IBM did a great job in providing solution for this problem.

Problem(Abstract)

Error 25003. Setup failed to create the VirtualCenter repository

Symptom

One may receive a message such as

"Error 25003. Setup failed to create the VirtualCenter repository"
when attempting to upgrade a VirtualCenter database to VC 2.5 version or  when attempting to install a new blank database at this version.

Cause

Security products such as McAfee Host Intrusion Software may contain policies that disable role changes in the SQL database.

Environment

VC 2.5 , MS SQL Server for VC database

Resolving the problem

Remove or reconfigure the security software to allow role changes in the SQL database.

https://www-304.ibm.com/support/docview.wss?uid=isg3T1010878&wv=1

Reply
0 Kudos
venkatesh710
Enthusiast
Enthusiast
Jump to solution

HI smithriver

There are no security softwares insatlled on my environment, any ideas ?

~venkat

Reply
0 Kudos
snaldurgkar
Contributor
Contributor
Jump to solution

I was also experiencing the same issue using remote SQL server 2008 R2 with windows authentication. enabling the 'sa' sql account with a password did the trick. On the ODBC configuration used the SQL 'sa' account and the installation completed successfully.

Reply
0 Kudos
ImranMogal
Contributor
Contributor
Jump to solution

Same issue using remote MSSQL server 2012 with windows authentication.

Create ODBC configuration used the MSSQL 'sa' account and the installation completed successfully.

Reply
0 Kudos