Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: st: problem with latest update?

From   Alan Riley <>
Subject   Re: st: problem with latest update?
Date   Tue, 5 Apr 2011 15:18:07 -0500

Paul Visintainer ( reported
having a problem obtaining the latest update for Stata 11:

> My group is getting some unusual errors following the latest update.  Running a simple linear regression (one dependent and one independent variable) gives the following error:
> (_coef_table() in lmatabase, compiled by Stata 11.2, is too new to be run by this version of Stata and so was ignored)
> <istmt>:  3499  _coef_table() not found
> r(3499);
> Our executables are dated:  04 NOV 2010 (latest available)
> Our ados are dated: 30 MAR 2011 (latest available)
> Utilities are dated 01 SEP 2010 (latest available)
> Version is 11.1 

Others suggested to Paul that he should force another update, which
he can do with the commands

    . update executable, force
    . update utilities, force
    . update ado, force
    . update swap

Paul reported that this resolved the problem.  He also reported
that this same problem had arisen with several machines at his
workplace, and that even though his machine now has the 30 Mar 2011
Stata executable on it, -update- is still showing the latest
available update is 04 Nov 2010.

There is nothing to worry about here; everything is fine with
both Stata and with the update for Stata on

The problem Paul is seeing is caused by a caching proxy server or
firewall at his organization improperly caching an 'update' file
from which contains the old update date of "04 Nov 2010"
rather than retrieving the latest version of the 'udpate' file from which contains the new "30 Mar 2011" date in it.

The file is literally named 'update' and literally has the text
string '30 Mar 2011' in it.  Stata reads this file over the Internet,
compares it to the date of itself, and determines from that whether
an update needs to be performed.

If a caching proxy server holds on to an old version of that file
and gives the old version to Stata when Stata tries to download it,
Stata can't see that there is a new update available.  The 'force'
workaround shows above will work so long as the proxy server does
not also cache the executables or ado-files.

Usually proxy servers which have cached such files will flush their
caches on a regular basis, either daily or weekly, so such a problem
would typically resolve itself within a short period of time.


*   For searches and help try:

© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index