- This topic has 10 replies, 2 voices, and was last updated 17 years, 6 months ago by
.
-
Posts
-
Hey there,
Ever since attempting to install the latest Windows Live Messanger Beta (Version 2009, Build 14.0.8050.1202) I have been getting the error:“Windows Live Communications Platform has encountered a problem and needs to close.”
If I choose to send an error report, or not to send one it takes me to the login screen of WLM again. This error occurs about 5 seconds into signing in. If I keep the error screen up after about a minute or so WLM freezes untill i click “Send error report” or “Don’t Send” and when I do this it presents the error:“We can’t sign you in to Windows Live Messanger” Error code: 80004002
When I debug the process in Visual Studio it shows this:
(Many Dlls excluded due to space difficulties. For full log: megaupload.com/?d=TKL1ZPOY)
‘wlcomm.exe’: Loaded ‘F:Program FilesWindows LiveContactswlcomm.exe’
‘wlcomm.exe’: Loaded ‘F:Program FilesUnlockerUnlockerHook.dll’, Binary was not built with debug information.
‘wlcomm.exe’: Loaded ‘F:WINDOWSsystem32nview.dll’
‘wlcomm.exe’: Loaded ‘F:Program FilesLogitechSetPointGameHook.dll’
‘wlcomm.exe’: Loaded ‘F:WINDOWSsystem32sxs.dll’
‘wlcomm.exe’: Loaded ‘F:WINDOWSsystem32rsaenh.dll’
‘wlcomm.exe’: Loaded ‘F:WINDOWSsystem32dssenh.dll’
‘wlcomm.exe’: Loaded ‘F:WINDOWSsystem32apphelp.dll’
First-chance exception at 0x7c91b1fa in wlcomm.exe: 0xC0000005: Access violation writing location 0x000110d0.
The thread ‘Win32 Thread’ (0x5c8) has exited with code 0 (0x0).
The thread ‘Win32 Thread’ (0x17a0) has exited with code 0 (0x0).
Then about a minute later the log continues:Heap corruption detected at 001477F0
Heap corruption detected at 000D4D70
First-chance exception at 0x775927d1 in wlcomm.exe: 0xC0000005: Access violation reading location 0x00740066.
Heap corruption detected at 00147990
First-chance exception at 0x77566c9d in wlcomm.exe: 0xC0000005: Access violation reading location 0x00740081.
The thread ‘Win32 Thread’ (0x11fc) has exited with code 0 (0x0).I have tried:
A complete reinstall inclusive of deleting temp files and all application data and temp appilication data. (Inclusive restart)
Rollback of version which works but does not allow me some of the features. (Must be significantly back for this error not to occur)
Deletion of contact data due to WLCP apparently being linked to sync of this data.
Reinstall of Windows. (This was not soley for WLM to work… of course..)
Several restarts.All this data leads me to believe that it is an application conflict, this is what I have tried in this area:
Shutting down of all firewalls and antivirus programs before launching the program.
Multiple virus and malware scans to remove any conflicting virii.
Shutting down applications that have been known to cause conflicts. (e.g. Netlimiter)I have yet to try shutting down processes one by one. There are only a few persistant processes however over the second install of windows, these would be:
Avira Anti-Virus
Microsoft Visual Studio 2008
Driver Programs (e.g Setpoint, G11 Keyboard Controller)
CD Emulation SoftwareMy Specs are:
Microsoft XP SP3
AMD Athlon 64 X2 4200+
4 GB RAM
Nvidia 8800GT OCI’m wondering if anyone has any ideas for me as I am completely stumped.
Are you experiencing problems with any other programs which might help us pinpoint something with regard to a conflict. Do other IM programs such as Yahoo or Skype work ok?
Are you using a router and if so have you checked to ensure you’ve allowed WLM through any hardware firewall the router might have.
When you ran virus and malware scans was anything significant found? I’m not referring to cookies or simple spyware – but to virus or trojans etc…
The ports are apprently 1-65000 so I can’t exactly port forward all those.. and my brother uses the same router so I wouldn’t want to limit his connectivity. I did have a trojan for a short while on the second installation of windows… however I have run multiple scans with about 5 different malware/virus removers and im fairly confident I do not have any anymore.
I am able to use Skype and many other IM programs including earlier versions of MSN as stated in the post.
Aports (a port finding process) shows two ports used by WLM when logging in and these obviously will be dynamic choices by the program.
So you reformatted your drive, reinstalled Windows and a trojan managed to survive that? Or you became infected after you reinstalled Windows? It makes a big difference.
Anyway…if other IM programs are working, it’s still more likely that you have a corruption in your WLM (although there is malware that could still be the culprit – but it’s less likely). The best way to truly remove it is to use the Windows CleanUp Utility. I don’t typically recommend it unless you truly need a thorough wipe of WLM but in this case it sounds like you really might. I know you removed and reinstalled it previously – but in many cases there are files and folders that may remain and this is really the best way to wipe it thoroughly. Please do not remove any other components with this – only WLM at this time.
Then, when you reinstall it, please make sure you do so from the official site. While you can obviously install a lot of the other Live components with the new installer – I’d strongly suggest only working with WLM until the problem is resolved.
Please let me know if this makes any difference and if the error persists.
I got the virus after I reinstalled windows, and as far as I can tell I do not currently have any malware or virii on my computer.
Ok I did as was instructed, I used the cleaner, but i cleaned all Windows Live programs I could see… I then redownloaded the installer, but Microsoft Office Outlook Connector and Microsoft Office Live Add-In were still installed.. I then proceeded to install just WLM. I also cleaned temp internet files and deleted some applicable application data files. But it still seemed to remember who I was… which says to me that its still left some files… Anyway same error.
Upon reinstall of the app I decided to try again… following your directions and not being an idiot and misreading things… I went to delete only WLM and got a runtime error within the cleanup program, I then pressed ok, it quit… i reopened it.. and the program is no longer in the list. So I opened WLM at this stage and attempted to sign in, it did not remember me, which I thought was a good sign.. but same error. I also tried creating a new user but that didn’t work either.
Ok, I then reinstalled after removing JUST WLM with the cleaner (as I said it got a runtime error) and it remembered me, and still got the same error.
“Run-time error ‘-2147024882 (8007000e)’:
System Error &H80004005(-2147467259).”8007000e refers to an Out of Memory error
80004005(-2147467259) is a Fail errorThe fact that you get a runtime error in the Cleanup Utility would seem to indicate that you have some other instability on your machine. I found a thread with the same problem in another forum related to the Cleanup Utility but sadly there was not a good resolution posted.
I did a bit of Google searching. I’m sure if you have SP3 for XP then you also have at least IE6 on your machine yes? If not it could be an issue – but I’d assume that you do. Also, please check and let me know if you are connecting to the internet or WLM through a proxy.
But have a look at this post and see if it helps at all. Most of the other articles with the 8007000e error seem to relate to WMP (Windows Media Player) or Windows ActiveSync. If you’ve been having trouble with either of those it would probably be helpful to know. Or if you’ve been getting any other runtime or Windows errors when using other programs it would be important information in helping to narrow this down.
I truly don’t think the problem is your installation of WLM at this point. Have you updated all the drivers for your various devices after reinstalling Windows? And, have you made sure all the optional updates from Windows were reviewed and any that related to your devices etc installed?
I have IE7, I don’t use WMP and not sure about activesync but I am currently updating my windows… i stopped the updates after SP3, so that may be the issue. I havn’t been getting any other errors with this installation of Windows, no runtime errors or system reboots or BSOD or anything similar, all my drivers are up to date apart from my bios.. but i doubt that would make a difference. I have very little idea why it would be out of memory however.. having just been installed and having a high amount of RAM… and no proxy.
I have been in contact with WLM support staff and they told me to give them some logs and so forth and while searching through I noticed this message in my Event Viewer:
Faulting application wlcomm.exe, version 14.0.8050.1202, faulting module ntdll.dll, version 5.1.2600.5512, fault address 0x0001b1fa.
Which is interesting because ntdll.dll is used by a dozen programs not associated with windows without difficulty, I have downloaded a new version (which is actually version 5.1.2600.2180) Im going to try and replace it when I get my dos up and running, if not ill just revert it back to the old dll. But I really don’t know if it will help/work.
Well, the errors you are getting with regard to memory seem to also be used by any number of different programs and to identify different things. They really don’t seem to have a lot to do with actual memory and you certainly have quite a bit at 4GB RAM.
I’m guessing there is something else going on. It would be good to finish any applicable updates for Windows and drivers etc.
If you’ve been in touch with WLM support I’m sure they’ll be able to give some guidance. Will you please let us know what they find and if it helps you?? It’s always nice to see the resolution and be able to better help others.
Ok, after much time wasted and so forth (And no help from windows live support whatsoever) I concluded that it was a memory issue. Some of my memory was faulty and needed replacing, you can use a program like “Memtest” to conclude this, my scan took about 24 hours and then i stopped it because i had 234 errors in memory, I removed two of my sticks of RAM and now I can sign in just fine. Just thought I should add this solution for anyone else out there.
- You must be logged in to reply to this topic.