SCORM manifest files

when i publish a project in Captivate 2, the manifest file
that generates is titled 'breeze-manifest', and it won't import
into our Pathlore LMS... in the 'reporting' window i have the
'scorm' radio button selected and completed all the required fields
in the 'manifest' area... can anyone help me figure out why i'm
getting the breeze-manifest stuff instead of the manifest
information for the course?...

Hi,
In Order to generate the imsmanifest.xml which will contain
the information for SCORM, you MUST have atleast one scoring object
in your project. That is either a question slide or any interactive
object (like button/click box) with tracking enabled.
To enable the tracking for an interactive object, go to the
reporting tab of the object (from object properties) and tick -
Include in Quiz and reporting.
After this when you publish the project with HTML you will
see the manifest XML file in the published location.
-

Similar Messages

SCORM Manifest Information Shows in LMS

We are uploading courses to our LMS (Cornerstone). When we launch the file, there is a section to the right of the actual course that appears to show information from the SCORM manifest file.
I have not been able to figure out if this is something I can turn off from either Captivate or from Cornerstone, but I know we don't want it to show (it looks messy, and takes up a lot of the screen).
Screen shot is below -- has anyone had this issue before and been able to remove it?
Much appreciated!

I'm coming back to this issue after a few months because it is seriously impacting a project I am trying to publish for a client.
If I publish as SCORM 2004, I get the screen pictured above.
If I show the TOC with a customized skin (via Captivate), I get the screen shown to the right. (TOC is pretty from Captivate, but I still get the extra window at the left.)
If I publish as SCORM 1.2, the extra window goes away, but I lose Seamless Tabbing, which completely screws up the tutorial, which uses Tab to enter data into the fields.
Cornerstone does not have an option to turn anything off when uploading a eLearning module. Even if they did, the fact that the screen disappears when publishing as SCORM 1.2 implies that there is something going on with the SCORM 2004 publish that is different.
I have read other threads that tell me to add a line to the SCORM 1.2 HTML file to fix the seamless tabbing issue. However, the HTML file simply routes out to the javascript file, so that can't be done.
And, although HTML 5 is a preferred solution, Captivate's HTML 5 version does not support rollover captions, which I use in my tutorial.
Do I have ANY other options here? I would very much appreciate some help.
Thank you.

SCORM package files for Dreamweaver/Coursebuilder interactions

Gentlefolk;
Trying to see if I can get Dreamweaver (CS3) with Coursebuilder interactions to play with LearnCenter LMS. The site is not loading because the LMS can't find the SCORM manifest files.
I don't see an export function in Dreamweaver that would create the manifest files. Is there a way to generate the manifest files, so LearnCenter has something to grab onto?
Or have I tumbled to the reason everyone is using Captivate?
Many thanks!
Don

Hi Vijay;
It has been a while since I started this thread or even looked at it, so I am hazy on my original inquiry. I will have to look again. Short answer to your question however is that every tool I play whith that outputs to SCORM-compliant content automagically creates the manifest files and all the related support files.
I just wanted to acknowledge your message right now. Let me look at the original thread and see if I have any more information that may directly assist you.
Don

Publishing in Captivate 3, SCORM 1.2, no manifest file...

I’m using Captivate 3, publishing to FLASH/SWF with SCORM 1.2 enabled. I’m only getting a zip with two swf files and nothing else.
I’ve selected Quiz Results only, Score to LMS as Percent, Report Pass/Fail with Reporting level as Interactions and score.
I’ve required Answer all – the user must answer every question to continue
Selected Allow user to review quiz, show score at end of quiz and show progress
In LMS Customization settings, nothing is selected.
When I access Advanced Interaction there are nothing but blank spaces in the Track Score column for the Quiz slides.
I believe this is why when I publish I’m not getting a manifest file, but I have run out of ideas.

On your Quiz Settings select:
Status Representation
Incomplete-->Complete
Success/Completion Criteria
Report slides viewed = 100%
Uncheck Quiz
Uncheck Data to Report/Interation Data
Click the Advanced button and select "Set extit to normal after completion".

SCORM 1.2 manifest file

Can zip and upload to SumTotal LMS, but manifest file does
not record test scores or completion of module.

Hi we use SumTotal, you need to change the order of the API:
Find the scorm_support1_2 Javascript file in the template
folder:
(Program
files>Adobe>Captivate3>Templates>Publish)
Changes the zero value to one on line 39 which looks like
this:
if(intAPISearchOrder==0) to look like this:
if(intAPISearchOrder==1)
ALSO: the SCORM settings within the project itself must be
'complete/incomplete', I have found that pass/fail doesnt work with
Sumtotal.
Save and re-publish your project, ready to re-load to
SumTotal.
Webbo

Problem with manifest file and Plateau LMS

I have published a course with a quiz in SCORM 1.2 and tried
to upload to a Plateau LMS.
It seems that a "page cannot be found" message is the result
after upload and we try to launch the course. The course works
outside the LMS (when run locally on my computer).
The Plateau LMS support team tried to help, and found the
following: "There is something wrong with this manifest, though I
cannot ascertain what that is exactly. Most of the file name is in
the parameter field, which is causing the launch path to look like
this:
/content/apmm/cbcgis/mars/BRTMAIN/MARS?BRT%20Maintenance%20Template_%2020080226.htm=
Everything in the parameters field is placed after the
filename in a URLencoded querystring after the question mark that
you see above. it should look like this:
/content/apmm/cbcgis/mars/BRTMAIN/MARS BRT Maintenance
Template_ 20080226.htm"
Can anyone please help resolve this, or have any advice?
This is the first time we have tried uploading Captivate
courses to this LMS, and we have been having problems with the
manifest file in general. I have looked at all the material I can
find on publishing and the manifest file, but cannot seem to
resolve my issue.
Thanks
Warwick

Warwick,
I have had this error with an Authorware set of SCORM files
when my LMS was looking for index.htm and I had named it index.html
- you wouldn't think that would cause an error but it did. I would
be more than happy to package a Captivate file of just a few
screens that works on my LMS (which is Learn.com's Learning
Center), and send you the SCORM files to test... That could be a
start anyhow. I will send you a private msg. with my e-mail
id.

Manifest File

I am making a WBT where I need to use the scorm feature with Presenter and PowerPoint. I have looked at the help file for the instructions on what options to select for scorm and when I publish my presentation as a .pdf file I am not getting a manifest file with it. What am I doing wrong?

I don't believe that the PDF version will do SCORM reporting. Publish out a zip of the Flash version and you will be able to see the manifest file in that zip. (don't publish directly to your desktop or you will end up with about 20 files and folders that you have to keep track of).

Manifest.xml - Manifest file in Captivate 6

Hello,
I am publishing a course and uplaoding it to my LMS using SCORM 2004 and it says the Manifest file (manifest.xml) could not be found and the page thus cannot be found. Does anyone know how to fix this or could walk me through what I did wrong?

If the Captivate publish dialog shows that it is zipping the files, then unzip one of them again yourself and see if you can see a file called imsmanifest.xml at the top level of the folder structure.

Captivate 3 not saving SCORM manifest

I'm trying to use Captivate 3 to create a quiz to upload to
Moodle. I've added grading to each question, enabled reporting for
SCORM 1.2 - and all the other settings appear to be fine. But the
only manifest I get, (and one Moodle doesn't recognize) is
breeze-manifest.xml - which doesn't look anything like a SCORM
manifest. Other than that i just have my 2 swf files and a
BDMetadata.xml file that isn't SCORM related either.
I am using Windows Vista - not sure if that matters - but
something about the LMS reporting is not working with Captivate 3 -
I've tried different settings - SCORM 2004, AICC - and the
breeze-manifest.zml is all I ever get.

Uncheck the 'publish Breeze metadata' (or something like
that) in the
Publish options to avoid the useless (if your not using
Breeze) Breeze
manifest. Be sure you have 'publish to zip file' (or
something like
that) checked. I'm pretty sure a manifest is not generated if
you don't
output the results to a zip file...
If you do both those, is there an imsmanifest.xml file in the
resulting
.zip file?
Erik
stace20 wrote:
> and the breeze-manifest.zml is all I ever get.
>

Licensing and Manifest File

We have two Lic for Adobe Captivate2. When we try to package
a captivate demo using SCORM, only one lic will create the manifest
file for us. Both Lic were purchased at the same time. Please help.
We just found out that when we package the same captivate
file using captivate Macromedia captivate, all the necessary files
are created and loaded successfully into our LMS (Saba).
Unfortunatlly, I cannot say the same thing about Adobe
Captivate 2.

AS I understand it, a manifest won't be generated if there's
nothing to
track. I always assumed that meant at least one interaction
had to be
marked as 'scored' and the Quiz Manager settings had to be
completed
(type of tracking, etc). I don't know if 'track by slide
views' means a
manifest will be generated or not...
But you're suggesting that on one system, without any scored
interactions and no Quiz Manager settings, that a manifest is
being
generated with just 'track by slide views' checked?
I'm not familiar enough to know if that's all that should be
needed, nor
if that option should result in a manifest.
A common workaround for content that needs to be viewed but
has no
'quiz' is to place a scored interaction on the first slide
that simply
says something like 'Click here to begin'. Since everyone
clicks to
start the course, they automatically score 100%, which can be
correlated
to a 'completed' status.
Erik
hxdabbas wrote:
> The settings are little bit different in both version. I
tried my best to come
> as close as possible. The zip file is produce but the
manifest file is not
> available. There is no quize to take. All I am trying to
do is track by slide
> views only option.
>
> I was told that there are some updates for Captivate 2
on the Adobe site that
> I cannot find.
>
Erik Lord
http://www.capemedia.net
Adobe Community Expert - Authorware
http://www.adobe.com/communities/experts/
http://www.awaretips.net -
samples, tips, products, faqs, and links!
*Search the A'ware newsgroup archives*
http://groups.google.com/group/macromedia.authorware

Export Scorm with Files

In Captivate 4, how can I include additional files (XLS, XLSX, PDF, JS , HTML) that is used to launch links (User clicks on link, launches PDF in seperate window. User click on link, Launches HTML in seperate window). The files must be included in the exported zip and included in the IMSManifest.xml. I must be missing something because ive tried every single way I know of to get it to import it including placing it in the Folder with Captivate. Any ideas?

Manually adding the files to your zip archive and editing the manifest file are probably your best bet. I'm not aware of any way, even in Cp4, to automatically add external files to your output folder or manifest (but I may be wrong -- it's been a while since I've needed to export SCORM-compliant output).

SCORM Support Files

I've read through similar issues on the forum and checked out
some support articles but I'll be danged if I can get Captivate 2
to generate SCORM manifest. I see .MGP filews in the My Adobe
Captivate Projects folder with today's date but my output is not
even directed there.
I inserted a scored question and enabled SCORM reporting.
The Export HTML check box is disabled on the publishing
option. I blew away the old DAT file in case that was the problem
but... no difference.
I find this SCORM business in Captivate to be poorly
documented. It's not as straightforward as the sparse directions
state. I'm not SCORM illiterate at all. But Captivate has me
flummoxed on this one.

Hi JackAnz
I think something else may also be clouding the issue. The
fact that Captivate 3 seems to insist on creating new folders for
output locations. Please allow me to explain.
For example, I just tested and published an "Untitled"
Captivate with no eLearning output enabled. When I did, Captivate
insisted on creating a folder named "Untitled" to store the files.
I published and looked inside the folder. So far so good.
I then enabled Reporting via SCORM and published again. As
you have seen, the HTML option becomes disabled. I believe this is
because HTML is a requirement for SCORM. (If you look closely, you
should see that there is a check mark inside the check box, but
it's disabled so you cannot DE-select it!) I also selected the .ZIP
option.
What was surprising to me was that the resulting .ZIP didn't
end up in the same place the previous output did. Instead, it was
in a folder level above my "Untitled" folder that Captivate
lovingly insisted needed to be there when publishing with no
reporting and no .ZIP. So I'm wondering if you weren't seeing the
files because you were being misled about where they should have
been.
Cheers... Rick

Validating Manifest File Error

Upon publishing my file, I run it through the ReloadScormPlayer 1.2. and get the following error with the manifest file. Any ideas as what I need to do to fix this?
Problem validating manifest
(file:/D:/Documents%20and%20Settings/kawittrock/reload/reload-scorm-player/server/webapps/ reload-scorm-player/course-packages/2009%20Scoring/imsmanifest.xml: 95, 102): cvc-id.2: There are multiple occurrences of ID value 'ahs_cont_scor_062309'.
(file:/D:/Documents%20and%20Settings/kawittrock/reload/reload-scorm-player/server/webapps/ reload-scorm-player/course-packages/2009%20Scoring/imsmanifest.xml: 95, 102): cvc-attribute.3: The value 'ahs_cont_scor_062309' of attribute 'identifier' on element 'item' is not valid with respect to its type, 'ID'.

Upon publishing my file, I run it through the ReloadScormPlayer 1.2. and get the following error with the manifest file. Any ideas as what I need to do to fix this?
Problem validating manifest
(file:/D:/Documents%20and%20Settings/kawittrock/reload/reload-scorm-player/server/webapps/ reload-scorm-player/course-packages/2009%20Scoring/imsmanifest.xml: 95, 102): cvc-id.2: There are multiple occurrences of ID value 'ahs_cont_scor_062309'.
(file:/D:/Documents%20and%20Settings/kawittrock/reload/reload-scorm-player/server/webapps/ reload-scorm-player/course-packages/2009%20Scoring/imsmanifest.xml: 95, 102): cvc-attribute.3: The value 'ahs_cont_scor_062309' of attribute 'identifier' on element 'item' is not valid with respect to its type, 'ID'.

WLS 6.1, SP2, Error Deploying WAR, Manifest file problem

Hi,
When I moved to SP2 on 6.1, I am getting a new error while deploying a war file.
It looks from the stack trace that there is a problem with my manifest file, but
I am just taking the manifest file created by jdk1.3 jar utility - My META-INF
dir is empty before jarring. When opened in notepad, the cursor can go to the
start of the line below the blank line. I mention this in case that is the EOF,
and relevant to the problem. Any help is much appreciated.
Mike
Manifest File:
Manifest-Version: 1.0
Created-By: 1.3.1 (Sun Microsystems Inc.)
Stack Trace:
####<Feb 22, 2002 10:32:36 AM EST> <Info> <HTTP> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101031> <[WebAppServletContext(1118014,ipp,/ipp)]
extracting classfiles to C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_myserver_myserver_ipp:>
####<Feb 22, 2002 10:32:36 AM EST> <Debug> <HTTP> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101158> <Exception
thrown while loading ipp: java.lang.StringIndexOutOfBoundsException: String index
out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1525)
     at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
     at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
     at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
     at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy32.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
     at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy98.addTarget(Unknown Source)
     at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
     at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy5.update(Unknown Source)
     at weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
     at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
     at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 22, 2002 10:32:36 AM EST> <Error> <J2EE> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <160001> <Error deploying
application ipp: Could not load ipp>
####<Feb 22, 2002 10:32:36 AM EST> <Error> <Management> <mdunbar> <myserver> <ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <141042> <Error deploying
application .\config\mydomain\applications\ipp.war: java.lang.reflect.UndeclaredThrowableException>

I figured out what was causing this for me. Apparently, the new Manifest reader
classes in WLS SP2 are a lot pickier ( polite way of saying they dont handle exception
cases very well ;-) ). I had 2 third-party jar files in my WEB-INF/lib directory
whose manifests had issues that the Manifest reader could not handle. One of
them was a header line that wrapped and the other had extra lines at the end of
the file. I had to unjar them, fix the manifests, and re-jar them. the server
started up fine after that.
It might be nice if they provided a better error message than "String Index Out
Of Bounds: -1" for this problem, but hey, you can't have everything because where
would you put it :)
"Mike Dunbar" <[email protected]> wrote:
>
Hi,
When I moved to SP2 on 6.1, I am getting a new error while deploying
a war file.
It looks from the stack trace that there is a problem with my manifest
file, but
I am just taking the manifest file created by jdk1.3 jar utility - My
META-INF
dir is empty before jarring. When opened in notepad, the cursor can go
to the
start of the line below the blank line. I mention this in case that is
the EOF,
and relevant to the problem. Any help is much appreciated.
Mike
Manifest File:
Manifest-Version: 1.0
Created-By: 1.3.1 (Sun Microsystems Inc.)
Stack Trace:
####<Feb 22, 2002 10:32:36 AM EST> <Info> <HTTP> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101031> <[WebAppServletContext(1118014,ipp,/ipp)]
extracting classfiles to C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\WEB-INF\_tmp_war_myserver_myserver_ipp:>
####<Feb 22, 2002 10:32:36 AM EST> <Debug> <HTTP> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <101158> <Exception
thrown while loading ipp: java.lang.StringIndexOutOfBoundsException:
String index
out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
     at java.lang.String.substring(String.java:1525)
     at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
     at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
     at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
     at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy32.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
     at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
     at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy98.addTarget(Unknown Source)
     at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
     at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
     at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
     at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy5.update(Unknown Source)
     at weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
     at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
     at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Feb 22, 2002 10:32:36 AM EST> <Error> <J2EE> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <160001> <Error
deploying
application ipp: Could not load ipp>
####<Feb 22, 2002 10:32:36 AM EST> <Error> <Management> <mdunbar> <myserver>
<ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'> <system> <> <141042> <Error
deploying
application .\config\mydomain\applications\ipp.war: java.lang.reflect.UndeclaredThrowableException>

Package load Failed! Invalid package Title, manifest file cannot be found

Greetings. I am new to UPK and am seeking guidance on an upgrade to 11.1.
A little background on what we are trying to do:
We have two machines:
Windows 2003 machine in domain 'X' | UPK 11.0.0.1.
Windows 2008 R2 virtual machine in domain 'Y' | UPK 11.0 on the new machine first, install the 11.0.0.1 patch, and then upgrade to 11.1.
We are using the same database as the old machine. Developer Server is Standard Authentication, Knowledge Center is Windows authentication.
==========================================================================================
So far we have installed 11.1 with the respective database upgrades, but are lost as to how to migrate the old Content Root data. We have copied all the content to the new Content Root, added it to IIS like the old machine, and verified that the UPK database Content Root path is correct and working.
For the rest of the post, I am remoted into the server from my local workstation, and then using IE to access KCenter on the server's FQDN, not via localhost.
Since I am green, so I presumed that I would need to import the titles under Manager in KCenter. I zipped each content folder individually (they are named "1", "9", etc), and then attempted to import each zip file.
NOTE: At this stage sometimes we are prompted to authenticate again. When it does, sometimes the credentials that we know work, get rejected and we are prompted again. This will repeat until we get a 401 and we have to start over. We have verified that the Windows account currently in session with the site is valid and has administrator authority within KC.
NOTE2: On the first few tries, .NET complained that maxRequestLength was not large enough. I had our servers team increase it on the actual server in order for us to proceed.
Provided we don't have to authenticate again, or that it actually accepts our credentials, we get to the 30% mark and then receive the error: *"Package load Failed! Invalid package Title, manifest file cannot be found"*
Does anyone have any wisdom for this process? The title importation section in the deployment manual is not helping, and the administrator from whom I am taking over this software has not had to deal with this before.
Thank you,
Ian
Edited by: 986290 on Feb 5, 2013 10:21 AM

Hi Marc, thanks for the post,
I have gone through an extensive troubleshooting process with Oracle, including their development team, in order to fully complete our project setup. As a supplemental bit of information, we also were having connection errors when attempting to publish directly to the knowledge center.
As far as the context of this post, here is the solution in brief:
1) Verify that the package being imported was published from the same version of the Developer Client as the Knowledge Center installation's.
2) Check for database consistency issues. In our case we were using a database that was built in another domain. After numerous attempts with Oracle support on the line to determine the inconsistency, it was decided to completely reinstall and build a new database from scratch in the new domain.
3) Check application pool identities and access (while we had some inconsistencies here, correcting them did not change the behavior of the import/publish errors)
In review, a lot of what we had setup was correct. Our primary point of failure, we feel, was using the old database. Technically this should not have been a problem, but Murphy likes to get his way sometimes.
Cheers,
Ian

SCORM manifest files

Similar Messages

Maybe you are looking for