Dariusz Macina
Oct 28, 2008
  8695
(0 votes)

Getting started with Windows Live Writer - troubleshooting

Yes, finally I've decided to create my blog page :)

I was thinking about things to write about and in general didn't expect technical problems in establishing a blog page.

Well... I was wrong.

 

Yes... I was following the blogging guidelines (http://world.episerver.com/en/System/Blog-info/Blogging-on-EPiServer-World/) and everything was fine until I tried to integrate my fresh EPiServer blog with Windows Live Writer.

Picture 1. Configuring Windows Live Writer

 

After entering homepage url, user credentials and clicking the 'Next' button... quite nasty and not much saying exception has occurred!

Picture 2. Unexpected exception

 

I have totally no idea why it did occur and if someone else had the same problem so I decided to ask the oracle - google of course ;)

But it gave me no clear answer. This was something really unexpected but made my brain up and running :)

Finally, I solved the problem and posted something here :)

 

If you're encountering the similar problem the following may help you.

1. Enter your newly created blog page

In my case: http://world.episerver.com/blogs/dariusz-macina

2. Take a look into the source of the page

In the <head> section you'll find something like this:

http://world.episerver.com/util/xmlrpc/RSD.aspx?pageid=25466

The link will get you to the RSD (Really Simple Discovery) file. The file in fact is an XML describing blog engine and what is more interesting (from this article point of view) containing a link to the API exposed by the EPiServer blog (methods used by the engine).

In my case it looks like:

<rsd version="1.0">

<service>

<engineName>MetaWeblog (EPiServer)</engineName>

<engineLink>http://www.episerver.com</engineLink>

<homePageLink>http://world.episerver.com/</homePageLink>

<apis>

<api name="Metaweblog" blogID="25466" preferred="true" apiLink="http://world.episerver.com/util/xmlrpc/Handler.ashx?pageid=25466" />

</apis>

</service>

</rsd>

 

Ok, we're getting closer.

 

3. Use the apiLink url instead of your blog page url

Yes, that did the trick - no exception anymore :)

Picture 3. Correct homepage URL 

 

4. Select the correct provider

Windows Live Writter won't detect the blog engine type automatically so we have to do it ourselves.

The engine type can be retrieved from the RSD file. Check the <engineName> node and you'll see that in our case the engine is MetaWeblog.

 

Select the MetaWeblog from the list and provide the apiLink url once more.

Picture 4. Selecting provider

 

5. Here it is up and running

Picture 5. Mission completed!

 

As you can see the homepage is now set to something like:

http://world.episerver.com/Templates/Blog/Pages/PersonalStart.aspx?id=25466&epslanguage=en

which is your newly created EPiServer blog page - problem solved :)

 

Enjoy!

Oct 28, 2008

Comments

Eric
Eric Sep 21, 2010 10:32 AM

You should now be able to follow our guidelines instead. We have hade some problems with upgrades of the module but it should now work! /Eric

Please login to comment.
Latest blogs
A Synonyms Manager for Optimizely Graph

If you’re using Optimizely Graph for search, synonyms are one of the simplest ways to improve relevance without touching content. But they’re also...

Pär Wissmark | Mar 17, 2026 |

Building a Better Link Validation Report in Optimizely CMS 12

Broken links frustrate visitors and damage SEO. I have made a custom broken links report, that makes it easier to work broken links than the built-...

Henning Sjørbotten | Mar 17, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Discover what's new in Jhoose Security Module 3.0, including site-level security configuration for multi-site Optimizely solutions with global...

Andrew Markham | Mar 15, 2026 |

Running 64 Sites on Headless Optimizely CMS with GraphQL

64 websites. Live. Running on headless Optimizely with GraphQL. We just wrapped a major rollout for our Rockwool Digital Experience Platform  and t...

Piotr | Mar 14, 2026