I am trying to run an .ocx library for a VB6 project that I have. However, every time that it calls the first object property, it generates the error below:
Line 937: Property OleObjectBlob in ICImagingControl1 could not be set.
Line 937: Cannot load control ICImagingControl1; license not found.
Some forums mention that the cause is using an old VB6 version, or a missing file FM20ENU.DLL in System32 (my case SYSWOW64). I already upgraded too the latest VB6 version (which is still quite old) and made sure the file was in the right folder. Neither of them worked for me, any ideas why is this issue happening?
Thanks
I installed and uninstalled several times the software, which created a reference to the wrong ocx in the registry. To solve this, I uninstalled IC Imaging Control, proceeded to erase the references in the tree, and reinstalled the proper version.
I was asked by a client of mine to edit an old vb6 project and ran in the same problem.
Googled for a solution until I found this:
https://jeffpar.github.io/kbarchive/kb/195/Q195353/
Downloaded and executed the program and the project could be perfectly edited.
Original text of this Microsoft article:
Q195353: FILE: VBUSC.EXE Provides Licensing for Discontinued Controls
Article: Q195353
Product(s): Microsoft Visual Basic for Windows
Version(s): 6.0
Operating System(s):
Keyword(s): kbfile kbusage kbCtrl kbLicensing kbVBp kbVBp500 kbVBp600 kbGrpDSVB kbFAQ kbVBp600FAQ k
Last Modified: 21-JUN-2002
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows, version 6.0
- Microsoft Visual Basic Professional Edition for Windows, version 6.0
- Microsoft Visual Basic Enterprise Edition for Windows, version 6.0
-------------------------------------------------------------------------------
SUMMARY
=======
VBUSC.EXE is a file that installs the Design-Time Licenses for ActiveX controls
that shipped with earlier versions of Visual Basic, but are no longer supported
and have been discontinued with the current version.
MORE INFORMATION
================
The following file is available for download from the Microsoft Download
Center:
VBUSC.exe
(http://download.microsoft.com/download/VB60Pro/Install/2/Win98/En-US/VBUSC.exe)
Release Date: August 15, 2000
For additional information about how to download Microsoft Support files, click
the following article number to view the article in the Microsoft Knowledge
Base:
Q119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current
virus-detection software that was available on the date that the file was
posted. The file is stored on secure servers that prevent any unauthorized
changes to the file.
FileName Size
---------------------------------------------------------
VBUSC.EXE 88k
The following controls are no longer supported by Microsoft Visual Basic:
ActiveX Control Name Filename
------------------------------------------------
Desaware Animated Button Control ANIBTN32.OCX
Microhelp Gauge Control GAUGE32.OCX
Pinnacle-BPS Graph Control GRAPH32.EXE
Microsoft Grid Control GRID32.OCX
Microhelp Key State Control KEYSTA32.OCX
Microsoft Outline Control MSOUTL32.OCX
Outrider SpinButton Control SPIN32.OCX
Sheridan 3D Controls THREED32.OCX
The ActiveX controls listed above are no longer supported, but ship with the
Professional and Enterprise Editions of Microsoft Visual Basic for backward
compatibility when upgrading existing projects.
These controls do not ship with the Learning Edition of Microsoft Visual Basic.
For the Professional and Enterprise Editions, the controls are located on the
installation CDs at the following locations:
Microsoft Visual Basic Edition Location
----------------------------------------------------------------------
Professional 6.0 \Common\Tools\VB\Controls
Enterprise 6.0 \Common\Tools\VB\Controls
Visual Studio Professional 6.0 \Common\Tools\VB\Controls (CD2)
Visual Studio Enterprise 6.0 \Common\Tools\VB\Controls (CD3)
Each of these directories contain a README.TXT with instructions on how to
install the controls for design-time use.
NOTE: Using the Learning Edition to upgrade a project developed in an earlier
version of Microsoft Visual Basic might result in licensing problems for these
controls.
The VBUSC.EXE installs the design-time licenses for the controls listed above if
Visual Basic is detected on the computer.
REFERENCES
==========
For additional information, please see the following articles in the Microsoft
Knowledge Base:
Q194784 INFO: Controls Shipped in Visual Basic 6.0
Q172193 INFO: List of VB 4.0 Custom Controls Discontinued in VB 5.0
Related
I cannot install the above mentioned package, which is requied to proceed the Visual Studio install. I checked on Microsoft's forums for solution but no luck.
I unchecked read-only checkbox in the root of the directory, also manually recreated x64 and x86 folders. The permissions on the users are as they should be also the cleaner app didn't help. I am using the 1809 Windows edition. The current VS version is 15.9.4.
The log is the following:
Something went wrong with the install.
You can troubleshoot the package failures by:
1. Search for solutions using the search URL below for each package failure
2. Modify your selections for the affected workloads or components and then retry the installation
3. Remove the product from your machine and then install again
If the issue has already been reported on the Developer Community, you can find solutions or workarounds there. If the issue has not been reported, we encourage you to create a new issue so that other developers will be able to find solutions or workarounds. You can create a new issue from within the Visual Studio Installer in the upper-right hand corner using the "Provide feedback" button.
================================================================================
Package 'Microsoft.VisualStudio.Setup.Configuration,version=1.18.21.37008' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.Setup.Configuration;PackageAction=Install;ReturnCode=1317
Details
MSI: C:\TempTmp\Nova mapa\Microsoft.VisualStudio.Setup.Configuration,version=1.18.21.37008\Microsoft.VisualStudio.Setup.Configuration.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 ALLUSERS="1" MSIFASTINSTALL="7"
Return code: 1603
Return code details: Fatal error during installation.
Message Id: 1317
Message Details: An error occurred while attempting to create the directory: C:\ProgramData\Microsoft\VisualStudio\Setup
Log
C:\TempTmp\dd_setup_20181215215511_001_Microsoft.VisualStudio.Setup.Configuration.log
Impacted workloads
Game development with Unity (Microsoft.VisualStudio.Workload.ManagedGame,version=15.0.27005.2)
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.9.28307.102)
Visual Studio core editor (Microsoft.VisualStudio.Workload.CoreEditor,version=15.0.27205.0)
Impacted components
.NET Native (Microsoft.Component.NetFX.Native,version=15.0.26208.0)
.NET Native and .NET Standard (Microsoft.VisualStudio.ComponentGroup.UWP.NetCoreAndStandard,version=15.8.27906.1)
.NET Portable Library targeting pack (Microsoft.VisualStudio.Component.PortableLibrary,version=15.6.27309.0)
.NET profiling tools (Microsoft.VisualStudio.Component.DiagnosticTools,version=15.8.27729.1)
ASP.NET and web development (Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions,version=15.8.27825.0)
Blend for Visual Studio (Microsoft.ComponentGroup.Blend,version=15.6.27406.0)
C# and Visual Basic (Microsoft.VisualStudio.Component.Roslyn.LanguageServices,version=15.8.27729.1)
ClickOnce Publishing (Microsoft.Component.ClickOnce,version=15.8.27825.0)
Data sources and service references (Microsoft.VisualStudio.Component.VisualStudioData,version=15.6.27406.0)
Developer Analytics tools (Microsoft.VisualStudio.Component.AppInsights.Tools,version=15.8.27825.0)
Image and 3D model editors (Microsoft.VisualStudio.Component.Graphics,version=15.6.27406.0)
JavaScript and TypeScript language support (Microsoft.VisualStudio.Component.JavaScript.TypeScript,version=15.9.28125.51)
JavaScript diagnostics (Microsoft.VisualStudio.Component.JavaScript.Diagnostics,version=15.8.27729.1)
NuGet package manager (Microsoft.VisualStudio.Component.NuGet,version=15.9.28016.0)
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.9.28119.51)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.9.28307.102)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.9.28307.102)
Visual Studio core editor (Microsoft.VisualStudio.Component.CoreEditor,version=15.8.27729.1)
Visual Studio Tools for Unity (Microsoft.VisualStudio.Component.Unity,version=15.7.27617.1)
WebSocket4Net (Component.WebSocket,version=15.0.26606.0)
Update 1.1.2019
I contacted the Microsoft support over chat, but didn't get any further. I was told to try to install an earlier release. I ended up formatting my SSD and installing all the software all over. It luckily succeeded. I am providing a vslogs overview of the error, before the format.
I've just installed the April 2015 release of the Azure SDK. It is version 2.6 and previously I was on 2.5. Now one of my projects will not load. It is the shared project in a Windows Universal application.
When I right-click the project and choose 'reload' I get the pop-up error
The method or operation is not implemented
The output window gives more detail:
Things.Shared.shproj : error : The composition produced a single
composition error. The root cause is provided below. Review the
CompositionException.Errors property for more detailed information.
1) No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
RequiredTypeIdentity Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
Resulting in: Cannot set import
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")'
on part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
Resulting in: Cannot get export
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")'
from part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
The other parts to the Windows Universal app (the Windows 8.1 project and the Windows Phone 8.1 project) have two Azure NuGet packages installed: Windows Azure Mobile Services 1.3.2 and Windows Azure Storage 4.3.0. (N.B. Those two projects load without issue.)
This is not a show stopper for me since uninstalling the Azure SDK 2.6 removes the load failure. To uninstall I go via the Control Panel to 'uninstall or change a program' and then uninstall Microsoft Azure Tools for Microsoft Visual Studio 2013 - v2.6
I would like to know how to fix this without uninstalling the Azure SDK 4.6.
Over on the Azure Mobile Services forum Chuck Weininger has posted the following answer:
The [fixed] build of Azure SDK 2.6 is now available, but it may not have
propagated to all download servers yet.
You can run the Web Platform Installer and if you don’t have the new
build installed, it should allow you to install 2.6 again. But it
might not if you are accessing a download server that doesn’t have the
new bits yet. If WebPI doesn't allow you to install 2.6 again, then
wait a few hours and try again.
The build number for the version with the fixes is build
2.6.30508.1601. You can identify the build of the SDK from Control Panel -> Programs and Features -> Microsoft Azure Tools for Microsoft
Visual Studio 2013 – v 2.6. The Version column will display the build
number
I have followed Chuck's instructions and have the new build and the shared project now loads without issue.
We have been able to reproduce the issue, but don't have a workaround at this time. If you want to use the Universal App projects with VS 2013, you will have to uninstall Azure SDK for VS 2.6. The issue does not happen on VS 2015 RC if you would like to give that a try. We hope to have news soon about how we can get a fix for this issue on VS 2013.
Chuck Weininger, Dev Lead, Microsoft
https://social.msdn.microsoft.com/Forums/en-US/e8123821-dcb1-477f-a746-f6f016a724ea/cannot-load-shared-project-in-windows-universal-app-after-upgrading-to-azure-sdk-26?forum=azuremobile&prof=required#de621720-3afc-458c-ba85-f691be9e74c1
I have an old Visual Basic 6.0 Installation.
In the information window (? -> About MS VB...) the Version Number is shown:
Version 9782
VBA: Retail 6.0.9782
Forms3: 12.0.6604.100
Now my questions:
What does Forms3 mean?
And where can I find updates for it (does updates exist?)?
Many thanks in advance!
Daniel
PDF: Chapter 2 Visual Basic 6 and Visual Basic .NET: Differences
The forms package found in Visual Basic 6 is local to that environment.
You can use Visual Basic 6 forms only in Visual Basic 6. Microsoft has tried in
the past to create a single, standard forms package that could be shared across
multiple products such as Visual Basic, C++, and Office. The initiative, called
Forms3 (pronounced Forms Cubed), never realized this goal. Forms3 is alive
and well in Office but was never made fully compatible with the Visual Basic
forms package.
This is VB6:
Version 9782
VBA: Retail 6.0.9782
Forms3: 12.0.6604.100
But the 12.0 Forms3 is from Office 2003. VB6 is tightly bound to Office in many regards and can even use the FM20 Forms Designer if you enable it. This gives you the option to "Add Microsoft Forms 2.0 Form" as well as native VB forms, primarily for creating Office add-in DLLs.
Running the WindowsSdkVer.exe shipped with Platform SDK 7.1 does not work.
None of the .BAT files in VS 2005 get updated.
can anyone please tell me how to correct this?
Also, how do I verify that VS2005 is using Platform SDK 7.1?
There are several articles for this in MSDN but none of them for above configuration.
Also, none of them describe the concrete way / definate way of verifying this
You could try to manually set the include and lib paths of the VS environment under
Tools->Options->VC++ Directories
or something like that (it's been a while).
For verification, you can add the /showIncludes parameter to the additional compiler options of the project, and /verbose:lib to the additional linker options to double check that the correct headers/libraries are being used when compiling/linking the project.
IIRC there was some kind of incompatibility between one of the newer versions of the SDK (could have been version 7) and using VS2005, but I can't recall off hand what that was.
You can use below method for using Windows SDK 7.1 with Visual Studio 2005.
Configuring Visual Studio for Visual C++ Development with the Windows SDK
In the link , you can find the contents with
"To use the Windows SDK Configuration Tool in Visual Studio 2008".
Even though it has such title, you can use the same procedure also for VS2005.
Start the Windows SDK Configuration Tool by clicking Start, then All Programs, then Microsoft Windows SDK v7.1, and then Visual Studio Registration.
Right-click Windows SDK Configuration Tool and then click Run as
administrator.
In the Windows SDK Configuration Tool, in the list, select v7.1.
Click Make Current.
I've downloaded a Vista icon from the web for a new application I'm developing. When I try to compile it in Visual Studio 2005 C++, I get an error message:
error RC2176 : old DIB in res\XXXXX.ico; pass it through SDKPAINT
The error message seems a little misleading, I think the "old DIB" is actually a newer format that it wasn't expecting. I've never heard of SDKPAINT, and Search doesn't find it installed on my system anywhere. Microsoft claims SDKPAINT comes with the Windows 3.0 SDK, but I can't download any SDK due to incompatibilities with our firewall.
I don't really need anything Vista specific in this icon, so anything that would dump the incompatible bits would be fine.
I did a little more digging, and I found this previous question:
Which Icon Editing Software would you recommend for creating icons for apps
The accepted answer for that question suggested IcoFX. I downloaded that and used it to delete the 256x256 and 128x128 versions of the icon, and now everything's fine.
There are two more ways to achieve this in Visual Studio 2005:
replace rc.exe and rcdll.exe of your Visual Studio 2005 installation with the ones from a newer SDK (e.g. Windows Vista, 7 ...) or DDK/WDK (ditto)
or integrate the newer SDK into your Visual Studio 2005 using the respective tool that comes with the SDK
The resource compiler is the part that creates the .res files and then the usual Visual Studio 2005 linker (with the first option) or the SDK tool chain's liner links that into the binary. Meaning that even in conservative scenarios where it is frowned upon to upgrade the tool chain as a whole, this should be harmless.