VMware Cloud Community
prakash9339
Enthusiast
Enthusiast

un able to connect to vcenter

pastedImage_0.png

0 Kudos
5 Replies
Shrikant_Gavhan
Enthusiast
Enthusiast

Hi Prakash,

Please check below KB article.

VMware KB: Starting the VMware VirtualCenter Server service fails with the error: Windows could not ...

Thanks and Regards,

Shrikant Gavhane.

Thanks and Regards, Shrikant Gavhane
0 Kudos
zXi_Gamer
Virtuoso
Virtuoso

That would be the most common message thrown about VCenter other than "A General Error has occured"

While restarting the service, please check at system logs under Event manager to deduce which process or service is failing to start the VC

0 Kudos
prakash9339
Enthusiast
Enthusiast

pastedImage_0.png

0 Kudos
King_Robert
Hot Shot
Hot Shot

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.

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.

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:

  1. Verify the actual name of the SQL Server instance used with vCenter Server.
    1. Start the ODBC Data Sources manager from the Control Panel > Administrative Tools > Data Sources (ODBC).
    2. Select VMware VirtualCenter DSN in the System DSN tab and click configure to see the details.
    3. The server name is shown in the Server edit box.
  2. Use the SQL Server command line tool to change the transaction log size limit.
    1. Start the command prompt.
    2. Run the command osql -S <server name from ODBC DSN> -E
    3. Run next SQL:
      1. go
      2. ALTER DATABASE [VIM_VCDB]
      3. MODIFY FILE ( NAME = N'VIM_VCDB_LOG', MAXSIZE = UNLIMITED )
      4. go
    4. Exit the command tool by typing exit.
0 Kudos
Madmax01
Expert
Expert

Hi theire, normally he pushes very helpfully Informations to the Eventviewer (eventvwr.msc). Based on that  > an helpfully Answer is better possible.

Best regards

Max

0 Kudos