MailSite Fusion - Knowledge Base

MailSite Fusion is a mail server, calendar server and contact server that works with Outlook 2007, iPhone, Windows Mobile and BlackBerry smartphones and provides a low cost alternative to Microsoft Exchange Server

Support Forum Knowledge Base Contacts Open Case Emergency

MailSite Knowledge Base

Enter text to search for or enter the document ID number.
Search: Match: Products:	Doc ID:

Common pitfalls when installing MailSite in SQL Connector Mode

Document #:10131

Applies To:

MailSite

Synopsis:

When installing MailSite in SQL Connector mode, there are a number of common errors that occur

More Information:

Information on how to install MailSite in the SQL Connector mode can be found in the MailSite manual under “SQL Connector”. Below is a summary of the procedure, along with some common pitfalls:

Create a new empty database within SQL Server
Set-up the System DSN on all MailSite servers
- Pitfall: Ensure you use SQL authentication, rather than NT authentication
- Pitfall: Ensure the account you use for authentication is an owner of the MailSite DB*. We highly recommend you DO NOT use the “sa” account
- Pitfall: Use “TCP/IP” as the network library, rather than “Named Pipes”
- Pitfall: The incorrect default database is selected
Install MailSite on the application servers
- Pitfall: Ensure that MailSite is installed with the services running as an NT user. This user should have the same user name and password on the application servers
- Pitfall: Ensure you use a UNC path for the BOX directory, pointing at the remote message store (although this can be changed / added later)
Select “Configuration connector” from the “Server” tab within the MailSite Windows console on the first server, and choose “SQL Connector”
Ensure you are creating a new cluster, rather than joining an existing one
- Pitfall: Ensure the correct DSN is selected
- Pitfall: Ensure the correct account is used for the login ID (that you created in SQL Server)
- Pitfall: Ensure you select the correct database
- Pitfall: Ensure you create the tables and stored procedures
Select “Configuration connector” from the “Server” tab within the MailSite Windows console on the other server, and choose “SQL Connector”
Ensure you are joining an existing cluster, rather than creating a new one
- Pitfall: Pitfalls as above
Give the mailsite-user access to the BOX directory on the remote message store
- Pitfall: Specifying a remote directory (share) that the mailsite-user does not have access to

* The account that accesses the Database during normal operation will need only Read & Write access. During the initial setup, this account will need to have permissions to modify the schema as the tables and procedures will need to be defined. At the very least the account needs to be an apart of db_Owner during setup. After that time, the privileges can be reduced if you so wish. When the tables and procedures need to be updated again, the privileges on the account will need to be promoted for this task. For best advice on SQL Server permissions discuss with your DBA or consult SQL Server articles on permissions.

See these other knowledge base documents:

10110:Updating your V.4 Datacenter DB to MailSite SP V.5 DB

Last revised 2007-5-8