Error after attempted 8.3 to 8.4 planning upgradde

[goldsmt]

Hi All



Attempting to upgrade planning from 8.3 to 8.4 on the same Server. Windows 2003 SP2 and SQL Server 2005. Exported the cogstartup.xml file, uninstalled 8.3 and installed 8.4. Copied back the cogstartup.xml file, opened Cognos configuration and tested each component sucessfully. Then attempted to start the Planning Server and get the following message.



"Successfully launched a test JVM with the memory setting of '768'. Note that this does not guarantee that IBM Cognos 8 will start and run successfully. To see which JVM options are based on this setting, view c8_location/bin/bootstrap_<OS>.xml and see your JVM documentation for an explanation of those options.
Since the value is empty, the feature is disabled. There is nothing to test."



Lots of references to the message on the web but no solution. IIS version was 6.5 and as stated all ran well under 8.3, no changes to the content store location, users, passwords etc



thanks in advance



Tony

[ericlfg]

Hi Goldmst,

This message is just a warning, it's not an error.  This message may indicate that a global setting for the "Archive Location File System Root" is blank (Actions > Edit Global Configuration > General tab within Cognos Configuration). 

You may want to confirm with the previous version what the setting(s) were for the global items against your 8.3 environment if it's still available.  This message should not hinder services or prevent a successful start up.

[Rutulian]

Hi Tony,

Have you got any notes from your initial 8.3 install?  There will be a few other things to do than plain exporting the cogstartup - if you can, follow through all the config steps taken last time.

The first thing to check is going to Control Panel -> Administration Tools and setting the service user to be a domain account with access to everything it's going to need (as it's an upgrade you probably had this for your 8.3 service), that can often not give clean errors because the executing user can't even get messages back from the log service.