Announcement

Collapse
No announcement yet.

Snapshot import fails with message: Archive error 13

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Snapshot import fails with message: Archive error 13

    When trying to import a snapshot the import fails because the database is in use and when the database cannot be overwritten a message similar to the following is shown: -

    +++++++++++++++
    FATAL ERRORS
    (File ExportFiles.cpp, Line 170) - Archive error 13 - Extract selected files call failed
    Library error - ChilkatLog:
    GetEntryByName:
    DllDate: Oct 28 2013
    ChilkatVersion: 9.4.1.68
    UnlockPrefix: SELLERZIP
    Username: NB-05:SDUser
    Architecture: Little Endian; 32-bit
    Language: Visual C++ 8.0
    VerboseLogging: 0
    entryToFind: ./CATALOG_SITE/ActinicCatalog.mdb
    caseSensitive: 0
    Found entry and returning ZipEntry object...
    --GetEntryByName
    --ChilkatLog
    has been caught.
    -------------------------

    The exact error may vary between versions but the important parts are

    Archive error 13 - Extract selected files call failed

    This means the file could not be exported

    entryToFind: ./CATALOG_SITE/ActinicCatalog.mdb

    This indicates that it is the database export from the snapshot that has failed as the folder 'CATALOG_SITE' is the folder that is stored within the snapshot that holds the site.

    This can happen for two reasons either:
    • The database is open in an external application such as Microsoft Access
    • The database is open from the SellerDeck software


    The second reason shown above can be possible if PHP code within the site's design features code that opens the database, but does not subsequently close it.

    For example code that opens the database could be : -
    Code:
    <actinic:block php="true" >
          $connect = odbc_pconnect("ActinicCatalog<actinic:variable name="ECMajorVersion" selectable="false" />", '', '', SQL_CUR_USE_ODBC);
    </actinic:block>
    If this code is missing the close command: -

    odbc_close_all();

    within it at some point, then the connection may not be closed and the error above may be seen.
Working...
X