Question

Please i have been seeing this error:

The connection name ‘SQL’ was not found in the applications
configuration or the connection string is empty. Description: An
unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the
error and where it originated in the code.

I know for a fact that the connection name “SQL” exists and it works properly on my local machine.

I started seeing this error after i fixed this other error on my deployment server:

Compiler Error Message: BC31007: Unable to open module file
‘C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

by setting up the access rights as suggested here

Please i would appreciate any help on this.

thanks!

Deployment Environment : Windows Server 2003, .net 4.0
Development Environment: Widows 7, .net 4.0

Please note: The deployed application has been working perfectly well on site, for over 3 months up till last Friday evening.

The client claims nothing on the server or in their environment has changed.

My Web Config:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <appSettings>
        <add key="LoginMode" value="2" />
        <add key="CustomeModules" value="True" />
        <add key="TopCallersRefeshInterval" value="600" />
        <add key="OperatorAccountName" value="" />
        <add key="ChartImageHandler" value="storage=file;timeout=20;dir=C:\TempImageFiles\;"/>
    </appSettings>
    <connectionStrings>
        <add name="SQL" connectionString="server=.\SQL2008;database=xxxxxx;uid=xxxxxx;pwd=xxxxxxxxxx;" providerName="System.Data.SqlClient" />
        <add name="SQLCustom" connectionString="server=.\SQL2008;database=xxxxxx;uid=xxxxxx;pwd=xxxxxxxxxx;" providerName="System.Data.SqlClient" />
    </connectionStrings>
    <system.web>
        <httpHandlers>
     <add path="ChartImg.axd" verb="GET,HEAD,POST" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false" />
    </httpHandlers>
    <pages>
     <controls>
        <add tagPrefix="asp" namespace="System.Web.UI.DataVisualization.Charting" assembly="System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
     </controls>
    </pages>
    <compilation debug="true" targetFramework="4.0" explicit="true">
            <assemblies>
                <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
                <add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
                <add assembly="System.Web.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
                <add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
                <add assembly="System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /></assemblies>
        </compilation>
    </system.web>
    <system.webServer>
        <defaultDocument>
            <files>
                                <remove value="login.aspx" />
                <remove value="iisstart.htm" />
                <remove value="default.aspx" />
                <remove value="index.html" />
                <remove value="index.htm" />
                <remove value="Default.asp" />
                <remove value="Default.htm" />
                <add value="home.aspx" />
            </files>
        </defaultDocument>
        <handlers>
            <add name="ChartImageHandler" preCondition="integratedMode" verb="GET,HEAD,POST" path="ChartImg.axd" type="System.Web.UI.DataVisualization.Charting.ChartHttpHandler, System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        </handlers>
    </system.webServer>
</configuration>

Answer 1

But, are you trying to connect to the remote database (i.e., the database on the deployment server) or to a local database.

Maybe somebody has touched the access privileges to the database…

By the way, how did you fixed the original error?