# Wednesday, June 17, 2009

I've been holding this one off for quite some time, but finally bit the bullet... migrate the server.Coming from Windows Small Business Server 2003 (32-bit) going to Windows Server 2008 with Exchange 2007 (both x64), including transferring the web site. There were a few nasty pieces in the process and I didn't have/take the time/resources to test it all though before jumping in... so I got a disruption of about one hour for the blog and inbound smtp.

First issue I encountered was the installation of the server, which I ordered from Dell without operating system. I am a Microsoft Action Pack subscriber, so I slammed the 64-bit Windows Server from the Action Pack on the system, entered the Product Key and then went on to phone based activation. After putting in the last confirmation code and pushing the next button... my activation wasn't accepted!!! ... to cut a long story short, after dozens of voice menu selections and 4 persons, I found the guy who could help me out: Philip. Though it still toke Philip and me about 20 minutes to find the actual problem... I wasn't an Action Pack subscriber anymore!!! Technical story here, but it happened when Action Pack was integrated more tightly with the Partner Program. Somehow I didn't complete the Action Pack renewal transaction completely in February, but the partner site didn't show that (it only showed I'm still good for the Partner Program).

Couple of days later, I could go ahead with the migration process. It turned out to be easier than I expected after I found a very useful document about Upgrading Small Business Server 2003 to Exchange 2007. Some pointers on using the document though;

  • Transferring the the other FSMO's (Schema Master is described); Determining FSMO Role Holders
  • With Windows Server 2008 you NEED the Exchange 2007 SP1 DVD, Exchange 2007 without SP1 will not pass installation checks.
  • Section Migrate mail send does not cover migrate mail receive. This caused me a bit of downtime... The issue was
    SMTP error from remote mail server after MAIL FROM:<abcd@efg.hi> SIZE=2703:
    host abcdef.ghi []: 530 5.7.1 Client was not authenticated

    And can be solved in the following manner in Exchange Management Console:
    • Go to the Server Configuration, Hub Transport. Select your server and add Anonymous to the Default SERVERNAME Receive Connector. While you're there, you can increase receiving message size here too.

And there were parts I did different;

  • I continue to rely on Vamsoft's ORF for the anti-spam. Version 4.3 is fully compatible with Windows Server 2008 and Exchange 2007 and an ease to configure.
  • Since I will continue the same DNS name for OWA and Windows mobile Active Sync, I transferred the Self-signed certificate from the SBS2003 (find it in your IIS, web site, directory security tab) to the new server.

My other bit of downtime was the blog... simply copy from the old server to the new one didn't cut it. So I downloaded the latest release of dasBlog from Codeplex, copied it into the virtual director of new server. Next I had to;

  • Copy my own theme
  • Compare (and adjust) the \SiteConfig files
  • Transfer \Content files and \Logs files
  • Make sure the account running the Application Pool has read on all dasBlog folders and change on \SiteConfig, \Content and \Logs.
  • The Application Pool is running in Classic Managed Pipeline Mode

Guess I can say I didn't plan for the blog to be upgraded... that just had to happen.

Wednesday, June 17, 2009 9:31:05 PM (W. Europe Daylight Time, UTC+02:00)
# Saturday, September 22, 2007

No big deal really and since I already toke some time to work on my server, I figured I might do the other outstanding chore too; upgrading the blog-engine to dasBlog 2.0.7226. I did a test upgrade on my (virtual) dev-server first. No real problems, just the an overzealous DasBlogUpgrader.exe (but you can prevent that by taking a good look at the badWords in DasBlogUpgrader.exe.config and removing the appropriate words from that list (like where free set out to delete some referrer-url’s that were okay)). Upgrade instructions are pretty straight forward, but when hitting the uploading section you need to run the difference check on the /config/site.config file too (and not just on the /web.config). ASP.NET issues were not applicable in my case, as I was already running dasBlog 1.9.7067 on ASP.NET 2.0.

One other nice feature, dasBlog now comes with a Windows Live Writer manifest file (wlwmanifest.xml), giving you some admin shortcuts from Live Writer (or take a look before you try).

Speaking of WLW, it seems a new version (Beta 3) was released at September 5th ... save this post as draft ... download new version ... well forget just about that for a moment ... I get the message stating no Windows Live products can be installed on my OS (x64 Windows Vista).

Also Microsoft's web servers are trying to be smart again about the version you should download; Dutch version: http://g.live-int.com/1rebeta/nl-nl/WLInstaller.exe , US-English version: http://g.live-int.com/1rebeta/en-us/WLInstaller.exe. So just download the language-culture you want by substituting the path... now just waiting for the confirmation of the problem on x64 (which you can find here, semi-official).

Technorati tags: ,
Saturday, September 22, 2007 8:53:39 PM (W. Europe Daylight Time, UTC+02:00)
# Monday, June 18, 2007

Earlier I posted about pingback spam and a little tool I created to remove the spamvertised links, today I upgraded the tool from version to version So what's changed;

  • The updated version doesn't leave empty Tracking elements after removing the spamvertied entries. From the dasBlog Eventlog I suspected that too many empty Tracking elements were causing errors in the trackbackList macro.
  • An XML file is only written back if something changed in the file.

Source and executable files have been changed.

--- So how does the tool work? ---

First create a config file

RemoveSpam "C:\My Config Folder\RemoveSpam.xml" /config

Look in your dayfeedback-files for the spamvertised PermaLinks (or you may already know about them if you have Notification Settings enabled for pingback and trackback). It's the PermaLink pattern that matters:

   <TargetTitle>Today's bad start</TargetTitle>
   <RefererExcerpt />
   <TargetTitle>Today's bad start</TargetTitle>
   <RefererExcerpt />

The pattern for the second Tracking entry is already included in the default config file, so you would only have to add the pattern for the first Tracking entry. To do so, you only need to add the following XML-element in the Configs section:

<Config Pattern="*-le-informazioni.info/*" />

With the updated config file, you can now run the tool to clean all XML-files in your content folder.

RemoveSpam "C:\My Config Folder\RemoveSpam.xml" \\MyWebServer\My_dasBlogShare\content

Next is figuring out why Akismet isn't working for me.

Technorati tags: , , ,
Monday, June 18, 2007 11:13:29 AM (W. Europe Daylight Time, UTC+02:00)
# Saturday, June 9, 2007

Recently I had a lot of pingback spam coming into my blog and I can tell you, it's more annoying than in your mailbox (Shift + Del and it's gone again). With dasBlog, it takes a little more effort, either via the admin interface or by deleting the spamvertised tarckings from the dayentry xml files. I even disabled trackback and pingback, temporarily!

Also I searched for solutions to this and came up with a several other affected blogs and akismet.com. With Akismet being the most promising, I tried, but spam kept coming in and Akismet was timing out (currently running dasBlog 1.9.7067.0.).

The external spam blocking service failed for pingback from http://9qk-information.info/56369818/index.html. Original exception: System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetRequestStream() at Subtext.Akismet.HttpClient.PostRequest(Uri url, String userAgent, Int32 timeout, String formParameters) at Subtext.Akismet.AkismetClient.SubmitComment(IComment comment, Uri url) at Subtext.Akismet.AkismetClient.CheckCommentForSpam(IComment comment) at newtelligence.DasBlog.Web.Core.AkismetSpamBlockingService.IsSpam(IFeedback feedback) at newtelligence.DasBlog.Web.Services.PingbackAPI.ping(String sourceUri, String targetUri)
while processing /ssb/PermaLink,guid,e63313c2-6f4d-434f-8a62-09f82a4b534c.aspx.

Hmm, if someone has some suggestions, I'd be happy to read your comment.


And that was about the spam coming in, I also had a nasty amount already polluting my blog. I could resign, disable *back permanently and clan manually once more... or fire up Visual Studio and write a piece of newbie/n00b code. Well the newbie pulled it off, his first useful C# program. At least, it removed the spammings from my blog.

So if you want to get rid of;

  • http://9??-free-porn.info/*
  • http://9??-information.info/*
  • or whatever disliked pattern of tracking permalinks on your dasBlog.

And you know that you try the followig stuff at your own risk and made a backup of your blog's content folder.

  • Compiled file (console application, run without parameters to see what you have to do to get it working. Then make the config file and if needed, edit it.). Requires .NET Framework 2.0.
  • Source-code (Visual Studio 2005, C#)

Disclaimer: It worked for me (dasBlog 1.9.7067.0.), it may not work for you and you use it at your own risk. However, feel free to comment with question, suggestions or other stuff.

<UPDATE date="2007-06-18">Version released, learn more here</UDPATE>

Technorati tags: , ,
Saturday, June 9, 2007 10:53:34 PM (W. Europe Daylight Time, UTC+02:00)
# Monday, May 14, 2007

Today I upgraded to the latest daily build (1.9.7067.0) for dasBlog. Went quite smooth, just did a compare between the old and new folders using WinMerge, copied the newer files and fire up the blog. Opening the blog (now on 1.9.7067.0) was very slow. A little later, I also experienced errors when hitting the config section. However after reviewing the site.config file, again piece of cake with WinMerge, both the error and the performance issue were gone.

Monday, May 14, 2007 3:06:08 PM (W. Europe Daylight Time, UTC+02:00)
# Friday, May 11, 2007

About 2 months ago I wrote that trackbacks didn't work from dasBlog... but I learned *backs do. But it toke a while to notice, here's what happened. Oh, let's clarify first, *backs are TrackBacks and PingBacks. Essentially you want to achieve the same thing with both, get a link on the (blog)page you reffer to.

I'm running my blog on a Windows Small Business Server 2003 R2, with ISA Server 2004. Also I had the blog configured to automatically ping the available servers using the XML-RPC Ping Interface. When I checked dasBlogs Eventlog after a couple of posts, it was filled with error messages like;

CookComputing.XmlRpc.XmlRpcServerException: Forbidden ( The ISA Server denied the specified Uniform Resource Locator (URL). )
at CookComputing.XmlRpc.XmlRpcClientProtocol.ReadResponse(XmlRpcRequest req, WebResponse webResp, Stream respStm, Type returnType)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at newtelligence.DasBlog.Runtime.Proxies.WeblogUpdatesClientProxy.Ping(String weblogName, String weblogUrl)
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.PingWeblogsWorker(Object argument)
while processing PingWeblogsWorker, pinging Yahoo.

So the configuration of the ISA Server was preventing the IIS Application Pool of reaching out to the world. Well, a little tweaking of the ISA config and the next posts' event resulted in... another error. Only this time the message wasn't saying ISA Server was in denial. The other end just didn't seem listening;

System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable host
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream()
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at newtelligence.DasBlog.Runtime.Proxies.WeblogUpdatesClientProxy.Ping(String weblogName, String weblogUrl)
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.PingWeblogsWorker(Object argument)
while processing PingWeblogsWorker, pinging Yahoo.

I also noticed that "normal" url (the ones I linked in my posts) were pinged, with much the same (= NO) result.

/* As above */
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.PingbackWorker(Object argument)
while processing PingbackWorker, auto-discovery of:

After that I left it be and didn't worry about TB and PB anymore. However, today I found a refferal in the activity log from lostcausegeek.blogspot.com, so I got curious again. I did nothing besides including a link to one of the posts, turns out something did work after all. Now back to the errors, so far I assume I'm looking at pingbacks (look here for a comparision on the *backs). In the end, it will pretty much come down to the blog service and the blog configuration, wether it works (or not).

Trackbacks, I think, is a different story with dasBlog and/or WindowsLiveWriter.


Technorati tags: , ,
dasBlog | ReSQueL | SBS
Friday, May 11, 2007 1:09:51 AM (W. Europe Daylight Time, UTC+02:00)
# Tuesday, March 6, 2007

I couldn't send trackbacks through dasBlog, which was a pity (either I don't know how to, or it's future functionality). Anyway, I solved it by signing up for . A little warning though on sending trackbacks works, but when I did so to the NewLevel blog, only the first URL was processed

Technorati tags: , , ,

Tuesday, March 6, 2007 12:05:38 AM (W. Europe Standard Time, UTC+01:00)
# Monday, March 5, 2007

Initially I planned using Windows SharePoint Services 3.0 to host my blog and I have been looking into it before, even wrote three posts about WSS 3.0 when I worked for NewLevel (, , ). But as you may notice, this blog is based on dasBlog, not WSS 3.0...

So what happened? First of all, WSS was eating away too many resources from my little server. Second, I knew WSS doesn't accept trackbacks by default, so you either should write your own webparts or find them on the net ( has some blogparts for WSS 2.0). Anyway I needed a good solution for the Windows Platform, no cost (in terms of financial transaction) and with a smaller footprint than WSS 3.0; it's called dasBlog.

Configuring dasBlog was real easy, as was customizing (I'm leaving the two issues I had for a later post). If you know a little about HTML and CSS, you're equipped to do some customization. Like this blog's theme, which is based on the Nautica 2.2. I did the customization, including the graphics (fractal header and torn-off page) in ~ 6 hours time.

Another nice thing about dasBlog... it's recognized by WindowsLiveWriter (my third little problem with WSS 3.0). Unfortunately some features, like sending trackbacks and adding categories don't seem to work.

Monday, March 5, 2007 7:41:40 PM (W. Europe Standard Time, UTC+01:00)