Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Upgraded to WLW 2009 and Now It Hangs RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I just upgraded to WLW 2009 and now when I try to publish a post it hangs with the animation of updating the post.  I let it go for about 30 minutes before having to "End Task" it.  I had just posted successfully with a previous version earlier today.  It also appears to hang when I try to "Update Account Configuration".  At least that has a "Back" button to get out of it.

    Any ideas why this would occur?  I checked my firewall and it's not blocking anything.
    Wednesday, January 7, 2009 4:40 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    My apologies for the premature posting.  It was my firewall causing the issue.  I had tried to upgrade WLW using the "web" version which seems to have caused my firewall to hang.  I ended up downloading and installing the stand-alone version but every new application trying to access the Internet was denied by the firewall because it was still hung up with the "web" WLW installer.  During a reboot, something "clicked" and then there was a flurry of requests from the firewall to allow programs to access the Internet.  Now that I've rebooted, WLW is able to access my blog service.

    Shouldn't there be a timeout when publishing in WLW for such events with an error message indicating that it was not able to reach its destination?
    • Marked as answer by Eros256 Wednesday, January 7, 2009 6:37 PM
    Wednesday, January 7, 2009 6:37 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    My apologies for the premature posting.  It was my firewall causing the issue.  I had tried to upgrade WLW using the "web" version which seems to have caused my firewall to hang.  I ended up downloading and installing the stand-alone version but every new application trying to access the Internet was denied by the firewall because it was still hung up with the "web" WLW installer.  During a reboot, something "clicked" and then there was a flurry of requests from the firewall to allow programs to access the Internet.  Now that I've rebooted, WLW is able to access my blog service.

    Shouldn't there be a timeout when publishing in WLW for such events with an error message indicating that it was not able to reach its destination?
    • Marked as answer by Eros256 Wednesday, January 7, 2009 6:37 PM
    Wednesday, January 7, 2009 6:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Normally there is a timeout.  I think it is set to 1 minute currently.  However, I would venture a guess that your firewall was holding up the request before the timeout timer event started.  I don't believe it starts till it thinks it has sent the request.  If it never sends, it can never timeout.
    -Brandon Turner [MSFT]
    Wednesday, January 7, 2009 11:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Brandon,

    Thanks for the explanation.  I wondered if that might be the case.  It would be good though if there were another timer that if after 5 minutes it has not received a response to pop up a message asking to retry or cancel.  It just seems messy to have to kill a process for something as simple as that... IMO.
    Friday, January 9, 2009 1:41 AM