Licensing error message with BeCubed 6
Boring introduction:
In my workplace, we have a very old WinForms product (on the market since 1994 and still running on VB3). It has three completely different versions, each going to one client. Clients pass them on to their users, some of which are shared. Versions can live side by side.
Five years ago, we rewrote one of these versions in C # .Net. Two years later another version was rewritten (call version M on it), and two years later it was time for the last remaining version (call version C on it) to be converted. We have been in production for one year and are going to production this week.
During the conversions, it was decided not to convert anything that was sold as an external module; they were built in VB6 and they used several controls from BeCubed and Farpoint . There are two such modules in version M and three modules in version C. Each module has its own MSI installer, which runs silently with the main product installer.
Mistake
During production, we found a bug: when version C is installed on a new computer, then version M is installed, we get a message as soon as the plug-in opens in version C:
After pressing the "OK" button, the module works. Also, this does not happen when they are installed in any other order, and both modules work fine in the M version.
Other information
- All OCX and DLL files are compared for all module settings; the files are identical.
- All modules work when only one version of M or C is installed, or when M is installed.
- We own licenses for all software we use, including BeCubed.
Does anyone know what might be causing such an error, what might be a possible solution?
source to share
Apparently one of the modules installed OCX in the system directory (by default C:\Windows\System
) and the others installed them in the program files directory ( C:\Program Files\CompanyName\Shared Files
). This probably leads to a conflict in OCX double registration or something. I have no idea what was wrong there, but when we changed one module to install in a folder Shared Files
like everyone else, the problem was fixed. I am writing this here, so if anyone has a similar problem, they can check that all files are installed in the same location.
source to share
Well, since nothing changes in the file, it is possible that something in the registry has changed.
But this looks like a problem that you should contact BeCubed, ask them how to enable extended logging or ask them for support.
Currently, there is not enough information to know what is really going on ...
source to share