4. Generating Errors

4.1. Generating Error Code 001-0803

Error code 001-0803 is returned by the friend library. This error code is caused by a failure to connect to the authentication server. It cannot occur when you connect to the Authentication Server Error Simulator. You must generate it through the following procedure.

  1. Confirm that you can connect to the Authentication Server Error Simulator from the software with support for Nintendo Network that you want to check.
    Note:     At this time, set a 002-XXXX error with the authentication server error simulator. When 003-XXXX is set, the 001-0803 error code is not generated.
  2. Prevent packets from being sent to the Authentication Server Error Simulator using a packet filter in the access point’s settings. Stop the sending of packets on TCP port 443 to 202.32.117.155 for the retail version of the software or to 202.32.117.156 for the test version of the software.
  3. Try to authenticate using the software with support for Nintendo Network that you want to check.

4.2. Generating 002-XXXX Error Codes

  1. Change the access point’s DNS settings and then configure a connection to the Authentication Server Error Simulator.
  2. Connect to the Authentication Server Error Simulator from your computer and set the error code that you want to generate, referring to Table 2-1 List of Selectable Authentication Errors.
  3. From the 3DS system’s network settings, configure the access point from step 1 as the connection.
  4. Try to authenticate from the Nintendo Network-compatible software that you want to check.
    Note: For more information about how to configure the settings in steps 1 and 2, see Chapter 2 Using the Authentication Server Error Simulator.

4.3. Generating 003-XXXX Error Codes

4.3.1. Generating Error Codes Using the Tool

You can use the NZSimulator.cia tool included in the package to check for errors that are generated when the CTR system attempts to connect to Nintendo Zone or a hotspot from an application with connection restrictions. You can prepare an environment to cause this error by running NZSimulator.cia on a development unit. The generated error code varies depending on the firmware version of the 3DS system you are using. See Table 4-1. System Firmware Versions and Corresponding Generated Error Codes.

Table 4-1. System Firmware Versions and Corresponding Generated Error Codes
System Firmware Version Generated Error Code

0.15.0 or later

003-3305

0.14.24 or earlier

003-3505

4.3.1.1. Running the Tool Using a Development Unit

To use NZSimulator.cia, you must prepare a separate development unit from the 3DS that runs the application you want to test. You must also configure the Internet connection settings for DS software on the development unit. For instructions on importing NZSimulator.cia, see the Readme file included with this package.

To use NZSimulator.cia, follow this procedure.

  1. Select System Settings from the HOME Menu on the development unit, and then set the access point to connect to the Internet with Internet Settings > DS Software Settings.
    • To perform DS Software Settings, you must start System Settings from the HOME Menu rather than the TEST Menu.
  2. Configure the settings so that you do not connect to the access point either by erasing connection targets 1–3 on the 3DS that runs the software to confirm the error, or by changing the SSID.
  3. 1. Use the development unit configured in step 1 to start NZSimulator. After NZSimulator is running, a Nintendo Zone signal that causes one of the errors is generated.
  4. Connect from the 3DS unit to the Nintendo Zone for which the development unit is the parent device.
    • The CTR normally connects to the Nintendo Zone automatically.
  5. From the 3DS HOME Menu, start the software used to verify errors, and try to connect to the Internet.
    • If signal strength is low, error 003-1099 (connection target not found) might occur if the CTR cannot connect to the Nintendo Zone.
    • The network daemon cannot establish a connection in the background immediately after the execution of the nn::uds::Finalize() or nn::ndm::SuspendScheduler() function. If the nn::ac::Connect() function is called at this time, the error code 003-1099 is generated if this tool is being used. This behavior is part of the specification. If your implementation is similar, it is not a problem if error code 003-3305 is not generated.
    • If the intended error does not appear, make sure that wireless communications is turned on for the development unit that is running NZSimulator. Wireless communication cannot be turned on after starting NZSimulator. If wireless communication is off, first exit NZSimulator and enable wireless communication, and then restart NZSimulator.

4.3.2. Generating Other Error Codes

For information about reproducing other errors under error code 003-XXXX, see the error code list.

4.4. Generating 006-XXXX Error Codes

After software using the NEX library has performed authentication, it connects to a game server via the NEX library to enable the use of the presence feature, matchmaking, and similar features. The Authentication Server Error Simulator is not used to check for errors that are generated when connecting to the game server via the NEX library.

The following table shows the procedure for generating errors for each error code.

This error does not occur in software that only uses the nn::nex::IndependentServer::RequestAuthenticationToken function because the NEX game server is not accessed.For this reason, you do not need to check the error codes in Table 4-1. Generating 006-XXXX Error Codes for such software.

Table 4-1. Generating 006-XXXX Error Codes
Error Codes Description of Errors and Generation Procedure
006-0502

Generated when connection to the game server cannot be established.

  1. Verify that the Nintendo Network-compatible software being checked can connect to the game server.
  2. Verify the global IP address obtained by resolving the errorsimulationmanual-nexlogin-d1.mng.nintendo.net domain with ping or nslookup.
  3. Using the packet filter from the access point settings, stop sending packets to the IP address obtained in step 2. Try connecting to the game server, and verify that this error code is generated.
006-0612

Generated when joining a P2P session fails.

Error code 006-0612 is generated only by software that uses the NEX matchmaking features and uses the NEX NetZ library with P2P communication.

  1. Prepare two Nintendo 3DS units (CTR A, CTR B) to perform matchmaking.
  2. Verify the global IP address used by CTR A.
  3. Using the packet filter from the settings of the access point used by CTR B, stop packet transmission to the IP address (to CTR A) verified in step 2.
  4. Perform matchmaking with CTR A and CTR B, and then try to join a P2P session.

In addition, if the NEX version is 2.x or earlier, you can generate error code 006-0612 by using the following method.

  1. Confirm that you can perform matchmaking using the software using the NEX library that you want to check.
  2. Using the packet filter from the access point settings, stop sending packets to addresses 202.32.117.142 and 202.32.117.143.
  3. Try to perform matchmaking using the software using the NEX library that you want to check, and then try to join a P2P session.
Note:

If the Pia library is used with P2P communication, this procedure generates one of the error codes listed in Figure 4-2. Error Codes Generated When Using Pia Library instead of error code 006-0612. The error code generated at this time differs depending on the NAT type of the network environment. For the NAT types of the error codes generated with the Pia library, see the error code list.

Figure 4-2. Error Codes Generated When Using Pia Library
Pia Versions Earlier Than 3.6.0 Pia 3.6.0 and Later
018-0201 018-0201
018-0510 018-0510
018-0511 018-0513
018-0512 018-0514
  018-0515
  018-0516
006-0811

This maintenance error does not need to be verified if appropriate error handling is being performed.

If this error needs to be verified, it is possible to temporarily set the game server to return a maintenance error. Contact Nintendo on the OMAS message boards. When this setting is implemented, a maintenance error will be returned to all users who connect to game servers of target titles.

Other error codes Currently, you do not need to check any other 006-XXXX error codes.

4.5. Generating 015-XXXX Error Codes

Error codes of the form 015-XXXX represent errors generated for OLV-related reasons.

The following table shows the procedure for generating errors for each error code.

Table 4-2. Generating 015-XXXX Error Codes
Error Codes Description of Errors and Generation Procedure
015-1002

Generated when browsing and posting to the Miiverse is not allowed because of parental control.

  1. On the 3DS, in the Parental Controls, select Miiverse and Restrict Viewing and Posting.
  2. Go to a scene that allows viewing of or posting to Miiverse, and check that game software generates this error code.
015-1003

Generated when posting to the Miiverse is not allowed because of parental control.

  1. Parental Controls On the 3DS, in the Parental Controls, select Miiverse and Restrict Posting.
  2. Go to a scene that allows posting to Miiverse, and check that game software generates this error code.
015-5003

Generated when the server is undergoing maintenance.

  1.  Prepare a network account with the Nintendo Network ID starting with 5003-.
  2.  Go to a scene that uses Miiverse features, and check that game software generates this error code.

* In the production environment, this error is not generated using this procedure.

015-5110

Generated because the official community you attempted to post to or get does not exist.

Note: This error does not always occur using the following procedure in cases when you get the official community list to check whether the target community for posting exists before posting. 

In cases where an official community has not yet been established, check that an error code occurs. If an official community has already been established, set the opening date of the official community to 0000-00-00 00:00:00 in MMAS, and then verify that an error code occurs. Also, when returning it to the original setting after verification, set the opening date to a past date.

4.6. Generating 022-XXXX Error Codes

Error codes of the form 022-XXXX represent errors generated for account-related reasons.

The following table shows the procedure for generating errors for each error code.

 

Table 4-3. Generating 022-XXXX Error Codes
Error Codes Description of Errors and Generation Procedure
022-2503

Generated when the latest EULA has not been agreed to.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.

  2. On the dashboard, in the Action section, select the Agreement Management option to transition to the accepted EULA management screen.

  3. Click the Reset button by any of the accepted EULA items to cancel the acceptance of that EULA.
  4. Restart the 3DS system, call the following functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
    • EC applet initialization function (nn::ec::CTR::EcApplet::RequestInitializeSession())

Note: This error no longer occurs in the system with the system update in December 2014 (System Version 9.3.0) or later.

022-2512

Generated when an application update is required.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.
  2. On the dashboard, in the Action section, select the App Test List option to transition to the screen for testing applications.
  3. Click the Add App Test button to transition to the screen for adding app tests.
  4. In Application Test, select Version Not Available Test. In Application, select the title you want to test, and then set the application.
  5. Click the Add button. The App Test List screen appears. Verify that "The App Test has been successfully added." is displayed.
  6. Restart the 3DS system, call the following service token retrieval functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
022-2631

Generated when the network account is deleted from another device.

Note that you cannot use a Nintendo Network ID after performing this action.

  1. In the Account Developer Portal, on the screen for managing test IDs, click the delete button to the right of the target Nintendo Network ID.
  2. A confirmation screen appears. Click the Delete button.
  3. Verify that the "Request is successful" message appears.
  4. Restart the 3DS system, call the following functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
    • EC applet initialization function (nn::ec::CTR::EcApplet::RequestInitializeSession())
022-2803

Generated when use of network services stops at the account level for the specified unique ID.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.
  2. On the dashboard, in the Action section, select the BAN Management option to transition to the screen for setting the ban status for user accounts.
  3. Click the Add BAN button to transition to the Add BAN screen.
  4. In Ban Type, select User + Game.
  5. In 3DS Title, select the target title.
  6. Click the Create Ban button, and then verify that the "A ban has been successfully created." message appears.
  7. Restart the 3DS system, call the following service token retrieval functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
022-2812

Generated when use of all network services stops at the device level.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.
  2. On the dashboard, in the Associated Device list, select the target device to transition to the dashboard for that device.
  3. On the dashboard, in the Action menu, select BAN Management to transition to the screen for setting the ban status for devices.
  4. Click the Add BAN button to transition to the Add BAN screen.
  5. In Ban Type, select Device Access.
  6. Click the Create Ban button, and then verify that the "A ban has been successfully created." message appears.
  7. Restart the 3DS system, call the following functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
    • EC applet initialization function (nn::ec::CTR::EcApplet::RequestInitializeSession())
022-2813

Generated when use of network services stops at the device level for the specified ID.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.
  2. On the dashboard, in the Associated Device list, select the target device to transition to the dashboard for that device.
  3. On the dashboard, in the Action section, select BAN Management to transition to the screen for setting the ban status for devices.
  4. Click the Add BAN button to transition to the Add BAN screen.
  5. In Ban Type, select Device + Game.
  6. Select the target title in the 3DS Title field that appears.
  7. Click the Create Ban button, and then verify that the "A ban has been successfully created." message appears.
  8. Restart the 3DS system, call the following service token retrieval functions in the application, and confirm that the error code occurs.

    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())

    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
022-2881

Generated when the service is undergoing maintenance.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.
  2. On the dashboard, in the Action section, select the App Test List option to transition to the screen for testing applications.
  3. Click the Add App Test button to transition to the screen for adding app tests.
  4. In Application Test, select Maintenance Mode. In Application, select the title you want to test, and then set the application.
  5. Click the Add button. The App Test List screen appears. Verify that "The App Test has been successfully added." is displayed.
  6. Restart the 3DS system, call the following service token retrieval functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
022-2882

Generated when a services has already been terminated.

  1. On the Account Developer Portal test ID management screen, select the desired Nintendo Network ID and open the user dashboard.
  2. On the dashboard, in the Action section, select the App Test List option to transition to the screen for testing applications.
  3. Click the Add App Test button to transition to the screen for adding app tests.
  4. In Application Test, select App End Date Expiration Test. In Application, select the title you want to test, and then set the application.
  5. Click the Add button. The App Test List screen appears. Verify that "The App Test has been successfully added." is displayed.
  6. Restart the 3DS system, call the following service token retrieval functions in the application, and confirm that the error code occurs.
    • Independent server token retrieval function (nn::act::applet::AcquireIndependentServiceToken())
    • Miiverse token retrieval function (nn::act::applet::AcquireOlvServiceToken())
Note:

In the Nintendo Network ID authentication that occurs when the EC applet starts, errors (022-2803, 022-2813, 022-2881, 022-2882) do not occur when the Account Developer Portal has been configured for a particular application. In that case, the EC applet authenticates the Nintendo Network ID rather than the application.

 

 


CONFIDENTIAL