1 Reply Latest reply on Dec 30, 2015 7:29 PM by Derek Lawson

    "Database is locked" error while upgrading shared toolbox with SW 2016 SP1.0 install

    Chris Bassett

      Background: we are upgrading from SW 2014 SP5.0 to SW 2016 SP1.0.  Our PDM server is on SP1.0.  However, our toolbox, which is shared in the PDM vault, still is of version 2014 (still uses the MDB file extension, and not the new SLEDB extension used by SW 2016).  Basically, I'm getting an error that says the database is locked.  Per the instructions from SW's website, it says to check out the SWbrowser.mdb file with a user that has full rights (I'm using the admin user that is installed when PDM is installed for this).


      I'vet already installed SW 2016 on some machines and when I try to point them to the shared toolbox in the vault, I get the error saying that it can't find the SLEDB file, which makes sense since the db is still in the old MDB format.  So, I have two more workstations to install, and I tried to get the 2016 SW installer to upgrade the toolbox but get the error shown in the picture below.



      Can anyone offer any suggestions as to why this is happenning?


      I've attached a screen shot of the error message, although it doesn't offer much help.,


      Here is a link to the instructions I have been following:

      2016 SOLIDWORKS PDM Help - Upgrading to Manage Toolbox Entirely in the Vault

        • Re: "Database is locked" error while upgrading shared toolbox with SW 2016 SP1.0 install
          Derek Lawson



          In the same location as the mdb (master database) file, is there another file with an ldb (lock database) extension? This file is created when modifications are being made to the toolbox and then deleted when finished, however I have seen an ldb file not get deleted and prevent the upgrade from moving forward properly. Deleting that file may be the solution, but without further research, I can't recommend deleting it without first being sure that there is nothing in your toolbox that actually is/was modified, as you may lose any of those changes if the ldb file is deleted.


          I would start there, and if you see an ldb file then that is probably what's holding you back, but I would definitely double check before deleting it.


          Derek M. Lawson