FIX: "This Control Has Expired" Err Message on DEC Alpha/RISC (181309)


The information in this article applies to:

  • Microsoft Win32 Application Programming Interface (API), when used with:
    • Microsoft Windows 95
    • Microsoft Windows 98
    • Microsoft Windows NT Server 3.1
    • Microsoft Windows NT Server 3.5
    • Microsoft Windows NT Server 3.51
    • Microsoft Windows NT Workstation 3.1
    • Microsoft Windows NT Workstation 3.5
    • Microsoft Windows NT Workstation 3.51
This article was previously published under Q181309

SYMPTOMS

On DEC Alpha (RISC) platforms, certain controls installed with Visual Studio Service Pack 2 (SP2) or Service Pack 3 (SP3) expire on March 1, 1998. On that date, applications that include those controls will display one or both of the following error messages:
Sorry, this control has expired. Please obtain a newer version.
-or-
License information for this component not found. You do not have appropriate license to use this functionality in the design environment.

CAUSE

An internal expiration date was inadvertently enabled in the SP2 and SP3 versions of the controls.

RESOLUTION

A fix for this problem is available at the following Microsoft Web site:

http://www.microsoft.com/msdownload/vs97sp/controlupdate.asp

The name of the fix file is SP3Updat.exe (2 MB).

Temporary Workaround

You should download the file from the URL mentioned above to fix the problem. However, if you must keep the application running while getting the fix, you can reset the computer clock to a date prior to March 1, 1998.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Version Number

Version number for all new controls: 6.0.80.55

Here is a list of the controls that will be updated: 
   Control                 Date stamp
   ----------------------------------------

   Comct232.ocx            2/25/98  1:19AM
   Comctl32.ocx            2/25/98  1:19AM
   Comdlg32.ocx            2/25/98  1:19AM
   Dblist32.ocx            2/25/98  1:19AM
   Mci32.ocx               2/25/98  1:19AM
   Mscomm32.ocx            2/25/98  1:19AM
   Msflxgrd.ocx            2/25/98  1:19AM
   Msinet.ocx              2/25/98  1:19AM
   Msmapi32.ocx            2/25/98  1:19AM
   Msmask32.ocx            2/26/98  1:55PM
   Msrdc20.ocx             2/26/98  1:55PM
   Mswinsck.ocx            2/25/98  1:19AM
   Picclp32.ocx            2/25/98  1:19AM
   Richtx32.ocx            2/25/98  1:19AM
   Sysinfo.ocx             2/25/98  1:19AM
   Tabctl32.ocx            2/25/98  1:19AM
Development Environments:

In addition to replacing the controls, the Installer also provides appropriate .dep files on computers that have Visual Basic installed. These files are used when creating a Setup.exe for applications.

Previously Deployed Applications:

If you have deployed applications that use any of the controls listed above, you must also ensure that your users receive the new versions of these files. To do that, you have the following two options:

Option 1

Redeploy Applications

There is no need to recompile applications, however, you must create a new setup and deployment package using the new files. The included .dep files ensure that the correct .ocx files are included with your setup package if you are using the Visual Basic setup toolkit to distribute your application.

Option 2

Distribute the Installer

You can redistribute the Installer to end users with instructions to run the Installer. The Installer places the correct files on the end users computer, allowing uninterrupted operation of deployed applications.
Modification Type:MinorLast Reviewed:12/17/2004
Keywords:kbbug kbfix KB181309
©2004 Microsoft Corporation. All rights reserved.