|
- I'm trying to run an application and I
keep getting a message that says I need a license to
use your product. What do I do?
If you
are trying to run an application and receive a
message that you are not licensed to use 'OLETools'
and must enter a serial number to activate, this is
a problem with the application and not our product.
This is a message you should never see.
We
produce tools for other software developers to use
in their products. This error is a result of them
not installing our product properly with their
product. There is absolutely nothing we can do
to fix or change it. The producer of the
software you are trying to run must make a
correction inside their installation program.
We can assist them in identifying the exact problem,
but unfortunately, we have no way of assisting you.
Please contact the application vendor and inform
them of the problem. This problem is known as
a 'Side-By-Side' issue.
"No", sending an
activation code will not help, it would then
immediately fail elsewhere. The licensing key
is not the problem - just a symptom.
-
I'm a software
developer using your tools. And an application of
ours use to work on the machine, and now it
doesn't. what do we have to do to make it run?
This usually happens when someother application
that also uses our tools is installed on the machine
and it uses an older version of our tools. More
than likely, you have both installed our tools into
the system/32 directory. This is a no-no. What is
happening is that the DLL's are colliding, this is
refered to on the MSDN as a 'side-by-side' issue, or
more commonly as 'DLL Hell'.
Quick and dirty
solution...Copy all the OCX files in the system/32
directory named "Mh*.OCX" to some other directory.
Delete them out of the system/32 directory. Then
reinstall your application. This will allow your
application to run, but will break the other
application in the process. This assumes the other
isn't also using other OCX's that you are using as
well. This is not limited to just Becubed controls,
but any third party tool supplier.
The more
permanant solution is to fix your installation
program to avoid thew collision, and isolate you
from getting stepped on again. I compiled all the
information needed from Microsoft's MSDN Library on
how to resolve this issue. You can download it here
SxS.ZIP.
-
I had to reinstall
your product on my machine, and now when I go to
build my project it says I'm using a trial version.
Our tools cannot be "copied" onto the
development machine, they must be installed using
our setup program. The setup will hash a key and
store it in the registry. The key is based on your
login user name, and drive 'C' serial number. If
either changes, the key will no longer match, and
the product must be re-installed to regenerate the
key.
In some cases, the regeneration fails to
overwrite the registry key. In this case you can
delete the key, then reinstall. the key is located
at ...
HKEY_CURRENT_USER\Software\Becubed software\{product
name}
Delete this key, then reiinstall using your
provided serial number that your received when you
purchased the developers license.
|
|
|
|
|
|
