View Single Post
Old 05-30-2005, 01:12 AM   #2 (permalink)
BlackBerry God
jibi's Avatar
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post

In SQL, expand Microsoft SQL Servers; expand SQL Server Group; expand LOCAL (or cluster name); expand Security; click on Logins. Make sure your BES service account is listed here. Right-click on the service account and click on Properties. Click on the Server Roles tab and make sure that everything is checked. Click on the Database Access tab and make sure that the BESMgmt database is checked (and user is dbo). Highlight BESMgmt (most likely already highlighted) and make sure Database roles (bottom portion) is checked for public and db_owner.

The above should give you database access for Windows Authentication connectivity.

You could add your own domain login to the BES SQL database (outlined above; substitute with your login) and test the permissions and connectivity from your local workstation by creating a new ODBC connection.

*Edit: I just noticed you posted on the other thread as well. That thread differs from yours because you have to enable network connectivity with MSDE 2000, whereas its already enabled in SQL 2000.
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.

Last edited by jibi : 05-30-2005 at 01:15 AM.