OpenSite/Guides/Troubleshoot startup

OpenSite 0.0.1 · DevelopmentSource scope and availability

Find the first package/configuration problem without changing engineering data.

Stable identifier: opensite.help.troubleshoot-startup

Prerequisites

The exact package/build identifier and access to the original package.

Steps

Check which executable you launched

The desktop is opensite-desktop.exe. opensite-cli and the headless Python consoles are different applications and are not expected to show the GUI.

Check package completeness

Keep Qt platform plugins, DLLs, extensions and runtime in their supplied locations. A missing Qt platform/runtime message is not fixed by changing a document. Re-extract the matching package rather than copying arbitrary files into system folders.

Check the build configuration

Release and Debug Python/CRT files are not interchangeable. Debug can require its developer environment. Do not point a Debug host at a Release runtime.

Separate graphics and Python failures

“The graphics renderer is unavailable” is a viewport/graphics status. “Python is unavailable” is a runtime/extension status. Record each separately. Do not infer that model files are corrupt from either message alone.

If preferences could not load

The normal desktop can continue with session settings when its settings file fails to load. Keep the original settings file before attempting a corrected copy; check path/permissions and report the error. An apparent Apply may be session-only if no settings file is configured.

Collect useful evidence

Record package/build, architecture, executable, exact first message, and whether a clean package with a new blank document reproduces it. Use OpenSite/Support and remove private data.