Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Newly installed modules giving sql errors.Newly installed modules giving sql errors.
Previous
 
Next
New Post
4/1/2008 7:14 PM
 

Hi,

When I try to install new modules there's not the problem, works like a charm.

However, when I add the installed module to a page -for instance blog/faq/usersonline- I get error like these.

Error: View_Blog is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not 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.ViewBlog.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

I'm currently using dnn 4.8.2 with an SQL 2000 Enterprise database (located on a other server)

Basicly I get this error for every newly install module.

Previous install modules (like wiki) are working just fine.

Any ideas anyone?

Regards, Lennard

 
New Post
4/1/2008 8:34 PM
 

that errors generated by sql express/sql 2005. Please check your web.config and ensure that you've set both your connectionstrings to your sql 2000 database, I suspect one is pointing to your local machine where it finds sql express, but can't login and hence generates the error.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
4/2/2008 2:17 AM
 

Ok tnx,

Well, I tried to do what you said, but I'm probably doing something wrong here is my config.

  <connectionStrings>
    <!-- Connection String for SQL Server 2005 Express -->
    <add name="SiteSqlServer" connectionString="Data Source=server\sqlinstance;Initial Catalog=Portal;User ID=sa;Password=mypassword" providerName="System.Data.SqlClient" />
    <!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
      providerName="System.Data.SqlClient" />
   -->
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" />
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    -->

I've tried to mimic the setting under connectionStrings to the appSettings, like so:

<add key="SiteSqlServer" value="Server=server\sqlinstance;Database=Portal;uid=sa;pwd=mypassword;"/>

But this only generates errors.

More Ideas?

Lennard

 
New Post
4/2/2008 3:24 AM
 

I finaly figured it out!

 <connectionStrings>
    <add name="SiteSqlServer" connectionString="Data Source=server\sqlinstance;Initial Catalog=Portal;User ID=sa;Password=mypassword" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <add key="SiteSqlServer" value="Data Source=server\sqlinstance;Initial Catalog=Portal;User ID=sa;Password=mypassword"/>

Just replacing the values didn't work so after multiple tries I came across the above settings.

But now I'm curious why the setting in the previous post didn't work what is the difference?

Regards, Lennard

 
New Post
4/2/2008 11:17 AM
 

you weren't editing the correct entries, the <!-- --> characters are comment characters. This means that in the sample below, the active connection is the one in italics, and the one in bold is actually commented out.

<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" />
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    -->


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Newly installed modules giving sql errors.Newly installed modules giving sql errors.


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out