Fix Windows Live Writer Error – The response to the wp.getTags method received from the blog server was invalid.

Windows Live Writer is in my opinion the most complex application that allows edit and PUBLICATION articles on a blog, the application can be used for both hosted blogs on WordPress.com, SharePoint, Blogger, TypePad, as well as those self hosting.
Before connecting Windows Live Writer to a blog with the platform WordPress, we must first tick the options of Remote Publishing. Atom Publishing Protocol and XML-RPC FROM Dashboard > Settings > Writing.

After connecting, Windows Live Writer imports some elements of the blog including graphics theme (optional) and tagthe. When the blog has a database very consistent, especially on Tag table-uri (large number) it is possible that the server on which the blog is hostat not to allow the connection of WLW and defend errors like:

Invalid Server Response – The response to the wp.getTags method received from the blog server was invalid.

This error occurs especially when we want to import the list of tags (wp_tags) in Windows Live Writer.

Error details:

Unexpected Error Occurred     
An unexpected error has occurred within the application.

WindowsLive.Writer.Extensibility.BlogClient.BlogClientInvalid     
ServerResponseException: Invalid Server Response - The response to the wp.getTags method received from the blog server was invalid:

Invalid response document returned from XmlRpc server     
   at WindowsLive.Writer.BlogClient.Clients.XmlRpcBlogClient.      
CallMethod(String methodName, XmlRpcValue[] parameters)      
   at WindowsLive.Writer.BlogClient.Clients.MetaweblogClient.      
WordPressGetKeywords(String blogId)      
   at WindowsLive.Writer.BlogClient.Clients.MetaweblogClient.      
GetKeywords(String blogId)      
   at WindowsLive.Writer.BlogClient.Blog.RefreshKeywords()      
   at WindowsLive.Writer.PostEditor.PostPropertyEditing.      
SharedPropertiesController.<.ctor>b__0(Object sender, EventArgs args)      
   at System.Windows.Forms.Control.OnClick(EventArgs e)      
   at WindowsLive.Writer.Controls.BitmapButton.OnClick(EventArgs e)      
   at System.Windows.Forms.Control.WmMouseUp      
(Message& m, MouseButtons button, Int32 clicks)      
   at System.Windows.Forms.Control.WndProc(Message& m)      
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)      
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)      
   at System.Windows.Forms.UserControl.WndProc(Message& m)      
   at System.Windows.Forms.Control.ControlNativeWindow.      
OnMessage(Message& m)      
   at System.Windows.Forms.Control.ControlNativeWindow.      
WndProc(Message& m)      
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The cause of the error:

At the time of import (of tags In our case) the server that hosts the blog is more requested than usual, again memory limit (RAM) allocated to the execution PHP scripts it is outdated. For this reason the server rejects the connection or stops the import. “Invalid response document returned from XmlRpc Server“.

Solving the error:

As with the error “Metaweblog.newpost“, the solution is also from .htaccess. We will have to add a line that will Mareasca memory limit allocated to the web hosting account on which the blog is. To do this, add in .htaccess line:

value memory_limit 256M

The value 256M a “memory_limit” Set Maximum expressed size baiti on which one PHP script can use it. Limit “memory_limit” is implicitly established at 128M by the file php.ini (config-ul Php_ini_all on the PHP server) on most servers that reset PHP 5.3.10. In the past before PHP 5.2.0 The value was 8M, and with the launch of the version PHP 5.2.0, this value has been set to 16M.
Before import Tags in WLW You can increase this limit over 128m, but you must also take into account the total memory of the web server. Directive “memory_limit” Practically prevents a PHP script written wrong to consume all the memory available on a server. It is recommended that after import to delete this line from .htaccess to return to the default value set by php.ini.

If you do not have access to the modification settings of the value “memory_limit”, in this situation you will need to address the provider who hies your blog for security and performance reasons, most web hosting providers restrict the access of accounts to settings “sensitive” of the server.