An error message received during installation on a monitored host:
"SQL Server does not exist or access is denied'
This is a Microsoft OLEDB error message and not specific to our product.
Microsoft's own knowledge base article to resolve this is here: http://support.microsoft.com/kb/328306
In the context of Performance Analysis for SQL Server, we are trying to establish an OLEDB for SQL Server connection from the middleware to the monitored host.
It can happen for several reasons, some of which are listed here...
A simple test to determine where the problem lies is in the 'Additional Information' section.
It is recommended to go through it before attempting any of the following solutions.
Performance Analysis for SQL Server will not be able to install properly unless you get a successful test using this method.
For a simple test, we try a basic OLEDB connection from the middleware to the monitored host:
1) On the middleware server, right click on the desktop and select 'New -> Text Document' and change the name of this file to 'test.udl'. This will create a Microsoft Data Link file.
2) Double-click this file, and on the 'Provider' tab, make sure that 'Microsoft OLE DB Provider for SQL Server' is selected.
3) Click on the 'Connection' tab, and enter your SQL Server instance name in box 1 by entering it or selecting it from the dropdown.
4) If using Windows authentication to connect it will use your currently logged in Windows user (if you need to use another user you must log off the server and log in again using the proper user). If using SQL Server authentication, enter the username and password for that user.
5) Click on either the dropdown list for 'Select the database on the server' or the TEST button. If you get a list of databases, the permissions are ok, if you get 'test connection succeeded' you are also ok.
6) If the test returns 'SQL Server does not exist or access denied' then proceed to the possible list of resolutions.