This article will help you understand what the following error codes mean and what to do in case you do come across them. Keep in mind that this is not a definitive list and that we'll keep it updated as soon as we have new information to share.
We will also list a series of general steps you can follow to fix most of these issues.
| Error Code | Info |
| GR-01: Engine Networking Issues | |
| GR-01-00 | A relevant net driver has already been created for this service |
| GR-01-01 | The net driver creation failed |
| GR-01-02 | The net driver failed its Listen() call |
| GR-01-03 | A connection to the net driver has been lost |
| GR-01-04 | A connection to the net driver has timed out |
| GR-01-05 | The net driver received an NMT_Failure message |
| GR-01-06 | The client needs to upgrade their game |
| GR-01-07 | The server needs to upgrade their game |
| GR-01-08 | There was an error during connection to the game |
| GR-01-09 | NetGuid mismatch |
| GR-01-10 | Network checksum mismatch |
| GR-02-00 | The join worked as expected |
| GR-02-01 | There are no open slots to join |
| GR-02-02 | The session couldn't be found on the service |
| GR-02-03 | There was an error getting the session server's address |
| GR-02-04 | The user attempting to join is already a member of the session |
| GR-02-05 | An error not covered above occurred |
| GR-03-00 | Success |
| GR-03-01 | Failed to create player party |
| GR-03-02 | Failed to start the player session |
| GR-04-00 | Party is already playing in game |
| GR-05-00 | Matchmaking regions are unavailable |
| GR-06: Matchmaking Issues | |
| GR-06-02 | No players were found |
| GR-06-03 | Queue not found |
| GR-06-04 | Not logged in to platform or/and Playfab |
| GR-06-05 | Error during polling for server details after match was found |
| GR-06-06 | The party leader’s Game Mode is different from the local player |
| GR-06-07 | Failed to destroy a previous matchmaking attempt (online session). |
| GR-06-08 | PlayFab failed to create a matchmaking ticket, or no players were added to the request. |
| GR-06-09 | N/A or new unhandled error |
| GR-06-10 | The provided matchmaking ticket status is invalid/unknown. |
| GR-06-11 | The provided matchmaking ticket result is invalid/unknown. |
| GR-06-12 | The provided matchmaking ticket cancel reason is invalid/unknown. |
| GR-06-13 | The provided matchmaking state change type is invalid/unknown. |
| GR-06-14 | The ticket was canceled due to a cancelation request. |
| GR-06-15 | The ticket was canceled due to a service error. |
| GR-06-16 | The ticket was canceled for an unknown reason. |
| GR-06-17 | Duplicate users aren't allowed in the ticket parameters. |
| GR-06-18 | At least one local user must be specified in the ticket parameters. |
| GR-06-19 | There were too many users in the ticket for the queue. |
| GR-06-20 | The ticket is already completed. |
| GR-06-21 | Encountered an unrecoverable failure when attempting to cancel the ticket. |
| GR-06-22 | One of the users is a member of too many tickets. |
| GR-06-23 | A matchmaking request rate limit was exceeded. The request wasn't automatically retried again because retries are disabled or the retry-after period was too long. |
| GR-06-24 | The timeout elapsed without the service completing the ticket. |
| GR-06-25 | The calling entity is invalid. |
| GR-06-26 | One of the users in the ticket has invalid attributes. |
| GR-06-27 | The match wasn't found. |
| GR-06-28 | The ticket wasn't found. |
| GR-06-29 | The user already joined the ticket. |
| GR-06-30 | The queue config is invalid. |
| GR-06-31 | One of the users in the ticket has an invalid entity profile. |
| GR-06-32 | Matchmaking isn't enabled for this title. |
| GR-06-33 | One of the users in the ticket has attributes that are too large. |
| GR-06-34 | One of the ticket attributes is invalid. |
| GR-06-35 | The user hasn't joined the ticket. |
| GR-06-36 | The number of queues has exceeded the limit for this title. |
| GR-06-37 | The API called doesn't match the type of ticket requested. |
| GR-06-38 | The request was malformed. |
| GR-06-39 | Match details can only be provided when the ticket is in the matched state. |
| GR-06-40 | The provided multiplayer protocol type is invalid. |
| GR-06-41 | The ticket was canceled by the service. |
How do I fix this?
All these issues should generally be fixed with the following steps:
Try restarting your game session. This would vary depending on the platform.
- If you are playing on a PC, you should be able to do this by re-launching the game.
- If you are playing in a console, please follow the regular steps to close or quit your game and relaunch it.
- If you are using a Cloud Gaming service, you will have to close the gaming sesion and re-launch.
Verify or reinstall your game files: (Steam)
- Open Steam and go to your Library.
- Right-click the game or click the gear icon on the game's page.
- Select Properties... from the menu.
- Click on Installed Files on the left panel.
- Click Verify integrity of game files.
- Wait for Steam to scan and automatically re-download any broken or missing
Rebuild the Database (Safe Mode, PS5)
If you suspect corrupted data or missing game elements, rebuilding the system database scans your drive and organizes your content. This usually helps reseting configurations for several engines.
- Turn off your PS5 completely.
- Press and hold the power button until you hear a second beep (about 7 seconds) to enter Safe Mode.
- Connect your controller with a USB cable and press the PS button.
- Select option 5. Rebuild Database.
Reinstall the Game
If a specific game file is truly corrupted and gives you error messages, you may need to reinstal the game completely.
My Error is not listed here.
If you come across new error codes, or none of the troubleshoot steps mentioned above helped, please do reach us out here. This link will guide you into the correct request form to open a ticket about this.
Comments
0 comments
Article is closed for comments.