Jessica
Nuke Newbie Posts:9
|
08/21/2009 8:59 AM |
|
I tried using the DNN blog module. When adding it to the content pane, I get a bunch of errors all the way down the page. I'm not really sure how to fix a problem like this and if you guys have any suggestion let me know. Here is the error:
No Entries were posted for this blog.
|
Error: View_Blog is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Value cannot be null.
Parameter name: connectionString ---> System.ArgumentNullException: Value cannot be null.
Parameter name: connectionString
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 --- |
<!-- End_Module_505 -->
|
|
|
Unhandled error loading module. DotNetNuke.Services.Exceptions.ModuleLoadException:
Unhandled Error Adding Module to ContentPane --->
System.ArgumentNullException: Value cannot be null.
Parameter name: connectionString 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_Init(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e) at
System.Web.UI.UserControl.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Control.AddedControl(Control control, Int32 index) at
System.Web.UI.ControlCollection.Add(Control child) at
DotNetNuke.Modules.Blog.MainView.Page_Init(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e) at
System.Web.UI.UserControl.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Control.AddedControl(Control control, Int32 index) at
System.Web.UI.ControlCollection.Add(Control child) at
DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo
objModule, PortalSettings PortalSettings) --- End of inner exception
stack trace --- |
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
08/22/2009 9:02 AM |
|
Which version of the Blog module are you using? Check in your web.config file and make sure that BOTH of the connection strings are correct. |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Jessica
Nuke Newbie Posts:9
|
08/25/2009 10:11 AM |
|
I am using the blog module version 03.05.01. I don't know how to do that in the web.config file. Can you give an example of where the "connection string" would be in that file? is this what you're talking about?
connectionStrings
!-- Connection String for SQL Server 2005 Express
add name="SiteSqlServer" connectionString="Data Source=;Initial Catalog=BE_LiveChat;User ID=id;Password=pass" providerName="System.Data.SqlClient" / --
!-- Connection String for SQL Server 2000/2005 --
add name="SiteSqlServer" connectionString="Data Source=;Initial Catalog=BE_LiveChat;User ID=id;Password=pass" providerName="System.Data.SqlClient" /
/connectionStrings |
|
|
|
|
Jessica
Nuke Newbie Posts:9
|
08/25/2009 10:19 AM |
|
I had to remove the <>. It was not showing the code i guess?
|
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
08/25/2009 10:31 AM |
|
yes that's right - yes the forum will not display code in < - add a space will take care of it:
You want to look for 2 connection strings, the first is placed in side a < connectionStrings > tag
ie something like: < add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=username;pwd=password;" providerName="System.Data.SqlClient" / >
and the second is below this in the appSettings tag: < add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=username;pwd=password;" />
You want to make sure that these 2 lines have the same values for server, database, uid and pwd
|
|
Lee Sykes Site Administrator Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts
Twitter: www.twitter.com/DNNCreative
|
|
|
Jessica
Nuke Newbie Posts:9
|
08/25/2009 10:41 AM |
|
< connectionStrings > < !-- Connection String for SQL Server 2005 Express < add name="SiteSqlServer" connectionString="Data Source=;Initial Catalog=BE_LiveChat;User ID=id;Password=pass" providerName="System.Data.SqlClient" / > -- > < !-- Connection String for SQL Server 2000/2005 -- > < add name="SiteSqlServer" connectionString="Data Source=;Initial Catalog=BE_LiveChat;User ID=id;Password=pass" providerName="System.Data.SqlClient" / > < /connectionStrings > This is all i can find that is similar, but some of the values are different from the example you give. like the connectionString="" does not have the same values like server= and database= |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
08/25/2009 10:22 PM |
|
In the web.config furnished with DotNetNuke, there are two versions of the connection string, and there are two places where a connection string needs to be specified. If you installed using the Wizard, then this will have been taken care of provided that you used the "Test" function.
The two versions of the connection string are for SQL Server and SQL Server Express. The two strings differ in format. The one that is not used is commented out, but you can delete it from web.config.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Jessica
Nuke Newbie Posts:9
|
08/27/2009 2:28 PM |
|
i removed the commented out connection string. But that hasn't made any change to the errors that I'm getting. Do you think it could be something else in the web.config file other than the connection string? |
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|
Jessica
Nuke Newbie Posts:9
|
08/27/2009 3:51 PM |
|
we got it figured out. the one that was commented out.. couldnt be. so we removed those < !-- -- > and then it worked. I didnt know you needed both. thanksfor all your help guys. I guess i just misinterpreted some of the stuff you said earlier in the posts. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
08/27/2009 6:51 PM |
|
Yes, there are TWO places where connection strings need to be specified in the web.config file. The second one is a "legacy" method, and the Blog Module still uses it. But ... I'm glad that you got it fixed! |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|