A moment of Bazinga: SQL Server and View Events configuration

Last modified date

Comment: 1

bazinga-bazzinga-lol-sheldon-cooper-tbbt-Favim.com-234798This past week I’ve been working on a variety of projects, including my home lab. I’ve been wanting to have a lab I can “use and abuse” to find all the ins and outs I can for the whole Horizon suite. For me, a lot of it centers around View and its configuration. Within our Education classes a lot of that is already pre-configured. This is done for both the instructor’s benefit (less troubleshooting) and the student’s (more consistent and better lab experience). But that also hides certain things from view. In particular, the SQL setup.

Installing View is easy but configuring SQL to work for things like the Events Database was troublesome. I spent nearly three days trying to figure out why I couldn’t get the Connection Server to talk with the SQL server. I had disabled all firewalls, had ensured proper name resolution in place, etc. I could telnet to the port but just didn’t seem able to connect to the service.

Anytime I get really stuck on a technical problem, my first stop is Google Search. Not surprisingly, my first hit was VMware’s KB about “Configuring VMware View Event database fails with the error: An error occurred while attempting to configure the database (1029537) “. I went through the check list and found that it was point 7 that I was hitting.


When I did the original install of Windows SQL 2008, I had configured the server for both SQL authentication and Windows authentication. Since the default account was using Windows authentication (and this isn’t supported), I had to create a new account specifically for the Events database. It’s a fairly simple process.

Screen Shot 2013-09-20 at 4.56.35 PM

1. Log into your SQL server.

2. Start Microsoft SQL Management Studio

3. Connect to your instance where the Events database resides (you can do this with Windows authentication)

4. Navigate to the Security –> Logins folder

5. Right-click Logins folder and choose New Login

6. Enter a login name (it’s ideal to not associate this with AD for security reasons)

7. Make sure the authentication is set to SQL Server Authentication

8. Set other settings as you may need for your environment.

9. Once ready, click the OK button

10. Then right click on the new account created and select Properties

11. Go to User Mapping

12. check the box beside the Events database and ensure that the Default Schema is set to dbo and the Databse Role Membership has db_owner selected.

Screen Shot 2013-09-20 at 5.02.27 PM13. Click OK.

Then configure the Events database connection on the View Connection server through the View Administrator interface.





Oh, where to begin? Let's see.. I lived in the US for 13 years (3 years in NYC and 10 years in Los Angeles area). I'm a huge MMORPG fan (I've been a die-hard World of Warcraft player since mid-2007 -- For the Horde!). And have numerous tattoos, including one about VMware and one about Warcraft. I enjoy the occasional cigar with a single malt (for a while, I even had a cigar aficionado blog). I used to enjoy long distance solo cycling and am hoping to restart it here in Nova Scotia. I live just outside of Halifax, Nova Scotia with my wife, our 3 cats and our Golden Retriever.

1 Response

I'd love to hear from y'all. Leave me a message or comment!

%d bloggers like this: