SQL Server and MainBoss Service

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.2.
For the latest version of this help file can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

MainBoss Service is a Windows service which handles MainBoss's incoming and outgoing email messages. It can run on any computer in your network which can access the computer where SQL Server runs. For more information, see MainBoss Service.

MainBoss Service runs under the Network Service login name on the computer where the service is installed. When such services interact with other computers, they do so under a name consisting of the computer name plus a dollar sign $. For example, suppose MainBoss Service has been installed on a computer named MSCOMPUTER. Then it interacts with other computers on the network using the login name MSCOMPUTER$. In particular, when this MainBoss Service makes use of SQL Server, it will do so under the name MSCOMPUTER$.

MainBoss Service must be installed by someone with SQL Server Administration privileges on the instance of SQL Server that manages the MainBoss database. The installation process makes use of these privileges to set up security permissions that will allow MainBoss Service to access the MainBoss database. In particular, the installation process adds an appropriate login name to SQL Server's list of recognized names. Using our previous example, this would mean adding MSCOMPUTER$ to SQL Server's list of authorized login names.

In our experience, some SQL Server administrators are unaccustomed to working with such names. If they notice a name like MSCOMPUTER$ in the list of authorized login names, they may delete it because it looks unusual. Deleting the name will prevent MainBoss Service from accessing the MainBoss database; the service will stop processing incoming and outgoing email messages and will write error messages to the MainBoss Service log until the problem is corrected.

< Previous section  |  Table of Contents  |  Index  |  Next section >