During my experimental EdgeSight setup, I have to face different error, mostly because everything was not ready or not well configure on my side but it can happen. I have install two Edgesight web server (Esx nlb) and two SQL Reporting Services serverÂ (Esx nlb too) with a database store on a SQL 2005 cluster. I didn't had the hand on the setup of the two nlb so things where a bit hard to understand since there is quiet a lot of issue and things to do to enable two VMWare ESX nlb communication. (I'm still working on it, any informations are welcome :) ) I will update this post everytime I will have an error, I hope it will help some of you. Error : Setup was unable to locate the requiered SQL Server Client Tools. The SQL Server Client Tools can usually be located on the SQL Server installation disk. You just have to install client components of SQL Server 2005 (or 2008) and RTM first :) You must have database and SQL Login creation rights on the server. This message means the credentials choose to create / access database needs to have sysadmin rights on the database server, I still hevn't understand why but still. Â Error -2147217900: failed to execute SQL string, error detail: MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) [...] Â This error message happen when you don't have enough space where you choose to record SQL data. I think that would me near the same for log space. Â The report server address used to communicate with Reporting Services is invalid This message will occure when your SQL Reporting is not reachable. I had this issue until my SQL Reporting Services ESX nlb works very fine. Error publishing reports: Server was unable to process request. ---> Timeout expired. This is a typical message when a timeout occure when you're uploding templates to the SQL Reporting Services.