Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Starting the VMware VirtualCenter Server service fails with the error: Windows could not start the VMware VirtualCenter Server on Local Computer (1038138)

Last Updated: 9/9/2014Categories: TroubleshootingTotal Views: 94663Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Cannot start the VMware VirtualCenter Server service.

Manually starting the VMware VirtualCenter Server service by navigating to Computer Management > Services and Applications > Service > VMware VirtualCenter Server fails.

You see the error:

Windows could not start the VMware VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.

In the vpxd.log file of vCenter Server, you see the error:

Database error: "ODBC error: (42000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]The transaction log for database 'VMDB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases" is returned when executing SQL statement "delete from VPX_VMFS_EXTENT with (rowlock) where ID = 177"

Re-installing vCenter Server does not resolve the issue.

Resolution

This issue occurs when transaction log (.ldf ) size of the vCenter Server database exceeds the maximum limit.

To resolve this issue, change the recovery model to simple and shrink the transactional logs. For steps to troubleshoot transaction log issues in the Microsoft SQL database server, see Troubleshooting transaction logs on a Microsoft SQL database server (1003980).

This issue may also occur if the password for the account on the SQL database server used to connect to the vCenter Server database has expired.

To resolve this issue, ensure that the account password is valid. For more information, see VirtualCenter Server service fails to start with the error: The password for user account ' <username></username>' has expired (1012498).

For a vCenter Server installation with a database on an embedded SQL Server Express, the issue might occur if the transaction log size is reached.

To resolve this issue, verify the name of the SQL Server instance and change the transaction log size.

To verify the name of the SQL Server instance and change the transaction log size:

Verify the actual name of the SQL Server instance used with vCenter Server.

Start the ODBC Data Sources manager from the Control Panel > Administrative Tools > Data Sources (ODBC).

Select VMware VirtualCenter DSN in the System DSN tab and click configure to see the details.

The server name is shown in the Server edit box.

Use the SQL Server command line tool to change the transaction log size limit.

Start the command prompt.

Run the command osql -S <server name from ODBC DSN> -E

Run next SQL:

go

ALTER DATABASE [VIM_VCDB]

MODIFY FILE ( NAME = N'VIM_VCDB_LOG', MAXSIZE = UNLIMITED )

go

Exit the command tool by typing exit.

Related Information

For translated versions of this article, see:

• 日本語: VMware VirtualCenter Server サービスの起動が次のエラーで失敗する： Windows could not start the VMware VirtualCenter Server on Local Computer (2032731)

"The transaction log for database 'VIM_VCDB' is full" error on a Microsoft SQL DB server
VMware VirtualCenter Server service fails to start with the error: The password for user account 'username' has expired
VMware VirtualCenter Server サービスの起動が次のエラーで失敗する： Windows could not start the VMware VirtualCenter Server on Local Computer
启动 VMware VirtualCenter Server 服务失败并出现错误：Windows 无法在本地计算机上启动 VMware VirtualCenter Server (Windows could not start the VMware VirtualCenter Server on Local Computer)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant