Wizard and startup issues
Port is already in use
Possible cause
Another instance of QV2QS or another application is using the same network port. The console displays ERROR: Port [number] is already in use.
Proposed action
Close the other application, or specify a different port with --port. Use --port 0 to allow the system to select an available port automatically.
The wizard opens in Internet Explorer or does not render correctly
Possible cause
Internet Explorer is the default browser on the machine. The QV2QS user interface requires a modern browser and does not function in Internet Explorer.
Proposed action
Install Google Chrome, Microsoft Edge, or Mozilla Firefox. QV2QS detects the default browser at startup and automatically opens a supported browser when one is available. If no supported browser is found, the console displays download links.
On Windows Server 2019, Internet Explorer is the only browser installed by default. Install a supported browser before running QV2QS in wizard mode. Alternatively, use the command-line interface, which does not require a browser. See Argument reference for the full list of CLI arguments.
Conversion fails or produces unexpected results in the wizard
Possible cause
The wizard displays a summary error but does not expose the full diagnostic detail needed to identify the root cause.
Proposed action
Re-run the same conversion from the command line with debug logging enabled. Do the following:
- In the wizard, navigate to the Review step.
- Click Copy command to copy the full CLI command to the clipboard.
- Open a terminal window and paste the copied command.
- Append
--logLevel DEBUGto the end of the command and press Enter.
The console displays verbose output covering every conversion decision, cloud API call, and object processing step. The full debug log is also written to the logs/ subfolder in the output directory.
The copied command includes all settings configured in the wizard. Appending --logLevel DEBUG is the only change needed to enable full diagnostics.
See Logging and diagnostics for details on log file format and location.
QV2QS has stopped
modal appears in the browser
Possible cause
The QV2QS process was closed, crashed, or terminated while the wizard was still open in the browser. The user interface monitors the backend service with a periodic health check and displays the modal when the service becomes unreachable.
Proposed action
Do one of the following:
- Reconnect to the current session. Copy the command displayed in the modal and run the command in a terminal. The command includes
--portand--noBrowserto reattach to the same browser tab on the same port. After the server starts, click Reconnect in the modal. The wizard resumes with all previously entered settings intact. - Close the browser tab. Click Close window in the modal. Any unsaved settings in the current wizard session are lost.
Example project file is missing or corrupted
Possible cause
The example QVW file in %TEMP%\QV2QS\examples\ was deleted, moved, or modified outside of QV2QS.
Proposed action
Delete the affected file from %TEMP%\QV2QS\examples\ and restart QV2QS. A fresh copy is extracted automatically on launch. To keep a permanent copy of an example file, copy the file to a local working folder before modifying. See Example projects.