Location: Configuring Server Preferences

Discussion: Executive Set-upReported This is a featured thread

Category: Discussion Forum / General Discussion
Showing 2 posts
desmogger
desmogger
Executive Set-up
Nov 25 2009, 11:42 AM EST | Post edited: Nov 25 2009, 11:42 AM EST
Our system is insalled in a Server Downtown no modems allowed. I am setting up Executive on my old polling Central System . Keep getting refused connection to IP adress and port? Do you find this valuable?    
Keyword tags: None
sdrevik
sdrevik
1. RE: Executive Set-up
Nov 29 2009, 11:20 PM EST | Post edited: Nov 29 2009, 11:20 PM EST
"Our system is insalled in a Server Downtown no modems allowed. I am setting up Executive on my old polling Central System . Keep getting refused connection to IP adress and port?"
I assume the downtown server is just for the SQL database? Keep in mind that there are three minimal components to the system- the SQL database (and related SQL server), the Executive (e.g., the PC running the AirVision service), and the Client application. They can all reside on one PC, two, or three separate PCs. The Executive (the PC running the AirVision service) would be the hardware point where any COM ports / modems would be referenced.

Usually, when you have this configuration and the Client can't log in and get that message, the problem is that the AirVIsion Service isn't running on the "Executive" PC at all. You can verify this by going to the Executive PC and selecting Manage->My Computer->Services (or typing Run->services.msc).

If the Service isn't running, there are two common reasons:
1. The local account (which is the default) on the Executive PC used to run the service (right click on the AirVision service, select Properties->LogOn) often doesn't have the rights in a domain environment to log into the SQL server. You may need to replace the default local system account with a domain admin account.
2. Server Settings editor hasn't been run on the Executive PC, or the SQL server instance is incorrectly entered. Make sure to use the exact name of the SQL instance.

If you've checked all of these and can't identify why the service isn't starting, grab your server log file (C:\Documents and Settings\All Users\Application Data\Agilaire\AirVision\Server\Log\AVServerExceptions.[date].txt) and email to Agilaire Support.
 Do you find this valuable?