Hi Jayan, > The output messages are copied in. Could you please suggest how to proceed > with debugging the "internal error".
2 things: 1) Try to get the logging working. Make sure that E:\dspace\config\log4j.properties contains the correct location for for the log file (something like E:\dspace\logs) If this does not work, try: 2) Often you can find the problem with an internal error by looking at the source of the internal error page. Near the bottom there will either be a stack trace or an error saying no stack trace is available. Good luck, Stuart _________________________________________________________________ Datblygydd Cymwysiadau'r We Web Applications Developer Gwasanaethau Gwybodaeth Information Services Prifysgol Cymru Aberystwyth University of Wales Aberystwyth E-bost / E-mail: [EMAIL PROTECTED] Ffon / Tel: (01970) 622860 _________________________________________________________________ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech