What is MMTracking.swf? And, how do we get rid of it?

Report · Dec 03, 2015

Our team uses Captivate 7 and 8 to deliver SCORM 1.2 content. We use Peoplesoft ELM 9.1 to launch and track. SCORM tracking fails because it's looking for the MMTracking.swf file. This results in the Learning Management System not initializing the SCORM API. No tracking will occur.

From research it appears that this has been a huge issue for Captivate users for years. How do we resolve this?

No where in the compiled code do I see a reference to MMTracking.swf?

This is a real show stopper for us. How do we resolve this issue?

Report · Dec 03, 2015

Man I thought this issue was long dead and gone. I haven't seen this brought up for years.

No this has NOT been a "huge issue for Captivate users". Most Captivate users will never have even heard of it. It's ONLY an issue with certain LMSs that have chosen to interpret the SCORM standard in a particular way, e.g. PeopleSoft.

The MMTracking.swf was a debugging file that seems to have been used at some point in Captivate's long history. Somewhere lurking inside the Captivate code-base there is still a reference to it, and your LMS thinks this file is essential to the SCORM output and (like a spoiled child) won't allow anything to happen until it sees a file by this name in the output.

The suggested fix (from my hazy long-term memory) was to create an empty TXT file, rename it MMTracking.swf and put it in the output where the LMS demands to find it. Even though the file does absolutely nothing, it is enough to get things working.

Report · Dec 07, 2015

Thanks for responding so quickly, Rod.

The fix eliminates the error messages on launching the course. We still have the issue of the SCORM API not tracking in Firefox and Chrome.

I'm curious where this files gets called. Nowhere in the code does it call for this. It's not in any of the XML files, so we're wondering what the deal is with this file?

Was there code in the MMTracking.swf that would be useful, or are our LMS consultants chasing an irrelevant target?

Thanks again, Rod.

Report · Dec 07, 2015

As I said, my recollection is that it was some kind of debugging file that was used waaaayyyyy back in the early days of Captivate 1 or 2.

I remember having an email conversation with the guy in Adobe that actually created a lot of their SCORM code back then (Andrew Cheney or something like that). This was long before Captivate 6 when Adobe moved over to the Rustici SCORM drivers.

I have never been able to find where this file gets called either, but I'm certain neither your current content nor your LMS needs this file. Perhaps your LMS people can tell you WHERE the LMS thinks the call is.