What happened to the Messenger Plus! forums on msghelp.net?
Shoutbox » MsgHelp Archive » Messenger Plus! for Live Messenger » WLM Plus! Help » WLM Isnt Working Error Code: 800706ba

WLM Isnt Working Error Code: 800706ba
Author: Message:
JuelzTheGreat
New Member
*


Posts: 2
Joined: Mar 2009
O.P. WLM Isnt Working Error Code: 800706ba
For Some Reason i can find any information on this Error Code.

Its Just Says "We Cant Sign you into windows live messenger - Signing into windows Live messenger Failed because the service is temporarily  unavailable...etc.
Error code: 800706ba"

Help Anyone?

This post was edited on 03-29-2009 at 05:06 AM by JuelzTheGreat.
03-29-2009 05:05 AM
Profile E-Mail PM Find Quote Report
ryxdp
Senior Member
****


Posts: 804
Reputation: 16
29 / Male / Flag
Joined: Jun 2006
RE: WLM Isnt Working Error Code: 800706ba
Like the error message says, the service is temporarily unavailable. You just have to wait a bit for it to come back up.

The error code appears to be some sort of RPC timeout error, I guess some of the Messenger servers are down or under maintenance perhaps.

This post was edited on 03-29-2009 at 05:09 AM by ryxdp.
03-29-2009 05:07 AM
Profile PM Find Quote Report
JuelzTheGreat
New Member
*


Posts: 2
Joined: Mar 2009
O.P. RE: WLM Isnt Working Error Code: 800706ba
oh really? case this error just recently happened. i just upgraded my messenger and all of a sudden after installling it and tried to sign in and i just happened to come across this error....Though i signed into Messenger from another computer and it worked perfectly fine...

This post was edited on 03-29-2009 at 05:14 AM by JuelzTheGreat.
03-29-2009 05:13 AM
Profile E-Mail PM Find Quote Report
AustinBrock
New Member
*


Posts: 1
Joined: Oct 2009
RE: WLM Isnt Working Error Code: 800706ba
This is a bit of an old thread, but it took a translation of a Japanese website to find a solution, so I thought I would post here in the hope that it'll help people cure their issue.

I was also getting an "Invalid IP" warning under the connection diagnostics.

Anyway, the problem was that the "DCom Server Process Launcher" needed to be started and set to automatic.

Start > Run or Windows Key + R
Services.msc
Find "Dcom Server Process Launcher"
Right mouse click, goto Properties.
Set to "Automatic", apply, and then click "Start".
Click ok, and close Services.

You may need to restart for it to take effect.

This post was edited on 10-21-2009 at 11:09 PM by AustinBrock.
10-21-2009 11:09 PM
Profile E-Mail PM Find Quote Report
« Next Oldest Return to Top Next Newest »


Threaded Mode | Linear Mode
View a Printable Version
Send this Thread to a Friend
Subscribe | Add to Favorites
Rate This Thread:

Forum Jump:

Forum Rules:
You cannot post new threads
You cannot post replies
You cannot post attachments
You can edit your posts
HTML is Off
myCode is On
Smilies are On
[img] Code is On