If the version of Control running is 5.x, use these instructions to upgrade to the latest build. If your version is 4.5 or later consult with Tier 2,3 Tech before moving forward.

  1. Go to www.cyrious.com/customer and log in.
  2. At the top of the page, hover over “Support”
  3. In the gray bar underneath, click Downloads.
  4. Download the Control 6.1 Update.
  1. Get all users to exit Control.
  2. Right-click the SSLIP icon and choose Shut Down > Launch SQL management Studio and back up the database.
  3. The SSLIP will warn you if there are still users logged in before shutting down.
  4. Once the SSLIP is shut down, run the Updater.
  5. The updater will first ask for the license key, which it should already have. Click OK, if you need the key you can get it by going to internal Control Explore Company > then click on Company > The license key will be in the upper right > just copy and past into the setups license key field.
  6. If the updater detects that Control is still running, first look for any instances of Control.exe running in Task Manager (make sure to click the Show Processes from all Users button if it's there) and also check in Control Panel > Administrative Tools > Computer Management > Shared Folders > Open Files for any files open in the Cyrious folder. If there are any, select all items in the Cyrious folder and right-click to close the open files. Then you should be able to proceed with the installation.
  7. Once the installer finishes, its a good idea to go to services and restart the SQL service then the Chapi service > then run the SSLIP.exe.
  8. Once SSLIP is started, log into Control to finish the update. Depending on how many tables have changed since the version prior, this may take several minutes. Do not log into Control from any other workstations until Control fully logs in the first time.
  9. You must also open an existing order in Control and edit and save an order making sure that Control is writing to the database, if an order is not available you can create a test order then void after testing.
You could leave a comment if you were logged in.