Most, but not all AirVision installations will have SQL Server and the AirVision server installed on the same PC. Where this is NOT the case, the administrator may run into some rights issues in getting the AirVision service to connect to the database, and a simple fix may be needed.

By default, the AirVision Server installation sets up the AirVision service to run under the local system account on that PC. For most domain systems, the local system account doesn't necessarily have full SQL Server privileges on a separate SQL Server PC. This can be easily adjusted in one of two ways:

1. Change the Properties of the AirVision Service to log on using a domain account with local machine admin and domain SQL privileges
2. Change the settings in the Server Settings Editor away from Windows Authentication, to instead log into the database using a SQL account user/password.

Either of these approaches will work and are equally viable.