topic Upgrading as releases become available in Alfresco Archive

Upgrading as releases become available

bd — Mon, 17 Oct 2005 00:57:12 GMT

I am finding difficulty in locating specific details about what actions to take when applying a later release (for example from 0.6 to 1.0).My reading of the release notes indicates that I must clear the old WAR file and related folders for the new files to be installed. Itherwise the Tomcat packag

Re: Upgrading as releases become available

gavinc — Mon, 17 Oct 2005 08:44:06 GMT

Yes, currently when moving between releases it is recommended that you delete the alfresco directory before unpacking the newer release. Obviously we will have an upgrade procedure for future releases.

If you have done this, did you reset the database? can you connect to the database?

Also the alfresco.log file in Tomcat's bin directory may contain some useful info, do you see anything in there or on the Tomcat console itself?

Re: Upgrading as releases become available

bd — Mon, 17 Oct 2005 22:41:33 GMT

Perhaps this information from my log file after the installation of version 1 gives a clue:

10:11:29,596 ERROR [org.alfresco.repo.content.transform.magick.AbstractImageMagickContentTransformer] ImageMagickContentTransformer not available: Failed to execute command: imconvert "C:\alfresco\tomcat\temp\Alfresco\ImageMagickContentTransformer_init_source_63108.gif" "C:\alfresco\tomcat\temp\Alfresco\ImageMagickContentTransformer_init_target_63109.png"
10:11:35,128 ERROR [org.alfresco.smb.protocol] CIFS server configuration error, null java.lang.NullPointerException

-And then a long list of 'at' statements, then-

10:12:52,070 ERROR [org.alfresco.web.app.ContextListener] Failed to initialise java.lang.NullPointerException

- And then more at statements, etc

Any ideas? or more info needed?

Re: Upgrading as releases become available

paulhh — Tue, 18 Oct 2005 07:30:38 GMT

Hi

Did you remove and recreate the Alfresco database and content? If not, that is the problem. There have been schema changes and we have only just said that from RC1 the schema will be fixed for some time. There isn't any easy way to migrate the data - apart from say FTPing it from an old server to a temporary area and then FTPing that back into an RC1 server. Of course, any additional metadata will be lost, as will rules. On Windows there is the db_remove.bat script that cleans the database and indexes, and db_setup.bat that recreates the database ready for use.

Cheers
Paul.