Error: 80040154 when signing in to live messenger 2009
ntentes
04-02-2009, 05:22 PM
i dowloaded and installed the new windows live messenger 2009 but every time i try to log in it says "signing in to windows live messenger failed because the service is temporarily unavailable. Please try again later. it has an error called error: 80040154. my internet is working perfectly fine and i also went to a website with steps on how to fix it but it still doesn't work!!?!?!
Please help.
Bobbye
04-03-2009, 04:06 PM
What operating system are you using?
Is it 64 bit?
Some good troubleshooting for this error with links here: http://oss.netfarm.it/wlm.php
Ad
04-03-2009, 04:06 PM
ntentes
04-04-2009, 10:11 AM
how do i check that again?
Bobbye
04-04-2009, 10:32 AM
Try Control Panel> System> General tab.
Heldarion
04-05-2009, 08:39 PM
Hey, I got that contacts.msi or whatever was suggested in the link in your post #2 in this topic and I thought wow finally I can log in BUT!
What happens now is that it looks like it's actually gonna log in, then it just drops back to as if I never entered the password O_O
How the hell to fix this?
edit: now I'm actually getting this again: Windows Live Communications Platform has encountered a problem and needs to close.
-.-
Bobbye
04-06-2009, 11:24 AM
Windows Live Communications Platform has encountered a problem and needs to close.
Find the Error in the Event Viewer that corresponds to the time of this message.
Start> Run> type in eventvwr
Do this on each the System and the Applications logs:
1. Click to open the log>
2. Look for the Error>
3 .Right click on the Error> Properties>
4. Click on Copy button, top right, below the down arrow
5. Paste here (Ctrl V)
For Vista: http://www.windowsnetworking.com/articles_tutorials/Monitoring-Event-Logs-Windows-Vista.html
You did not answer: What operating system are you using?
Is it 64 bit?
For more information, see Help and Support Center at [microsoft link]
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 6c 63 ure wlc
0018: 6f 6d 6d 2e 65 78 65 20 omm.exe
0020: 31 34 2e 30 2e 38 30 35 14.0.805
0028: 30 2e 31 32 30 32 20 69 0.1202 i
0030: 6e 20 6e 74 64 6c 6c 2e n ntdll.
0038: 64 6c 6c 20 35 2e 31 2e dll 5.1.
0040: 32 36 30 30 2e 35 35 31 2600.551
0048: 32 20 61 74 20 6f 66 66 2 at off
0050: 73 65 74 20 30 30 30 31 set 0001
0058: 62 31 66 61 0d 0a b1fa..
Bobbye
04-06-2009, 07:05 PM
Would it make you feel any better if I told you that a multitude of users are having this same problem? And so far, there does not seem to be one firm answer. So here is some information that hopefully you can use:
I found this particularly interesting:
wlcomm.exe is part of the Windows Live Messenger Contacts Server.
Recommendation: wlcomm.exe uses excessive system and memory resources with no corresponding benefit. Applications such as these should be disabled to improve overall system performance
http://forums.techarena.in/windows-messenger/1095282.htm
The ntdll.dll file is a file created by Microsoft that has a description of "NT Layer DLL" and is the file that contains NT kernel functions. ntdll.dll can become corrupt, but if it did, you wouldn't be able to boot.
These two solutions worked for these people:
There was a solution for me.I had installed nVidia Forceware Access Manager. After removing it, everything works fine.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.live.messenger&tid=07137163-891c-435e-bb1b-42684b3dfa3e&cat=&lang=&cr=&sloc=&p=1
AVG anti-virus program has been causing problems letting users log-in. If your unable to login, make sure you check your firewall settings, and if you’re using AVG try disabling it.
http://www.blogsdna.com/1725/fix-windows-live-messenger-9-2009-build-1202-login-sign-in-issue.htm
Please let us know if you find somethings that works for you- maybe we can pass it on to the next person who asks. Sorry I can give you anything else- maybe Microsoft will issue a patch! lollollol
Heldarion
04-07-2009, 11:10 AM
Would it make you feel any better if I told you that a multitude of users are having this same problem? And so far, there does not seem to be one firm answer.
LoL, the only implication I get out of this is that WLM is seriously screwed up, means bad work was done. Kinda doesn't make me feel better xD
I think for me only the first suggestion is viable (got Avast - I guess this shouldn't cause problems, or should it?) so how do I disable wlcomm.exe.
Thanks for the help anyways :)
Bobbye
04-07-2009, 01:49 PM
so how do I disable wlcomm.exe.
Take it off of Startup:
Start> Run> msconfig> enter> Selective Startup> Startup tab> UNCHECK any processes related to WLM> Apply> OK.
You may have to go into the programs itself and disable it. Use Windows explorer: right click on Start> Explore> Programs> click on WLM> check files on the right screen.
NOTE: the first time you reboot after making a change on Startup, you will get a nag message that you can ignore and close after checking 'don't show this message again.' Stay in Selective Startup.
I found another comment:
i am rolling back to 8.5 for now. Maybe in another 6 months enough people will have this problem MS will figure it out.
Ad
04-07-2009, 01:49 PM
Heldarion
04-08-2009, 09:16 AM
Take it off of Startup:
Start> Run> msconfig> enter> Selective Startup> Startup tab> UNCHECK any processes related to WLM> Apply> OK.
You may have to go into the programs itself and disable it. Use Windows explorer: right click on Start> Explore> Programs> click on WLM> check files on the right screen.
Hm. The only process related to WLM was some msnmsgr.com/background or something and it didn't really change anything. However, I found the file itself but can't really see a way to disable it (at least no such option) - should I make it read-only or?
And since I doubt it's gonna work, how do I roll back to 8.5? Whatever WLM I try to download is that latest shitty version, can't really find anything solid :|
Bobbye
04-08-2009, 11:20 AM
The WLM is within the Window Live program.
So modify this:
You may have to go into the programs itself and disable it. Use Windows explorer: right click on Start> Explore> Programs> click on WLM> check files on the right screen.
Instead, click on the Windows Live program, then look on the right screen for the messenger.
Consider uninstalling the program then installing the earlier version. As I mentioned, there are a lot of questions about this problem but very few answers.
Heldarion
04-09-2009, 08:56 AM
-.-
Uninstalled the latest version (14.something), tried installing MSN 7.5 and it just says that I have a newer version installed and that I should uninstall it before continuing. Like wtf? I uninstalled 3 times over and computer still says it's there (with numerous restarts inbetween).
Might as well just go to some other client :x
Bobbye
04-09-2009, 09:58 AM
Use the Windows Installer Cleanup Utility to remove any remaining files:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
It's a small download, save to the desktop, run to install, open then highlight the remaining WL and WLM files.
ntentes
04-21-2009, 06:59 PM
by the way i have mocrosoft xp proffesional and it doesnt say in general tab 32 or 64 bit...i dont know what it is. its a pretty old computer, its probably 5 to 7 years old
Bobbye
04-21-2009, 08:34 PM
ntentes, you started this thread two weeks ago. You most likely have 32bit.
Please give update of what's happening with the system>> exact error message and what you are doing when it comes up.
gnowave
05-18-2009, 02:12 PM
Use the Windows Installer Cleanup Utility to remove any remaining files........:
......It's a small download, save to the desktop, run to install, open then highlight the remaining WL and WLM files.
no, dont bother, for most folk it dosnt work,
better to try ZapMessnger, google for it, then instal, and start it, ( on instalatio n it will run auomatically, clik start when it starts up), and it will clean out all the bunk left over.
THEN go into add or remove programmes (assuming you are on XP ), and uninstal windows live anything at all..
now re-instal earlier version..
only problem you may get is it may give you an error 80040154
and i have seen NO conclusive resolve for this at all...
but i was given windows clean up utility by the official windows team, and really i was flabbergasted that it didnt do anything for me.. and a non windows team device (ZapMessenger) did it in seconds flat!!
gnowave
05-18-2009, 02:15 PM
oh! also for error: 80040154, it was suggested to reregister a .dll, that didnt work,
also to instal an msxml3.dll (?) and THAt too didnt work,
and am finding no answers even from "experts having this issue
ho hum! maybe back to yahoo, skype, or anything, never had so much hassle from any other messenger
Bobbye
05-18-2009, 10:28 PM
To gnowave:
no, dont bother, for most folk it dosnt work,
It worked for me.
also to instal an msxml3.dll (?) and THAt too didnt work,
and am finding no answers even from "experts having this issue
Rudeness is a big turn off for us. We are all volunteers, out help is free. Only those who are inexperienced waste time telling people they are experts!
ZapMessenger is specifically for the MSN Messenger- it might indeed work for that program. The Windows Installer Cleanup Utility is not tto uninstall programs> it should be used to remove orphan files that can't be deleted.
but i was given windows clean up utility by the official windows team,
There is someone using this board who represents himself as a member of the "official Windows team." He isn't and neither are the other 3 people who represent themselves that way. Every forum they have posted on has questioned them on this.
Error: 80040154 is a COM error. Do you even know what that is?
hawkeye1234
09-22-2009, 09:31 PM
hi im having the same problem
long story short, new computer, deleted windows messenger because it wasnt working, tried to reinstall it said it was already installed, found a program called zapmessenger and it deleted it off of my computer, reinstalled it opened up, i tried to log in got error 80040154, tried this method 3 times, still isnt working, went to the official site tried all their methods to fix this and nothing has worked,