I don't know if you were talking to me, but I checked my web.config and the connection strings seem OK, this is what I have:

  <connectionStrings>

    <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;AttachDbFilename=|DataDirectory|Database.mdf;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient" />

  </connectionStrings>  <appSettings>

<add key="SiteSqlServer" value="Data Source=.\SQLExpress;AttachDbFilename=|DataDirectory|Database.mdf;Integrated Security=True;User Instance=True" />

</appSettings>

And I am still getting the above stated issue.

Thanks.

I reinstalled DotNetNuke, this time version 4.4.1 and installed the Blog - still the same error....

ModuleId: 379
ModuleDefId: 97
FriendlyName: Edit Entry
ModuleControlSource: DesktopModules/Blog/EditEntry.ascx
AssemblyVersion: 04.04.01
PortalID: 0
PortalName: JochenKluger.de
UserID: 3
UserName: Jochen
ActiveTabID: 55
ActiveTabName: Blog
RawURL: /jochenkluger/Blog/tabid/55/ctl/Edit_Entry/mid/379/Default.aspx
AbsoluteURL: /jochenkluger/Default.aspx
AbsoluteURLReferrer: http://localhost/jochenkluger/Blog/tabid/55/Default.aspx?BlogID=1
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; .NET CLR 2.0.50727; InfoPath.2)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 72e4be93-d229-4a09-8499-0fc61013916f
InnerException: The server tag is not well formed.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.TemplateParser.ProcessError
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: The server tag is not well formed. ---> System.Web.HttpParseException: The server tag is not well formed. ---> System.Web.HttpException: The server tag is not well formed. at System.Web.UI.TemplateParser.ProcessError(String message) at System.Web.UI.TemplateParser.DetectSpecialServerTagError(String text, Int32 textPos) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---
Source:
Server Name: KLUGER-MOBIL

I tried the SQL legacy statement in the web.config file then readded the blog module. No change. I still get the same error. They say they are working on it so be patient. For me since this is a personal website it's not vital it has a blog, but I would still like to have one.