topic Re: 3.4.d to 4.0.d Upgrade Woes with LDAP... in Alfresco Archive

3.4.d to 4.0.d Upgrade Woes with LDAP...

zanity84 — Thu, 16 Aug 2012 18:00:49 GMT

Hello everybody!I have been adamantly searching this knowledge base as well as other sites looking for the methodology of upgrading from 3.4.d to 4.0.d that will work in our system. I've followed this post https://forums.alfresco.com/en/viewtopic.php?f=8&t=45911, with some slight tweaks of what

Re: 3.4.d to 4.0.d Upgrade Woes with LDAP...

jpotts — Thu, 16 Aug 2012 23:04:48 GMT

LDAP is just for authentication (and, optionally, syncing users and groups) so you should definitely be able to move your database and content store over, validate that everything came over okay, and then get LDAP working.

Jeff

Re: 3.4.d to 4.0.d Upgrade Woes with LDAP...

zanity84 — Fri, 17 Aug 2012 03:17:11 GMT

Thank you for the response,

I kind of figured that this was the case, but I'm glad it's confirmed. I guess my problem lies in the migration in general. I'm looking the logs, and the only one that I think is causing problems when trying to log in is "unable to retrieve license from server 404" error alfresco.log. I'm not sure what's causing this error; I tried disabling the firewall temporarily to see if it was that type of issue, but I received the same error regardless.

When opening a browser after restarting the Alfresco service, the login screen automatically generates the error "The remote server may be unavailable or your authentication details have not been recognized" before even trying to log in. I'm thinking this might be why it's not indexing. Thanks!

Re: 3.4.d to 4.0.d Upgrade Woes with LDAP...

jpotts — Fri, 17 Aug 2012 15:19:36 GMT

Can you try logging in to /alfresco instead of /share, just to verify that the repository is okay? Also, please check the alfresco log for any messages and include those here within

‍

tags.

Last, I think if you followed the directions in that other blog post you've probably already done this, but just to make sure, make sure you've disabled Solr and are using Lucene instead. After the migration you can switch to Solr if you'd like. When you do, you'll need to address the expired SSL cert problem.

Jeff

Re: 3.4.d to 4.0.d Upgrade Woes with LDAP...

zanity84 — Fri, 17 Aug 2012 19:19:36 GMT

Thank you,

Indeed, I had commented out the solr configuration part and made sure Lucene was put in the properties file. As I was working today, I noticed what may be causing my problems. I'll have you guys confirm this, but I noticed that the requirements of Alfresco 4.0 included having Mysql 5.5 installed. I've been using 5.1.61 from installing via "yum install mysql-server." Is it possible that I am having compatibility issues with Alfresco being able to contact the mysql databse because of the different versions?

Re: 3.4.d to 4.0.d Upgrade Woes with LDAP...

zanity84 — Fri, 17 Aug 2012 20:46:51 GMT

Hello again,

I was able to update to mysql 5.5 and import, but I'm encountering the same error. I tried logging into the /alfresco site, but it gives me a 404 error "the requested resource is not available." I have the mysql connector in the tomcat/lib folder. I'm not sure what else to do at this point.

Re: 3.4.d to 4.0.d Upgrade Woes with LDAP...

jpotts — Mon, 20 Aug 2012 20:10:46 GMT

Seeing a 404 error on /alfresco most likely means there was an error of some sort when the repository tried to start up. Can you check $TOMCAT_HOME/logs/catalina.out for any exceptions or other error messages that might be in there?

Jeff