'=' character not found in line SBS crash (User file corruption)

'=' character not found in line SBS crash (User file corruption)

If SBS crashes on loading a scenario and the error message mentions '=' character not found in line and refers to a *.user file in the Data/Scenarios folder, it means that User file has become corrupted. 

The error will look similar to the image below:


To fix the issue, navigate to the folder which contains the file mentioned in the crash. Next delete the file mentioned in the error dialogue box.
Warning
Make sure you delete the .user file and NOT the .smeta file
The scenario should now run.
    • Related Articles

    • pCurNode SBS Crash

      SBS pCurNode Crash: Condition: pCurNode Location: LangSys.cpp The crash is caused by a corrupted language file. Copy the language file from another PC and then Overwrite the file on the PC on which the crash occurs. The language file is located in ...
    • Multimon SBS Crash

      Multimon SBS Crash: Condition: SetDisplayDimensions(pDisplay, aDisplays) Message: CMultiMon::SetConfiguration: Dimensions not found for display Multimon configuration settings incorrect - SimCAB display PC was connected to the multimon network when ...
    • SBS White Screen

      If SBS on the operator screens shows a white screen instead of the usual blue, it means the screens have not been set up correctly. The issue is due to the different operator screens having different resolutions OR different scaling and the ...
    • Determine Software Build Version

      In order to determine the exact version of the software build follow the steps below. Open SBS on the simulator computers, using SBS Manager. On the instructor computer, usually PC1. Click on the Help menu option, located on the top left of the SBS ...
    • Fixing an Ethernet Motion Platform which is unresponsive in SBS but connects correctly in the Ethernet Hardware App (EHA)

      If a motion platform performs its homing movement on power on and you are able to connect to it via the EHA but it does not work in SBS then the most likely culprit is that the serial number of the motion base does not match the serial number in the ...