Upon diverse tasks from within Simulink - Error: The server threw an exception.

Dear fellow Developers,

currently I encounter the following issue upon trying to update a Requirementset of my Simulink Model.

The Set is loading properly and the Update of the original document can be validated via commandline properly.

As soon as I either trigger the update from the GUI of the Requirement Editor (Filedialog pops up and I select the File) or after executing the command below I get the displayed behavior.

[status,changeList] = updateFromDocument(topRef)

status =

    'Error: Ausnahmefehler des Servers.
     '


changeList =

     []

On the other Hand I also had this error while a customized set of Rules was load to the Model Checker and I tried to either generate code or perform model checks. Same error behavior. I get a popup stating Error: The server threw an exception. with no further Details.

This Error only happens on my system and even happened accross mutliple Matlab Versions R2022b, R2023a as well as R2023b (with and without Update 1) Same Simulink project and customized rules on a different machine work fine with all the mentioned Matlab versions.

Currently the only lower Version availlable on my PC is R2015b due to project maintenance reasons.

Is there either a possibility to get more detailed logs about what actually causes this Application Server error so that I can try to clear up the Issue?

Answer 1

[Kai]

Apparently the solution to this was also related to a COM-Plugin of Excel being incompatible with Matlab in the background.

My described usecases did not make it obvious for me, that Matlab was actually always throwing this error while directly interacting with Excel while our Validation environment utilizing Spreadsheetlink works absolutely fine.

The Requirement topic was not obvious as I didn't perform any explicit XLSWRITE operations to the Requirement definition file. But Matlab of course performs a XLSREAD call.

For the Simulink Check scenario it was even more obfuscated as our Ruleset installs scripts which load check definitions from a configuration *.xlsx file to propagate configurations across projects and users. So here again a unexpected XLSREAD happened which could cause this error.

Troubleshooting was a step by step process deactivating one COM-AddIn at a time in Excel and restarting both Applications over and over until the combination of a working set of active and inactive COM-AddIns could be achieved.