"500 Internal Server Error"

[nassima]

Hello,

I installed atom-1.3.2 on xamp , the installation has been successfully finished , but when i want add an entry after filling required informations i receive the following message: 

[Dan Gillean]

Hi there,

A couple of things first:

At this point, ICA-AtoM 1.x is no longer being developed or maintained - we strongly suggest you check out the 2.x version of the application. More information:

• Homepage: https://www.accesstomemory.org
• Version 2.2 installation instructions: https://www.accesstomemory.org/docs/2.2/admin-manual/installation/linux/
• Demo site: http://demo.accesstomemory.org
• Intro to AtoM 2.1 webinar recording: https://youtu.be/kkPYSuSK77k
  

Unfortunately, we at Artefactual do not test, or have much experience, with installing AtoM using XAMPP or WAMP, though we know it is possible. There are some older threads on our user forum that might be of use to you for configuration and troubleshooting - see:

• https://groups.google.com/d/msg/ica-atom-users/hOkzOu1Lu7g/81kcV-YLL6sJ
• https://groups.google.com/d/msg/ica-atom-users/vs4XdhS6I4w/gP5m-nhgUdAJ

XAMPP tends to be useful for a local install, but as I understand it, it is not generally designed to scale for use in production. If you are looking to test locally on a Windows machine, you might consider trying out our Vagrant box instead?

• https://www.accesstomemory.org/docs/2.3/admin-manual/installation/vagrant/

We also have a brand new series of tutorials that will help you install our Vagrant box, and teach you to use some of the command-line tools included in AtoM. See:

• https://www.youtube.com/playlist?list=PLZiwlG5eSMeyeETe15EsEBSu5htPLK-wm

Remember, the Vagrant box is not designed for use in production either! Like XAMPP, it is designed to create a local virtual environment for testing and development, not full-scale production-ready virtualization. If you are looking to use AtoM in production on a Windows based server, I think that there are probably other virtualization options that will be easier to configure, and will allow you to follow our recommended installation set-up.

Regarding your issue, the first thing I would do would be to try putting the application in Debug mode - this will allow you to see the full stack trace output of your 500 error, which can help us to determine what the issue is. To do so, first change your URL to include qubit_dev.php where it normally says index.php.

So for example, this URL:

• http://www.example.com/ica-atom/index.php/;informationobject/list

becomes:

• http://www.example.com/ica-atom/qubit_dev.php/;informationobject/list

Or, if your URL does not include the index.php, then you can insert the qubit_dev.php after the base URL.

In this case, this URL:

• http://www.example.com/;informationobject/list

becomes:

• http://www.example.com/dcb/qubit_dev.php/;informationobject/list

Please share with us the output of any stacktrace / full error message you get when in Debug mode and you repeat the actions that cause the 500 error. If there is anything useful in your webserver logs, share those as well.

Regards,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/d9bb5c34-41ed-4d88-a201-39e9af963e0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.