SCORM file errors

[Vijay5CA8]

When we play the SCORM file in Local, it generates warning errors but plays, the same file when we test this file on SCORM Cloud, we encounter no errors.

When we upload the same file in our application, it doesn't work though it works with other SCORM files.

What could be the issue here?

How can we fix this?

[Lilybiri]

If it works fine in SCORM Cloud, which is THE standard, the problem is with the LMS, not with Captivate.

[RodWard]

If the 'errors' you see when running the SCORM from your local hard drive are saying something about being 'Unable to find API' then that is just the SCORM telling you there is no LMS for it to talk to.  That would be perfectly normal.

What 'application' are you loading the SCORM into where it does not work?  If it is an LMS, which one?  What version of SCORM are you publishing to?  If you are publishing to SCORM 2004, have you tried using SCORM 1.2 instead?

[Vijay5CA8]

This is the error we get on the application:

An error has occurred:

Error - unable to acquire LMS API, content may not play properly and results may not be recorded.  Please contact technical support.

Press 'OK' to view debug information to send to technical support.

It is our custom built application and it runs other user's SCORM files without any issues except for this user's files.

We are using V1.2 and we have also tried playing the file after removing special characters from the file name, it still doesnt work.

Thanks for the support

[Lilybiri]

You can check if the Captivate course is correct by uploading it to SCORM Cloud, which is THE standard for SCORM compliance. If it works perfectly on SCORM Cloud, the problem is with your (custom) LMS...

[Vijay5CA8]

Yes, we understand that SCROM cloud is reference for SCORM compliance,and the file works with the cloud.

But our LMS doesnt have problem with any other user's files and the SCORM is generated using adobe captive for them too.

[Lilybiri]

There must be a difference with the other files, something which is not supported in your LMS: other interaction data maybe? 

[Vijay5CA8]

We noticed that we are getting this issue only when we enable the reporting,

Can this help us find a solution

[Lilybiri]

It is not a SCO if you do not set up Reporting. If you have Reporting on you need to upload to a LMS, you cannot test locally.

[Vijay5CA8]

Yes, understood that the error will comeup if we do it locally. It still comes up if we use the LMS ( as I said, other users do not face the issue)

What are the options we have to identify the root cause?

[RodWard]

If you create a new blank project with a couple of question slides and publish that to SCORM and upload do you get the same error message?  If so, the issue must be related to your Captivate installation.  If not, then the issue is with your problem CPTX.

Alternatively, as another test, send the same CPTX to one of the other Captivate users whose output seems to work fine on your LMS.  Ask them to publish a test output from their PC and upload that to your LMS for testing.

If they can successfully publish a SCORM that works in the LMS then the issue would appear to be something with your own installation of Captivate or some change to the template files at your end. 

If their output has the same issue as yours, then the problem is in the CPTX project file.  

[Vijay5CA8]

Hi

In response to the troubleshooting ideas you have provided :

1. We have republished the project from a fresh installation of Adobe Captivate on a different computer than the original version and PF produced the same error.
2. We created a new project on a different computer than the original project with a fresh installation of Captivate. This project contained only default question and results slides and was published using only default settings according to the SCORM 1.2 Standard. This project produced the same result.

[RodWard]

If you upload this new test project you just created to SCORM Cloud, does it perform as expected?

If it does, I would have to say that your custom-built LMS is most likely to be the issue.  Captivate's SCORM output is generally quite bullet proof when the LMS is completely SCORM compliant.  But all bets are off if your LMS is 'homegrown'.

[Vijay5CA8]

Thank you for the response,

It does work well in the SCORM Cloud.

We have no issues with any of the other users in our LMS for the last 4 years,

This issue popped up last month with one of the users and trying to figure out the solution,

[RodWard]

Just ONE user has this issue?   Did you mention that before?

If all this is just about a problem experienced by a single user it could be almost anything. They could have some overzealous app on their PC or mobile device that is blocking the SCORM API.  

I'm sorry but I misunderstood this to be an issue you were having with the entire project, not just ONE single user that was having the issue.  Are you saying everyone else has no problem with this project playing from your LMS?

[Vijay5CA8]

Yes, just this specific user,

I mentioned before yes -  It is our custom built application and it runs other user's SCORM files without any issues except for this user's files.

They think that the problem is with the way our lms handles the SCORM file, but we did not have similar issues. We want to help them sort out for the user and we have tried all the suggestion given so far.

Based on what you mentioned now, can I ask them to check on a different system if that would help? Our Lms is online, could it make a difference with which system they are using?

[RodWard]

Each LMS is different.  They all claim to comply with SCORM, but they all have a slightly different interpretation of what it means.

However, your case is somewhat different.  I don't have any more ideas I can suggest.  There has to be something about this one particular user that we haven't heard so far.

[mlisonbee]

Thanks for your response, but I test the SCORM files using schoox.com LMS. Everything seems to work fine but when the training is closed, the LMS does not seem to report the score accurately.

[RodWard]

Is this the same issue as the original one mentioned on this thread about not being able to find the LMS API?  If not, please start a new thread.