Simulink Startup Error shows Server Error

Hi, When I start my Simulink, it shows two errors

Task name: 'sltemplate.internal.request.loadTemplates' Task arguments: '' Error Type: 'Server Error' Error Message: 'Forbidden;403'

Task name: 'sltemplate.internal.request.loadSimulinkHistory' Task arguments: '' Error Type: 'Server Error' Error Message: 'Forbidden;403'

Any reasons and solution to this please? Thank You

Answer 1

[Pradeep Kumar]

After uninstalling and reinstalling MATLAB thrice, I think I may have found a solution to this problem.

Let me first list out things that don't work:

1. Reinstalling MATLAB
2. Reinstalling MATLAB in a drive different than the original drive (D:\ instead of C:\ e.t.c.)
3. Executing the commands listed in the above answer.
4. Regenerating the MATLAB preference folder as instructed in the link provided in the above answer.

Now the solution is pretty simple. This error goes away if the internet connection is turned off when MATLAB/Simulink is opening.

The connection can be turned ON once simulink has opened successfully.

Although this is only a work-around, it seems to be the only way to get around this problem until MathWorks comes up with a solution.

[Pradeep Mp]

Thanks a lot bro. After struggling so many times to open simulink, I thought of uninstalling matlab. But after seeing your answer, I used your trick and it worked.

[Pradeep Kumar]

Great to know that it worked for you! Cheers.

[Shravan Kumar]

this method is not working

Answer 2

[Sonam Gupta]

Execute the following commands in your MATLAB command window to resolve this issue:

 restoredefaultpath
 rehash toolboxcache
 savepath
 sl_refresh_customizations

If the above commands do not work then regenerating MATLAB preference folder by following the instructions at this link may help:

https://www.mathworks.com/matlabcentral/answers/99625-how-do-i-regenerate-my-matlab-preferences

[Pradeep Kumar]

This does not resolve the issue. I have tried regenerating the MATLAB preference folder as well, as directed by the above link. However, the problem still persists.

Please look into this issue at the earliest and provide a resolution.