Ok...the problem corrected without my intervention approx 36hrs ago. AND
today I finally got a response back from Customer Support....it was a server
issue....now THAT was timely.
I've suggested to them that the "Service Status" link on the sign in window
should be fixed, to include info regarding this type of server issue, to
preclude the false impression that there is NOTHING wrong with Microsofts
equipment and that the problem must be the fault of the user in the field.
This would cut down on the frustration level on our part and preclude lots of
people from trying all sorts of drastic measures on their own (to no avail).
As it stands now, when you click on the sevice status it just says " All
Systems are stable and running" which is hoooey.
"Fernando Gómez" wrote:
> Hello,
>
> it's been 25 hous now since I can't connect to the messenger. It's annoying,
> really annoying... :-(
>
> "Jonathan Kay [MVP]" wrote:
>
> > Greetings,
> >
> > This error code indicates a server-based problem accessing your account and is usually
> > resolved within 24-hours.
> >
> > --
> > Jonathan Kay
> > Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
> > Associate Expert
> > http://www.microsoft.com/windowsxp/expertzone/
> > Messenger Resources - http://messenger.jonathankay.com
> > All posts unless otherwise specified are (c) 2007 Jonathan Kay.
> > You *must* contact me for redistribution rights.
> > --
> >
> > "Fernando Gmez" <Fernando > wrote in message
> > news:239B7875-BFB1-49E5-8B9D-...
> > >
> > > Hello fellows,
> > >
> > > I'm the same as you here. I've been unable to log to MSN with one account; I
> > > created another one and that's working fine. As some of you, I had the same
> > > problemo back in October. This last time, I sent a mail to tech support and
> > > they replied me five days later, saying that they had problems with their
> > > server. So today I changed some registry settings to point to another MSN
> > > server, yet it yielded no result. It's been 12 hours now and still with no
> > > messenger. Grrrrr....
> > >
> > > "dragon1" wrote:
> > >
> > >> Same thing here guys...started on the 22Jan....same errors as you guys are
> > >> getting. I've also sent message to tech support and have an incident number
> > >> issued but no response yet. And as you say when i checked the status of
> > >> system it just says everything is 'ducky'....lol...ya sure...this same thing
> > >> happened to me also last Oct.."fixed itself" 2 days later. Ask me if I'm
> > >> ****ed off.
> > >>
> > >> "Lordthomas21" wrote:
> > >>
> > >> > I'm getting the same errors as Gene. 81000306 or 81000314. I was able to use
> > >> > this Friday with no problem. I tried another account on my computer and it
> > >> > worked just fine. Gotta be an account problem on Microsoft's servers. I
> > >> > emailed for assistance to MS at support.live.com to help expedite my account
> > >> > problems. Would suggest you do the same if your having this problem.
> > >> >
> > >> > "Gene Rayburn" wrote:
> > >> >
> > >> > > I've been getting some connection issues today (81000306 and I think 81000314
> > >> > > was the other one) on one of my accounts, while my other one logs in fine. I
> > >> > > also cannot login to this account in web messenger
> > >> > >
> > >> > > I had this same problem back in October when it took Microsoft a few days to
> > >> > > fix the problem (after many angered users posting on this newsgroup). I hope
> > >> > > it won't take that long this time.
> >
> >