Latest revision as of 11:13, 11 May 2022

Contents:	200s 300s 400s 500s 600s 700s 800s 900s

200s

	MSNP Protocol
	Introduction • Terms • Clients
	Reference
	Error List • Commands • Relying Party Suite • Spotlife
	Services
	XMPP • HTTP Gateway • Tabs • Activities
	Documentation
	Development Tools • MSNP Grid
	Polygamy • URLs used by MSN
	Documents
	Protocol Versions
	Version 21
	Version 18
	Version 16
	Version 15
	Version 14
	Version 13
	Version 12
	Version 11
	Version 9
	Version 8
	Version 2
	MSNC
	Introduction • P2P • Object Descriptor • Display Pictures • File Transfer
	Scenarios
	Microsoft Messenger for Mac
	MSNP on WebTV (MSNTV)

200

Invalid Syntax Never before encountered.

201

Invalid parameter Sent if the command has a parameter that is considered invalid by the server. Setting your status to FLN would be an example.

>>> CHG 19 FLN 0\r\n
<<< 201 19\r\n

Also sent if you try to ADD an invalid email address.

>>> ADD 20 FL a@b a@b\r\n
<<< 201 20\r\n

205

Invalid principal Sent if you try to ADD a non-existent, but valid, account name.

>>> ADD 21 AL non_existent_account@passport.com non_existent_account@passport.com\r\n
<<< 205 21\r\n

With MSNP10 and above, this has changed to error 208.

206

Domain name missing When you try logging in with a name like: "81.153.72.241@" with no domain.

207

Already logged in If the client sends a USR after already logging in, this error will be sent in response.

>>> USR 20 TWN I example@passport.com\r\n
<<< 207 20\r\n
>>> USR 21 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n
<<< 207 21\r\n

208

Invalid principal Sent from the switchboard in reply to a CAL with an invalid account name.

>>> CAL 2 @@a\r\n
<<< 208 2\r\n

Also sent by the notification server if you try to ADC (MSNP10 and above) a non-existent, but valid, Passport account.

>>> ADC 453 FL N=this_account_doesnt_exist@hotmail.com F=this_account_doesnt_exist@hotmail.com\r\n
<<< 208 453\r\n

209

Nickname change illegal Sent in reply to REA when there is a blocked word/phrase in the new nickname or when the Passport has not yet been confirmed.

>>> REA 18 principal@passport.com look%20msn\r\n
<<< 209 18\r\n

210

Principal list full Sent in response to an ADD/ADC command if the list in question is already full. The principal will not be added. Currently (as of October 2005), the limit is 600 principals on FL and 1000 on RL.

>>> ADD 23 FL principal@passport.com principal@passport.com 0\r\n
<<< 210 23\r\n

213

Invalid rename request? Don't know exactly how to describe this, but I got this error when attempting to rename a telephone number. (eca0d232-2d18-4b30-9200-63d94add303d = tel:+131123456789)

>>> SBP 1102 eca0d232-2d18-4b30-9200-63d94add303d MFN banaan
<<< 213 1102

215

Principal already on list Sent if you try to ADD a principal to a list, but the principal is already in that list.

>>> ADD 26 AL principal@passport.com principal@passport.com\r\n
<<< ADD 26 AL 824 principal@passport.com principal@passport.com\r\n
>>> ADD 27 AL principal@passport.com principal@passport.com\r\n
<<< 215 27\r\n

Also sent if you try to ADD a principal to your FL in a group that the principal is already in.

>>> ADD 28 FL principal@passport.com principal@passport.com 2\r\n
<<< ADD 28 825 FL principal@passport.com principal@passport.com 2\r\n
>>> ADD 29 FL principal@passport.com principal@passport.com 2\r\n
<<< 215 29\r\n

Also sent if you try to invite (CAL) a principal into a switchboard session that has already been invited and/or is already present.

>>> CAL 5 example@passport.com\r\n
<<< CAL 5 RINGING 286195\r\n
>>> CAL 6 example@passport.com\r\n
<<< 215 6\r\n

216

Principal not on list Sent in reply to REMs that try to remove principals that are not in the list. Also sent if you try to remove non-existent or invalid account names.

>>> REM 14 FL principal_not_in_list@msn.com\r\n
<<< 216 14\r\n

This error is also sent in reply to invitations to the switchboard (CALs) to principals that either have you in their BL or have opted to 'block all others' (BLP BL). This is only sent when the principal is online. If the principle is offline, you will receive 217 instead. As of January 2004, error 217 is returned in this instance!

>>> CAL 2 example@passport.com\r\n
<<< 216 2\r\n

Also sent in reply to renaming principals that are not in any of your lists.

>>> REA 48 random_principal@randomdomain.com nickname\r\n
<<< 216 48\r\n

217

Principal not online This error is sent in reply to invitations to the switchboard (CALs) to principals that are currently either offline or appearing offline. This error will also be sent in reply to invitations to non-existent account names.

>>> CAL 2 myname@msn.com\r\n
<<< 217 2\r\n
>>> CAL 3 non_existent@passport.com\r\n
<<< 217 3\r\n

218

Already in mode Sent in reply to GTC or BLP if it is already in that mode.

>>> GTC 15 A\r\n
<<< GTC 15 150 A\r\n
>>> GTC 16 A\r\n
<<< 218 16\r\n

>>> BLP 17 BL\r\n
<<< BLP 17 151 BL\r\n
>>> BLP 18 BL\r\n
<<< 218 18\r\n

219

Principal is in the opposite list Send in reply to an ADD that causes the same principal to be in the BL and the AL at the same time. Obviously, that cannot be possible, and the principal will not be added.

>>> ADD 15 AL example@passport.com example@passport.com\r\n
<<< ADD 15 AL 108 example@passport.com Mike\r\n
>>> ADD 16 BL example@passport.com example@passport.com\r\n
<<< 219 16\r\n

223

Too many groups Sent if you try to add a group (ADG) so that you have more than 30 groups (the maximum). The group with the ID of zero counts toward the limit.

>>> ADG 38 thirtyfirst%20group 0\r\n
<<< 223 38\r\n

224

Invalid group Sent if you try to ADD a principal to your FL with a non-existent group ID. Also sent in reply to REMs to non-existent groups. Also sent in reply if you try to remove (RMG) or rename (REG) a non-existent group.

>>> RMG 24 15\r\n
<<< RMG 24 12065 15\r\n
>>> ADD 25 FL example@passport.com example@passport.com 15\r\n
<<< 224 25\r\n
>>> REM 26 FL example@passport.com 15\r\n
<<< 224 26\r\n
>>> RMG 27 15\r\n
<<< 224 27\r\n
>>> REG 28 15 New%20Name 0\r\n
<<< 224 28\r\n

225

Principal not in group Sent if you try to remove (REM) a principal from a group that they are not currently in.

>>> REM 27 FL example@passport.com 3\r\n
<<< 225 27\r\n

227

Group not empty Sent if you try to remove (RMG) a group that is not empty.

>>> RMG 28 15\r\n
<<< 226 28\r\n

228

Group with same name already exists Sent if you try to rename (REG) a group and a group on your Hotmail (not Messenger) contact list already exists with the same name.

>>> REG 25 1 New%20Name 0\r\n
<<< 228 25\r\n

The official client reports:

You have already used this name for another group in your Messenger or Hotmail contact list. Please choose another name.

However, it will let you create a new group with the same name, then if you delete the group on Messenger, it disappears from Hotmail too!

229

Group name too long Sent if you try to add a group (ADG) with more than 61 bytes in the name.

>>> ADG 50 this%20group's%20name%20is%20sixty%20two%20bytes%20in%20length 0\r\n
<<< 229 50\r\n

230

Cannot remove group zero Sent if you try to remove (RMG) the group with the ID of zero.

>>> RMG 28 0\r\n
<<< 230 28\r\n

231

Invalid group Never before encountered.

240

Empty domain If you try to add an empty group of users (domain) in the ADL command, you'll receive the 200 error and get disconnected.

>>> ADL TrId xxx
    <ml>
        <d n="hotmail.com">
              <c n="user" l="3" t="1" />
        </d>
        <d n="yahoo.fr" />
    </ml>
<<< 240 TrId

280

Switchboard failed Never before encountered.

281

Transfer to switchboard failed Never before encountered.

282

P2P Error? Sent if you goof up with Protocols/MSNP/MSNSLP. Check whether your MSG length argument is correct, you can screw up pretty badly and still get the ACK, but if this argument is wrong you'll get 282 no matter what else (note that the length consists of ANYTHING sent after the CRLF in that message).

300s

300

Required field missing Never before encountered.

302

Not logged in Never before encountered.

400s

402

Error accessing contact list Indicates that the servers are experiencing problems. When signing in, the client will give a "You cannot sign in because your contact list is currently unavailable" message. When trying to add/remove contacts from any list the client will give "We cannot update your address book at this time. Please try making this change again later."

Should be treated as a generic contact list error.

403

Error accessing contact list Indicates that the servers are experiencing problems. When signing in, the client will give a "You cannot sign in because your contact list is currently unavailable" message. When trying to add/remove contacts from any list, the client will give "We cannot update your address book at this time. Please try making this change again later."

Also returned when using bad format for REM (like using email for FL or N= prefix, etc.).

Should be treated as a generic contact list error.

420

Invalid Account Permissions This is received when a non Beta Tester user tries to login to Messenger Beta. It is also received in response to a CVR command with an unofficial client name or version.

500s

500

Internal server error When the servers are down, this might be sent in reply to your USR command to the NS containing your ticket. The official client interprets this as "Service Temporarily Unavailable". This error might also be sent if your account has banned.

>>> USR 4 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n
<<< 500 4\r\n

501

Database server error Never before encountered.

502

Command disabled Sent if you try to use a command associated with an MSN Messenger feature that no longer exists.

>>> FND 3 fname=Bill lname=Gates city=* state=* country=US\r\n
<<< 502 3\r\n

510

File operation failed Never before encountered.

511

Banned User account you are attempting to connect with is banned.

520

Memory allocation failed Never before encountered.

540

Challenge response failed Sent in response to a QRY that is invalid. The server will close the connection after sending the error.

<<< CHL 0 15570131571988941333\r\n
>>> QRY 10 msmsgs@msnmsgr.com 32\r\n
    4f2f5a91b72102cd28355e9fc9000d6e
<<< 540 10\r\n

600s

600

Server is busy Never before encountered.

601

Server is unavailable Can be sent in reply to the initial USR to the NS if the server is somehow unavailable.

>>> USR 10 TWN I example@passport.com\r\n
<<< 601 10\r\n

602

Peer nameserver is down Never before encountered.

603

Database connection failed Can be sent in reply to the SYN command when the NS server is having some sort of problems.

>>> SYN 10 0 0\r\n
<<< 603 10\r\n

604

Server is going down Never before encountered.

605

Server unavailable Never before encountered.

700s

700

Could not create connection Never before encountered.

710

Bad CVR parameters sent Sent in reply to a CVR if you send an invalid LCID.

>>> CVR 1 0x0809 winnt 5.1 i386 MSNMSGR 6.0.0602 MSMSGS example@passport.com\r\n
<<< 710 1\r\n

711

Write is blocking Never before encountered.

712

Session is overloaded Never before encountered.

713

Calling too rapidly When the client repeatedly calls someone who is offline or blocking them, this error message will be sent in response to the commands that the server rejects.

>>> CAL 5 blocking_you@passport.com\r\n
<<< 216 5\r\n
>>> CAL 5 blocking_you@passport.com\r\n
<<< 216 5\r\n
>>> CAL 5 blocking_you@passport.com\r\n
<<< 216 5\r\n
>>> CAL 5 blocking_you@passport.com\r\n
<<< 216 5\r\n
>>> CAL 5 blocking_you@passport.com\r\n
<<< 216 5\r\n
>>> CAL 5 blocking_you@passport.com\r\n
<<< 713 5\r\n

714

Too many sessions Never before encountered.

715

Not expected Sent in response to a PRP setting an invalid phone type of three or less characters.

>>> PRP 30 PHV 555-0690\r\n
<<< 715 30\r\n

Also sent in response to a change of display name (REA) on an unverified Passport account.

>>> REA 31 me@passport.com newname\r\n
<<< 715 31\r\n

And when logging in, when you swap the GCF and the SYN order.

>>> GCF 12 Shields.xml
>>> SYN 13 0 0
<<< 715 12

717

Bad friend file Never before encountered.

731

Not expected Sent in response to a badly formatted CVR.

>>> CVR 2 foo\r\n
<<< 731 2\r\n
<o> Server Closes Connection\r\n

800s

800

Changing too rapidly When the client tries to change the display name (REA) too rapidly, this error message will be sent in response to the commands that the server rejects. This does not affect renaming other principals.

>>> REA 100 me@passport.com NAME\r\n
<<< REA 100 2000 me@passport.com NAME\r\n
>>> REA 101 me@passport.com NAME\r\n
<<< REA 101 2001 me@passport.com NAME\r\n
>>> REA 102 me@passport.com NAME\r\n
<<< REA 102 2002 me@passport.com NAME\r\n
>>> REA 103 me@passport.com NAME\r\n
<<< REA 103 2003 me@passport.com NAME\r\n
>>> REA 104 me@passport.com NAME\r\n
<<< 800 104\r\n

Also when the client tries to change the status (CHG) too rapidly.

>>> CHG 105 NLN 0\r\n
<<< CHG 105 NLN 0\r\n
>>> CHG 106 HDN 0\r\n
<<< CHG 106 HDN 0\r\n
>>> CHG 107 NLN 0\r\n
<<< CHG 107 NLN 0\r\n
>>> CHG 108 HDN 0\r\n
<<< CHG 108 HDN 0\r\n
>>> CHG 109 NLN 0\r\n
<<< 800 109\r\n

Also when requesting too many switchboard sessions. You can request up to 8 switchboard sessions in any 60-second period. Failed requests (i.e. requests that receive this error in reply) also count towards this limit.

>>> XFR 126 SB\r\n
<<< 800 126\r\n

900s

910

Server too busy When the servers are busy, this might be sent in reply to your USR command to the NS containing your ticket.

>>> USR 4 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n
<<< 910 4\r\n

911

Server is busy Sent in response to some invalid formats of the USR command to the DS or NS. Also sent if the account name is invalid or non-existent.

>>> USR 3 TWN S example@passport.com\r\n
<<< 911 3\r\n

>>> USR 3 TWN I passport.com\r\n
<<< 911 3\r\n

Sent in response to an invalid ticket sent in the second USR command to the NS.

>>> USR 4 TWN S t=some_invalid_value\r\n
<<< 911 4\r\n

Also sent in response to problems authenticating with the switchboard with USR or ANS.

>>> USR 1 myname_123@hotmail.com 486979.1047702516.105\r\n
<<< 911 1\r\n

>>> ANS 1 myname_123@hotmail.com 849102291.520491932 11752098\r\n
<<< 911 1\r\n

912

Server too busy Never before encountered.

913

Not allowed when hidden Sent in reply to commands that are not allowed in the HDN status. The only known command that is prohibited when hidden (before MSNP13) is XFR.

>>> XFR 13 SB\r\n
<<< 913 13\r\n

914

Server unavailable Never before encountered.

915

Server unavailable Never before encountered.

916

Server unavailable Never before encountered.

917

Authentication failed Never before encountered.

918

Server too busy Never before encountered.

919

Server too busy Never before encountered.

920

Not accepting new principals Never before encountered.

921

Server too busy When the servers are busy, this might be sent in reply to your USR command to the NS containing your ticket.

>>> USR 4 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n
<<< 921 4\r\n

922

Server too busy Never before encountered.

923

Kids' Passport without parental consent Sent in reply to the second USR to the NS if client is logging in with a Kids' Passport without parental consent to chat online.

>>> USR 4 TWN S t=53*1hAu8ADuD3TEwdXoOMi08sD . . . \r\n
<<< 923 4\r\n

This is also sent in reply to a badly formatted ticket in the second USR. (eg, you did not html decode the ticket properly).

924

Passport account not yet verified This sometimes happens after attempting to change display name on a recently created passport account.

928

Bad ticket Sent in reply to the second USR to the NS if your ticket is invalid. Mostly seen if you don't handle redirections properly with the login server connection and use an @msn or @hotmail account.

>>> USR 4 TWN S invalid_ticket\r\n
<<< 928 4\r\n

928 errors will also be seen if you didn't HTML entity decode the token received using the new MSNP13 authentication protocol. Main offender I've seen is & amp; - this needs to become a plain ol' '&' before you can send it as part of the final USR

931

Account not on this server Sent in reply to the first USR to the NS if your account is not on that server. It will happen when you cache the NS server (you don't use the dispatch server everytime) and msn has moved the account from the cached NS.

>>> USR 3 TWN I unavailable@account.com\r\n
<<< 931 3\r\n

@@ Line 1: / Line 1: @@
+{{Protocols/MSNP}}
 <center>
 {| id="toc" border="0"

Protocols/MSNP/Reference/Error List: Difference between revisions

Latest revision as of 11:13, 11 May 2022

200s

200

201

205

206

207

208

209

210

213

215

216

217

218

219

223

224

225

227

228

229

230

231

240

280

281

282

300s

300

302

400s

402

403

420

500s

500

501

502

510

511

520

540

600s

600

601

602

603

604

605

700s

700

710

711

712

713

714

715

717

731

800s

800

900s

910

911

912

913

914

915

916

917

918

919

920

921

922

923

924

928