Unable to login to vCenter Chargeback Manager

I was not able to use the vCenter Chargeback Manager in my home lab for a while. After booting the server, the login window showed this message: “An error has occurred. Please contact the system administrator or try again later”.

CBM-login-01Figure 1

After a quick search on the Internet, I have found VMware KB 1030532, unfortunately, it is not applicable in this situation.
Another source is the “Best practices and Troubleshooting Guide for vCenter Chargeback Manager 2.0.0.”. Page 23 presents a similar problem, as a probable cause it points to the database, which may has run out of disk space.

In my case the MS SQL did not ran out of disk space; however one of the error logs was larger than 14 GB, so time for some cleanup.

The Windows Application Log, showed what went wrong; the vCCM_User account, created during the installation of the server was not able to login, due to password expiration.

CBM-login-02Figure 2

For the installation of this server, see my previous post.

So time to start the “Microsoft SQL Server Management Studio” and look into the account created during the installation.

CBM-login-03Figure 3

Select the account and open the “Properties

CBM-login-04Figure 4

We are now able to reset the password. It also becomes clear what caused the problem. During the creation of the account, the option “Enforce password expiration” was enabled. This option and the other “Enforce password policy” use the locally defined policies. Read  more in this post.
So, to prevent future problems, remove the tick at “Enforce password expiration”.

CBM-login-05Figure 5

After restarting the database service and the vCenter Chargeback Manager service, the Login window looks like this. We are now able to login tothe application.

CBM-login-06Figure 6

As always, I thank you for reading. I welcome any suggestion and tips regarding MS SQL configuration.

Advertisements

One Response to Unable to login to vCenter Chargeback Manager

  1. […] a database user, in my case: vCCM_User. I have used SQL Server Authentication. UPDATE: read this post. Do not place a tick at “Enforce password […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: