Skip to main content
Inspiring
February 14, 2014
Answered

imsmanifest.xml file mislabeled

  • February 14, 2014
  • 1 reply
  • 1004 views

After publishing a module under SCORM 1.2, I discovered that the imsmanifest.xml file had been mislabeled msmanifest.xml. This caused it to not upload to Litmos LMS. Since the file was zipped for SCORM, I tried to unzip it and change the name, but unzipping the files appears to remove one file from the list. I checked my settings against those of an associate who was having no problem publishing and inserting modules into the same LMS. We could not find anything different. Does anyone know what would cause the imsmanifest.xml file to leave off the i from the file name? I'm baffled!

Windows 7 Enterprise 64-bit

Adobe Captivate 6.0.0.199

Litmos LMS

SCORM 1.2

Darin

This topic has been closed for replies.
Correct answer IDarin

The best answer I can come up with is that Captivate 6 just does not like networks. I found I can publish to my hard drive without any problem, then move it to my network drive. Ironically, launching Captivate as an Admin restricts where you can save/publish you modules, while launching as a non-admin allows you to save your work wherever.

I look forward to a day when Captivate will not have any Admin requirements.

Darin

1 reply

IDarinAuthor
Inspiring
February 20, 2014

I have since upgraded to Captivate 6.0.1.240. Unfortunately, it has not solved my problem. Upon further review, I find that all of my file names that are zipped for SCORM 1.2 have had the first letter trunkated. Thus, the LMS does not know what to do with them. This sounds like a bug to me. Please help.

Darin

IDarinAuthorCorrect answer
Inspiring
February 27, 2014

The best answer I can come up with is that Captivate 6 just does not like networks. I found I can publish to my hard drive without any problem, then move it to my network drive. Ironically, launching Captivate as an Admin restricts where you can save/publish you modules, while launching as a non-admin allows you to save your work wherever.

I look forward to a day when Captivate will not have any Admin requirements.

Darin

RodWard
Community Expert
Community Expert
February 27, 2014

Captivate has NEVER really "liked" networks, if what you mean by this is that you wanted to work over a network on CPTX files stored on the LAN rather than on your hard drive.

Note the tips here for setting up your system to work with Captivate so as to avoid issues:

http://www.infosemantics.com.au/adobe-captivate-troubleshooting/setting-up-your-computer-to-work-with-captivate

http://www.infosemantics.com.au/adobe-captivate-troubleshooting/how-to-set-up-preferences