SQL Response
Latest version: 1.3
Knowledge Base
SQL Response client not connecting to Alert Repository
Category: Troubleshooting & error messages
Date: 29 Sep 2009
Product: SQL Response
When connecting to the SQL Response Alert Repository, the following error may occur:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
In some cases, the remoting connection will fail when multiple network adapters are installed and the network adapter that connects to the Alert Repository's network is not the first in the list.
Confirm that the public card, ie, the one that you are trying to connect to, is the top binding card.
To find this, go to the machine that the alert repository is on and go to Network Connections in the Windows Control Panel and then choose "Advanced Settings" from the "Aadvanced" menu. You may change the connection order in the "Aadapters and Bindings" tab.
Document ID: KB200909000431 Keywords: SQL,Response,connect,bindings,failed,respond
Was this article helpful?
What does SQL Response monitor?SQL Response
- Troubleshooting Computer Unreachable and Access Is Denied Error Messages
- SQL Response Security Setup
- Upgrading from Version 1.0 to 1.1 where the SQL Response Client and Alert Repository exist on the same machine
- Moving your Alert Repository Data
- Licensing SQL Response on a clustered SQL Server
- Server licenses may show "trial period has expired"
- How do I use the SQL Response client across domains?
- Where are the SQL Response data files stored?
- SQL Response client not connecting to Alert Repository
- The alert details are not recorded and SQL Response reports "Alert is still being written" when viewing an alert or multiple alerts
- Error when connecting to the Alert Repository using Windows 7
- Alert Repository transferring large amounts of data from the SQL Server
- Log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Response
- Migrating your Alert Repository from Windows 2000
- Tips for configuring SQL Response in your network environment
- SQL Response release notes - version 1.xx
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs
