We have published Rise courses in Scorm 1.2. The packages have been tested and function in scorm cloud. However - an error message always returns stating that the LMS cannot locate the indexAPI.html file. The LMS is FIS (Regulatory University).
In reviewing discussion boards, this seems to be a very common error that users are not getting resolution for.
We have built a work around (inserting into 360) but would like to recommend that Articulate make Rise more LMS agnostic so workarounds are not needed.
I'm glad to hear the course worked correctly in SCORM Cloud, but we want it to work just as smoothly in your LMS, too!
Are you doing anything special to the LMS output file before uploading it to your LMS? Have you tried linking directly to the index.html file inside the scormcontent folder?
I submitted a support case. Essentially, there are two issues. The first is that the Rise manifest file packages/lists files incorrectly. It adds additional file paths that the LMS cannot navigate around. When we manually fix the manifest file by removing all the false path directories that existed in it, we can get around that error (even though I don't think we should have to). Now, we are getting the system cannot locate the indexAPI.html file. It looks for it in a pathway that doesn't exist either which leads me to believe there is another file path pointing error that I have to locate in the code. This really shouldn't be that hard. This product is disappointing from a deployment perspective.
If it's working correctly on SCORM Cloud, then the problem is likely coming from your LMS. I recommend reaching out to your service provider directly to see if they can help you find a solution.
In the meantime, if there's anything else I can do to help, please let me know!
4 Replies
Hi Jennifer!
I'm glad to hear the course worked correctly in SCORM Cloud, but we want it to work just as smoothly in your LMS, too!
Are you doing anything special to the LMS output file before uploading it to your LMS? Have you tried linking directly to the index.html file inside the scormcontent folder?
I submitted a support case. Essentially, there are two issues. The first is that the Rise manifest file packages/lists files incorrectly. It adds additional file paths that the LMS cannot navigate around. When we manually fix the manifest file by removing all the false path directories that existed in it, we can get around that error (even though I don't think we should have to). Now, we are getting the system cannot locate the indexAPI.html file. It looks for it in a pathway that doesn't exist either which leads me to believe there is another file path pointing error that I have to locate in the code. This really shouldn't be that hard. This product is disappointing from a deployment perspective.
I'm having similar issues. The package works just fine on SCORM Cloud, but our LMS keeps throwing the following error message:
It looks like it's combining the file paths somewhere (scormcontent and scormdriver). Thoughts?
Hi Mike,
If it's working correctly on SCORM Cloud, then the problem is likely coming from your LMS. I recommend reaching out to your service provider directly to see if they can help you find a solution.
In the meantime, if there's anything else I can do to help, please let me know!
This discussion is closed. You can start a new discussion or contact Articulate Support.