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 900
The `code 900` error indicates a failure in the VR rendering service startup. This error can be triggered by several environmental or configuration issues on the deployment server. The following causes should be investigated in order. ## Cause 1: LarkXR Is Installed in a Directory with Chinese Characters The LarkXR deployment path contains Chinese (non-ASCII) characters, which can cause the rendering service to fail during initialization. ### Solution Reinstall LarkXR to the root directory of a drive letter (e.g., `C:\LarkXR`), ensuring the full installation path contains only English alphanumeric characters and standard symbols. ## Cause 2: Incorrect SteamVR Path Configuration The SteamVR path entered in the LarkXR configuration is incorrect or uses an invalid format. ### Solution 1. Open the LarkXR configuration and locate the **SteamVR Path** field. 2. Verify that the path points to the correct SteamVR installation directory. 3. Ensure the path uses the correct format — the directory separator should be `\\` (double backslash), for example: `C:\\Program Files (x86)\\Steam\\steamapps\\common\\SteamVR`. 4. Save the configuration and restart the rendering service. ## Cause 3: Rendering Server Not Restarted After Display Plug/Unplug The rendering server was not restarted after a physical display was connected or disconnected from the server. This can leave the rendering service in an inconsistent state. ### Solution Restart the rendering service manager to allow it to re-detect the display configuration. Refer to the [Restart the rendering service manager](https://www.pingxingyun.com/contribute/detail?topicId=10106&categoryId=3) guide for step-by-step instructions. ## Notes - Always use a short, English-only installation path for LarkXR to avoid encoding-related startup failures. - After any hardware change (such as connecting or disconnecting a display), always restart the rendering service manager before launching a session.
admin
2026年5月12日 11:27
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期