Unattended Installation


How do I get the installer for Community Edition to run in a silent, unattended mode?


See the Installation guide for the product in question.

Documentation on unattended installation is limited in scope because the functionality is limited. There are many outcomes which might be desired that the command line for the exe installer cannot support.

Unattended installation under the Community Edition license is Strongly Discouraged.
A requirement for unattended installations is associated with use cases that are Beyond Development, or are OEM Redistribution.
- Commercial entities must have a senior license for use Beyond Development.
- All cases of Redistribution must have a senior license.
Without the opportunity to review the terms of the Community Edition license, an end-user will be liable for complying with the license without being aware of the terms.

For ActivePerl, Legacy Build or Enterprise Edition versions can provide an MSI style installer with more extensive support for unattended installations.

Komodo License not Working


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:

Trial Issues:

  • A. Download a new Komodo installer and reinstall Komodo
  • C. Contact and tell them you're trial license won't start and they should be able to help.

License Installed but not Used:

  • A. Download a new Komodo installer and reinstall Komodo
  • C. Do the same as the last step but also download your license installer again from
  • D. Contact and tell them you're license won't work and they should be able to help.

- If you already have a previous Komodo license you are STILL ENTITLED to a Komodo trial of whatever the new version is.

Extending Komodo IDE trial


How do I extend my Komodo IDE trial license?


To extend your Komodo trial license past the initial 21 days, please contact

Can't create license file on OS X


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 is my ActiveState license file installed?


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: C:\Users\<username>\AppData\Roaming\ActiveState\ActiveState.lic
Windows XP: C:\Documents and Settings\<username>\Application Data\ActiveState\ActiveState.lic
Mac OS X: ~/Library/Application Support/ActiveState/ActiveState.lic
Linux: ~/.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.

Installing licenses for multiple users on networked machines


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?


What is the license for the code in the language cookbooks? Can the code be used in commercial projects?


The recipes in the language cookbooks are licensed under the BSD license, without the attribution clause (a.k.a. the "New BSD license").

This means that the code can be used in commercial and open source projects, including projects licensed under the GNU GPL (General Public License).

Komodo Invalid License error


I get an 'Invalid License' error message when starting Komodo. Why?


Ensure that the version of Komodo you have downloaded and installed matches the license you have purchased (i.e. Komodo Personal vs. Komodo Pro -- the licenses are not interchangable).

You can check the version of the the installed ActiveState license here:

Windows XP:

%USERPROFILE%\Application Data\ActiveState\ActiveState.lic

Windows 7:




Look for the line that says "Komodo". Immediately following the version number will be either Personal or Professional. Whichever it is is the version of Komodo you should install. If you have the appropriate license installed, try removing the license file (specified above) and reinstalling the license.

Installers for all versions of Komodo (including older releases) can be downloaded from: