Problem after update LogicalDOC CE 6.1 -> 6.3.5

Problems with installing LogicalDOC? No problems, the solution is closer than you think.

Moderator: car031

louie
Posts: 3
Joined: Wed Mar 07, 2012 6:20 pm

Problem after update LogicalDOC CE 6.1 -> 6.3.5

Thu Mar 08, 2012 9:59 am

Hi!

I have problems updating LogicalDoc from version 6.1 to 6.3.5. I installed the new version into the appcontainer and updated the context.properties.

But I cannot login after the update. I'll get a "Acess denied".

Has the DB changed in this version?
The log files gives me following exception:

Code: Select all

07.03.2012 11:36:48,299 WARN   (com.logicaldoc.web.service.SecurityServiceImpl: 183) -- User cschnei is not valid
07.03.2012 11:37:31,954 WARN   (org.hibernate.util.JDBCExceptionReporter: 100) -- SQL Error: 1054, SQLState: 42S22
07.03.2012 11:37:31,955 ERROR  (org.hibernate.util.JDBCExceptionReporter: 101) -- Unknown column 'attributes0_.ld_editor' in 'field list'
07.03.2012 11:37:31,956 ERROR  (com.logicaldoc.core.security.dao.HibernateUserDAO:  90) -- could not initialize a collection: [com.logicaldoc.core.security.Group.attributes#6]; SQL [select attributes0_.ld_groupid as ld1_0_, attributes0_.ld_label as ld2_0_, attributes0_.ld_mandatory as ld3_0_, attributes0_.ld_type as ld4_0_, attributes0_.ld_editor as ld5_0_, attributes0_.ld_position as ld6_0_, attributes0_.ld_stringvalue as ld7_0_, attributes0_.ld_intvalue as ld8_0_, attributes0_.ld_doublevalue as ld9_0_, attributes0_.ld_datevalue as ld10_0_, attributes0_.ld_name as ld11_0_ from ld_group_ext attributes0_ where attributes0_.ld_groupid=? order by attributes0_.ld_position asc]; nested exception is org.hibernate.exception.SQLGrammarException: could not initialize a collection: [com.logicaldoc.core.security.Group.attributes#6]
org.springframework.dao.InvalidDataAccessResourceUsageException: could not initialize a collection: [com.logicaldoc.core.security.Group.attributes#6]; SQL [select attributes0_.ld_groupid as ld1_0_, attributes0_.ld_label as ld2_0_, attributes0_.ld_mandatory as ld3_0_, attributes0_.ld_type as ld4_0_, attributes0_.ld_editor as ld5_0_, attributes0_.ld_position as ld6_0_, attributes0_.ld_stringvalue as ld7_0_, attributes0_.ld_intvalue as ld8_0_, attributes0_.ld_doublevalue as ld9_0_, attributes0_.ld_datevalue as ld10_0_, attributes0_.ld_name as ld11_0_ from ld_group_ext attributes0_ where attributes0_.ld_groupid=? order by attributes0_.ld_position asc]; nested exception is org.hibernate.exception.SQLGrammarException: could not initialize a collection: [com.logicaldoc.core.security.Group.attributes#6]
	at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:629)
	at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:412)
	at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:411)


	......
Anyone an idea?

thanks!
numer
Posts: 11
Joined: Fri Oct 21, 2011 8:32 am

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Sat Mar 24, 2012 2:05 pm

I'm facing the same problem. Users can not login.

Is there at least a way getting my documents without loggin to logicaldoc. Maybe from the shell, or the database? Is there a script that can backup the data onto a usb or similar.

This is really annoying.
mmeschieri
Posts: 242
Joined: Mon Apr 19, 2010 3:40 pm

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Sat Mar 24, 2012 2:42 pm

The database schema changed a lot since the 6.1, that's why you have the problem
numer
Posts: 11
Joined: Fri Oct 21, 2011 8:32 am

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Sat Mar 24, 2012 7:07 pm

I will be so happy when I get rid of LogicalDoc
mmeschieri
Posts: 242
Joined: Mon Apr 19, 2010 3:40 pm

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Mon Mar 26, 2012 9:47 am

Each production-ready solution, like LogicalDOC, requires database changes from one release to another. This is due to new implemented features, and here we are working hard to implement the new feature requests coming from our huge users base.

If you want to get rid of LogicalDOC this is a possible procedure:
  • Restore your 6.1 application
  • Startup your Tomcat
  • Enter the application and browse the folders to export the contents using the zip-export feature
At the end you will have all your documents outside of LogicalDOC already organized in your folders tree. Now you are ready to import your data to another product that fits better your needs.
louie
Posts: 3
Joined: Wed Mar 07, 2012 6:20 pm

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Tue Mar 27, 2012 7:33 am

It there a way to update the database schema between the versions?
I have a big and well organized document database and just want to update to a new version of LogicalDOC without losing all my content.
mmeschieri
Posts: 242
Joined: Mon Apr 19, 2010 3:40 pm

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Tue Mar 27, 2012 8:16 am

Louie, the update packages that automates the upgrade of a release are available on the commercial editions only.

In any case feel free to ask the support team to provide you the database script to upgrade your 6.1 into 6.3.5, by writing an email to support@logicaldoc.com.
Please use your corporate email if you want to have more chances.
numer
Posts: 11
Joined: Fri Oct 21, 2011 8:32 am

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Fri Mar 30, 2012 4:35 pm

I did not do any upgrades. I use 6.3.1 and I had to reboot. The result was, that logicaldoc does not accept any user anymore.

The dms.log gives this entry any time I try to login with any user:
30.03.2012 17:33:27,913 WARN (com.logicaldoc.web.service.SecurityServiceImpl: 183) -- User admin is not valid

I can't export my data. This is really the only mechanism I want logicaldoc to be able to do. Give my data back, nothing else.
agaspa
Posts: 709
Joined: Tue Apr 20, 2010 8:24 am

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Sat Mar 31, 2012 8:17 am

The best solution for me would be that you reinstall an old logicaldoc CE 6.1.
During the installation you must specify the same database connection and the same working folder of your pre-existent LD 6.1 installation.
After the installation of LD CE 6.1 you must clean completely the cache of your browser and you should be able to login again into LogicalDOC.
To this point you can proceed with the export of your documents requesting the ZIP archive of the various folders
Rabbit80
Posts: 29
Joined: Mon Oct 04, 2010 3:18 pm

Re: Problem after update LogicalDOC CE 6.1 -> 6.3.5

Tue Apr 03, 2012 4:15 pm

I have sorted this out for myself.. I added the following code to the upgrade.sql in the 6.0-6.1 upgrade package.

Can't guarantee it is perfect, but seems to work for me!

Code: Select all


alter table ld_bookmark add column ld_type int not null default 0;

alter table ld_document add column ld_comment VARCHAR(1000);
alter table ld_document add column ld_workflowstatus VARCHAR(1000);
alter table ld_document add column ld_published int not null default 1;
alter table ld_document add column ld_startpublishing timestamp default '2011-04-04 00:00:00';
alter table ld_document add column ld_stoppublishing timestamp default '2011-04-04 00:00:00';

alter table ld_document_ext add column ld_editor int not null default 0;

alter table ld_folder add column ld_templateid bigint;

alter table ld_generic_ext add column ld_editor int not null default 0;

alter table ld_group_ext add column ld_editor int not null default 0;

alter table ld_template add column ld_retentiondays int;

alter table ld_template_ext add column ld_editor int not null default 0;

alter table ld_user add column ld_welcomescreen int;

alter table ld_version add column ld_workflowstatus VARCHAR(1000);
alter table ld_version add column ld_published int not null default 1;
alter table ld_version add column ld_startpublishing timestamp default '2011-04-04 00:00:00';
alter table ld_version add column ld_stoppublishing timestamp default '2011-04-04 00:00:00';

alter table ld_version_ext add column ld_editor int not null default 0;
This can be applied to your database and all should work. If you have login problems, clear your browser cache.

Return to “Installation”

Who is online

Users browsing this forum: Google [Bot] and 1 guest