Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Oct 15 2009, 3:12 PM EDT (current) | sdrevik | 167 words added |
| Oct 15 2009, 2:57 PM EDT | sdrevik |
Changes
Key: Additions Deletions
One common error in any client/server application is the error message when a client can't talk to the server ("Airvision: service gateway URL refuses the connection").
This usually has some common causes:
In initial installations, the most common problem is that the local system account used to run the AirVision service doesn't have SQL Server User privileges. Check the Server error logs to confirm a login error, and use your user administration tools to add the local system account to a group with SQL Server database privileges.
Alternately, you can edit the service properties and add an account login to run the service with an appropriate administrative user account.
This usually has some common causes:
- AirVision service is not running on the server (run "services.msc")
- Internet connection down or port blocked (default port is 9885)
- Server connection settings (IP/hostname or port) incorrect... check login details
- Client - server registrations incorrect (Version 1.00 only.. check Server Registration Tool)
In initial installations, the most common problem is that the local system account used to run the AirVision service doesn't have SQL Server User privileges. Check the Server error logs to confirm a login error, and use your user administration tools to add the local system account to a group with SQL Server database privileges.
Alternately, you can edit the service properties and add an account login to run the service with an appropriate administrative user account.
