Dear Sir/Madam,
I have installed Dspace1.5.1 on Redhat 9. When I tried to use
the option Feedback its displaying internal system error. Inspite of giving
all the details correctly in Mail settings in dspace.cfg, it's not working.
Kindly help me.
Thank You in advance.
Internal system error means, go look in the logs for your servlet
container (such as Tomcat) and see what the error is. If the
relevant log entries are unclear to you, please post them here.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles
Geetha,
Take a look at our How to Troubleshoot an Error page. It will help
you to look at your log files to tell what the real error is. The
internal server error message is just a generic error that says
something went wrong, so you'd need to look at the logs to see what the
real problem
An update on this issue, we had the suggested modification and it resolved
the issue. Users without an email specified in AD can auto login/register.
Anthony Avarca
aava...@anl.gov
630.252.4940
On Fri, May 7, 2010 at 1:09 PM, Avarca, Anthony aava...@anl.gov wrote:
We are seeing a similar
Hi
I've started emailing myself exceptions in the cocoon pipeline and
noticed cocoon exceptions when deleting items (see below). Is anyone
else seeing this in the cocoon log (there are no signs of any problem
from the user interface)?
I can't figure this out, so am working round it by
Dear DSpace Community,
Today we have launched a Sponsorship Program to help sustain the DuraSpace
organization. We have posted a press release (see a portion below) as well as
some informational resources on the duraspace.org website. We have also mailed
out 600 sponsorship packets to library
Ever since moving to 1.5 (and subsequently 1.6) I no longer receive emails when
dspace throws an internal error. My address is still configured in the
dspace.cfg.
Did this feature go away or do I need to do something to enable this?
Richard, Thank you very much for this documentation. I've been experimenting
with it today, and I just have few questions.
1.It seems like making the terms field a date type in the
input-forms.xml file would be the safest thing to do, instead of a textarea.
Any thoughts on this?
I think that launcher.xml should indicate what to run for embargo-lifter, but
there is no entry for it. Is this a bug in 1.6?
Thanks!
Jose
From: Blanco, Jose [mailto:blan...@umich.edu]
Sent: Thursday, May 20, 2010 3:56 PM
To: Richard Rodgers; Jizba, Richard
Cc:
Hello,
I updated a Collection description in one of our DSpace instances, a few
times this morning. Each time I noticed that it took awhile for the update to
complete. I finally looked in the log and saw errors referring to write.lock
in /dspace/search. I looked in the /dspace/search
No, it didn't go away. You should get an email when an internal error occurs.
Have you checked your server to make sure your emails are being released? We
had a situation recently where that happened.
Also, have you checked the dspace.log file(s) for any error messages that may
be occurring
It's a bug in 1.6.0. Will be fixed in 1.6.1.
Here's the page for the bug in Jira. The bugfix is there.
http://jira.dspace.org/jira/browse/DS-506
--Jason Fowler
From: Blanco, Jose [blan...@umich.edu]
Sent: Thursday, May 20, 2010 4:18 PM
To: Blanco, Jose;
Hi Jose:
Re #1. Date would be safe, but then you would not be able to enter the
'forever' (open ended) value, which is not a date. I would normally just use
'onebox' (smaller than a text-area).
Re #2. I'm not positive I understand the question, but the embargo does not
hide the metadata or
13 matches
Mail list logo
