Skip to content
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.

When specifying SQL instance name at install time, web.config file doesn't reflect the instance name #24

Open
nfields03 opened this issue Feb 22, 2017 · 1 comment
Labels

Comments

@nfields03
Copy link

I was installing this today on one of our servers after successfully working with it in the lab, and noticed I was getting a SQL connection error after installation even though the database was created and I could get into SSMS with the same login. After a bit of tinkering I noticed that if you specify a SQL instance name in the install screen, it doesn't necessarily update the web.config file during the install process (mine showed "localhost" as the datasource in the connection strings section of the Web.Config file, but once I edited it to be "localhost\falconorch" to match the instance name, I did an IISRESET and the site came up. It goes to the other suggestion for some validation during the installation script, but hopefully this helps anyone else who runs into the same issue.

@mr-burnse mr-burnse added the bug label Mar 6, 2017
@mr-burnse
Copy link
Contributor

Thanks for pointing this out. Definitely a bug that will be addressed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants