Blog Hiccups

Btw, the entire site had an upgrade to a newer version of Community Server last night, as a consequence, some things are somewhat confused right now. 

In general, the transition has been pretty seamless, but there are some quirks (like the extra blank lines in my top post).

The good news is that the Telligent guys are working on the issues as they've been reported, and the issues should be resolved really quickly.


Comments (11)

  1. Anonymous says:

    The good news about the web is easy and automatic deployment.

    The bad news about the web is easy and automatic deployment.

    Beside the breaking changes to the Atom feed that I’ve been running into this morning (curable by unsubscribing and resubscribing to the RSS 2.0, but a painful experience), I notice that I often get a “this request cannot be completed” or words to that effect when going directly to blog pages (to get the RSS 2.0 feed link). Usually I can get it after a couple of refresh attempts.

    This brings me back to a question I’ve always wondered about since I learned that Blogger is most likely to break on a Thursday (when they do system-wide updates).

    What is an effective QA process for a web site? What’s the equivalent of automated regression testing, nightly builds, and all of those good things? What’s the feedback process for capturing incident reports in a form that reach someone who can act on them. How do you roll-back after an “uh oh?” and so on.

    I’m asking because I don’t know. But I do get to experience live failures a lot as a visitor to many sites and often as an eCommerce customer. I’m baffled how this can be managed.

    I’m super-conservative with my personal sites, but I don’t test for multiple browsers I have made no effort to discover what the accessibility guidelines are, for example. (I am in denial about mobility provisions altogether.)

  2. Anonymous says:

    Oh, while I’m here, “receive” is misspelled in the Comment Notification item, and there is a missing space between “register” and “here.”

  3. Anonymous says:

    it seems that none of the Atom feeds are worked… I had to switch to RSS.

  4. vince says:

    It’s a bit amusing that with all the resources MS has, it can’t even arrange to have a blogging software upgrade go correctly.

  5. Anonymous says:

    And I thought the lack of availability to at times was due to an effective DoS due to everyone trying to get to the IEBlog!

  6. Anonymous says:

    Larry – Got to say this. Your’s is the best blog of all the MSDN ones. So we could tolerate the little blog hiccups as long as we can read some kick ass content.

    BTW, did anyone notice that Larry ran out of great stories and thus ended up with this post?!

    Vince – Larry wasn’t working on the blog upgrade. That makes me think – Larry did you ever try/write a modern day Web Application? What are your thoughts on this subject?

  7. Dean Harding says:

    vince: is run by a company called Telligent, not Microsoft.

  8. Anonymous says:

    “Telligent. Exceptional Service. Predictable Results.”


  9. vince says:

    > vince: is run by a company called

    > Telligent, not Microsoft.

    Yes, I realize that. And if they can’t do the job maybe MS should find someone else.

    It looks silly if I tell someone "hey, look at this MS guys blog, he tells about how committed MS is to backwards compatibilty, that you can upgrade with minimal downtime or fuss" only to have them try to go to the blog and say "oh, it’s down due to a poorly run upgrade".

    It doesn’t matter who runs the place, if they have a microsoft URL it reflects poorly on the company.

  10. Anonymous says:

    This is getting ridiculous.  This morning I have tons of new feed entries from MSDN bloggers.  Oh no, I think.  They’ve hacked the feeds again.

    Whatever it was, some kind of site-wide refresh/update that apparently has nothing to do with feed content, it causes all of the feeds to appear changed and all of the RSS 2.0 ones I have switched to and all of the Atom ones that I haven’t fixed because they are quiet have refed their quota.

    So I have to look at all of them, and see if they are empty atom ones, the ones that are broken and no one has done anything about (I suspect it was an intentional breaking change).

    For the atom one I have to delete the bogus feed entries, unsubscribe from the feed, use an old saved feed entry to go to the web site, find the RSS 2.0 button, fetch it (sometimes the XSLT fails), have NewsGator subscribe to it, go back and edit where I want the feed to be delivered in my Outlook organization, select all of the fresh RSS 2.0 copies I got, move them to the intended destination, delete the automatically created folder, and then go into my collection and see which ones are duplicates of ones I kept, which ones I didn’t keep and delete them again, etc.  (I discovered that some of the authors have deleted articles and they haven’t refed, but I still have copies.)

    For the RSS 2.0 ones that have refed (I can’t tell why), I just move them into the folder where I collect that feed, then check which are duplicates of ones that I kept.  Then mark all as read, etc.

    The procedure I have for sorting stuff that I hold onto works great except when the feeds urp, then I have to be careful. I’ve made two mistakes already and I’m only halfway through this morning’s vomitus.  

    Hey the sun is shining and I can catch up on system backups and housekeeping while the rest of the world is watching some kind of athletic event.  


  11. Anonymous says:

    Scott Watermasysk contacted me today and I dug a little deeper in finding information that he could troubleshoot with me.  I discovered that (1) my version of NewsGator Outlook 2.5.9 was out of date and the currentt 2.5.12 solves the problem with its support for Atom 1.0.  

    And I had filed an update notice from NewsGator last September and then not done anything about it.  

    My sad story is now at

Skip to main content