This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1243: mmWave Studio control via MATLAB Error Solution Fails

Part Number: AWR1243

Unfortunately the solution posed in the linked question did not solve the issue . An error is now encountered when opening mmWave Studio and prevents it from opening. Two error message appear, one after the other.

The first: Error registering Lua functions

                System.TypeInitializationException:The type initializer for 'RSTD.LuaWrapperUtils'

                threw an exception. ---> System.IO.FileLoadException:Mixed mode assembly is

                built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0

                runtime without additional configuration information.

                  at LuaInterface.LuaWrapper..ctor()

                  at LuaRegister.LuaWrapper..ctor()

                  at RSTD.LuaWrapperUtils..cctor()

                  ---End of inner exception stack trace ---

                  at RSTD.LuaWrapperUtils.get_LuaWrapper()

                  at RSTD.frmMain..ctor()

The second: The type initializer for 'RSTD.LuaWrapperUtils' threw an exception.

                     Stacktrace:

                         at RSTD.LuaWrapperUtils.get_LuaShellCommands()

                         at RSTD.frmLuaShell.PrimerHelpMenu()

                         at RSTD.frmLuaShell..ctor(frmMain main_form)

                         at RSTD.frmMain..ctor()

                         at RSTD.Program.Main(String[] args

Restoring to the original config file then allows mmWave Studio to start as normal.

Any help would be appreciated.

Thanks,

Sam

  • Hi Sam,

    Could you please let me know the following:
    1) The version of Windows you're running on?
    2) The versions of .NET frameworks installed (you can get this from Start -> Run -> appwiz.cpl and scroll down to "Microsoft .NET Framework ...")

    I will check and see if there is a dependent version we require for mmWaveStudio that is missing in this list.

    Best Regards,
    Anand
  • Hi Anand,

    1. Windows 7 Professional 64-bit service pack 1
    2. In the name it says "Microsoft .NET Framework 4.7.1" and in the version number it says 4.7.02558 (Not sure which you wanted).

    Thanks,
    Sam
  • Thanks Sam, both the name and version number field are useful.

    Could you confirm for me that there is only .NET Framework 4.7.1 installed, and no other entries for prior versions (4.5* or 4.6*)?
  • Yes, that is the only one installed.
  • Sam,

    Would it be possible for you to try after installing .NET Framework 4.5.2 or version 4.6.2?

    Version 4.5.2 is available here: www.microsoft.com/.../details.aspx
    and
    Version 4.6.2 is available here: www.microsoft.com/.../details.aspx

    - Anand
  • I downloaded version 4.6.2 and then swapped the config files again. A different error message appears:

    C:\mmwave_studio_01_00_00_00\mmWaveStudio\RunTime\mmWaveStudio.exe

    The application has failed to start because it's side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

    Replacing the configuration file again allows mmWave Studio to open normally.

    Thanks,
    Sam
  • Sam,

    Thanks for trying this out. We will need some time to check this behavior.

    I will try and get back to you as soon as I have an update.

    Best Regards,
    Anand
  • Sam,

    Could you please check with the attached updated config file?

    Thanks,

    Anand

    5684.mmWaveStudio.exe.config
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    <?xml version="1.0"?>
    <configuration>
    <configSections>
    <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
    <section name="RSTD.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false"/>
    </sectionGroup>
    </configSections>
    <userSettings>
    <RSTD.Properties.Settings>
    <setting name="MainConsolePosition" serializeAs="String">
    <value>50, 50</value>
    </setting>
    <setting name="MainConsoleSize" serializeAs="String">
    <value>625, 566</value>
    </setting>
    <setting name="MainConsoleZoomFactor" serializeAs="String">
    <value>1</value>
    </setting>
    <setting name="MainConsoleFilterExclude" serializeAs="String">
    <value/>
    </setting>
    <setting name="LastScriptsRun" serializeAs="String">
    <value/>
    </setting>
    <setting name="LastTreePath" serializeAs="String">
    <value/>
    </setting>
    <setting name="LastMonitorPath" serializeAs="String">
    <value/>
    </setting>
    <setting name="BrowseTreeSize" serializeAs="String">
    <value>854, 582</value>
    </setting>
    <setting name="BrowseTreePosition" serializeAs="String">
    <value>343, 338</value>
    </setting>
    <setting name="LastScriptPath" serializeAs="String">
    <value/>
    </setting>
    <setting name="LastDllPath" serializeAs="String">
    <value/>
    </setting>
    <setting name="MainConsoleFilterInclude" serializeAs="String">
    <value/>
    </setting>
    </RSTD.Properties.Settings>
    </userSettings>
    <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
    <assemblyIdentity name="LuaInterface" publicKeyToken="1E1FB15B02227B8A" culture="neutral"/>
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Rttt.Controls.DockPanelSuite" publicKeyToken="51101D49406257D3" culture="neutral"/>
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="Rttt.Controls.DockPanelSuite" publicKeyToken="51101D49406257D3" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-2.2.3596.32777" newVersion="2.2.3596.32777"/>
    </dependentAssembly>
    <dependentAssembly>
    <assemblyIdentity name="RtttRemoting" publicKeyToken="51101D49406257D3" culture="neutral"/>
    <bindingRedirect oldVersion="0.0.0.0-1.0.3700.35917" newVersion="1.0.3700.35917"/>
    </dependentAssembly>
    </assemblyBinding>
    <loadFromRemoteSources enabled="true"/>
    </runtime>
    <startup useLegacyV2RuntimeActivationPolicy="true">
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • Hi Anand,

    1. I replaced the config file with the new one provided. Upon opening mmWave studio the initial splash screen appeared but then the same (i believe) errors appeared. I have attached an image of the errors when this occured. The top one appeared first and then the second appeared when okay was pressed on the first.

    2. I then change the name of the config file to remove the 5684. from the front of the file. This also did not work and the same errors occured.

    Thanks,

    Sam

  • Sam,

    The file I uploaded to e2e in the last post appears to be corrupted - I'm not sure why that happened.

    We were able to replicate your issue yesterday and the config file update should solve it.

    I have zipped up the corrected file and attached it again. The only change compared to the original .config file from the original mmWaveStudio installation is one word on line 5. (RTTT -> RSTD)

    Could you please either make this change manually, or try again with the file from the attachment? We expect this update should solve your original issue.

    Best Regards,

    Anand

    mmWaveStudioConfigUpdate.7z

  • Apologies for the delay in replying but this appears to have worked.

    Thanks,
    Sam Bonsor
  • Great. Thanks for confirming.

    This fix will be part of the next released version.

    - Anand