Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogWindows Live Writer reports an ErrorWindows Live Writer reports an Error
Previous
 
Next
New Post
11/24/2008 10:10 AM
 

I have followed the tutorials for setting up Windows Live Writer to connect to my blog.

I am DNN 4.9, the latest version of the blog.  I have Friendly URLs on, but I do not have any other URL redirector running.

Here is the info:

I went to test the WLW and for some reason it fails. I have DNN 4.9 and The latest Blog module.
Here is my weblog link: ww2.coelhome.com/DesktopModules/Blog/blogpost.ashx?tabid=108

When
WLW tries to connect I get: 500 internal server error.
In the DNN event viewer I get the following error (Sorry, It is long):

UserID: -1
UserName:
ActiveTabID: 108
ActiveTabName: City Blogs
RawURL: /DesktopModules/Blog/blogpost.ashx?tabid=108
AbsoluteURL: /DesktopModules/Blog/blogpost.ashx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Windows Live Writer 1.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID:(...removed)
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Reflection.Assembly._GetType
StackTrace:
Message: System.Exception: Unhandled Error: --->
System.IO.FileLoadException: Could not load file or assembly 'CookComputing.XmlRpc,
Version=2.1.0.3,
Culture=neutral,
PublicKeyToken=(...removed)' or one of its dependencies.
The located assembly's manifest definition does not match the assembly reference.
(Exception from HRESULT: 0x80131040)
File name: 'CookComputing.XmlRpc, Version=2.1.0.3, Culture=neutral, PublicKeyToken=(...removed)' at
System.Reflection.Assembly._GetType(String name, Boolean throwOnError, Boolean ignoreCase) at
System.Reflection.Assembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase) at
System.Web.UI.Util.GetTypeFromAssemblies(ICollection assemblies, String typeName, Boolean ignoreCase) at
System.Web.UI.SimpleWebHandlerParser.GetType(String typeName) at
System.Web.UI.SimpleWebHandlerParser.GetTypeToCache(Assembly builtAssembly) at
System.Web.Compilation.SimpleHandlerBuildProvider.GetGeneratedType(CompilerResults results) at
System.Web.Compilation.BuildProvider.CreateBuildResult(CompilerResults results) at
System.Web.Compilation.BuildProvider.GetBuildResult(CompilerResults results) 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.SimpleHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at
System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) at
System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. --- End of inner exception stack trace ---

 
New Post
11/24/2008 12:36 PM
 

Hi Phil,

could you check if Ventrian NewsArticles (or some other 3rd party module using the CookComputing.XmlRpc library) is installed on your DNN install?

Best regards,
Dario Rossa

 
New Post
11/26/2008 3:58 PM
 

Dario Rossa wrote
 

Hi Phil,

could you check if Ventrian NewsArticles (or some other 3rd party module using the CookComputing.XmlRpc library) is installed on your DNN install?

Best regards,
Dario Rossa

I am using Ventrian NewsArticles.  Is there something I can do to work around the issue?

I updated the Ventrian news articles module to 00.07.17  but noticed that the dll was still the wrong version.

I overwrote the dll with the one from the latest version of the blog, and now everything is working.

I will go back and see if things are still happy with News Articles.

Thanks for pointing me in the right direction.

 
New Post
11/28/2008 2:29 AM
 

Hi Phil,

the conflict between NewsArticles and the Blog module is a known issue that arose some days ago. I think that Scott McCulloch is on his way to fix it soon. You can have further information in this post on the Ventrian website.

Best regards,
Dario Rossa

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogWindows Live Writer reports an ErrorWindows Live Writer reports an Error


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