Sign in or 
Share this
Client/Server Troubleshooting
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.
sdrevik |
Latest page update: made by sdrevik
, Oct 15 2009, 3:12 PM EDT
(about this update
About This Update
Edited by sdrevik
167 words added view changes - complete history) |
|
Keyword tags:
None
More Info: links to this page
|
| Started By | Thread Subject | Replies | Last Post | ||
|---|---|---|---|---|---|
| desmogger | here is the error when trying to connect to TCPIP route direct to BAM | 5 | May 5 2011, 3:29 PM EDT by desmogger | ||
|
Thread started: Jan 13 2011, 2:27 PM EST
Watch
Rebex.Net.ProxySocketException: No connection could be made because the target machine actively refused it. ---> Rebex.Net.ProxySocketException: No connection could be made because the target machine actively refused it. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.175.64.98:9886
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at 328075837.13357030529.151169660(String , IPAddress , Int32 ) --- End of inner exception stack trace --- at 328075837.13357030529.151169660(String , IPAddress , Int32 ) --- End of inner exception stack trace --- at 328075837.13357030529.362804169(IAsyncResult , String ) at 328075837.13357030529.15613119759(IAsyncResult , Int32 ) at Rebex.Net.ProxySocket.Connect(String serverName, Int32 serverPort) at 328075837.1960841591..ctor(Telnet , ShellChannelOptions , TerminalOptions , Int32 , Int32 ) at Rebex.Net.Telnet.Rebex.TerminalEmulation.IShellChannelFactory.CreateShellChannel(TerminalOptions options, Int32 columns, Int32 rows) at Rebex.TerminalEmulation.TerminalControl.Bind(IShellChannelFactory factory) at Rebex.TerminalEmulation.TelnetTerminalControl.Connect() at AirVision.DataSources.Controls.TelnetControl.Connect(String host, Int32 port) at AirVision.DataSources.Views.LoggerDownload.LoggerEmulationView.Connect() |
||||
| desmogger | Safe handle has been closed | 0 | Jan 13 2011, 2:25 PM EST by desmogger | ||
|
|
Thread started: Jan 13 2011, 2:25 PM EST
Watch
No connection could be made because the target machine actively refused it 10.175.64.98:9886
what does this mean cannot direct connect to any IP ADDRESS on routes |
||||
Showing 2 of 2 threads for this page
