ServiceDesk

 View Only
Back to discussions
Expand all | Collapse all

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.

  • 1.  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.

    Posted Dec 31, 2013 12:21 PM

    Hi everyone,

     

    I am having this issue on Servicedesk Server and on clients while accessing the Servicedesk portal. 

    SQL is offBox and is pingable, has port open 1433 and custome port on both Servers, but still I get this error. When my client open Any Any ports between both Servers (Servicedesk and SQL Server) it starts communication but when only specifice like ports for instance or SQL default ports are opened its start giving error.

    I have changed the Connection strings for custom port at >>>> Workflow Explorer, SymQ Configuration > SymQ_Local_Defaults it is set up under local.workflowsqlexchange-, local.orm and in Workflow_Core under local.workflowsqlexchange-

    still no goodluck

     

    Server Error in '/ProcessManager' Application.

    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.Data.SqlClient.SqlException: 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:

     

    [SqlException (0x80131904): 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)]

       System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +6256377

       System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +245

       System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +6270399

       System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +181

       System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +6271401

       System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +6271208

       System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +354

       System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +703

       System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +54

       System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +6272472

       System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +81

       System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +1657

       System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +88

       System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +6275911

       System.Data.SqlClient.SqlConnection.Open() +258

       LogicBase.Framework.DataLayer.DALProxy.ExecuteCommandMultipleRecords(IDbCommand cmd, Type entityType) +292

     

    [DataLayerException: Error executing sql query.]

       LogicBase.Framework.DataLayer.DALProxy.ExecuteCommandMultipleRecords(IDbCommand cmd, Type entityType) +1502

       LogicBase.Framework.DataLayer.DALProxy.ExecuteQueryMultipleRecords(IDbConnection con, String sqlQuery, IDataParameter[] sqlParams, Type entityType) +714

       LogicBase.Framework.DataLayer.DALProxy.PrivateExecuteQueryMultipleRecordsTransactionLess(String sqlQuery, IDataParameter[] sqlParams, Type entityType) +149

       LogicBase.Framework.DataLayer.DALProxy.ExecuteQuerySingleRecord(DatabaseQuery query) +788

       LogicBase.Ensemble.Settings.DataLayer.MasterSettings.LoadByID(String MasterSettingsID) in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\Settings\DataLayer\MasterSettings.cs:295

       LogicBase.Ensemble.Settings.DataLayer.SettingsHelper.GetSettings() in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\Settings\ServiceCore\SettingsHelper.cs:16

       LogicBase.Ensemble.Settings.EnsembleSettings.get_Settings() in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\Settings\ServiceCore\EnsembleSettings.cs:25

       LogicBase.Ensemble.GlobalHelper.InitializeGlobal() in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\GlobalHelper.cs:30

       LogicBase.Ensemble.Global..cctor() in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\Global.asax.cs:167

     

    [TypeInitializationException: The type initializer for 'LogicBase.Ensemble.Global' threw an exception.]

       LogicBase.Ensemble.Global..ctor() in c:\build\projects\WF75_SDSP1_Apollo\ensemble\LogicBase.Ensemble\Global.asax.cs:955

       ASP.global_asax..ctor() +9

     

    [TargetInvocationException: Exception has been thrown by the target of an invocation.]

       System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0

       System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +146

       System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +298

       System.Activator.CreateInstance(Type type, Boolean nonPublic) +79

       System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +10364299

       System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +258

       System.Web.HttpApplicationFactory.FireApplicationOnStart(HttpContext context) +11303825

       System.Web.HttpApplicationFactory.EnsureAppStartCalled(HttpContext context) +161

       System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +115

       System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +196

     

     

    Kindly any one point me what is wrong I am doing.

     

    Regards

     

    Vicky

    Version Information: Microsoft .NET Framework Version:2.0.50727.5446; ASP.NET Version:2.0.50727.5420



  • 2.  RE: 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.

    Posted Jan 02, 2014 10:15 AM

    Check the general connection string in the ServiceDeskSettings profile in your ProcessManager... that might need updating.



  • 3.  RE: 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.
    Best Answer

    Posted Jan 13, 2014 06:46 PM

    Hi Reecardo,

    I have resolved this problem by entring the connection string for SQL Server with the help of this article.

    https://www-secure.symantec.com/connect/articles/how-change-processmanager-sql-database-connectionconnection-string-custom-ports-servicedesk