SYMPTOMS
When you try to sign in to Messenger, you may receive the following error message:
"Signing in to Messenger service failed because the service is temporarily unavailable. Please try again later. 81000314"
PROBABLE CAUSE
- The Messenger service is temporarily experiencing difficulties.
- The Messenger cache has become corrupted.
TROUBLESHOOTING STEPS
Try the following solutions in the order that they are listed:
1. The Messenger service may be experiencing temporary connectivity issues. To verify the status of the Messenger service, visit http://messenger.msn.com/Status.aspx. The temporary sign-in issues may also be related to a server that you are connected to that is allowing users with some e-mail addresses on the same computer to sign in but not allowing users with other e-mail addresses to sign in.
2. Try to sign in again later.
3. If the issue persists, follow these steps to clear the MSN Messenger cache:
a. If Messenger is running, right-click the Messenger icon in the notification area at the far right of the taskbar, and then click "Exit."
b. Open a Command Prompt window:
- On Microsoft Windows 2003, Windows XP, or Windows 2000, clic k "Start," click "Run," type "cmd," and then click "OK."
- On Windows 98 or Windows Millennium Edition, click "Start," click "Run," type "command," and then click "OK."
c. At the command prompt, type "CD", and then press ENTER.
d. At the command prompt, type the following command, and then press ENTER:
CD %appdata%microsoft
e. At the command prompt, type the following command, and then press ENTER:
CD "MSN MESSENGER"
f. At the command prompt, type the following command, and then press ENTER:
DEL /S ListCache*.dat
Note: The "S" is uppercase.
This command deletes all .dat files whose names begin with "ListCache" in all subfolders. You may see a list of the files that are being deleted.
g. At the command prompt, type "exit", and then press ENTER.
h. Restart Messenger.
4. If the issue persists, send us a connection log file. This log will help us determine the cause of the issue you are experiencing.
a. If you are not already using MSN Messenger 7.0 or 7.5 or Windows Live Messenger, install the latest version:
i. Visit the following Web site:
http://spaces.msn.com/messenger-support/blog/cns!8B3F39C76A8B853F!3772.entry
ii. Determine whether you are running the latest version. Download and install the latest version, if it is necessary.
b. To generate connectivity logs for MSN Messenger 7.0 or 7.5 or Windows Live Messenger, follow these steps:
i. Right-click the Messenger icon in the notification area at the far right of the taskbar, and then click "Exit."
ii. Delete the already existing connection log file.
- MSN Messenger 7.0 or 7.5 or Windows Live Messenger
a. Start MSN Messenger 7.0 or 7.5 or Windows Live Messenger, but do not sign in.
b. On the Messenger "File" me nu, click "Open Received Files."
c. In the My Received Files folder, locate and select the MsnMsgr.txt file, and then press DELETE.
iii. Make sure that Connection Logging is enabled:
- MSN Messenger 7.0
a. Start MSN Messenger, but do not sign in.
b. On the "Tools" menu, click "Options."
c. In the "Options" dialog box, click "Connection."
d. Under "Connection Logging," make sure that the "Save a log of my server connections to help troubleshoot connection problems" check box is selected.
e. Close the "Options" dialog box.
- MSN Messenger 7.5 and Windows Live Messenger
a. Start Messenger, but do not sign in.
b. On the "Tools" menu, click "Options."
c. In the "Options" dialog box, click "Connection," and then click "Advanced Settings."
d. Under "Connection Logging," mak e sure that the "Save a log of my server connections to help troubleshoot connection problems" check box is selected.
e. Close the "Options" dialog box.
iv. Sign in to Messenger again: click "Sign In." The new connectivity log file (MSNMsgr.txt) is automatically generated in the My Received Files folder that is described in step 4.b.ii.c.
c. To send the MsnMsgr.txt log file to Messenger support, send a reply back to the support incident response, and attach the log file to the e-mail.