Difference between revisions of "Sql Connection Configuration Issues"
From Agility
(→Investigation Procedure) |
m (Sychu moved page Sql Connection Issues to Sql Connection Configuration Issues) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:FAQ]] | ||
==Symptoms== | ==Symptoms== | ||
| − | Agility (or background) throws exception to event log that system is unable to connect fastNet database | + | 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== | ==Investigation Procedure== | ||
| Line 13: | Line 14: | ||
#Validate '''ConnectionString''' in configuration file. | #Validate '''ConnectionString''' in configuration file. | ||
#Ensure that firewall do not block sqlserver ports (on all machines with: agility service, background, sqlserver). | #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 | + | # 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). |
| − | 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:
- 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).
