Warning 400 there was a problem communicating with the Learning Record Store

Forum|Forum|10 years ago
November 3, 2015
2 replies
1311 views

Hi All

Has anybody seen this error when launching a Captivate 8 course from an LMS. It doesn't do it on my work pc but it does on my client's. The full message is this

Our LMS provider suggested that I add a number of email domains to the client's whitelist which they have done, but this hasn't sorted the problem. It happens on launch only. If they click OK it will let them proceed but am sure that's not good.

Any advice on this would be most welcome. There was a previous question on this back in May but no answers on it.

Many thanks

Janet

This topic has been closed for replies.

TLCMediaDesign

Inspiring

Did you publish Tin Can?

It's happened everytime I've tried Tin Can, even the SCORM Cloud and Rustici wrote the Captivate SCORM and Tin Can code.

J

Janet WeldonAuthor

Known Participant

Hi TLC

I've reported this as a bug to Adobe. It's an intermittent problem whereby sometimes Captivate just doesn't send the course ID to the LRS which causes the error. The course ID is definitely there and sometimes it works. I'm trying to go back to SCORM but it needs to be reported if Adobe are to get their TinCan solution working reliably. I was wondering if you would log a bug too, the more the merrier and might get some action.

Many thanks and good luck with your courses.

Janet

BDuckWorks

Inspiring

I would suggest you confirm your SCORM/AICC versions against the documentation for the LMS.

Click configure to see:

You can see, I've specified SCORM 1.2, but you might be using SCORM 2004, or even AICC.

Also, you might want to search the message board of the LMS for 'Captivate Error 400' to see if someone has already tackled this.

J

Janet WeldonAuthor

Known Participant

Hi there

I'm using TinCan, could that be the problem?

I searched for Error 400 and only my post came up.

I can't replicate the error at my end, is my client that gets it. I wondered if it was something in their setup but don't know what to suggest. They updated their whitelist with our domain names but that doesn't appear to have solved anything.