DNN Blog: Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces
Dear all,
Today i was faced a problem problem setting up Blog module, one of the exception blocks is shown below:
Error: Blog is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ---> 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Modules.Blog.Data.SqlDataProvider.GetBlogModuleSettings(Int32 PortalID, Int32 TabID) at DotNetNuke.Modules.Blog.Business.Utility.GetBlogModuleSettings(Int32 PortalID, Int32 TabID) at DotNetNuke.Modules.Blog.BlogList.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Solution :
you should check that both the connection strings in web.config match and are correctly set. This is because the actual module still uses the connection string in thenode of the web.config file. I already fixed this in the next version, and in the future you'll need to update the connection string in one only place.
Regards
Rashid Imran Bilgrami
CEO Best visualization
http://www.bestvisualization.com
Today i was faced a problem problem setting up Blog module, one of the exception blocks is shown below:
Error: Blog is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ---> 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Modules.Blog.Data.SqlDataProvider.GetBlogModuleSettings(Int32 PortalID, Int32 TabID) at DotNetNuke.Modules.Blog.Business.Utility.GetBlogModuleSettings(Int32 PortalID, Int32 TabID) at DotNetNuke.Modules.Blog.BlogList.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Solution :
you should check that both the connection strings in web.config match and are correctly set. This is because the actual module still uses the connection string in the
Regards
Rashid Imran Bilgrami
CEO Best visualization
http://www.bestvisualization.com
Comments
Post a Comment
Thanks for the Comments , Your review will display soon