Precision, Performance, Confidence. ™

Step by step installation and upgrade for Met/Base Software

Step-by-Step Met/Base Installation and Upgrade

 

Step by step upgrade/ installation including bringing over files from an old installation.

You will need to put aside some time for people to be down before you do this.  You can do a test installation using a copy of the database and at least one client so you don’t have to take your whole group down.  But you will eventually need to completely stop the old server and point all clients to the new one.  You can’t run the two systems in parallel without loss of data.

 

  • If you are using CD’s you will need to physically mount the cd’s in the server – you cannot do this remotely.  You can run remotely, but the CDs have to be in the actual server machine.  Alternately you can mount an ISO image file. 
  • You need to shut down the database engine on the existing machine so you can copy the mtrack.db file from your old 7.X installation. (or possibly metbase db if you are using 7.2SP3)
  • Install the software on the new server, do a typical installation of server features only (use the auto run – this will ensure that you install all the necessary windows prerequisites.)
  • When it prompts you for a database name – DO NOT keep the default “metbase”, metbase_ABC or metbase_company_name or something unique would be good, do not use the same one you used for your old installation either.
  • Reboot after installation.
  • Stop the database engine on the new server. Go to start>all programs>fluke calibration>stop calibration data engine
  • If you are upgrading from 7.2 and earlier go to start>all programs>fluke calibration>dbupdate
  • When dbupdate launches you will get a screen that asks you to browse to the database in the first line. Browse to your old mtrack.db file (copied over from your old server or just browse to the old server and grab the mtrack.db file from the metdata directory)
  • Launch the update, saying “YES” when it asks you if you want to overwrite the database. You are overwriting only the stock database that the installer installs.
  • You will need to share the file c:\programdata\fluke\metbase\shared so share “shared” only. NOTE*** ProgramData is a HIDDEN directory so you will need to unhide it. DO NOT confuse it with Program Files (X86)
  • Copy files from the old Metcal directory: NOTE PROC is handled differently.
  1. Copy all pic files from the old metcal\pic directory into the shared\pic directory.
  2. Copy all prompt files from the old metcal directory into the new shared\promptfiles directory (pass_db.txt, fail_db.txt and promptdb.txt – don’t worry about those with the letter designator “J”
  3. Copy any CUSTOM reports from the old metcal directory into the new shared\reports directory.
  4. The procedure directory: I would recommend that you rename the old metcal\proc to proc_old. Once it is renamed, locate the shared\proc directory and drag the directory proc_old (the WHOLE directory – do not copy and paste individual files) into the shared directory so it is at the same level as shared\proc
  • Restart the database engine on the server by going to start>all programs>fluke calibration>start calibration data engine.
  • Backup files on the client machines.
    1. Find the c:\metcal\station directory on the client machines and take a copy of the file called “config.dat”
  • Uninstall software on client machines. Browse into the windows directory and manually remove the metcal.ini file.
  • Reboot the machine after uninstall.
  • Map a virtual drive letter on the client machine to the “shared” directory on the server. The client installation program will ask you for the drive letter during the installation.
  • Install the client software on the client following the “typical” installation process and again using “autorun” (to install necessary prerequisites).
  • Enter the unique database name that you created in step 4 of the server installation where it prompts.
  • Select the drive letter you mapped to in step 16.
  • Complete the installation and reboot.
  • Test the installation by logging in to Met/Track. If you get “database server not found” errors first make sure your database has started on the server and second, follow the attached trouble shooting app note.
  • Launch Met/Cal runtime and re-set your default procedure directory. From Met/Cal runtime, click “ctrl and D”, browse to the “shared” directory and select “proc_old” to retrieve all of your existing procedures.
  • Put back your saved config.dat file into(from step 13) c:\programdata\fluke\metcal (overwriting any existing)
  • Call 800-825-7411 or softwaresupport@fcom for assistance.

 

 

Have more questions? Submit a request

Comments

Please sign in to leave a comment.