View 4.5 Event Database Configuration

[Poort443]

I have some trouble adding the View 4.5 event database. It's a SQL Express 2005 on the vCenter server. It's configured to listen to static port 1433. I use SQL authentication, and an SQL account. I've attached screenshots with the settings. I keep getting "an error occurred while attempting to configurate the database" Anybody here know what I'm doing wrong? I'm thinking maybe the database name should be in a different format, but I've tried different things without success.

Tia,

-Poort.

[Poort443]

Great to hear it's working now. I should award points to myself

[mclark]

Glad you got it going!

[willrodbard]

Hi Guys,

I just wanted to add my 2 pence (cents for the US) worth.

I was having the same issues and couldn't for the life of me get this to work. I read through this post as well as a few others including this one:

http://www.thatsmyview.net/2010/08/30/using-the-event-database-in-view-4-5/

None seemed to help, even creating a new SQL Express dbase on the View server itself as per the above blog.

My environment consists of a 64bit SQL 2005 install that has the vCenter, View Composer and VUM databases instances on.

I added the ViewEvents database, and tried all of the hint and tips to get it working to no avail.

In the end I went back to thinking about the ODBC connector, I found I had used the SQL Native client driver to create the connection, I deleted this and changed it to the "SQL Server" driver instead and lo and behold this ended up working for me.

The only thing I now need to confirm is whether or not the mixed authentication mode actually helped or not.

Thanks to all of the rest of you for your posts.

If like me you are stuck and all the other posts didn't fix it check out the ODBC connection.

cheers

Will

I wish VMware produced a decent install and config doc for this new feature

[JackMac4]

I'll post this to some of our internal lists and see if we can get some better documentation in this regard.

[willrodbard]

JackMac4

You're very kind sir, thanks

Will

[mjpagan]

I would hurry up with that documentation because I'm guessing this issue is more widespread. I am also having the same issues and none of the above fixes have worked.

Mike P

MCSE, VCP3/4

[Eknapen]

i had these exact same issues. adjusted all the stuff i needed to adjust and just diddnt resolve the issue.

troubleshooted the ODBC connection and tested the dataconnection. it all worked but when i used the VMware view administration console it kept telling me that it could not connect.

The problem at my end was a JAVA plugin issue in my current Internet browser. i used a other system with a diffrent version of java and diddnt got the error message and the VMware view administration console adjusted the settings and enabled the Event Database.

error message that triggerd me:

AJP connection test failed: com.vmware.vdi.ob.tunnelservice.da: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error

[nickgcdha]

Hi, Had similar issues and fixed it by creating an account in the database. Here is the link:

http://msdn.microsoft.com/en-us/library/aa337562.aspx

I am using a dedicated windows 2008 r2 server with sql 2008 installed. My vcenter and view database are on the same server.

[jjgunn]

Thanks everyone for your help.

Since the View Installation pdf tells us to use SQL authentication only, by default SQL 2008 uses windows auth only.

You must switch SQL to mixed mode. Once I made the switch, the login was successful.

This of course assumes you have the proper TCP/IP ports open and access thru the firewall

[JRendon20111014]

Use SQL Authentication - easy to overlook

Verify Password - as the logs from VMWare don't tell you this, just says can't log in

Verify SQL Ports - one of our SQL Servers had a miss configured port (mostly finger fumble) as 14333 {d'oh!}

I'd like to say thank you for those can came before me and troubledshooted this error, it has helped me in my troubleshooting.

[TexRob]

It's absolutely absurd that in 2013 VMware forces you to use SQL auth.  From an administration standpoint, using SQL auth is terrible.  It's silly that nowhere in the process does VMware bother to mention that you can't use a Windows AD account to setup an event database, not even in their KBs.

[noobuser]

Agreed, it sucks big time. But it is stated in their documentation and as well on the documentation center.

VMware View 5.0 Documentation Center

Configure the Event Database
The event database stores information about View events as records in a database rather than in a log file.

You configure an event database after installing a View Connection Server instance. You need to configure only one host in a View Connection Server group. The remaining hosts in the group are configured automatically.

You can use Microsoft SQL Server or Oracle database reporting tools to examine events in the database tables. For more information, see the VMware View Integration document.

Prerequisites
You need the following information to configure an event database:

■  The DNS name or IP address of the database server.

■  The type of database server: Microsoft SQL Server or Oracle.

■  The port number that is used to access the database server. The default is 1521 for Oracle and 1433 for SQL Server. For SQL Server, if the database server is a named instance or if you use SQL Server Express, you might need to determine the port number. See the Microsoft KB article about connecting to a named instance of SQL Server, at http://support.microsoft.com/kb/265808.

■  The name of the event database that you created on the database server. See Add a Database and Database User for View Events.

■  The username and password of the user you created for this database. See Add a Database and Database User for View Events.

Use SQL Server Authentication for this user. Do not use the Integrated Windows Authentication security model method of authentication.

■  A prefix for the tables in the event database, for example, VE_. The prefix enables the database to be shared among View installations.