britgeek:Setting the Initial Catalog to the test database re-produced the error I was hitting before. We've double checked and even dropped and re-granted permissions for the service account on the views/tables on that database that it should be able to access without success.
Does the account need to have full access to the entire database for this to work?
In order to be able to detect the database schema, the account being used to access the database needs to at least have SELECT access to the database's following system views:
- systypes
- sysobjects
- syscolumns
And EXECUTE access to the following system stored procedure:
I can't say for sure that those will be enough, but it may be enough. Could you give that a try? In the end, it may be more practical to grant the account reader access to the whole database and deny access to certain DB objects that should be off limits.