Instant Messaging
Windows/macOS
Quick Start
Product Description
Overview
Features
Limits
Feature overview
Account Integration and Login
Messaging
Team
Chat Room
Chat Room Tags
Multi-device Login
Statistics Monitoring
Development Integration
Overview
Integration mode
Initialization
Login and Logout
Messaging
Recent Chats
History
Host user information
Host user relationship
Team Chat
Superteam
Chat room
System Notification
Event Subscription
Audio Recording and Playback
Document Conversion
API References
Status Codes
Reference Documents
Instructions for Upgrading
Development Example
Windows UI Library Tutorial
Package and Release
Description of class and constant definitions

Status Codes

Update time: 2021/08/20 18:58:39

Windows (PC) status codes

code Detail description
Session message error codes
10200 Send file message and stop NOS upload.
10206 Receive file message and stop NOS download.
10404 Local resources cannot be found.
10414 The message has been received. Resource download address is invalid. It is impossible to download.
10417 The message has been received. Local resources can be found. It is not necessary to download.
10450 API is called and typed parameter is wrong.
10502 Sending message and uploading are failed.
Message history related error codes
10600 Verification for identity and encryption key is not passed when message history is imported.
10601 Recording is failed when message history is imported.

Details for status codes

Wrong user name or password 302

When client SDK executes login and calls status code 302, you shall check whether current AppKey and accid (account) correspond to token. The common causes include "token is wrong or not the latest", "this accid cannot be found under AppKey".
See About failed IM login-return 302 for details.

Illegal operation or no permission 403

When an illegal operation is executed, status code 403 will be returned. Common illegal operations include:

  • If NetEase ConnectEase console configures that non-friend cannot send messages, status code 403 will be returned when client SDK sends message to non-friend.
  • In chat room service, the manager can be changed to common users directly through canceling his permission. The manager cannot be set as a normal member directly, otherwise, status code 403 may be returned.
    In chat room service, only the creator can change manager, but the manager cannot change creator and other managers' otherwise, status code 403 may be returned.
  • In the third-party callback service, if the third-party callback function does not allow a certain message, then sender SDK will call back and return 403.
    If the user is added to a blacklist, the third-party callback will be executed firstly when the user sends message to receiver. If it is not allowed, SDK will return 403; otherwise, SDK will return 7101.
  • If the account has exited or been kicked out of the team, when the user tries to revoke a team message, status code 403 will be returned. In the revoking duration, manager can still revoke other messages that are sent by common team members kicked out of the team via client.
  • If current YunXin App corresponding to AppKey is closed, {"desc": "app is forbidden", "code": 403} will be returned when IM server API is called.
  • When IM server API is called, and typed nickname, signature and the like are filtered by anti-spam (e.g. involving politics, prohibition, ads), then {"desc": "forbbiden info", "code": 403} will be returned.
  • In the function of uploading file transcoding under interactive white board service, file related information can be queried by the uploader only; otherwise, 403 will be returned.
  • IM server API team related interface applies to advanced team and SuperTeam only, instead of common team/discussion team. The operation for common team/discussion team can be made via client SDK interface. Otherwise, {"desc": "no support", "code":403} will be returned.
  • If both are not friends, then 403 will be returned when the interface of updating friend information is called.

Before opening/enabling a certain function, status code 403 will also be returned when a corresponding interface is called. Common situations include:

  • If event subscription (commonly used for online event subscription) is not opened, 403 will be returned when related functions are used.
  • The current app cannot send and receive IM message (corresponding tip in console). When the interface of sending message is called, 403 will be returned. See sales consultant for details.
  • When roaming message is deleted, if the message roaming function is not enabled under the App and related interface is called, 403 will be returned.

Object cannot be found. 404

When the interface calls 404 status code, you shall check that typed parameter is correct. Common situations include:

  • When the required parameter is void, status code 404 may be called.
  • The typed parameter cannot be found actually. For example, unregistered accid or unreal team ID is typed.

Client request is time out. 408

When the interface calls 408 status code, you shall check that current network is normal. Common situations include:

  • When networking request interface is called after network disconnection, 408 will be called.
  • When the login is not successful, networking request interface is called.
  • Android SDK 4.3.0 and earlier versions applies to Android 8.0 and above system. The status code 408 may be found when you log in, so that you shall update SDK to the latest version.

Parameter Error 414

When the interface calls 414 status code, you shall check that typed parameter is correct. Common situations include:

  • The data type of typed parameter is not consistent with interface requirement.
  • If Perform security verification of identity: If the identity of the client App requesting login is not in the above list, reject the login request is selected in Console> Applications> App Key Management> Identity Management, when client App token (iOS Bundle Identifier / Android Package Name) cannot be found in configuration list, status code 414 will be returned via login interface.
  • When server interface is called and unregistered accid is typed, status code 414 will also be returned.
  • If chat room is closed in chat room service, status code 414 will be returned when querying chat room message history. For example, {"desc": "check roomid", "code": 414} will be returned when IM server API "Query chat room cloud message history" is called.
  • If the message is filtered by anti-spam, when it tries to revoke, error code 414 will be returned.
  • It is possible to add the user himself as friend, otherwise, status code 414 will be returned.
  • When SMS related interface is called, if the parameter typed by the developer is not consistent with JSON format, {"code": 414, "msg": "'mobiles' / 'params' should be json format"} will be returned. Please correct.
  • In Web SDK, "teamMsgReceipts" parameter under team message receipt function is array format and the limit of array elements is 50. If the limit is exceeded, error code 414 will be returned.
  • {"desc":"bad http headers", "code":414} will be returned when IM server API is called. This may be an error in verification information. For verification information, please Click to see.
    [Note] CheckSum is calculated with AppSecret, instead of AppKey.
  • Returning {"desc": "CurTime is illegal", "code": 414}/{"desc": "CurTime is expired", "code": 414} means that the typed CurTime parameter is not consistent with current UTC timestamp (leading or lagging). Possible causes include:
    • The developer did not dynamically acquire current UTC timestamp in real time.
    • The time zone and time configured for app server are not consistent with actual conditions.
  • {"desc":"body not json", "code":414} is returned. The request Content-Type via IM server interface is application/x-www-form-urlencoded. Please execute urlencode for parameter value to avoid failure in resolution due to special character.
  • {"desc":"retry again", "code":414} is returned. When Create NetEase ConnectEase IM Account and is called and creation account is sent, this error may be returned if same accid parameter is typed for different requests.
  • When common team is created, at least two member accounts shall be typed, otherwise, error code 414 will be returned.
  • If server API is called again after disabling creator account to cancel the team, {"desc": "check accid001", "code": 414} will be returned.
  • {"desc":"parameter roomid should be long","code":414} is returned for chat room related API. The possible causes include but not limited to:
    • Error coding is made for roomid parameter by the developer. For example, executing json_encode in PHP may result in this error.
  • For "Update chat room information", if only roomid, needNotify and notifyExt are typed, instead of any other parameters requiring update, then {"desc": "no valid param provided, skip update!", "code": 414} will be returned.
  • When Create NetEase ConnectEase IM Account is called, {"desc": "Exceed the maximum account XXX", "code":414} will be returned. Possible causes include:
    • The limit of IM free accounts is 100.
    • IM Pro version (trial) is expired. There is no limit for accounts of IM Pro version during trial. The limit is declined to 100 after trial. If you want to use IM Pro version again, please contact sales consultant to open official version.

Repeated operation 417

  • When the client logs in automatically, status code 417 is called. See Automatic login return 417 for possible causes.
  • When a multi-member audio and video room is created, status code 417 is called. See Notes for multi-member audio and video communication/interactive live streaming room for possible causes.
  • When IM server API calls Configure user role in chat room, {desc:"duplicate...", code:"417"} is returned. Possible causes include but not limited to:
    • Repeated operation. For example, a certain role is configured again after a configuration, or canceled again after cancellation.
    • Incorrect configuration. For example, manager role is canceled for non-manager, or operation is made for non-chat room members.

No permission 802

  • When IM SDK "actively leave team" interface is called, status code 802 will be returned. The creator of advanced team cannot leave a team directly, but can transfer the team and then exit, or directly cancel the team.
  • When members of a common team are acquired, status code 802 is returned. Possible causes include but not limited to:
    • The new member of a common team is not activated ( he is not belonging to the team temporarily). When receiving team message, the new member is activated automatically and then can call "get team member" interface.
  • When Team mute interface is called to configure or cancel team mute, if muteType is typed with 3, the whole team is mute (including team creator). In this case, if SDK/client tries to call mute interface again, status code 802 will be returned.
Was this topic helpful?
Yes
No
  • Windows (PC) status codes
  • Details for status codes
  • Wrong user name or password 302
  • Illegal operation or no permission 403
  • Object cannot be found. 404
  • Client request is time out. 408
  • Parameter Error 414
  • Repeated operation 417
  • No permission 802