Dot indexing is not supported for variables of this type: Error message after Matlab startup.

I am recieving error message:

Dot indexing is not supported for variables of this type.
Error in rmiml.getAll
and 
Error in matlab.internal.codingui.warmupProgrammingAids

straight after start up..

When I try to run imshow() the same error appers again and no figure is generated.

Dot indexing is not supported for variables of this type.
Error in imshow (line 269)
    style = s.matlab.imshow.InitialMagnificationStyle.ActiveValue;

Now I use Matlab 2020a but I had the same problem with Matlab 2017. But 2017 worked well some time ago...

[Walter Roberson]

What shows up for

which -all settings

If anything shows up before toolbox/matlab/configtools/settings.m then you have a conflict, a file that should not be there.

[Jakub Jon]

I am not sure what do you mean by: "If anything shows up before toolbox/matlab/configtools/settings.m then you have a conflict"

Output of this command looks like this:

C:\Program Files\MATLAB\R2017b\toolbox\matlab\configtools\settings.m

Is this correct or not? What would it meant to have a conflict.

Yes this is 2017. 2020 I use on different PC but basically main problem is the same that I can not run imshow on any of those to PCs.

I suspect that it could be somehow caused by wrong installation or windows environment which is managed by our company..

[Jakub Jon]

When I run 2017 version I see different error message after start up:

com.mathworks.jmi.MatlabException: Invalid default value for property 'Impl' in class 'connector.internal.ConnectorManager':
Struct contents reference from a non-struct array object.
	at com.mathworks.jmi.NativeMatlab.SendMatlabMessage(Native Method)
	at com.mathworks.jmi.NativeMatlab.sendMatlabMessage(NativeMatlab.java:259)
	at com.mathworks.jmi.MatlabLooper.sendMatlabMessage(MatlabLooper.java:120)
	at com.mathworks.jmi.Matlab.mtFeval(Matlab.java:1713)
	at com.mathworks.jmi.Matlab.mtEval(Matlab.java:1647)
	at com.mathworks.jmi.Matlab.mtEval(Matlab.java:1628)
	at com.mathworks.matlabserver.connector.impl.AutoStartImpl$2.run(AutoStartImpl.java:63)
	at com.mathworks.matlabserver.connector.impl.AutoStartImpl$TaskListener.mvmChanged(AutoStartImpl.java:200)
	at com.mathworks.matlabserver.connector.impl.AutoStartImpl$TaskListener.mvmChanged(AutoStartImpl.java:182)

[Walter Roberson]

https://www.mathworks.com/matlabcentral/answers/370874-m-file-not-opening-in-editor-window-2017b

https://www.mathworks.com/matlabcentral/answers/463666-error-while-launching-matlab-error-when-trying-to-open-scripts-m-files-and-error-close-all-in-r (which leads to saying to check which -all isrow )

[Jakub Jon]

yes I saw those too.. unfortunately there is no solution..

1) I have the same pathdef.m file in both directories and I do not have two installations of Matlab on one PC

2) What do you mean by: "which leads to saying to check which -all isrow " is it somehow related to my problem?

I tried:

restoredefaultpath
rehash toolboxcache
savepath

but problem stil persist..

[Walter Roberson]

Potentially. Third-party isrow messes up processing of startup and pathdef

[Jakub Jon]

ok output is:

>> which -all isrow
built-in (C:\Program Files\MATLAB\R2017b\toolbox\matlab\elmat\isrow)
isrow is a built-in method                                                    % string method
C:\Program Files\MATLAB\R2017b\toolbox\matlab\datatypes\@categorical\isrow.m  % categorical method
C:\Program Files\MATLAB\R2017b\toolbox\matlab\bigdata\@tall\isrow.m           % tall method

is there anything I can do?

[Walter Roberson]

That looks okay.

Answer 1

[Jakub Jon]

RESOLVED

root cause similar to this:

https://uk.mathworks.com/matlabcentral/answers/480471-returns-error-after-clicking-on-a-plot

current folder contained my own .m file called settings..

[Walter Roberson]

That is the first thing I asked about...