Server Error in '/Services' Application.

Error on Channel.LoadByPath(Home/AJTU/EN/Projects). A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

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.

Exception Details: System.Exception: Error on Channel.LoadByPath(Home/AJTU/EN/Projects). A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[Exception: Error on Channel.LoadByPath(Home/AJTU/EN/Projects). A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]
   AJCMS.Library.Channel.LoadByPath(String pPath, Boolean LoadEvenDeleted, Boolean pIgnoreCache) +1249
   SearchResults.FillSearchableProjects(Boolean TextInArabic) +164
   SearchResults.set_Language(String value) +1157
   ASP.search_default_aspx.__BuildControlSearchResults1() +134
   ASP.search_default_aspx.__BuildControlContent1(Control __ctrl) +378
   System.Web.UI.MasterPage.InstantiateInContentPlaceHolder(Control contentPlaceHolder, ITemplate template) +103
   ASP.templates_postinglayouten_master.__BuildControlcphBody() +185
   ASP.templates_postinglayouten_master.__BuildControldvContent_Left() +291
   ASP.templates_postinglayouten_master.__BuildControlTemplate01() +118
   ASP.templates_postinglayouten_master.__BuildControlTree(templates_postinglayouten_master __ctrl) +300
   System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) +1263
   System.Web.UI.Page.get_Master() +67
   System.Web.UI.Page.ApplyMasterPage() +18
   System.Web.UI.Page.PerformPreInit() +62
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +297


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2623.0