VMware Cloud Community
bluemoon
Contributor
Contributor

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

Hi everybody,

after searching this forum and a lot of other sites I decided to ask directly - unfortunately I didn't find any help elsewhere.

I'm running a vCenter Server 5 under Windows Server 2008 R2 Enterprise, local MS SQL 2008 R2 Standard (10.50.2500.0) installed. Both localized - German.

Now my problem: I want to update/upgrade from 5.0 to 5.0U1. I can start the Setup and it detects the installed version. It tells me the installed version will be upgraded - so far okay. Right at the end of the process there occurs an error: Error 25004.Setup failed to create the vCenter Server repository.

I have checked my ODBC connections - everthing fine there. The vminst.log says:

VMware VirtualCenter-build-623373: 04/09/12 15:14:16 --- CA exec: VMFormatDb
VMware VirtualCenter-build-623373: 04/09/12 15:14:16 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe"
VMware VirtualCenter-build-623373: 04/09/12 15:14:16 Launch as logon user administrator
VMware VirtualCenter-build-623373: 04/09/12 15:14:16 Found "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe"
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 Process returned 0
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 Successfully created the VirtualCenter repository
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 End Logging
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 Begin Logging
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 --- CA exec: VMUpdateDbVersion
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 ----------UpdateDbVersion():---------
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 SQLBindCol: 0
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 DbFetchResults(), Return code SqlFetch result: [0]
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 DbFetchResults(), SqlFetch result: [0]
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 record pushed: [501]
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 DbFetchResults(), Exited normally, SqlFetch result: [100]
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 SQLRETURN value is: 0
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 SQLRETURN value is: 100
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 ERROR: Failed to get SQL error msg: 100
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 Failed to update VC level version.
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 ERROR : Unable to update the database version.
VMware VirtualCenter-build-623373: 04/09/12 15:14:33 Posting error message 25004
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 MsiProcessMessage returned: 1
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 End Logging
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 Begin Logging
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 --- CA exec: VMRollbackUpdateDbVersion
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 ----------RollbackDbVersion():---------
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 Executing query: UPDATE VPX_VERSION SET VER_ID= WHERE VER_ID=501
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 SQLRETURN value is: -1
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 SqlState: <42000>, NativeError: <156>, msg: <[Microsoft][SQL Server Native Client 10.0][SQL Server]Falsche Syntax in der Nähe des WHERE-Schlüsselworts.>, msgLen: <106>
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 ODBC Error: [Microsoft][SQL Server Native Client 10.0][SQL Server]Falsche Syntax in der Nähe des WHERE-Schlüsselworts.
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 Failed to insert database version.
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 ERROR : Unable to rollback the database version.
VMware VirtualCenter-build-623373: 04/09/12 15:14:44 Posting error message 25004
VMware VirtualCenter-build-623373: 04/09/12 15:19:40 MsiProcessMessage returned: 1
VMware VirtualCenter-build-623373: 04/09/12 15:19:40 End Logging
VMware VirtualCenter-build-623373: 04/09/12 15:19:54 Begin Logging
VMware VirtualCenter-build-623373: 04/09/12 15:19:54 --- CA exec: VMRollbackProxyXml
VMware VirtualCenter-build-623373: 04/09/12 15:19:55 Getting Property CustomActionData = C:\ProgramData\VMware\VMware VirtualCenter\;4f82e020
VMware VirtualCenter-build-623373: 04/09/12 15:19:55 Found "C:\ProgramData\VMware\VMware VirtualCenter\proxy.xml"
VMware VirtualCenter-build-623373: 04/09/12 15:19:55 C:\ProgramData\VMware\VMware VirtualCenter\proxy.xml file attributes changed successfully
VMware VirtualCenter-build-623373: 04/09/12 15:19:55 Did not find file/directory: "C:\ProgramData\VMware\VMware VirtualCenter\proxy.xml.4f82e020"
VMware VirtualCenter-build-623373: 04/09/12 15:19:55 Cannot copy non-existent file: C:\ProgramData\VMware\VMware VirtualCenter\proxy.xml.4f82e020
VMware VirtualCenter-build-623373: 04/09/12 15:19:55 End Logging
VMware VirtualCenter-build-623373: 04/09/12 15:20:01 Begin Logging
VMware VirtualCenter-build-623373: 04/09/12 15:20:01 --- CA exec: VMCleanupRegistry
VMware VirtualCenter-build-623373: 04/09/12 15:20:01 Getting Property TEMPLATE = x64
VMware VirtualCenter-build-623373: 04/09/12 15:20:01 Warning: Deleting a key that isn't empty: "HKEY_CURRENT_USER\VMW"
VMware VirtualCenter-build-623373: 04/09/12 15:20:01 Warning: Deleting a key that isn't empty: "\InstRTPaths"
VMware VirtualCenter-build-623373: 04/09/12 15:20:01 End Logging

As you can see, there is a German SQL error. I am wondering about: SQL Native Client 10.0 but SQL Server 10.5 ? Is this correct? Can this work? Could this be my problem or do you have any other hints for me?

Any help highly appreciated!

Chris

Tags (4)
Reply
0 Kudos
18 Replies
JasonBurrell
Enthusiast
Enthusiast

I had the same issue when updating from 4.1 to 5.0 U1 and I ended up installing vSphere 5.0 with no problem.  Seems to be a problem that only shows up in vSphere 5.0 U1.  I would love to know the fix.

I'm running SQL 2008 R2 SP1 English with the same version of the native client.

Reply
0 Kudos
JasonBurrell
Enthusiast
Enthusiast

Upon futher research I had a couple other issues that might have caused this.  During the initial try though the upgrade I got an error about a sql statement not executing.  This was due to the log files not being set to unrestricted growth.  The fix requires that the SQL DB is restored.  So it's possible that I had a 1/2 upgraded database and that's why I got the error about the vCenter Server repository.  Restoring the DB and then running the upgrade again did not produce the same error.

Reply
0 Kudos
bluemoon
Contributor
Contributor

Hi Jason,

thanks for your help. I had this error without noticing any prior errors - so I'm not sure if there were other SQL script not executed. I found no messages in the logs pointing in this direction.

So, should I try to set the log file size to unlimited growth rate? In my installation it is also limited (to about 2 Gig).

Even if I would I can not restore to an older backup. I will loose all the data and this is not acceptable for us. The vCenter is running fine without Update1. So there cannot be a big problem with my database (I'm pretty sure).

Looking into the claimed table VMW.VPX_VERSION I see VER_ID is 500 and VERSION_VALUE set to VirtualCenter Database 5.0.

Seems to be correct.

Reply
0 Kudos
JasonBurrell
Enthusiast
Enthusiast

If your database is running fine then I would just take another backup and try the update with the log files set to unlimited growth.  My log files were also limited to 2GB and it presented a problem.

Hope it helps!

Reply
0 Kudos
bluemoon
Contributor
Contributor

When I set the filesize to unlimited it sets the size to 2.097.152 MB (2TB) As of MS this is standard http://msdn.microsoft.com/en-us/library/bb522469.aspx

MAXSIZE { max_size| UNLIMITED }

Specifies the maximum file size to which the file can grow.

max_size

Is the maximum file size. The KB, MB, GB, and TB suffixes can be used to specify kilobytes, megabytes, gigabytes, or terabytes. The default is MB. Specify a whole number and do not include a decimal. If max_size is not specified, the file size will increase until the disk is full.

UNLIMITED

Specifies that the file grows until the disk is full. In SQL Server, a log file specified with unlimited growth has a maximum size of 2 TB, and a data file has a maximum size of 16 TB. There is no maximum size when this option is specified for a FILESTREAM container. It continues to grow until the disk is full.

I can't see any problems anymore.

But the update still stops at the same point...

Reply
0 Kudos
rebaudin
Contributor
Contributor

Hello,

Additionally to this issue I had some network issues (sometimes the RDP disconnected...)

If it helps someone. I have fixed this issue by changing the IP address of my vcenter. It looks like there was something wrong with the IP address configured...

I didn't investigated further, because of time...

Regards,

Regis

Reply
0 Kudos
skywalkr
Contributor
Contributor

Ran into this one upgrading from vSphere 4.1 --> 5.0 U1a when we encounted the dreaded DNS resolution message and after much frustration, continued anyway and the install of course failed.   Lesson, if the install cannot find the vCS via reverse lookup - stop, fix it, do not past that point until it is fixed.  This message started appearing on all following attempts to upgrade after we fixed the DNS lookups.  We contacted VMware Support.   After some initial attempts to rectify, we concluded it was due to the aborted install which did not rollback the database changes - even though it said it did - the logs indicated otherwise.

Solution:  Per VMware support we:

1) Backed out of the current install

2) Rebooted the system

3) Restored the vCS Database (SQL 2008) from the SQL backup taken prior to attempting the upgrade

4) Restarted the install

Install completed.

Later, GC Mobley
Reply
0 Kudos
leaffan
Contributor
Contributor

Thanks for the steps.

I came across this error after my .iso disconnected during the vCenter 5.0 U1 database upgrade from 4.1.

  • Rollback
  • Reboot
  • Restore DB from backup
  • Reinstall

Everything worked and another reason to always remember to backup your databases before performing any upgrade.

Reply
0 Kudos
Ann8
Contributor
Contributor

Thanks for this great info.  I had the exact same errors as Jason.  Restored the DB....set the logs to unrestricted growth and ran the 5.0 U1 installer again.  It worked like a charm!!

Reply
0 Kudos
aechols
Contributor
Contributor

Confirmed, this also worked for me. Smiley Happy

Reply
0 Kudos
kurbycar32
Contributor
Contributor

I had the same error and none of the above fixes helped.  I was able to resolve the issue by creating a new DSN and selecting that connection when prompted to reuse the database.  I am running SQL2008r2 express and noticed that the DSN Vcenter was trying to use was using the old SQL2005 client to connect.  I made sure to create a similar DSN using the 2008 driver and it worked just fine.

Reply
0 Kudos
CraigRJET
Contributor
Contributor

Thanks.  Restoring DB and setting logs to unrestricted growth worked for me also.

Reply
0 Kudos
DaveatWin
Contributor
Contributor

None of the above worked for me.    I'll post if I get it sorted.

Reply
0 Kudos
Doug_Yoder
Contributor
Contributor

Were you able to get this issue fixed then? I've tried to re-install several times (after database restore), and made sure the database is set to unrestricted growth.

Reply
0 Kudos
skywalkr
Contributor
Contributor

FWIW, when installing we

1)  switch the vCS database recovery models from SIMPLE into BULK-LOGGED and then when done we switch them back to SIMPLE. 

2) We have had installs fail when left in Simple and at one time, I think even VMware recommended this during vCS installs. 

3) We also preallocated the vCS DB to 20+GB with a max of 40+GB and the logs to 2GB/8GB Max as a performance enhancement.

Cheers. 

Later, GC Mobley
Reply
0 Kudos
DaveatWin
Contributor
Contributor

Unfortunately no.   I opened a service request with Vmware, restored the db from a backup and tried installing components in differing  orders.    All with no luck.   It was finally suggested to install from scratch.  I am basically going to rebuild my whole VDI infrastructure because I don't want remnants of all the mistakes made along the way hanging out there.    I don't have a lot of confidence in the upgrade process.  My coworker has done of scratch installs of the latest version without any trouble.

Reply
0 Kudos
vmtntokheim
Contributor
Contributor

Hi,


Sorry for opening an old threat like this but I have the same issue (but different logging.)

I'm trying to upgrade my vCenter 5.0 U2 to 5.0 U3 and get the following error when the upgrade is almost complete:

error 25004. setup failed to create the vCenter repository

But my logging is a little different (just a small piece from vminst.log)

----------UpdateDbVersion():---------

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 SQLBindCol: 0

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 DbFetchResults(), Return code SqlFetch result: [0]

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 DbFetchResults(), SqlFetch result: [0]

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 record pushed: [503]

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 DbFetchResults(), Exited normally, SqlFetch result: [100]

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 SQLRETURN value is: 0

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 SQLRETURN value is: 0

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 SQLRETURN value is: 0

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 Value cache 9223372036854775807.

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 SQLRETURN value is: 100

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 ERROR: Failed to get SQL error msg: 100

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 Failed to update VC cache size.

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 ERROR : Unable to update the database version.

VMware VirtualCenter-build-1300600: 11/07/13 13:15:27 Posting error message 25004

VMware VirtualCenter-build-1300600: 11/07/13 13:15:36 MsiProcessMessage returned: 1

VMware VirtualCenter-build-1300600: 11/07/13 13:15:36 End Logging

As you can see, in my case the logging says "Failed to update VC cache size." not "Failed to update VC version."

Is there a solution? I've already tried all the possible solutions in this threat.

Thanks!

Regards

Reply
0 Kudos
skywalkr
Contributor
Contributor

Nothing specific but I would check

1) The things I outlined a couple of posts back

2) Ensure that the DB logs are either preallocated large and can grow or that growth or space is not restricted.

3) Uninstall, reboot and then reinstall vCS clean.

This smells like an SQL issue.

Sorry, that's all I can think of..

Cheers.

Later, GC Mobley
Reply
0 Kudos