It looks like you're new here. If you want to get involved, click one of these buttons!
I am getting 500 internal server error when i access the tao test from moodle instance.
I integrated the tao and moodle. created the test also. But when i access the test as a test taker from moodle i am getting the error.
Can you provide more information such as the error from the logs and the version of Tao?
Hi Amy, Thanks for the response. I am using TAO 3.2.0 and Moodle 3.6.
I have integrated tao as an activity in Moodle. I could see the test name and number of executions correctly as a Moodle admin. But when i try to launch the test as a student i am getting "500 - Internal server error". Which is not logged in both Moodle and TAO logs.
You may wish to set the system to debug by updating config/generis.conf.php. No restart will be needed and that may provide you with more information.
That really helps. I am getting following error in debug mode.
SQLSTATE: Integrity constraint violation: 1062 Duplicate entry 'http://localhost:1234/taotest/taotest.rdf#i1552464430965124' for key 'PRIMARY'
So that means there's already a DB entry with the primary key you're trying to bring over. You might want to make a copy of the DB then remove the item and try again.
Yes in DB there is a duplicate. But removing the DB entry wont solve the issue right. Can you please let me know is there any known issue raised for this issue. Any work in progress. Thanks for the support.
Removing the entry would let you re-import without the conflict. There are currently no open issues but you may wish to try Tao 3.3, RC01 https://github.com/oat-sa/package-tao/releases/tag/v3.3-rc01
The first thing you need to know about an 500 Internal Server Error is that the error can only be resolved by fixes to the Web server software. It is not a client-side problem meaning that the problem is not with your browser, your computer, or your internet connection. This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 Internal Server Error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error. However, there are often ways to quickly get around the problem:
I was also getting 500 server error when i tried to access Moodle after deployment on my moodle hosting. I contacted the support and they told me i am trying to access the wrong url. Did you check that possibility?
I've read it