IIS Connection String not being inherited

connectioniis-7.5

I have an issue where I've set up a connection string at the Machine level in IIS, and it is inherited all the way down as expected… EXCEPT for the application I want to use the string in. Other applications at the same level do inherit the string.

The application in the past had the connection string with the same name defined. Removing it at the application level removes it permanently: it will not be inherited. Adding it at the application level makes it local. I can't find a way for that application to inherit the connection string.

Is there some way to reset this behavior? Short of removing the application entirely?

Best Answer

Open the AppHost configuration at C:\Windows\System32\inetsrv\config\applicationHost.config and search for the name of your app, review the matches, do any of them have to do with connectionstrings?

Does your app has a parent that may remove the connection string in question?

Related Solutions

Iis – ASP.NET custom configuration section declaration breaks IIS Manager Configuration Editor

Hey Kev. This worked for me right away using your examples. Here's where I placed everything:

Path:

%systemroot%\system32\inetsrv\config\schema\simpleconfig.xml

Content:

<configSchema>
  <sectionSchema name="SimpleConfigGroup">
    <element name="SimpleConfigSection">
      <attribute name="MySetting" 
                 type="string" 
                 validationType="nonEmptyString" />
    </element>
  </sectionSchema>
</configSchema>

Path:

%systemroot%\system32\inetsrv\config\applicationHost.config (in <configSections> element).

Content:

<section name="SimpleConfigGroup" 
         overrideModeDefault="Allow" 
         allowDefinition="Everywhere" />

Path:

Site's web.config

Content:

  <SimpleConfigGroup>
    <SimpleConfigSection MySetting="Hello World" />
  </SimpleConfigGroup>

Sql-server – Authentication between IIS & SQL Server for Load Balanced App

Create an account for sql to use, either a windows or sql account, and specify that in the connection string. For security purposes, you should also encrypt the web.config after doing this using the command:

%SYSTEMROOT%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -prov "RsaProtectedConfigurationProvider" -pef connectionStrings "[PathToWeb.Config]"

That account should have the required permissions to the database, such as db_DataReader and db_DataWriter.

Best Answer

Related Solutions

Iis – ASP.NET custom configuration section declaration breaks IIS Manager Configuration Editor

Sql-server – Authentication between IIS & SQL Server for Load Balanced App

Related Topic