Horizon View 5.x Events Database Configuration Error

While configuring the Events Database in VMware Horizon View 5.x, you might see the following error message:

An error occurred while attempting to configure the database. Double check the database parameters and ensure that the database is not down, restarting, or otherwise unavailable

View Event Database Error

A customer had this problem for a while and they had tried quite a few things to resolve this without success.  All the usual things e.g. Firewall, UAC, database ownership etc. were as expected but all attempts to configure the database resulted in the error message shown above.

The environment was slightly different from the norm in the sense that the database server (Microsoft SQL 2008 R2) had “SQL Instances” configured.  So, I double-checked that TCP Dynamic Ports setting is disabled and a static port is configured for that instance. It was all good too!

Running out of options, I checked the collation set for the database.  It was set to “Case Sensitive” i.e. Latin1_General_CS_AS.  As far as I knew, it should be set to “Case Insensitive” i.e. Latin1_General_CI_AS so the database was deleted and recreated using that collation.  Once done, the configuration was retried and it worked immediately!

Collation is not something that one would look at normally and hence this post. It can happen if you don’t set anything on the database when creating it, in which case, the database is created with the collation set on the server.  That collation might not be what you want.  Obviously, it could also be a genuine mistake and set manually or via a script upon creation.  Either way, the fix is to recreate the database with the case-insensitive collation set.

Hope this helps!


By |2016-12-11T15:25:05+00:00March 13th, 2014|Horizon View, How To, View, Virtualization, VMware|5 Comments

About the Author:

Ather Beg is a technology and virtualisation blogger and is Chief Virtualogist at Virtualogists Ltd, which is a consultancy focusing on virtualised solutions. Ather has worked in IT for over 20 years and contributes his findings on this blog. In addition to holding several industry-related certifications, he has also been awarded vExpert status by VMware.


  1. […] persistently pestering me the message contained in the title of the post. On the Internet you can find quite a few hints as to deal with it, but none has proved to be helpful for […]

  2. andrew0349@gmail.com December 10, 2014 at 12:40 PM - Reply

    Hi Ather,

    I had very big exhausting experience with this problem. Every step was taken, nothing left out, to run the database properly. So in my case it was:
    I got a certificate from my sysadmin without private key! I installed it and it seemed ok. Then I tried to configure the database and it went wrong. Numerous days and hours and nothing until:
    I ran mmc and added the certificate add-in and went to Certificates/Personal/Certificates and right click on my installed certificate and disabled for all intended purposes.

    What a surprise after I restarted the service and tried to add the DB. It smoothly connected.

    But be careful “ODBC connection is not same as direct connection”. I had no problems with ODBC but with the direct connection. In this case it was Horizon View 6.0.1 Connection Server which needed this direct connection.

    Best regards,

    • Ather Beg December 10, 2014 at 12:43 PM - Reply

      Cheers Andrew!

      This is great and very helpful feedback. I’ll definitely keep this in mind.

      Best regards,


  3. Joseph May 23, 2015 at 9:50 PM - Reply

    Thanks Ather. It’s not a rocket science to configure event database but I always fail to configure this first time 🙂

    There is an alternate option to configure event database i.e syslog server, local / UNC file event logging.



    • Ather Beg May 25, 2015 at 11:25 AM - Reply

      Thanks Joseph. Indeed, it isn’t rocket science to configure the events database but still, there are many ways in which one can get it wrong. Case in point the article above – not a common error!

      Of course, there are many other options but the client in this case, wanted the events database itself 🙂


Leave A Comment

%d bloggers like this: