Hi
I am using Windows live Messenger 9 beta and its giving me Error 8100078 again and again anybody help!
Hi
I am using Windows live Messenger 9 beta and its giving me Error 8100078 again and again anybody help!
Uninstall and then reinstall the Windows live messenger 9.
download fresh copy from here Windows live messenger 9.
Since the release of Windows Live Messenger 9 beta, servers Microsoft tests are saturated and some users unable to connect to the service. They receive an error message 81000378 accompanied by the "Windows Live Messenger can not access your address book." Here's how to resolve this incident ...
The error 81000378 ( "Windows Live Messenger can not access your address book") betrays a saturation server connection Microsoft. The error occurs often at each update and change the version of Windows Live Messenger. It is particularly common at this time, with the release of the beta.
There are two solutions to this problem:
Solution 1: patience!
The first solution is to simply wait! In general, just try to connect an hour later and the problem likely to resolve itself.
Solution 2: Trick!
The second solution is to give a small helping hand to Windows Live Messenger to help locate servers relief probably less congested.
- Start a command prompt in administrator mode (with Vista: CMD then [Ctrl] + [Shift] + [Enter])
- Enter the following commands now validating each line by [Enter]:
CD \
CD WINDOWS
CD SYSTEM32
CD DRIVERS
CD ETC
HOSTS ATTRIB-R
NOTEPAD HOSTS
- The notebook is in charge with a text file of settings IP address and DNS.
- Add at the end of file the following lines:
- 65.54.239.80 messenger.hotmail.com
- 65.54.239.80 dp.msnmessenger.akadns.net
- Save the file and restart the PC
- Try a new connection to the service
- An hour later, it is imperative to come republish the HOSTS file and put the two lines added in comments by adding a "#" before each.
NOTE:
This trick is not guaranteed. The problem may be linked to a more serious dysfunction servers Live Messenger. In this case, only the first solution (patience) will resolve the incident!
Very very thanks for awesome reply. I'll try this and I'll tell you the further repot.
Bookmarks