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 404
The `Code 404` error usually indicates that the rendering environment on the server is not available or is not configured correctly. This is commonly caused by remote desktop redirection, missing display output devices, unsupported GPU configuration, or an unsupported operating system version. ## Cause 1: The Desktop Session Was Redirected by Windows Remote Desktop If you log in to the rendering server by using the built-in Windows Remote Desktop feature, the desktop session may be redirected. This can interfere with the rendering environment used by LarkXR. ### Solution 1. Connect to the rendering server by using a remote management tool such as Sunlogin, TeamViewer, or VNC instead of the built-in Windows Remote Desktop client. 2. Restart **LarkXR Rendering Manager**. 3. If necessary, restart the rendering server. ## Cause 2: No Monitor or Dummy Plug Is Connected to a GeForce or Quadro GPU On GeForce or Quadro GPUs, the rendering server may require a connected monitor or a display emulator (dummy plug / display spoofer) so that the system can detect an active display output. ### Solution Connect a monitor or display emulator to the rendering server GPU, then restart the rendering service. Reference: [NVIDIA Video Encode and Decode GPU Support Matrix](https://developer.nvidia.com/video-encode-decode-gpu-support-matrix#Encoder) ## Cause 3: Tesla GPU Driver or License Requirements Are Not Met If the rendering server uses a Tesla-series GPU, the required GRID driver or license configuration may be missing. ### Solution For public cloud deployment, confirm that the Tesla GPU has the correct GRID driver and licensing setup. Reference: [Tesla GPU GRID Driver and License Requirements](https://docs.paraverse.cc/doc/505/) ## Cause 4: The Operating System Version Is Not Supported Windows 7 is no longer supported for this deployment scenario. ### Solution Use a supported operating system version, such as: - Windows 10 - Windows Server 2016 or later ## Recommended Troubleshooting Order 1. Confirm that the server is not being accessed through built-in Windows Remote Desktop. 2. Check whether the GPU has a valid active display output, especially for GeForce or Quadro GPUs. 3. If the server uses a Tesla GPU, verify the GRID driver and license configuration. 4. Confirm that the operating system version is supported. ## Notes - `Code 404` in this article is related to rendering-server environment readiness, not to an HTTP 404 web error. - Display detection and desktop session type can directly affect whether the rendering service can initialize correctly. - If multiple conditions may apply, check them in the order listed above.
admin
2026年5月11日 16:30
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期