Troubleshooting BlogML - Export Tool
After writing an introduction to troubleshooting BlogML as well as two posts about BlogML schema and .NET library, now I want to talk about troubleshooting export tool issues.
You know that a BlogML migration consists of two main steps: export the blog content to BlogML format and import the content. The first step, export, is critical because if you can't get a well-formed BlogML file (that is valid against BlogML schema) then can get in serious troubles when importing the file. Solving an issue for a blog with 200-300 posts can be annoying enough to force you give up so you need to be careful when exporting your blog into BlogML files.
For those who are using .NET BlogML converters, a main part of the export process should be done by BlogML .NET library but however, there are always some specific points about the export tools. For .NET library users, same issues of .NET library can come to export tool as well.
First common issue for export tools is the timeout error when you try to export a lot of blog data into BlogML. In this case, based on your platform, you need to increase the timeout value or use better resources if they can't handle your data.
The other common issue about export tools is the structure of result. This is something that export tool developers should take care about it but if they generate a wrong structure that is not valid against BlogML schema then you have many troubles ahead!
Another issue about the size of output in ASP.NET is your website configuration that must allow the size of file to be transferred. For large files you need to increate the request size value in Web.Config file. This is a common issue for import tools as well.
I personally would like to suggest you to try to export your blog to BlogML on a local installation of your blog to be able to manage the process easier and avoid any problems on the production server.
The other recommendation is about embedded post attachments that can significantly increase the size of your BlogML file and make the export process longer. I can recommend you to not to export embedded attachments to BlogML to keep your files smaller.
[advertisement] Axosoft OnTime 2008 is four developer tools in one: bug tracking, project wiki, feature management, and help desk. It manages your development process so developers can focus on coding. Installed or Hosted – Free Single-user license -- Free 30-day team trial.
2 Comments : 09.28.07
#1
Keyvan Nayyeri
10.09.2007 @ 6:40 PM