Difference between revisions of "Sql Connection Configuration Issues"

From Agility
Jump to: navigation, search
(Created page with "Symptoms: User can connect to SQL instance with SQL management studio, but Agility (or background) throws exception (in event log) that fastNet it is unable to connect with sql")
 
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
Symptoms: User can connect to SQL instance with SQL management studio, but Agility (or background) throws exception (in event log) that fastNet it is unable to connect with sql
+
[[Category:FAQ]]
 +
==Symptoms==
 +
 +
Agility (or background) throws exception to event log that system is unable to connect fastNet database, but user can connect to SQL instance with SQL management studio
 +
 
 +
==Investigation Procedure==
 +
 
 +
Ensure system configuration:
 +
#Check '''SystemName''' in ''web.config'' and in ''sxpBacground.exe.config'' files.
 +
#Ensure windows registry setup (for standard and Wow6432Node):
 +
#* HKEY_LOCAL_MACHINE\SOFTWARE\SoftSolutions\SXP\SystemName
 +
#* HKEY_LOCAL_MACHINE\SOFTWARE\'''Wow6432Node'''\SoftSolutions\SXP\SystemName
 +
#Validate '''SystemConfigFilePath''' from registry with physical file path.
 +
#Validate '''ConnectionString''' in configuration file.
 +
#Ensure that firewall do not block sqlserver ports (on all machines with: agility service, background, sqlserver).
 +
# If '''Data Source''' in connection string uses named instance check if additional port for SqlServerBrowser is opened (port 1434, for details check: http://dba.stackexchange.com/questions/133203/does-udp-port-1434-need-to-be-open-for-named-instances-with-static-tcp).

Latest revision as of 11:02, 14 December 2016

Symptoms

Agility (or background) throws exception to event log that system is unable to connect fastNet database, but user can connect to SQL instance with SQL management studio

Investigation Procedure

Ensure system configuration:

  1. Check SystemName in web.config and in sxpBacground.exe.config files.
  2. Ensure windows registry setup (for standard and Wow6432Node):
    • HKEY_LOCAL_MACHINE\SOFTWARE\SoftSolutions\SXP\SystemName
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SoftSolutions\SXP\SystemName
  3. Validate SystemConfigFilePath from registry with physical file path.
  4. Validate ConnectionString in configuration file.
  5. Ensure that firewall do not block sqlserver ports (on all machines with: agility service, background, sqlserver).
  6. If Data Source in connection string uses named instance check if additional port for SqlServerBrowser is opened (port 1434, for details check: http://dba.stackexchange.com/questions/133203/does-udp-port-1434-need-to-be-open-for-named-instances-with-static-tcp).