Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error message when trying to update user-written programs from SSC with adoupdate

    I was trying to check for updates of user-written programs on two laptops with the adoupdate command and got the following error message:
    Code:
    . adoupdate
    (note: adoupdate updates user-written files; type -update- to check for updates to official Stata)
    
    Checking status of installed packages...
    
        [1] st0030_3 at http://www.stata-journal.com/software/sj7-4:
            installed package is up to date
    
        [2] sg162 at http://www.stata.com/stb/stb60:
            installed package is up to date
    
        [3] st0125 at http://www.stata-journal.com/software/sj7-2:
            installed package is up to date
    
        [4] xtlsdvc at http://fmwww.bc.edu/repec/bocode/x:
    
    connection timed out -- see help r(2) for troubleshooting
                     fopen():   603  file could not be opened
             loadsscupfile():     -  function returned error
     pkg_update_status_ssc():     -  function returned error
         pkg_update_status():     -  function returned error
    pkg_update_status_noisily():     -  function returned error
     extract_update_exists():     -  function returned error
        pkg_chk_and_update():     -  function returned error
                     <istmt>:     -  function returned error
    r(603);
    I got this error message on both laptops. adoupdate runs smoothly as long as the user-written program was originally installed from a source different from SSC. It breaks when it tries to look up the first program installed from SSC (http://fmwww.bc.edu/repec/bocode/x). On my other laptop, the first SSC program is a different one. Thus, the problem is not related to the specific program above.

    Does anyone else experience similar problems?
    https://twitter.com/Kripfganz

  • #2
    Hi Sebastian. Yes, I saw the same thing this morning.

    Code:
    . adoupdate
    (note: adoupdate updates user-written files; type -update- to check for updates to official
           Stata)
    
    Checking status of installed packages...
    
        [1] st0076 at http://www.stata-journal.com/software/sj4-4:
            installed package is up to date
    
        [2] dm91 at http://www.stata.com/stb/stb61:
            installed package is up to date
    
        [3] polychoric at http://web.missouri.edu/~kolenikovs/stata:
            package no longer available
    
        [4] fapara at http://www.ats.ucla.edu/stat/stata/ado/analysis:
            package no longer available
    
        [5] st0169 at http://www.stata-journal.com/software/sj9-3:
            installed package is up to date
    
        [6] tab3way at http://fmwww.bc.edu/RePEc/bocode/t:
    
    connection timed out -- see help r(2) for troubleshooting
                     fopen():   603  file could not be opened
             loadsscupfile():     -  function returned error
     pkg_update_status_ssc():     -  function returned error
         pkg_update_status():     -  function returned error
    pkg_update_status_noisily():     -  function returned error
     extract_update_exists():     -  function returned error
        pkg_chk_and_update():     -  function returned error
                     <istmt>:     -  function returned error
    r(603);
    I assume it is a problem with the bc.edu website that will be fixed eventually.
    --
    Bruce Weaver
    Email: [email protected]
    Web: http://sites.google.com/a/lakeheadu.ca/bweaver/
    Version: Stata/MP 18.0 (Windows)

    Comment


    • #3
      It appears to have been fixed already. I just ran -adoupdate- myself (before reading this post) and encountered no problem.

      Comment


      • #4
        Confirmed! It worked for me just now too.
        --
        Bruce Weaver
        Email: [email protected]
        Web: http://sites.google.com/a/lakeheadu.ca/bweaver/
        Version: Stata/MP 18.0 (Windows)

        Comment


        • #5
          Confirmed, too.
          https://twitter.com/Kripfganz

          Comment

          Working...
          X