LarkXR Troubleshooting Reference
Deployment
Troubleshooting Backend Intranet Access Failure
Troubleshooting Backend External Access Failure
Troubleshooting Database Startup Failure
Troubleshooting Black Screen on Server Startup
Troubleshooting Service Startup Failure
Cluster Edition (Linux)
Troubleshooting “not found” Errors in sh Startup Scripts
Public Cloud
Tesla GPU GRID Driver and License Requirements
Configuring a Virtual Display for the Second vGPU
Troubleshooting Resolution Below 1080p on Tesla GPUs
Error Code Explanation
Web Client
Troubleshooting “No available render server, Please try again later.”
Code 102
Code 103
Code 202
Code 203
Code 401
Code 402
Code 403
Code 404
Code 500
Code 501
Code 502
Code 504
Code 601
Stuck on 5/5 Loading Page
Cloud Application Exit Detected
Point-to-Point Connection Disconnected
Frontend & Backend Inaccessible
VR Client
Code 11
Code 900
Code 1001
Continuous Loading
UDP Connection Failure
Other Issues
Code 1002
AR Client
UDP Connection Failure
Secondary Development
Data Channel
Unable to Communicate — Troubleshooting Guide
Failed to Pass the Message Body
Incorrect Message Delivery
Delay in Receiving Messages
UE5 Plugin Packaging: Possible Reasons for "Unknown Cook Failure"
WebSDK
1-5 Cards Loading
SDK License Does Not Exist
vue2-react Running Error (Node v18.12.1)
H.265 WebCodec Not Supported by Browser
Interface call
No Access Permissions
Signature and Timestamp Cannot Be Empty
Invalid Key Pair
Others
Apps Can't Sync
LarkXR Launcher: Check Environment Error
User Experiences
Live Streaming Screen is Black
Picture Quality is Not Clear
SN
Local SN
Invalid Authorization Code
Cloud SN
Authorization Code Is Disabled
Authorization Code Does Not Exist
-
+
首页
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.  ### 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.
admin
2026年5月11日 15:39
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期