Java error when running script

Hi,

I get the following error when attempting to run my script:

%Error using matlab.internal.editor.eval.FileInfo
Java exception occurred:
java.io.IOException: java.lang.RuntimeException: Internal Exception in reading MLX file : fl:filesystem:AccessDenied
  at com.mathworks.services.mlx.MlxFileUtils.writeCode(MlxFileUtils.java:204)
Caused by: java.lang.RuntimeException: Internal Exception in reading MLX file : fl:filesystem:AccessDenied
  at com.mathworks.services.mlx.MlxFileUtils.nativeWriteMlxFile(Native Method)
  at com.mathworks.services.mlx.MlxFileUtils.writeCode(MlxFileUtils.java:202)
Error in matlab.internal.editor.eval.TmpFilePath.get
Error in matlab.internal.editor.evaluateCode
Error in matlab.internal.editor.evaluateCode

I'm trying to figure out what is causing this error, please help!

[Guillaume]

From

Internal Exception in reading MLX file : fl:filesystem:AccessDenied

I would guess you don't have permissions to read(?)/write(?) to a file

[Optical_Stress]

It seems that the error was initiated by having the same script open on multiple desktops (the current path is directed to a cloud folder). After closing matlab on all but one desktop, the error ceased.

Never mind, still seem to be getting the error...

[Optical_Stress]

So the script runs fine, the error only shows up when I attempt to run double commented segments of the script.

[Guillaume]

If you copy the script to a non-synched folder does the error still occur?

[Optical_Stress]

Yes the error is still triggered when all files are synced. I noticed that this started during an update with Dell drivers (graphics card related). Following the update, MATLAB's command terminal output a number of errors indicating that it will now use some virtual low performance graphics card... I have not been able to revert this setting/feature.

[Guillaume]

I meant copying the file into a folder that's completely independent of the cloud.

It may be a red herring but the error message and your initial comments would suggest that something is opening the file at the same time as matlab. The only thing I can suggest is looking at which processes try to access the file with something like process monitor.

[Optical_Stress]

I'm tempted to believe it may be related to the fact that each desktop I have owns a different iteration of matlab (2016a, 2017b and 2018a). Perhaps by going between each one I may triggering java run time errors.

Answer 1

[Howard Lam]

Because some path settings are migrated from older version to newer version. Those paths that point to 2017a rather than 2017b or higher will cause these access errors.

[Millard Alexander]

I have the same error. howard, how do I reset my path so that this doesn't happen?