Skip to content
All library documents

Diagnosing a VeighNa DataManager Startup Encoding Error

Article vn.py community
Read the original

Summary

A forum user reports that starting VeighNa’s DataManager fails while retrieving the configured data service. The traceback shows that the application attempts to print a Chinese warning because no datafeed has been configured, then crashes when the Windows console uses the cp1252 encoding, which cannot represent that text.

The evidence points to two related conditions: the global datafeed configuration is missing, and the console’s encoding prevents the warning from being displayed. The thread contains no reply or confirmed fix, so it does not establish how to configure a provider or change the console encoding. It is useful as an example of distinguishing the underlying configuration issue from a secondary Unicode output error; resolving only the encoding problem may still leave the data service unset.

Key ideas

  • The traceback indicates that no datafeed provider is configured in the global settings.
  • The warning then fails to print because the Windows console encoding cannot represent its Chinese characters.
  • The thread provides diagnostic evidence but does not report a verified fix.

Tags

China markets

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.