While working with a customer in a new VDI design and implementation a problem was brought to my attention in regards to some of the configuration items in View 4.5 in relation to Microsoft SQL Server 2008. The issue that was happening had to do with the configuration of the view events database. While trying to add the SQL Server 2008 database to in the View Admin Console the system kept generating the same error message, even thou all the information was accurate and the database was already available on the server. The error is displayed in the screenshot below:
View Events Database Error
The problem here has to do with authentication. In order to configure the View Events database correctly you have to use a SQL Server base account and not a Windows based account. This is a requirement for this to work. The environment on which this View implementation was being deployed was brand new and included new installations and instances of SQL Server 2008. All of the SQL Servers were configured for Windows based authentication only (single sign-on). The fix it’s somewhat simple as long as there aren’t any constraints that will prevent changing or updating the authentication method of the SQL Servers. The servers have to set to support both methods of authentication Windows, and SQL based. The screenshot below displays the location where to make the necessary changes on the SQL Servers.
SQL Server 2008 Authentication Settings
After making those changes and creating a SQL based account for that database the configuration of the View Events database succeeded without any issues.Google+