Heres some links to step by step instructions which help fix errors you maybe recieving;

• Error 80004005
• Error 80040111 or 80040154
• Error 80048820, 8004840a or 80072ee7
• Error 80048821
• Error 80048823
• Error 80072745
• Error 8100030d
• Error 81000306

Hopefully these will solve your problems you may be experiencing with Messenger. Remember to check out the other articles at Messenger Support Blog relating to other error codes and problems relating to Messenger.

Sign In
The .NET Messenger Service is temporarily experiencing difficulty. You may be unable to sign in. Please try again later.
Last Update: 4/12/2007 3:00:00 PM Pacific Time (GMT -8:00)

As it says, just try again later. It doesn’t appear to be very widespread, I’m having no problems signing in and have the usual number of contacts online. But, traffic to this Web site has increased a little, so there’s definitely something going on.

Last September the same problem could be solved by changing the server which Messenger connects to, I’ve just tested it and it still works.

Update: Looks like I posted this shortly after the problem had already started to come right, I even missed the acknowledgment from Nicole at the Windows Live Messenger blog.

If you have recently purchased an Acer notebook or desktop PC with Windows Vista installed, you can now download a patch from Acer to correct the problem.

Leave a comment on whether or not the patch fixes the problem for you – I’m interested to see if there is anyone else having this problem but from different causes.

» rofl @ you, http://improfile.net/members.php?msn=example@example.com

The Web site has been shutdown to stop it from spreading. The DNS is set to loopback (127.0.0.1) and “Closed for Fraud” is in the whois information.

Kelvin has created a tool called impFix to remove the virus, so give it a try if you believe to be infected with this pest.

Among all the posts for help in the newsgroups, Jimmymac posted (6th post down) explaining he fixed it by deleting messenger’s registry settings. Jonathan Kay created a .reg file that will automatically delete the settings for you, remove_msgrsettings.reg.

Before running the .reg file, completely exit Windows Live Messenger by right clicking the buddy icon near the clock and clicking Exit. Once you have run the file and clicked Yes, try signing in again.

One of the side effects of this solution is you will lose some customised settings, but hopefully you’ll find it’s worth it!

Leave a comment if this does or doesn’t work for you.

Add the following to entries to your hosts file:

65.54.239.80 messenger.hotmail.com
65.54.239.80 dp.msnmessenger.akadns.net

As he states, it’s a fairly dirty fix. Be sure to remove the two entries once the problem has been resolved on the server end. This post will be updated when that happens.

Update: Looks like it is now fixed for most users, make sure to revert any changes you made to your hosts file.

The biggie is a fix for error 80004005, caused by Messenger miscalculating the length of the local friendly name upon sign in:

Say limit is 6 characters per friendly name. Messenger would let me type “LeahJ” no problem, because it was counting the whole emoticon as one character, and thus my friendly name was 5 characters total. But the next time I tried to sign-in, Messenger would do a check which would count each character of the emoticon separately and thus “Leah:-)” added up to 7 characters, which is over the max limit of 6. Error.

You can get this new release from get.live.com

Windows Live Messenger is currently experiencing technical difficulties

Person A: So what kind of technical difficulties are we talking?

Person B: Apparently, some people are signing in and then are unable to see some/all of their contact list. And a little notification that says something about “Due to a connection problem…”

Person A: Oh dear! What should these people do?

Person B: NOT WORRY. The Messenger team is working hard to fix the problem. They sincerely apologize for any inconvenience this is causing Messenger customers. They’re asking that people be patient and check back on the blog for more information.

Person A: Guess what I heard? Even the Messenger Blogger, Leah, is running into this problem on her computer. So she’s gonna make SURE this gets fixed as fast as possible. Isn’t that reassuring?

Person B: That is very reassuring. Will she let us know when there is more information?

Person A: Absolutely. (She promised me herself)

check out these pics of us! http://p1392.pic-myspace.info
check out this pic of you on myspace! p1392.pic-myspace.info

According to the original post, it was using the domain pics-myspace.info, but on that same day pic-myspace.info was registered and the worm started using that instead. The whois information looks valid…?

Some helpful visitors have posted comments on how to remove it, check out SgSiaoKia’s comment and head over to Serena’s site for full instructions.

In “C:\Documents and Settings\<your user>\Local Settings\Application Data\Microsoft” there is two folders one called “Windows Live Contacts” and one called “Messenger” I deleted both of these and now I’m not having any problems.

The folder Messenger is data for the Sharing Folders feature, and the Windows Live Contacts folder appears to be where the list cache is now stored in Windows Live Messenger, as opposed to ListCache.dat in MSN Messenger 6.x and 7.x. The sub-folders in Windows Live Contacts are the sign-in addresses of all users that have signed in on that Windows account, and there are two sub-folders in each of those: real and shadow. The data in these folders seems to be what is encrypted when you enable Encrypt contact list data so that it is not accessible outside of Windows Live Messenger.

I’m not sure why it just isn’t encrypted by default, or why e-mail addresses are used instead of Passport IDs in the Windows Live Contacts folder.

I earlier made a program called List Cache Deleter which lets you remove ListCache.dat if it becomes corrupt and you are unable to sign in.