After updating to version 6.7.3 custom workspace failed to load

otcscan

Member
Joined
Jan 19, 2022
Posts
10
Likes
2
Hi,
Does anyone has the same problem? It's for MW 6.7.3 on Windows10, CQG.
After making modifications to my workspace (deleting some templates and importing few others) MW at the next start opens in default mode with EP an NQ charts without my custom workspace. Restoring the workspace from file does not work: MW returns over to default workspace and none of TaskBar commands further work, so it could be closed only by force quit from Windows Task Manager. Output file contains:
08:55:15 SEVERE Startup::loadWindows() error reading windows file: Expected a ':' after a key at 5790988 [character 5790989 line 1]
08:55:15 SEVERE
...
08:58:03 INFO Restoring from backup: D:\MotiveWave Backup\Test May-08 16-47.zip
08:58:05 INFO MWInstrument::load() load instruments: 3573 elapsed: 34
08:58:05 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\alert_history.json
08:58:05 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\trade_panel_templates.json
08:58:05 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\note_styles.json
08:58:05 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\order_actions.json
08:58:05 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\custom_orders.json
08:58:05 WARNING BarTheme::register() theme already added! Dark
08:58:05 WARNING BarTheme::register() theme already added! DarkDark
08:58:05 WARNING BarTheme::register() theme already added! DarkRedGreen
08:58:05 WARNING ChartTheme::register() theme already added! Black
08:58:05 WARNING ChartTheme::register() theme already added! Dark Grey
08:58:05 WARNING ChartTheme::register() theme already added! Black Dark
08:58:05 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\scans.json
08:58:07 WARNING RestoreWorkspaceDialog::copy() deleting: C:\Users\Admin007\AppData\Roaming\MotiveWave\workspaces\Test\config\desktops.json
08:58:07 INFO RestoreWorkspaceDialog::restoreFromBackup() restore time: 2428
08:58:09 SEVERE Startup::loadWindows() error reading windows file: Expected a ':' after a key at 5790987 [character 5790988 line 1]
08:58:09 SEVERE
...
08:58:09 WARNING Startup::loadWindows() console not loaded. Loading from defaults
08:58:09 WARNING DockableWatchListFactory::read() watchlist not found: Indices
08:58:09 WARNING MWJSONUtil::readTable() column not found: <openInterest>
08:58:09 WARNING StudyFactory::createStudy() study is not supported: Auto Harmonics com.motivewave;HARMONIC
08:58:09 WARNING StudyFactory::createStudy() study is not supported: Hurst Cycles com.motivewave;HURST_CYCLES
08:58:09 WARNING StudyFactory::createStudy() study is not supported: Auto Elliott Wave com.motivewave;ELLIOTT_WAVE
08:58:09 WARNING MWJSONUtil::readTable() column not found: <cashBalance>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <marginBalance>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <fcmId>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <closed>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <minimumMargin>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <minimumBalance>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <buyingPower>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <usedBuyingPower>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <reservedBuyingPower>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <lossLimit>
08:58:09 WARNING MWJSONUtil::readTable() column not found: <status>
 

Donovan2580

Well-known member
Joined
Sep 13, 2020
Posts
442
Likes
239
Just wanted to let you know it isn't just you - I have had the same issues.

I believe support has the bug tracked down and we should be seeing a new release to address this issue very shortly.

Until then I have been running an older version :)
 

otcscan

Member
Joined
Jan 19, 2022
Posts
10
Likes
2
It was OK for me as well till I started to make modifications after 6.7.3 update. I found earlier post on this issue from April concerning ver 6.7.0, seems like the problem is still not solved.
 
Last edited:
Top