Palo Community Forum

Dear Palo Community,
as we are releasing the Palo 3.2 Community edition today, in addition to the What's new document, please have a look at the following notes for this release:

- for Updates of existing installations, we recommend uninstalling the old versions, then installing the new version into a fresh directory and afterwards migrating your databases and, for Palo Web, storage directories. As the System database has a partially changed structure,, we recommend using the new System database and migrating your existing Users / groups etc. "manually" (.e.g. via ETL)
- one of the new properties in the System DB is the "inactive" property for users groups and roles. While this property is needed internally for Palo Web, chaning the setting for a given User / Group / Role will NOT disable this user (this is only available in the Premium Edition)
- when installing Palo Web, the link in the Windows Start Menu will always point to the adress "http://localhost:8081", but you can manually edit the link
- when installing Palo for Excel, if you chose to leave the OLAP interface empty (=bind to all interfaces), the created default connection in the Excel-Addin will not work (it will not set a host adress). You can edit the connection via the Modeller.
- by default, Palo Web uses a Palo user called "_internal_suite" with the same password to connect to the OLAP server. We recommend changing this user's password, then adapting the necessary config files (palo_config.xml, config.php)
- there will not be a "Palo"-Ribbon in Excel version 2007 and 2010; you will find the Palo menu in the "Addins" ribbon
- the 64bit versions are "Premium only" and not included in the Open Source version. You can use the source code from SF.net to compile 64bit bianries.

Hi,

1) the "file doesn't exist" error means Palo Web can't locate the specific file you're trying to open. I see two possible causes, depending on wether or not you migrated the "storage" directory from your old installation:
a) storage directory was migrated. In this case I'd assume the reason is that the old installation had a different install path than the new one. The storage path is saved in the fgrp databases (which you migrated, I reckon) and thus, Palo Web still looks at the old place. What you can do:
- Move the storage directory to the old location (if necessary, create parent directories)
- try to open files
- if it works, you can again migrate storage to the new location (or some other) by changing the Properties of "root folders" in Palo Web Studio. (Note: changing path in those properties will only work if the currently set path is actually correct)

b) storage directory was not migrated. In this case:
- migrate storage to new installation.

Of course you could have c), being combination of a) and b)

2) the #NV errors in Excel probably mean that something with Excel Addin installation didn't work correctly. You can check wether the log file (PaloXLAddin.log) contains errors.

As for different migration method: you could try to write e.g. a php-script that creates new properties in the System database itself (this would mean the ste_...rights objects, and the "inactive" property for users / groups, and roles). This script would basically modify your existing System DB to work with the new version.

By the way: the setup guide only concerns the Update of older versions to the 3.2 Premium version, not the Community Version.