Measurement Studio Application is Still Using Evaluation Versions of Controls After Licensing Measurement Studio

Updated Aug 31, 2018

Reported In

Software

  • Measurement Studio

Issue Details

I was using Measurement Studio ActiveX evaluation controls in my project, and then I bought and installed an earlier version of Measurement Studio. Why is my project still using the Measurement Studio evaluation controls?

Solution

If you install newer, unlicensed versions of Measurement Studio ActiveX controls on a machine that has previously licensed versions of the Measurement Studio controls, the controls might exhibit one of the following behaviors:
  • The licensed controls become evaluation software for 30 days.
  • The licensed controls do not let you use functionality that was present in the licensed version.
Fix these states by using the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder.

If the license fixer doesn't work, you should try to delete the control from your project, drop it in again, and, if applicable, recompile. Sometimes there is a linking issue for controls in existing projects.

If that doesn't work, then the evaluation version is probably a newer version than the one included in your purchased version. You can try uninstalling the evaluation version before installing the purchased version.

Some symptoms of a newer version existing during an installation include either a message or a pause and apparent skip over a section of the full installation.

If some control still appears as an evaluation version, then you can find the particular files for the control that is reporting evaluation version and unregister and delete them before installing your purchased version. For this example, assume that you have this problem with the DataSocket control. You can follow these steps:
  1. Uninstall Measurement Studio.
  2. Unregister the problematic ActiveX control(s) using regsvr32.exe:
    1. Select Start»Run.
    2. In the dialog box that appears, type regsvr32 /u [Full path of .ocx file], where [Full path of .ocx file] is the location of the .ocx file. The .ocx file should be in the C:WINDOWS\system32folder. If you have a 16-bit control, you can run regsvr instead of regsvr32.
  3. Find the names and locations of the ActiveX .dll files you need to delete. For DataSocket, the file you need to remove is nids.dll. For Measurement Studio ActiveX user interface controls, you need to remove cwui.ocx. These files are located in WINDOWS\system or WINDOWS\system32.
  4. Install your purchased version and test the controls that didn't work.

WAS THIS ARTICLE HELPFUL?

Not Helpful