Why won't Komodo allow me to do the 21 day trial? Or let me use my actual license?
If you're having trouble starting your Komodo trial or it won't pick up your freshly purchased and installed license, there are a few things you can try to work around the issue:
- If you already have a previous Komodo license you are STILL ENTITLED to a Komodo trial of whatever the new version is.
How do I extend my PDK trial license?
To extend your PDK trial license:
1. go to this link in your browser:
2. sign in to your ActiveState.com account (you may need to register if you have not previously)
3. download and install the new Trial license
How do I extend my Tcl Dev Kit (TDK) trial license?
Until the TDK 4 release, please extend your trial license by logging into your account at:
If you do not have your password, one can be requested by clicking on "Forgot your Password?" underneath the sign in prompt.
Once signed in, click on "Downloads" at the top right hand side of your screen.
Click on "Download Free Trial" beside the product you wish to try.
A download wizard will pop-up and take you through the download and installation steps.
How do I extend my Komodo IDE trial license?
To extend your Komodo trial license past the initial 21 days, please contact
When I start Komodo IDE 4.0.0 for the first time, I get a dialog that says 'Your license is incompatible with this version of Komodo', and an option to buy or upgrade. What is going on?
We have discovered a problem affecting some Trial users of Komodo 4.0.0 where they will not be able to start a 21-day trial on the first start of Komodo. This is now fixed in Komodo 4.0.1:
Why do I get the message "Can't create '/Users/myusername/Library/Application Support/ActiveState/ActiveState.lic"? What can I do about it?
Occasionally when you are installing a new ActiveState license or starting a trial or beta product that installs a temporary license you will get the following message:
Can't create '/Users/myusername/Library/Application Support/ActiveState/ActiveState.lic
This is due to the directory the license is being installed in being owned by another user or not having the appropriate permissions. The easiest way to fix this is from the Terminal, by typing the following two commands:
sudo chown -R myusername /Users/myusername/Library/Application\ Support/ActiveState
chmod 0755 /Users/myusername/Library/Application\ Support/ActiveState
You may have to enter your password after typing the first command. This is normal, and required because you are executing that command as root (which is needed to change the ownership of files not owned by the current user).
Where do I find my license file after I run the license installer?
Sometimes it's handy to be able to find your license file after you run the license installer. It can be helpful for debugging license issues and can make life easier when you start using your ActiveState product on another machine.
All directories below are shown relative to your home directory (found in the environment variable HOME on Linux and Mac OS X and in the environment variable USERPROFILE on Windows):
Windows XP: C:\Documents and Settings\<username>\Application Data\ActiveState\ActiveState.lic
Mac OS X: ~/Library/Application Support/ActiveState/ActiveState.lic
The Application Data directory is usually hidden under Windows, so you may have to set Explorer to show hidden files or simply "cd" to that directory in a command prompt.
We would like install your product so that it is accessible on all machines on our network for the users holding the license. We have already purchased the licenses. The license says it is good for one user (per license) on all platforms. What's the best way to go about this?
Licenses for ActiveState products are per-user licenses that are not specific to a machine or platform. If the same user has accounts on a Windows machine, a Linux box, and a Mac, they are free to install their license on all three machines. Similarly if the same user uses multiple accounts on any of the machines, they can install the same license on all of the accounts they use, provided the software is not used by unlicensed users.
When the license installer is run it installs a license file to a subdirectory of the user's home directory. This means that the license must be run as the user who will be using the software. For example, if I am going to use my kevinw account to run Komodo, I have to run the license installer as kevinw, rather than as root or another user. This also means that the license needs to be installed separately on each machine I am going to use, of course.
You can also copy the license files directly from machine to machine. For information on where to find your license file after you run the license installer (and where it should be installed on the machine you're copying it to), see the licensing FAQ entry entitled "Where is my ActiveState license file installed?".
We are looking into ways of making this more convenient, but for now that's the process.
What is the license for the code in the language cookbooks? Can the code be used in commercial projects?
Komodo Pro won't start after evaluating Komodo Personal. How can I fix
If you evaluated Komodo Personal edition prior to purchasing Komodo
Professional edition, you may encounter problems when you try to start
Komodo. This is a known issue when moving from Komodo Personal to
Professional. To get around this, you will need to delete your Komodo
preferences directory, located here:
C:\Documents and Settings\username\Application Data\ActiveState\Komodo\3.5\
Linux and Solaris:
Mac OS X:
If you have already customized Komodo or added to the toolbox, you
will need to back up some files first in the above directory. Copy out
the toolbox.kpf file to preserve your toolbox, and the
schemes sub-folder to preserve any key-binding or font coloring