How to resolve this unknown licensing error?

Hi all

I am all of a sudden receiving this license-error (see below) on a number of scripts that used to work and that I should be licensed for. When following the paths specified at the bottom I can not find the R2012b_license or license.dat file. Only the .lic file exists. I tried "Update current licenses" but to no avail. I do not have a license for the statistics toolbox, but then again none of my programs (to my knowledge) needs it or calls elements from it. It puzzles me most that this happens with programs that used to work.

What has happened?

Thanks in advance!

Answer 1

[Sean de Wolski]

Contact our installation support team. They'll help you address the licensing problem.

Answer 2

[Walter Roberson]

That can happen if you accidentally create a .m file with the same name as something in one of the toolboxes.

Answer 3

[Image Analyst]

You can see which files it thinks it needs to get from the Statistics toolbox. Try one of these two links:

http://www.mathworks.com/matlabcentral/fileexchange/14176-depfuntoolbox

http://www.mathworks.com/matlabcentral/fileexchange/17291

I think the second one, fdep, is the more comprehensive. Or you can do it with the depfun() function. From the help:

Creating Dependency Reports

Use the Current Folder pane to navigate to the foldercontaining the files for which you want to produce a Dependency Report. 

Note:  You cannot run reports when the path is a UNC (Universal NamingConvention) path; that is, a path that starts with \\.Instead, use an actual hard drive on your system, or a mapped networkdrive.

On the Current Folder pane, click , and then select Reports > Dependency Report.

The Dependency Report opens in the MATLAB Web Browser.

If you want, select one or more options within thereport, as follows:

To see a list of all MATLAB code files (children)called by each file in the folder (parent), select Showchild functions. 

The report indicates where each child function resides, forexample, in a specified toolbox. If the report specifies that thelocation of a child function is unknown, it can be because:

The child function is not on the search path.

The child function is not in the current folder.

The file was moved or deleted.

To list the files that call each MATLAB codefile, select Show parent functions. 

The report limits the parent (calling) functions to functionsin the current folder. 

To include local functions in the report, select Showsubfunctions. The report lists local functions directlyafter the main function and highlights them in gray.

Click Run Report on Current Folder.

Answer 4

[Jakob Sievers]

depfuntoolbox doesn't work because of the same error.

fdep however reveals all dependencies but they remain restricted to either Matlab itself or the couple of toolboxes I do have a license for. Nothing seems to call anything from the statistics toolbox.

I have also tried renaming a couple of files which I figured could be names used by matlab (I basically just added a "my" in front of all of my functions), but to no avail.

No reply from Mathworks yet, likely due to easter. This is getting a bit frustrating I have to admit. Its like looking for the needle in a haystack. Do you think a re-install might help?

[Image Analyst]

This should have been a comment, not an "Answer". Anyway, I don't think reinstalling should be necessary, but we've all seen weird things before so why not? Especially if it will get you running today. Easter has nothing to do with it. They're never there any Sunday. It's because it's the weekend. In the US Saturday and Sunday are not usually workdays for people, except for those with certain jobs that require them to be there (retail stores, hospitals, police, airports, etc).

[Jakob Sievers]

Oh right. Been locked in work-mode for so long I have lost track of time. And sorry about the "answer" bit. That was an honest mistake :)

Answer 5

[Nathaniel Thomas]

I had a similar issue to you but with the Mapping Toolbox. I have been developing some code that closely mirrors functions contained in that particular toolbox for a navigation class and I suddenly could not save or set a breakpoint in my code let alone run it. doing the following solved the issue for me:

look in the folder that you saved the functions that your script calls and ensure any offending functions named like those in the "Statistics Toolbox" and remove them.

having a toolboxed function in your file directory seems to cripple every function saved in that file regardless of what those functions contain.

hopefully this helps!

regards,

Nate