View Events Database

[esnmb]

I am trying to setup the events db and I keep getting the "Database configuration error" message.  Our View environment is pretty small so I didn't create a full SQL installation.  We will have less than 200 users I believe for quite some time so I used SQL Express.

I have created the db called ViewEvents and created a sql user called view that has db_owner rights for the ViewEvents db.

In the View Admin console I enter the info but get the config error.   See attached.

[six4rm]

I also had all sorts of trouble configuring the Events Database. I ended up asking for advice in this thread - http://communities.vmware.com/message/1614812 - and managed to get it resolved.

My advice is...

- Check what port SQL is listening on (SQL Configuration Manager -> TCP/IP Settings).

- Check that your SQL user 'view' doesn't have a password policy enforced (this was my problem).

** EDIT **

I'd also use the FQDN of the SQL server.

[AndreTheGiant · Accepted solution]

I've follow this guide and it works:

http://www.thinkvirt.com/?q=node/222#

See also the note in the previous post about the FQDN.

Andre

[idle-jam]

have a look at this tutorial, it maybe helpful. http://www.thatsmyview.net/2010/08/30/using-the-event-database-in-view-4-5/

[esnmb]

VMware Support replied with this:

Just left a brief message on your mail. You do need a full blown MS SQL server to create event database.

Please let me know if that install you needed to know or you have other related concerns.

If you all were able to do it with SQL Express, what are they talking about?

[Poort443]

That's just not true. You can have the Events Database on an Express instance.

-Poort

[esnmb]

A message was left saying something about the events database needs remote connectivity...  The databases are on my vcenter server, so would this be a problem?

[six4rm]

That's simply not true. I'm using the SQL Express instance that installed with vCenter as my Events Database. There is remote connectivity, as long as you have it enabled within SQL. The guide that Andre linked to above looks spot on.

As I said in my previous post, just be sure that "Enforce password policy." is NOT ticked within the SQL user properties, that's where I was going wrong.

[esnmb]

I got it working.  I was using the incorrect port.  I had to use the IPAll port...  Thanks all.  Especially for the links as they helped a ton!