Difference between revisions of "Sql Connection Configuration Issues"
From Agility
| Line 1: | Line 1: | ||
| − | + | ==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 | 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: | Ensure system configuration: | ||
| − | #Check | + | #Check '''SystemName''' in ''web.config'' and in ''sxpBacground.exe.config'' files. |
| − | #Ensure registry | + | #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. | ||
| + | #Ensure that firewall do not block sqlserver ports (on all machines with: agility service, background, sqlserver) | ||
Revision as of 10:44, 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.
- Ensure that firewall do not block sqlserver ports (on all machines with: agility service, background, sqlserver)
