Re: [dspace-tech] Re: Help getting back to dspace 3.3 after bad upgrade to 5.5

2017-07-28 Thread Tom Avino
Tom: Thank you everyone with helping me solve this problem. Once I cleaned out the directories, it solved most of my issues. I also discovered that I needed to remove the dspace/target/dspace-3.3-build directory. For some reason, older versions of some files remained and did not update during

Re: [dspace-tech] Re: Help getting back to dspace 3.3 after bad upgrade to 5.5

2017-07-27 Thread George Kozak
Tom: I concur with Hardy. It might be something in your dspace home directory. Renaming the existing one and creating a whole new one before you compile the source might fix the problem. George Kozak Cornell University On Wed, Jul 26, 2017 at 9:01 PM, Hardy Pottinger

Re: [dspace-tech] Re: Help getting back to dspace 3.3 after bad upgrade to 5.5

2017-07-26 Thread Hardy Pottinger
Tom, if you haven't cleaned out your DSpace dir (where you have the webapps deployed) you probably have old/cached config and lib folders. Easiest thing to do is move the old one out of the way, make a new DSpace directory, and deploy to the new directory with ant. On Jul 26, 2017 7:23 PM, "Tom

Re: [dspace-tech] Re: Help getting back to dspace 3.3 after bad upgrade to 5.5

2017-07-26 Thread Tom Avino
George, It does sound similar to my problem. I did drop the database and restore from a good 3.3. I also validated that my dspace.cfg file was the original one. I did complete rebuild using maven and ant. I get a 404 error when I try to bring up out website. This is getting to be a real

Re: [dspace-tech] Re: Help getting back to dspace 3.3 after bad upgrade to 5.5

2017-07-26 Thread George Kozak
Hi, Tom: I am not sure if this is the same problem as you are having, but I had a similar problem when I tried to back out of a DSpace 6.0 install to DSpace 5.5. I discovered that for some reason that I had some remnants from the DSpace 6.0 install left in the PostGres database and config files

[dspace-tech] Re: Help getting back to dspace 3.3 after bad upgrade to 5.5

2017-07-26 Thread Tom Avino
The errors listed below in cocoon, happen when Tomcat is started back up, not when trying to load the webpage. I hope this helps Tom On Wednesday, July 26, 2017 at 11:08:16 AM UTC-4, Tom Avino wrote: > > I have done a few of these upgrades from 3.3 to 5.5 without any issues. > This one