Issue
Agility is not functional after updating the SQL username and password for the enterprise.
Affected Products & Versions
Any On site (self-hosted) Agility instance
Cause
There is a mismatch of the SQL user, username, and password in the application config files vs what the customer has set the SQL username and password to be in the enterprise.
Workaround/Resolution Action
The following is the process for updating SQL usernames and passwords in Agility and Analytics:
- Run the Agility installer for the version you want to run in your environment
- Uninstall all of the applications. Make sure you do not delete the Agility database during the uninstall process.
- Re-install Agility. When doing the reinstall, use the option to use SQL user credentials provided by my DBA. Enter your SQL user name there and the current password.
- Connect to the existing Agility database and then let the setup complete
Doing the above steps is necessary (and the easiest way) to get the application set to use a provided SQL username and password.
Once all three applications are installed, configured (any custom files replaced and lic. dropped in), and tested as accessible and working, you need to make the following changes:
- Create a user.config file with the connection string below and place that file in the following
directory - c:\inetpub\wwwroot\YourV1ApplicationName\ - (for the VersionOne application)
<add key="ConnectionString" value="Data Source=xxxxx;Initial Catalog=VersionOne;User ID=
{username}Password={password};Enlist=False;Pooling=True;Connect Timeout=5;Application
Name="xxxxx (xxxxxx)"" /> - Create a user.config file with the connection string below and place that file in the following
directory - c:\inetpub\wwwroot\YourAnalyitcsApplicationName\ - (for the Analytics application)
When you have to change a password, you must update the password in the above connection strings in the user.config files.
<add key="ConnectionString" value="Data Source=xxxxx;Initial Catalog=VersionOne;User ID=
{username};Password={password};Enlist=False;Pooling=True;Connect Timeout=5;Application
Name="xxxxx (xxxxxx)"" />
In addition to the creation of the user.config files, the following changes will also need to be made:
Considerations
If during the initial install directories other than the default directories were used, the above files may be located in different locations. You will need to find out what those locations are and document them for your records.
Comments
Please sign in to leave a comment.