[dspace-tech] You are not authorized to submit to any collections

[Umesh Kushwanshi]

I'm not able to do new submission

Help me, I have tried my best to resolve this issue.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

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

[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 
wrote:

> 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 Avino"  wrote:
>
> 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 pain.
>
> Thanks for your input!
>
> *Tom Avino *
>
> o: 757.864-8495 <(757)%20864-8495> | thomas.w.av...@nasa.gov
>
> f:  757.864-6649 | thomas.av...@saic.com
>
> On Wednesday, July 26, 2017 at 6:41:53 PM UTC-4, George Kozak wrote:
>
>> 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 in the
>> dspace home directory (even after I removed all of teh DSpace 6.0 stuff).
>>
>> In my case. I found that I had to drop the dspace database, and then
>> recreated it, and then added the data from the restored backup. I did the
>> same with the dspace home directory.  It may be that you already did all of
>> this, but that is what I found helped my problem.
>> George Kozak
>> Cornell University
>>
>> On Wed, Jul 26, 2017 at 2:01 PM, Tom Avino  wrote:
>>
>>> 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 however failed and could not find the issue, so I decided
 to start over.  I had done this a few times before on another Dspace
 instance.

 What I did then was

- restore my postgres database back to pre-upgrade
- changed dspace .bash_profile back to maven 2.2.1 from 3.3.9
- logged off dspace then logged on
- shut down Tomcat
- did a rebuild from my original dspace 3.3 src
- restarted tomcat

 This is the error I get.  The application just shows a blank screen,
 and the message below is from cocoon.

 2017-07-26 10:27:15,200 ERROR org.springframework.web.context.ContextLoader
  - Context initialization failed
 org.springframework.beans.factory.BeanCreationException: Error
 creating bean with name 'dspace.eventService' defined in ServletContext
 resource [/WEB-INF/spring/applicationContext.xml]: Instantiation of
 bean failed; nested exception is org.springframework.beans.fact
 ory.BeanDefinitionStoreException: Factory method [public
 org.dspace.services.EventService org.dspace.utils.DSpace.getEventService()]
 threw exception; nested exception is java.lang.IllegalStateException:
 DSpace kernel cannot be null
 at org.springframework.beans.factory.support.ConstructorResolve
 r.instantiateUsingFactoryMethod(ConstructorResolver.java:581)
 at org.springframework.beans.factory.support.AbstractAutowireCa
 pableBeanFactory.instantiateUsingFactoryMethod(AbstractAutow
 ireCapableBeanFactory.java:1015)
 at org.springframework.beans.factory.support.AbstractAutowireCa
 pableBeanFactory.createBeanInstance(AbstractAutowireCapableB
 eanFactory.java:911)
 at org.springframework.beans.factory.support.AbstractAutowireCa
 pableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFac
 tory.java:485)
 at org.springframework.beans.factory.support.AbstractAutowireCa
 pableBeanFactory.createBean(AbstractAutowireCapableBeanFacto
 ry.java:456)
 at org.springframework.beans.factory.support.AbstractBeanFactor
 y$1.getObject(AbstractBeanFactory.java:294)
 at org.springframework.beans.factory.support.DefaultSingletonBe
 anRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
 at org.springframework.beans.factory.support.AbstractBeanFactor
 y.doGetBean(AbstractBeanFactory.java:291)
 at org.springframework.beans.factory.support.AbstractBeanFactor
 y.getBean(AbstractBeanFactory.java:193)
 at org.springframework.beans.factory.support.DefaultListableBea
 nFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
 at