Komodo probs with Vista

Posted by nexo on 2009-04-19 08:02
Forums: Komodo support | OS: Windows Vista

Neither Komodo Personal 3.5 nor Komodo Edit 5.11 work on my Vista platform. Both versions install withour problems. After program launch, I get this error message:

"Komodo was unable to open file: startpage.xml#vie-startpage".

and then:

----------------------------
"Error activating Code Intelligence backend: CantOpenError: unable to open database file

Komodo personal, version 3.5.3, build 262321.
Built on Wed May 03 11:40:26 2006." (and a respective message with Komodo Edit 5.11)
-----------------------------

After an attempt to load a Perl script, I get this error message:

"Error activating Code Intelligence backend: CantOpenError: unable to open database file"

I tried to install and uninstall both versions several times. I even performed a system recovery to the point before the first attempt to install Komodo. Nothing helped. Any idea?

Thank you, Nexo

toddw
ActiveState Staff
Sun, 2009-04-19 09:16

You'll need to be using Komodo 5, as Komodo 3 does not support Vista.

I have not seen these type of errors before, is your user profile stored on a networked/external drive?

Check the Komodo log files at:
http://community.activestate.com/faq/komodo-file-locations#log_files

Cheers,
Todd

nexo | Mon, 2009-04-20 02:58

I have the same problems with Komodo 5.11. My user profiles (do you mean Windows or Komodo?) are both stored locally on the same machine where KomodoEdit is installed.

In version 5.11, I do not get error messages, but no file will open, not even a new file. In Properties, I find an empty API catalogs list under "Code Intelligence". When trying to add an API catalog for Perl, it seems that there are no catalogs included.

Any idea?

toddw
ActiveState Staff
Mon, 2009-04-20 10:15

There seems to be something corrupt with the either the Komodo installation or the Komodo profiles.

Try renaming all of the existing Komodo profile directories, these are directories named Komodo, KomodoEdit and KomodoIDE. The directory locations are described here:
http://community.activestate.com/faq/komodo-file-locations#appdata_dir

This will force Komodo to create a new profile.

Does that help solve the Komodo catalogs problem?

If not, try uninstalling Komodo 5.1.1, then re-install Komodo 5.1.1.

Cheers,
Todd

rpsantoro | Sun, 2009-04-26 17:49

I am running Windows Vista 64 (Ultimate) SP1 with all updates and have experienced similar behavior with Komodo 4.4.1 which ran without a problem about a month ago. When I tried to run it a couple of days ago, I got the following two error messages:

error creating “:No such file or directory

and then

could not determine the host user data dir

followed by termination.

I upgraded to Komodo 5.1.1 with the same exact behavior and note that the directory

C:\Users\user\AppData\Roaming\ActiveState\KomodoIDE\5.5

is NOT created.

I have made no changes to the machine in the past month except for the Windows updates – is it possible that one or more of these updates is the culprit?

toddw
ActiveState Staff
Mon, 2009-04-27 10:04

It is hard to be sure on what is causing this error, but you could try the following:

  • Directory permissions
    Check that your able to write to the folder:
    C:\Users\user\AppData\Roaming\ActiveState\KomodoIDE\
  • Environment variables
    Check your environment variables to ensure everything is correct, such as USERNAME, USERPROFILE, HOME, etc...
  • KOMODO_USERDATADIR
    Try setting the KOMODO_USERDATADIR environment variable in a Windows command prompt, then starting Komodo from the command line:
    set KOMODO_USERDATADIR=C:\komodo
    "C:\Program Files\ActiveState Komodo IDE 5\komodo.exe"

    see note 2 at:
    http://community.activestate.com/faq/komodo-file-locations#pref_reset

Any of that help?

Cheers,
Todd

rpsantoro | Tue, 2009-04-28 02:32

It did help, indeed.

There was no KOMODO_USERDATADIR environment variable which, when created,
and set to the default path,
C:\Users\<user>\AppData\Roaming\ActiveState\KomodoIDE\,
cured the problem.

I don't recall having to set this environment variable to the default path in the past and don't know what has happened to make it necessary now.

Anyway, my sincere thanks for the suggestion.

crliinc | Sun, 2009-04-26 20:33

I am running Windows Vista 64 SP1 with all updates and have experienced no problems. Thanks

Rodolfo Vargas
Costa Rica land Investments Inc.
Investment Consultant
rodolfo@crliinc.com
www.crliinc.com