Home › Forums › Archives › Instant Messaging › Windows Live Messenger Support › Service Temporarily Unavailable Error 81000314 – only with a certain MSN account
- This topic has 49 replies, 37 voices, and was last updated 17 years ago by
mark_87.
-
AuthorPosts
-
April 17, 2006 at 8:26 pm #123247
angelface26
ParticipantMy IT manager deleted all my settings and other files, this is the webpage that helped him.
it works perfectly, I just have to change back my settings, etc. 😀
July 27, 2006 at 11:56 pm #123251rezurect
MemberWhy don’t u guy’z try a system restore….works for sure…..well it did work for me….
Start>All Prog>Accessories>System Tools>System restore…..
Choose a system restore point…..and yeah your MSN should work fine once it’z done…..
September 13, 2006 at 12:03 am #123252TheVicChick
MemberI don’t know if anyone cares about this, or if I am late on the draw here, but after doing EVERYTHING everyone suggested in this thread, I still did not have a working MSN… so I went to the online webmessenger.msn.com and signed in there, then just by chance I tried my msn messenger again, while I was signed in and it worked. I dont’ know why, it just did. So yeah, I do’nt know if it will work for anyone else, but it worked for me.
I tried ALL the steps listed here right from page one, I restored my system to 3 different restore points and I installed most of the downloadable fixes atleast twice. I uninstalled MSN messenger so many times that it didn’t know if it was installed or not and started the installer automatically if I clicked on the program icon. Nothing worked…
again, sign into your messenger at
webmessenger.msn.com
then sign into your msn. see if that works.
September 13, 2006 at 2:18 am #123253ironmaiden54
MemberHey guys I FOUND THE ANSWER! I read everything on here and I tried EVERYTHING. Still nothing worked, so I follwed some more msn troubleshoot procedures and found the answer! Just click start, then run. enter all of these one by one: note: you’ll get a message after you enter each one saying accepted…all of them will say accepted except 1 seems that it doesn’t…in about 5 min it will come up
REGSVR32 softpub.dll
REGSVR32 wintrust.dll
REGSVR32 initpki.dll
REGSVR32 Rsaenh.dll
REGSVR32 Mssip32.dll
REGSVR32 Cryptdlg.dll
REGSVR32 Dssenh.dll
REGSVR32 Gpkcsp.dll
REGSVR32 Slbcsp.dll
REGSVR32 Sccbase.dllSeptember 21, 2006 at 6:00 am #123254Confucious
MemberI have been getting 81000314 all day yesterday on 3 different machines. I can log in no problems with Windows Messenger and have downgraded one PC to 7.5 which works fine.
I do not wan to change my password as I still have a 4 char password – could this be the problem? I have no intention of changing to a 300 char password with caps and numbers or whatever the latest stupid security measures are – I’m quite happy with my 4 char passord which I’ve had for years.
I am using the 812 build – this error message is amaisingly unhelpful! I don’t believe it is a dll or cache problem as it happens on 3 sperate machines (Work, home and laptop) so am leaning towards a password problem unless someone else has any better ideas.
All 3 coms were working fine until yesterday – and I believe all 3 had Windows updates the day before – is it something in there that has broken it?Any help would be appreciated – otherwise it’s back to 7.5 for me!
Thanks
September 24, 2006 at 5:09 pm #123255sensor
Member@princeG 182274 wrote:
…
DEL /s ListCache.dat* Note: This command deletes all the ListCache.dat files in all subfolders. You may see a list of the files that are being deleted.
…Well, I’ve searched the net for a while looking for the description and use of the ListCache.dat files, but didn’t find anything useful. Could you reply to this post putting what that files do?
Thanks a lot =)*complaining mode on*
Couldn’t connect to the web messenger, and the crappy thing is it doesn’t give the reason for not connecting… No, it gives the reason: here is the url in answer:
MSN Web Messenger – te interesting part of the url is just /session/signout.aspx?t=1&errorcode=ERR_SERVER_UNAVAILABLE
LOL? XDBesides that, tried use the REGSVR32 solution to register/update the .dll files said to help, but no succes, too… Waaah, no virtual life =P
*complaining mode off*September 25, 2006 at 4:40 am #123256LarnyLoo
MemberI have this error message too…only for the msn account I WANT to use. I opened a new msn account today and that works fine!
Does this problem ever rectify itself??
I think I’m just too impatient 🙁
September 25, 2006 at 5:04 am #123213Jeff Hester
KeymasterI too am impatiently waiting for this problem to be fixed. I can’t stand it. You’d think MS would get there *expletive* together and fix it. I have tried all the little fixes too, and had my go-go-geeky-gadget-heart broken each time. By the end of this debacle, we’ll need a support group! ;(
10:18 PM
Remarkably, my messenger has now (finally) signed in. Maybe the problem is fixed for everyone!?September 25, 2006 at 5:23 am #123257LarnyLoo
Member@MaddestMax 207901 wrote:
I too am impatiently waiting for this problem to be fixed. I can’t stand it. You’d think MS would get there *expletive* together and fix it. I have tried all the little fixes too, and had my go-go-geeky-gadget-heart broken each time. By the end of this debacle, we’ll need a support group! ;(
10:18 PM
Remarkably, my messenger has now (finally) signed in. Maybe the problem is fixed for everyone!?SAME!! I was just able to sign in aswell!!! Now I feel at ease…. this damn problem has taken up about 4.5hours of my day!!!
So HAPPY!!! 🙂 🙂 🙂
Agreed, a support group is definately needed for this problem, lol.
October 18, 2006 at 2:34 am #123258pax681
Memberwell here’s a fix that WORKS!
on XP go to c:windowssystem32driversetc
and you will see lots of files there.
there are two files you need to make an addition to
first is this one
hosts
right click and open with notepad
it should look like thisQuote:# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost
now place these two lines under the localhost so it looks like this
Quote:# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost
65.54.239.80 messenger.hotmail.com
65.54.239.80 dp.msnmessenger.akadns.netthen onto the next file which is hosts.msn
which looks exactly like the 1st one…because it is really the same but with a diffent nameQuote:Quote:# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost
and add the same two lines that you did before
Quote:Quote:# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost
now place these two lines under the localhost so it looks like this
Quote:# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a ‘#’ symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host127.0.0.1 localhost
65.54.239.80 messenger.hotmail.com
65.54.239.80 dp.msnmessenger.akadns.netREMEMBER TO SAVE THE CHANGES TO BOTH FILES before closing them
then close the windows and then sign into msn.
just worked for me and will work for you too.
Pax681
p.s.you can thank the cold virus for making me cough and splutter myself awake to discovermsn had signed out and wouldn’t sign back in again. a google search privided many crap “fixes” that wouldn’t work but careful checking found this one which works a treat and is simple to doOctober 18, 2006 at 5:03 pm #123260Peebly
MemberI just started having this problem yesterday..and it still hasn’t corrected itself. I have tried logging on both at work and at home…so what I don’t understand is two things..
1)Why, if I am having to fix dll files would it have to be done on multiple computers…
2)Why would this problem all of a sudden happen?. I just don’t get it.
Either way, it has been a day and a half and I am still unable to log in 🙁
October 18, 2006 at 5:40 pm #123259Lord Cutter
Membersame for me
it’s been 2 days now and still couldn’t log in
i tried web messenge rbut that also didn’t work
i hope they fix it soon
i’m rly getting crazy without msnOctober 21, 2006 at 5:08 pm #123261silvertree
MemberAlright I was wondering around the net trying to find a solution to my brand new error code 81000314 I had recieved from my wonderful msn messnger live as I sighned into it. I tried all the information that I could find only to get frustrated to the point that I could not spell any more can you tell? Any way here is how I solved my problem I have no idea how it worked or why it solved my problem but it did hope this helps somebody else out there.
Any way all I did was open my E-mail Outlook Express once that was opened I then sighned onto my msn messenger live account and woot!!! I was in no more error so then I am thinking great now I have to open my outlook express every time I want to sighn into messenger. However after testing by rebooting and trying to sighn into msn messenger with out outlook express being opened I have not had a single error code again it has been a week now with no error codes 🙂
Hope this helped somebody 😉
Silvertree
November 26, 2006 at 3:55 am #123262secretgardenguy
MemberHello all, I was receiving the same error message. I un-installed, ran registry mechanic and re-installed to no avail. Essentially this is a connectivity issue. But not with the .NET servers. All I did was reset my modem (I am using a cable hook up so I am not sure if this will work with DSL or dial up). Pull the power cord from the back of the modem, wait 5 mins and plug back in. Voila! Worked like a charm. You may have to reboot to reset the connection. Hope this works for you!!
S.G. GuyNovember 26, 2006 at 7:09 pm #123219detn8r
ParticipantThanks for registering and posting your solution.
-
AuthorPosts
- You must be logged in to reply to this topic.