Startup configuration problems after installing R2017a parallel to R2012a

Question

walli 2017-3-17

1
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/330361-startup-configuration-problems-after-installing-r2017a-parallel-to-r2012a

评论： Mayela 2018-11-20

Hi,

til yesterday I'ved used only Matlab R2012a on my machine. Everything was fine and working well - however, due to the usage of some functions, which were not available under R2012a, I had to install R2017a yesterday. The installation itself worked smoothly. But after the startup of R2017a I'm getting a lot of warnings and errors in the command window. Typical warnings are:

Warning: Name is nonexistent or not a directory:
C:\Users\wallscheid\Documents\MATLABC:\Program
Files\MATLAB\R2017a\resources\opti 
Warning: Name is nonexistent or not a directory: C:\Program
Files\MATLAB\R2017a\resources\opti\examples 
Warning: Name is nonexistent or not a directory: C:\Program
Files\MATLAB\R2017a\resources\opti\help 
Warning: Name is nonexistent or not a directory: C:\Program
Files\MATLAB\R2017a\resources\opti\help\opti_html 
Warning: Name is nonexistent or not a directory: C:\Program
Files\MATLAB\R2017a\resources\opti\solvers 
Warning: Name is nonexistent or not a directory: C:\Program
Files\MATLAB\R2017a\resources\opti\solvers\mosek 
Warning: Name is nonexistent or not a directory: C:\Program
Files\MATLAB\R2017a\resources\opti\solvers\mosek\utilities 
...

Also, I'm getting the follow errors messages during startup:

Undefined function or variable 'rmiml.getAll'.
Undefined function or variable 'rmiml.visibleInToolstrip'.
Undefined function or variable 'rmiml.visibleInToolstrip'. 
Undefined function or variable 'matlab.internal.environment.context.isMATLABOnline'.

During my work with R2012a I've installed some open-source toolboxes, such as IPOPT (https://projects.coin-or.org/Ipopt). Some of these toolboxes configured Matlab automatically to link theirselves with Matlab, so I'm not sure what exactly had been changed in the startup routine. I somehow assumed that a new Matlab installation will have its completly own startup routine, but that seems to not be the case.

As I'm not a "Matlab Pro", I would be very grateful for receiving adivce how to fix that startup problem under R2017a.

Kind regards, walli