Code 402

The `Code 402` error usually indicates that the cloud application could not be launched correctly on the rendering server. The most common causes are missing application files, incorrect launch path settings, startup failure on the rendering server, or application data being stored on network storage with slow response times.

## Solution by Render Type

| Render Type | Recommended Check |
|---|---|
| SR Exclusive | Confirm that the application is installed on the rendering server. |
| SR Exclusive | Check whether the configured application path is correct. |
| SR Exclusive | Check whether the application can be started successfully on the local rendering server. |
| SR Shared-PXY or Exclusive | If the application database is stored on network storage, move it to local storage to avoid data access timeouts. |

## Recommended Checks

### 1. Confirm That the Application Is Installed

For `SR Exclusive` applications, verify that the target application is installed on the rendering server and that all required files are present.

### 2. Check the Launch Path Configuration

Verify that the configured startup path is correct, including the executable path, working directory, and any required startup parameters.

### 3. Test Local Startup

Log in to the rendering server and launch the application manually. If the application cannot start normally on the local machine, resolve that issue first before testing through LarkXR again.

![Code 402 troubleshooting reference](https://docs.paraverse.cc/media/202504/a92a5600677a4ac5af4b172abb851b644181.png)

### 4. Check Storage Location for Application Data

For `SR Shared-PXY` or `Exclusive` scenarios, if the application database or required runtime data is stored on network-attached storage, data interaction may time out during startup. In this case, store the database locally on the rendering server instead.

## Notes

- `Code 402` is usually an application-side startup problem rather than a client connection problem.
- Start with local verification on the rendering server, because this is the fastest way to determine whether the application itself can launch successfully.
- If the application depends on local databases, configuration files, or project data, confirm that these resources are available locally and can be read without network delay.