EVDashboard 0.16
Last Updated on Thursday, 25 February 2010 10:44 Written by Jeremy Knight Monday, 11 August 2008 01:12
EVDashboard - Monitor your Enterprise Vault environment
EV Health Checks
System Services
MSMQ
Search Indexes
Disk Usage
User mailbox / archive properties
Archiving rates
Installation Instructions
Changelog
Installation
Notice:
This software is made up from various vbscripts which have been incorporated into the .asp pages of the site. Whilst every effort has been made to sure high quality code you should test this site thoroughly before putting it into your production environment.
It is highly recommended you install this into your test environment to verify functionality before installing into your production environment.
At the end of the day there is only one person who holds the responsibility for the integrity of your IT infrastructure; you. The authors of this software will not be held responsible for any adverse effects from the use of this software. You use at your own risk.
For the rest of the installation instructions please visit https://www-secure.symantec.com/connect/articles/ev-dashboard-installation. This makes it easier to maintain current, and accurate notes.
Change Log
For the up to date changelog pleasee see https://www-secure.symantec.com/connect/articles/ev-dashboard-changelog.
Subscribe to this comment's feed
Does a forum exist to discuss problems in getting EVDashboard to work?
I've installed it and created the database / tables. However, I can't connect to the database from the web page. I'm trying the "Test Database Connectivity" page and it returns the following to the page:
"Error: Cannot connect to server / database.
Error Number -2147467259: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "EVDashboard,1433" requested by the login. The login failed."
Check the SQL logs I can see the attempt coming it but it returns the error:
"Message
Error: 18456, Severity: 14, State: 16."
MT
Paul
Paul,
I have just addded forum threads for EV Dashboard. I suspect your problems are down to your SQL server denying remote connections on port 1433. SQL Express 2005 for example disables remote script SQL connections by default.
The other possibility is a firewall blocking that port.
Thanks,
Jeremy.
