TAG | troubleshooting
3
Windows Live Essentials 2011 – msnmgr.exe Error “The program can’t start because wldlog.dll is missing from your computer. Try reinstalling the program to fix problem”
23 Comments · Posted by Ferry Meidianto in Windows Live
After long wait, at last Windows Live Essentials 2011 reaches its RTM. There are 2 installer versions we can use:
Today I had chance to install it. Everything else went smooth but I got msnmgr.exe error when I was “first time” starting the Windows Live Messenger.
The error says The program can’t start because wldlog.dll is missing from your computer. Try reinstalling the program to fix problem.
The error message was only thrown once. But… after that every time I tried to login to Messenger it threw error 80040154. The solution link that leads to msxml3.dll fix didn’t help at all for this version nor reinstalling the Windows Live Messenger.
After long day of research, at last I got the solution. It seems the new Windows Live has grouped the wldcore.dll and wldlog.dll (used by Messenger, Contacts and Mail) to a folder c:\Program Files\Windows Live\Shared
Maybe because I did upgrade install it screwed up things.
The solution was simply copy paste those 2 files wldcore.dll and wldlog.dll from c:\Program Files\Windows Live\Shared to
- c:\Program Files\Windows Live\Messenger
- c:\Program Files\Windows Live\Contacts
- c:\Program Files\Windows Live\Mail
Now I can login to Windows Live Messenger and enjoy the whole Windows Live Essentials 2011 products.
Make donation to this article:
error · Fix · troubleshooting · Windows Live Essentials · windows live messenger · wldlog.dll
26
How to Solve SharePoint Designer’s Check In Issue
No comments · Posted by Ferry Meidianto in SharePoint
Been 2 days I couldn’t check my files in and the SharePoint Designer keeps throwing below error on every Check In.
At last I found a fix on it.
The error was because I opened a Site using it’s IP Address, for example:
http://192.168.11.22:3445/MySite
The solve is by opening that site using the Computer Name (in my case I’m working locally – LAN), for example:
http://MyServerName:3445/MySite
If you’re working on the internet site, I think the fix is the same. Use FQDN, for example:
http://www.MyDomain.com/MySite
Hope this help.






