Windows Live Messenger

Discussion in 'Windows Desktop Systems' started by michali, Jun 28, 2006.

  1. michali

    michali OSNN Junior Addict

    Messages:
    15
    I have been using WLM Beta for months now and never had a problem signing in until today. I have not been able to sign in at all today on either computer. I keep getting a 81000314 error message. I know there have been some problems, but most seem to have been resolved, except for mine! I upgraded to the new final build but that made no difference. Should I just be patient and hope I will be able to connect in the morning? Has anyone else had this problem?
     
  2. Bman

    Bman OSNN Veteran Original

    Messages:
    8,799
    Location:
    Ottawa, Ontario
    I have not had this problem, at least wait till tommorow sometime. If not, reinstall again.
     
  3. Johnny

    Johnny .. Commodore .. Political User

    Messages:
    5,015
    Location:
    Happy Valley
    try updating it to the latest version ...
     
  4. michali

    michali OSNN Junior Addict

    Messages:
    15
    Thanks for responses....I did upgrade as I said in my post and it made no difference but I am now on again! I guess it just needed some patience.
     
  5. Bman

    Bman OSNN Veteran Original

    Messages:
    8,799
    Location:
    Ottawa, Ontario
    np, it's always server problems about 90% of the time
     
  6. Khayman

    Khayman I'm sorry Hal... Political User Folding Team

    Messages:
    5,518
    Location:
    England
  7. Geffy

    Geffy Moderator Folding Team

    Messages:
    7,805
    Location:
    United Kingdom
    do you have a netgear dg834 dsl router?
     
  8. Johnny

    Johnny .. Commodore .. Political User

    Messages:
    5,015
    Location:
    Happy Valley
    I had a problem when I had my linksys router. So, it could very well be a router problem ...
     
  9. michali

    michali OSNN Junior Addict

    Messages:
    15
    No, I have a linksys router and have had for nearly a year now, so it could not be that that was causing the problem. It was obviously just the server that was down as it is fine now.