Error r(3499)

[Parviz Alizada]

I have Stata/SE 15.1 at SE 15.0 on Windows 64 bit on different computers. Now, when I run

stintreg

estimation on 15.1 it returns an error message but the same thing works on 15.0 version. Why could this be the case?

I run the following command

stintreg `variables', interval(date0 date1) dist(weibull) vce(robust)

This is the error message I receive:

Fitting constant-only model:
(Mopt_drop_external() in lmataopt, compiled by Stata 15.1, is too new to be run by this version of Stata
and so was ignored)
<istmt>: 3499 Mopt_drop_external() not found
(Mopt_drop_external() in lmataopt, compiled by Stata 15.1, is too new to be run by this version of Stata
and so was ignored)
<istmt>: 3499 Mopt_drop_external() not found
r(3499);

I use same environtment, matsize and maxvar settings in both:

clear
clear matrix
clear mata


set matsize 10000
set maxvar 32760

clear matrix
set type double
capture log close
set more off,permanently

[Clyde Schechter]

Well, it sounds like you are having some version incompatibility going on. I suggest that you update both Stata installations to the most recent update of 15.1, and then I think the problem will go away. I suspect that the version 15.1 that is giving you the error message is somehow only partially updated and you are ending up with some code that is partly appropriate for version 15.0 and partially appropriate for 15.1.

[Parviz Alizada]

Well, it sounds like you are having some version incompatibility going on. I suggest that you update both Stata installations to the most recent update of 15.1, and then I think the problem will go away. I suspect that the version 15.1 that is giving you the error message is somehow only partially updated and you are ending up with some code that is partly appropriate for version 15.0 and partially appropriate for 15.1.

Clyde, thanks for replying. I have checked 15.1 version, it is up to date. Another one I am accessing through cloud; therefore unable to change or update it. Do you think this problem can be related to my computer's capacity? Or perhaps some updates in 15.1 are blocking this code to run properly.

[Clyde Schechter]

It doesn't sound like any kind of computer capacity issue; if that's really it, then the message is very misleading. Granted, sometimes Stata's error messages are misleading in ways like that, but it doesn't happen often. If you were to post an example of your data that triggers this problem on your setup (use the -dataex- command to do that; see FAQ #12 for instructions on -dataex-), I would be happy to run it on my own setup to see if I can reproduce the problem. (You would also need to give the complete command, since I have no way of knowing what's in local macro variables. And similarly you would need to show how you -stset- the data.) I have a completely up-to-date version 15.1. If I can reproduce the error, then it is most likely a bug. If it runs on my setup but not yours, then it is probably a problem with your installation. If that is the case, I would do -update all, force- on the off chance that some part of your 15.1 is not actually up to date even though you and -update- both think it is.

[Parviz Alizada]

It doesn't sound like any kind of computer capacity issue; if that's really it, then the message is very misleading. Granted, sometimes Stata's error messages are misleading in ways like that, but it doesn't happen often. If you were to post an example of your data that triggers this problem on your setup (use the -dataex- command to do that; see FAQ #12 for instructions on -dataex-), I would be happy to run it on my own setup to see if I can reproduce the problem. (You would also need to give the complete command, since I have no way of knowing what's in local macro variables. And similarly you would need to show how you -stset- the data.) I have a completely up-to-date version 15.1. If I can reproduce the error, then it is most likely a bug. If it runs on my setup but not yours, then it is probably a problem with your installation. If that is the case, I would do -update all, force- on the off chance that some part of your 15.1 is not actually up to date even though you and -update- both think it is.

I did -update all, force- and found out that I had two Stata applications in the same directory. One is "StataSE-64" and another one is "StataSE-64_old". Apparently, this problem was caused by the use of the latter one. So, I ran the first one and the execution of the command went smoothly. I renamed "StataSE-64_old" and ran -update all, force- on "StataSE-64". With the update "StataSE-64_old" application was written to the same directory again.

[Clyde Schechter]

Yes, when you run -update-, Stata does not obliterate your pre-existing Stata. It renames it with an _old prefix and leaves it in your directory. That way, if the updated version is broken (which has never happened to me, but I suppose it can happen) you can revert to what you had before until the problem is fixed. Anyway, Stata*_old.exe should not be actually used. It is just there as a backup to enable you to restore the pre-update version in the event of a problem.