Difference between revisions of "Sql Connection Configuration Issues"
From Agility
(→Investigation Procedure) |
|||
| Line 11: | Line 11: | ||
#* HKEY_LOCAL_MACHINE\SOFTWARE\'''Wow6432Node'''\SoftSolutions\SXP\SystemName | #* HKEY_LOCAL_MACHINE\SOFTWARE\'''Wow6432Node'''\SoftSolutions\SXP\SystemName | ||
#Validate '''SystemConfigFilePath''' from registry with physical file path. | #Validate '''SystemConfigFilePath''' from registry with physical file path. | ||
| − | #Ensure that firewall do not block sqlserver ports (on all machines with: agility service, background, sqlserver) | + | #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). | ||
| + | http://dba.stackexchange.com/questions/133203/does-udp-port-1434-need-to-be-open-for-named-instances-with-static-tcp | ||
Revision as of 10:53, 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:
- 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).
