Javascript bug and random frames: alternative solution?

Hello all,
I'm working on a SCORM 1.2 compatible eLearning project on Captivate 6.1.0.319 (subscription edition), and I've just come across the bug described very precisely here:
http://www.youtube.com/watch?v=Vq9K9lvq-5I
and here:
http://www.cpguru.com/warning-adobe-captivate-6-and-javascript-bug/
Basically, any javascript used in the project would break the SCORM compatibility, either sending wrong completion information to the system, or in my case, also shutting down the eLearning module and also closing the window. This problem occurs only in IE, as other browsers seem to work fine.
My target group of users is a corporate environment, in which IE is the #1 platform; it's unrealistic to ask for a browser update, so I have to find a solution to be able to publish the project correctly. The same blogger who uncovered the problem wrote that it's possible to receive a patch from Adobe which consists of an updated version of the file Mainmovie.swc to swap in one of the program's directories (more info here:http://www.cpguru.com/fix-for-the-adobe-captivate-6-javascript-bug/ ).
The problem is that the supposed fix (which you have to request via email and it's not directly downloadable), is said to be available only for Captivate 6.0.xx and not for the 6.1 Subscription edition.
As my project contains a lot of drag and drop interaction, I cannot afford to downgrade to 6.0 to try to use the patch, and I was wondering if somebody has had the same problem and can help out.
In detail, I only use javascript in one slide to simulate a random display of rollover images (a button calculates the current position of the playhead and jumps to a random point of the slide, chosen from an array of predefined frame numbers; at every 'stop' there is a different rollover image and a button that makes the playhead jump again to display another 'random' image).
I was wondering if there is any way to reproduce this behavior not using javascript, so that if there is no fix (I'm obviously in a very tight deadline...), I can get around the problem by avoiding javascript altogether.
Thank you very much for your help!
n
(crossposted on the general Adobe Captivate forum)

I don't have a solution for you, but I want to compliment you for a great post. I wish others would follow your lead, and include the information about their system, the problem, the steps already taken, etc.
Have you tried creating a new project, with a new HDV sequence, and editing a short timeline as a test to see if it's a problem with that one timeline or not?

Similar Messages

  • Dear Apple, unfortunately, I think I have found a bug in ios 7. During an incoming call is no call rejection or selection of the ability to send a text message. I hope it is a bug and there is a solution. Thank you very much.

    Dear Apple, unfortunately, I think I have found a bug in ios 7. During an incoming call is no call rejection or selection of the ability to send a text message. I hope it is a bug and there is a solution. Thank you very much.

    Please report via Apple Feedback. These are user forums. You aren't speaking to Apple here.

  • Best coverflow and missing feature alternative solutions for all platforms.

    Personally for me coverflow was a important feature. Not JUST a feature but what really defined iTunes as BEING iTunes.
    I would have actually loved if apple instead of removing it expanded on it and made it faster,better,stronger. With things like back label support  so on and so forth.
    I'd like the communities thoughts on some of the best alternatives for the missing coverflow & other features currently left out of iTunes 11 on both Mac and Windows.
    Also, If there is a way to link(link up) any of those to iTunes 11 for track and volume control. Ideally for not just sending but also receiving track and volume input.
    And whats the absolute BEST solution for each platform. I understand running iTunes 10.7 or 11 sandboxed or on another machine may also be an option.
    So.. lets look at things like resource usage Vs usability...
    For me CAD (CD Art Display) has always been helpful especially combined with raindrop even tho it doesn't have flow options for the most part on 99% of themes. It still makes my library pop.
    Looks like there are 3 options for Mac
    Steel Sky (SteelSkies)
    Everplay
    CoverStream
    Its worth noting Everplay has Last.FM support. Not sure if that can be integrated into iTunes 11 somehow.
    For windows the only thing i could find remotely like coverflow is a widget called XDeskCover
    To mods:
    Please stop deleting my posts. If you want to take the time to completely remove a feature from a program atleast let us explore some alternatives so we can continue actually using apple products.

    another method suggested in these forums in the post "session manager stopped working with firefox 3" by Charles Anderson works for me and allows me to use my little X.
    go to options -> General tab
    under startup/when firefox starts -> change to something other than "show my windows and tabs from last time".
    I've had this on show my homepage previous and it got changed somewhere and I think it was from an update or addon which is why a few others are having the same issue.

  • Captivate 7 - The Exit Bug and a Solution

    Hey Everyone,
    I wanted to take a second and share some good information I found in regards to SCORM and the Exit functionality in Captivate 7. Below is the blog post that shows how to make the Adobe Exit functionality "SCORM Compliant" and solved my issues when uploading my project and getting them to exit. Hope this helps
    Captivate 7, Exit Bug and a Solution
    Several of our Inquisiq R3 users have alerted us to the fact that courses developed with Captivate 7 published to HTML5 and SWF do not close properly when using the “Exit” button, forcing the user instead to manually close the browser window by clicking the “X” in the upper-right corner of the browser window.
    Through our investigation into this issue, it appears that the process that Adobe has implemented when clicking the “Exit” button is to simply attempt to close the content window and rely on the LMS to capture and commit the session data. Nowhere did we see that the content was actually calling the “LMSFinish()” [SCORM 1.2] or “Terminate()” [SCORM 2004] methods in the LMS’s SCORM API to commit the lesson data to the LMS as required by the SCORM specification.
    Adobe uses their own defined function, “DoCPExit,” to close a lesson window.  This method contains a “window.close()” call and additional logic to “bubble up” the command through the frame parents (if they exist and also contain the “DoCPExit” method - presumably because they would also be Adobe-published content files within your package).
    There are several flaws to this approach.
    By not calling “LMSFinish()” or “Terminate(),” the content is, by definition, not SCORM conformant.  Part of the minimum requirements for conformance are that the content calls the initialization method “LMSInitialize()” in SCORM 1.2 or “Initialize()” in SCORM 2004 and the  termination method “LMSFinish()” in SCORM 1.2 or “Terminate()” in SCORM 2004. The LMS is not required to clean up the data left behind when the content fails to make this call. So if your LMS doesn’t take this additional step (of setting ‘LMSFinish’ or ‘Terminate’ if the lesson does not), your data will be completely lost…i.e. no record of you taking the lesson will be recorded.
    The call to close the browser window will fail if the LMS is running the content within a frame or iframe. Since the SCORM specification allows content to be launched in frames or iframes (in addition to new browser windows), lessons need to be able to accommodate this scenario. Even with the “bubble up” logic, once the call reaches the top most content window, and the next parent window in line is the LMS container page, the call will no longer be passed and a “window.close()” call will be fired within the framed page.  When this call is made, nothing will happen as a framed page cannot close the browser window using this command. Through our investigation, we’ve learned that at least 4 other well-known LMSs have experienced this particular issue.
    Ironically, the solution that we’ve discovered is not only SCORM conformant, but also very simple and follows what we would consider to be SCORM “best practices”.  The foundation and logic for the solution is already contained within the published Captivate files (and it is the same solution whether you publish to SCORM 1.2 or SCORM 2004).
    We simply modify the “DoCPExit” method that is contained within the “Utilities.js” file to call the “Finish()” method.  Just replace all the code appearing between the “{“and the “}” as you see here:
    function DoCPExit(){     Finish();
    The “Finish()” method that we have inserted is, as mentioned, already contained within the published Captivate files and contains the logic to properly set the exit parameters and correctly identify whether the content is SCORM 1.2 or SCORM 2004; it will therefore make a call to the correct close method (“LMSFinish()” or “Terminate()”) accordingly.  Once the LMS has received this command, it should take care of removing the content properly, leaving no need for any “bubble-up” logic or window close calls within the content code.
    Overall, if the lessons you develop with Captivate 7 work as expected and required in your LMS, there is no need to implement this change. However, if your lesson’s Exit button is not working as it should, and/or you are losing progress and status data when closing the lesson, the fix described here should resolve all those issues.
    The biggest issue here is that since we’re changing published code, the next time you update and publish that same Captivate project, you have to remember to change that published function code AGAIN, as Captivate will simply publish the default code.
    We have been in touch with the Captivate team to discuss this problem and they are investigating. We would hope a patch to address this flaw would be released in the near future
    All credit of this fix goes to http://blog.icslearninggroup.com/2013/10/captivate-7-exit-bug-and-solution.html

    Try clearing out your project cache (Preferences > General > Clear Cache) then republish using the option to Force Republish All Slides.
    If that doesn't resolve the issue, you may be seeing the early stages of project file corruption.  Check the suggestions in this post about troubleshooting issues where you may need to copy all slides to a new blank project shell to try and strip out corruption:
    http://www.infosemantics.com.au/adobe-captivate-troubleshooting/basic-troubleshooting-tech niques

  • Transferring Purchases Bug and Solution

    I just found a bug, and after some of trial-and-error, I also found a solution, so I thought I'd post it here in case anyone else is having the same problem, and to make apple aware of it so it can be fixed in a future iPod Touch update.
    I recently purchased a song on my iPod Touch, but when I plugged it in, it wouldn't transfer it to my mac. I eventually discovered that this was because I had dragged the 30 second preview from the iTunes store to a playlist (a "Wish List" if you will), and had forgotten that it was there. This must have confused iTunes into thinking that I already had the song on my mac. However, I did not, it was merely the preview in the music store. So if any of you are having a problem, check to see if this helps.

    Thank you so much!!!! I was frustrated with it not transferring, and I do the same thing with wish lists. That helped me a lot. Thank you!!!

  • Acrobat 9.1.1 and javascript bug

    Does the latest version of Acrobat, 9.1.1, correct the problem with the javascript bug that was discovered
    a few weeks ago and the recommendation to turn off javascript?
    Thanks!

    I think that I found the answer in the following link:  https://bugs.launchpad.net/bugs/cve/2009-1492
    CVE-2009-1492 refers back to CPSID_49013 which is the latest Adobe update for Acrobat and Reader.

  • N80: Feeds Client bug and possible solution

    Hi everyone,
    I've found what appears to be a bug in Feeds Client V. 3.0(0529) in my Nokia N80 Internet Edition.
    I've added a couple of feeds when connecting to a WLAN, but when I tried to read those feeds again, this time away from that WLAN range, it didn't even gave me the choice of network connection: it just tried to go back to the same connection without asking.
    I deleted that network's entry in Tools->Network->Access points. Because I only had two feed address saved, I've also deleted them.
    But this time the phone didn't even allow me to go into the Feeds folder!
    What appeared to solve the bug was something like this.
    1) Create a new bookmark with the feed address (e.g. Google News). You can delete it later.
    2) Start browsing the feed. Your browser should ask what is the network to use, if you've configured that way.
    3) You get the feed list, hopefully. If you choose Back, the mobile will show the feed list you've saved (in my case, only the feed I'm reading because I've previously deleted all of them).
    This seemed to do it. If you want to be sure, save the new feed in the Feeds folder again, and delete the previous feed.
    Hopefully this will allow you to go around the bug and let the Feeds Client think it should access the network connection you want. The problem is, it still only lets you read the feeds through the network connection you've selected!
    Regards,
    J.B.

    A better test would be to move one at a time (Desktop folder) until you find the codec causing the trouble.
    Two of my guesses:
    Out of date DivX
    VLC plug-in

  • Captivate 6.1 Javascript bug / subscription edition

    Hello all,
    I'm working on a SCORM 1.2 compatible eLearning project on Captivate 6.1.0.319 (subscription edition), and I've just come across the bug described very precisely here:
    http://www.youtube.com/watch?v=Vq9K9lvq-5I
    and here:
    http://www.cpguru.com/warning-adobe-captivate-6-and-javascript-bug/
    Basically, any javascript used in the project would break the SCORM compatibility, either sending wrong completion information to the system, or in my case, also shutting down the eLearning module and also closing the window. This problem occurs only in IE, as other browsers seem to work fine.
    My target group of users is a corporate environment, in which IE is the #1 platform; it's unrealistic to ask for a browser update, so I have to find a solution to be able to publish the project correctly. The same blogger who uncovered the problem wrote that it's possible to receive a patch from Adobe which consists of an updated version of the file Mainmovie.swc to swap in one of the program's directories (more info here: http://www.cpguru.com/fix-for-the-adobe-captivate-6-javascript-bug/ ).
    The problem is that the supposed fix (which you have to request via email and it's not directly downloadable), is said to be available only for Captivate 6.0.xx and not for the 6.1 Subscription edition.
    As my project contains a lot of drag and drop interaction, I cannot afford to downgrade to 6.0 to try to use the patch, and I was wondering if somebody has had the same problem and can help out.
    In detail, I only use javascript in one slide to simulate a random display of rollover images (a button calculates the current position of the playhead and jumps to a random point of the slide, chosen from an array of predefined frame numbers; at every 'stop' there is a different rollover image and a button that makes the playhead jump again to display another 'random' image).
    I was wondering if there is any way to reproduce this behavior not using javascript, so that if there is no fix (I'm obviously in a very tight deadline...), I can get around the problem by avoiding javascript altogether.
    Thank you very much for your help!
    n

    You can open 6.1 files in Cp version 6.01.  So that IS an option, though albeit probably not a very palatable one if you've just upgraded everyone around you to 6.1.
    If your main reason for developing in 6.1 was the drag and drop interactions, you may not have been aware that there have been AS3 widgets available to do drag and drop in Captivate since version 4.  Those widgets are also now compatible with all Cp versions up to and including 6.01 and 6.1.
    More information here:
    http://www.infosemantics.com.au/adobe-captivate-widgets/drag-and-drop/which-adobe-drag-and -drag-and-drop-widget-comparison
    Free trial versions downloadable here:
    http://www.infosemantics.com.au/adobe-captivate-widgets/download-free-trial-widgets

  • Problems working with non drop and drop frame DVCPRO HD material in project

    I am having playback problems with my non drop frame HDV material. It stutters.
    All of our projects up to this point have been shot in drop frame. During our last shoot however the Bcam was recorded in non drop. I loaded both the non drop bcam tapes as non drop and the drop frame Acam tapes as drop. All of the drop frame Acam material plays back fine in the source viewer and the timeline. The non drop Bcam material seems to randomly stutter in the source viewer, or causes the system to serve a "dropped frames warning" in the timeline.
    Is there a bug with fcp 5.1.2 about mixing non drop and drop frame material in a project. Or is this not possible? They are the same frame rate.
    I have exported the non drop clips in a drop frame timeline and re-imported them as drop frame clips - thus correcting the problem. Is this the best solution?
    All of the material was loaded thru a kona card as 1080i60 DVCPROHD 29.97
    I had no problems capturing the material as long as I used the corrrect firewire setting (ndf vs df).
    Anyone have a problem like this? I would greatly appreciate a response.
    Thanks,
    Mark

    http://bssc.sel.sony.com/BroadcastandBusiness/DisplayModel?m=10014&p=2&sp=141&id =78439
    The camera can record 60i, and 30F:
    "HDV 1080, 50i/60i/30F/25F Recording and Playback capable"
    Look at the clips...look at their frame rates. What do they say? Is one 59.94? Is the other 29.97?
    You would never need to render if you mixed NDF and DF footage. The footage runs at the same speed, on the TC numbers are different. But, you would need to render if your footage had different frame rates. LOOK AT THE CLIPS.
    Shane

  • Transitions double 1st frame/drop last frame: a solution

    I have found that Transitions in iMovie 5 are problematic. The first frame in a Transition doubles and the last frame drops out. This is not noticeable in a slideshow but can be very noticeable in an exported video.
    Transitions cannot be edited frame by frame unless one exports video out to a camera and then imports it back into iMovie. The original clips and transitions are now seamless clips. One can delete extra frames and then find and import the missing frames from original sources. HOWEVER, this process is incredibly frustrating and time consuming.
    THIS IS WHERE THINGS GET INTERESTING.
    To avoid the above, I thought I would add textless Titles over a few key clips and transitions where the glitching is most obvious. I had noticed that Titles longer than the clip they were inserted into, merge together the clip with its transition and following clip.
    i.e.,
    1. DEselect 'Over black' in the titles window.
    2. Select a title format and then a length longer than the 'glitched' transition.
    3. Split the clip so that the Title can be inserted.
    4. Insert a TEXTLESS Title that spands the clip, transition and into the next clip.
    5. Then edit out duplicate frames and insert missing frames from the the now 'single' clip.
    STILL just a piecemeal. STILL labour intensive.
    THIS IS WHERE IT GETS MORE INTERESTING.
    I tested this on a couple of clips and, LO AND BEHOLD, 'Title-merging' a clip with its transition and following clip results in the duplicated first frame of the transition DISAPPEARING and the previously dropped frame of the transition, REAPPEARING. A fix.
    One could blanket a video with long textless Titles (i.e., 45 seconds at a time with Rolling Credits) to fix the transition glitches.
    I know that this is not a great solution, but it does allow me to export video with the quality I need.
    Is there a better solution? (I find it ironic that years later, iMovie 2.1.2 is still, for me, the most successful of all the iMovie applications.)

    the duplicated and dropped frames move to the beginning and end of the added short (4 seconds, for example) texless title. Using a longer title (10 seconds, for example) fixed also this.
    if I understand your original reply correctly, it is important that the blanket transition ends in the middle of a clip and not a transition.
    In my tests I used a blanket title (did you invent this descriptive word?!) that spans some of the previous clip (I split it 1-2 seconds before the transition so I could add the blanket title), the transition and some (1-2 seconds) of the next clip.
    If it ends in a transition, the transition plays and then the ORIGINAL clip plays, duplicating the first part of the clip.
    I didn't quite follow. I just tried this with a 30 frame transition. Then I added a 1:15 blanket title 1:00 before the transition (so the blanket title ended in the middle of the transition). Result: The first frame of the blanket titles was duplicated and the last frame of the blanket title was dropped. Otherwise it played as expected.
    shift select the clips to establish a total length of the video clips and them add a title that ends just inside the last clip.
    Yes, I did just that to measure how long a title was needed. In my tests it seemed that it was important that the blanket title wasn't very short (<4 seconds) because then the problem frames were just moved to affect the title. Using a longer blanket title (10 seconds) seemed to fix the problem for both the transition AND the blanket title.
    <div class="jive-quote">With a textless title blanketing an entire video, my COMPRESSION TIME to Quicktime is incredibly shortened (1/3 to 1/2 the time).
    That's interesting. I've noticed that simple projects (i.e. not much cuts) export faster than real time to Full Quality .dv. But complex projects take MUCH longer to export as .dv. AFAIR this didn't matter in iMovie 1-4. Maybe the blanket title simplifies the relevant parts of the project?
    [sigh] I wish we didn't need to be aware of the plethora of obscure gotchas and workarounds like this. I don't expect there to be an iMovie HD 5 update anymore. I guess some bugs will be fixed and some brand new bugs will be introduced in v6.
    The same thing happened with iMovie 4 bugs. ...So this time I thought to quickly gather AND report all iMovie 5 bugs to Apple so they could quickly fix them during the first months. ...but it seems that the iLife team just isn't granted enough resources to fix them. Many known old bugs are again just described in the knowledgebase articles.

  • GPU Acceleration causes random frame in encode?

    New Mac Pro (6 core, d500 cards, 32GB RAM, OSX10.9.4). Adobe Media Encoder CC 2014.0.1. Tested on two separate machines of the same configuration.
    I have a just over 2 hour long 1080p ProRes file that I was encoding to MPEG2 for DVD. During QC of the disc, a random frame from another part of the movie was found in a spot about 39 minutes into the encode. The issue was in the encoded MPEG2 stream.
    The client also wanted a lower resolution h264 proof of the video, and that was encoded on the same machine at a separate time. That had the same random frame at the exact same spot.
    I encoded the preview h264 in just a few minute segment of the video around the glitch on the second Mac Pro. It showed up again. I used the same setting but turned off GPU Acceleration, and the frame is gone.
    Does anyone have any ideas as to what is going on here? Obviously there is a problem with GPU acceleration on the new Mac Pro's with Media Encoder, but what could be specifically causing it and what could be done to fix this? With all of the issues in Premiere and After Effects, some of which are being caused by software updates, and the issues with the one Mac Pro needing to be replaced due to bad video cards, I feel like there is just a ton of problems that didn't exist on our outdated Mac Pro with Final Cut Pro 7.
    Please let me know of any ideas to make me not doubt every encode I do on these machines with GPU Acceleration turned on. Thanks.
    -Phil

    Does anyone have any additional ideas on this? I heard from the CreativeCow forums that this has been a known bug with GPU Acceleration on the new Mac Pros. Is this the case? Has anyone else had this issue looked at by Adobe?

  • Play random frames

    I am trying to make the movie play random frames when it is
    opened using the following script:
    gotoAndStop(random(13)+2);
    I managed to do this successfully using numbers in each frame
    to see where the movie was but then found that when I added
    content(images and movie clips) to the frames a blank screen (that
    didn't exist )kept appearing at random intervals and some of the
    content in certain frames was missing.
    Does anyone know why this is or have an alternative script or
    method I can use for the randomisation i need?
    p.s I am using Flash 8

    You have to wait until a frame is loaded before you can go to
    it.
    In the first frame:
    // wait for all frames to load before jumping to random
    this.onEnterFrame = function(){
    if(this._framesloaded == this._totalframes){
    this.onEnterFrame = undefined;
    this.gotoAndStop(random(13)+2);
    Alternatively, you could check if a range of frames is
    loaded:
    this.onEnterFrame = function(){
    if(this._framesloaded >= aframenumber){...}
    "Dilroy" <[email protected]> wrote in
    message
    news:e2o0s5$l61$[email protected]..
    > I am trying to make the movie play random frames when it
    is opened using
    the
    > following script:
    >
    > gotoAndStop(random(13)+2);
    >
    > I managed to do this successfully using numbers in each
    frame to see
    where the
    > movie was but then found that when I added
    content(images and movie clips)
    to
    > the frames a blank screen (that didn't exist )kept
    appearing at random
    > intervals and some of the content in certain frames was
    missing.
    >
    > Does anyone know why this is or have an alternative
    script or method I
    can use
    > for the randomisation i need?
    >
    > p.s I am using Flash 8
    >
    >

  • Master Pages and Buttons - Bug and Fix Request

    I think I'm the only person in the world who has encountered this bug, and I've filled out the bug report form on the Adobe site twice in a couple of years.
    Just wondering if anyone else has encountered it, and I'm curious to know if it still exists in Creative Cloud (I'm still using CS6).  However, I think this bug appeared in CS5.5, prior to that, results were as one would expect.
    So here's the gist of it . . .
    Prior versions of InDesign allowed you to put a button on a Master Page, then upon export to PDF the page number would be appended to the button name. CS6 appends random numbers to the button names on export.  (It seems the number appended to the button names is the instance count of the button in question.)  This problem becomes incrementally worse if you use different combinations of master pages, some with buttons and some without.
    Steps to reproduce bug:
    Create a button, named "menubutton" and add it to a master page
    Apply that master page to 10 pages.
    Export the ID file to PDF enabling buttons and interactive elements.
    Check the button names in the PDF from Acrobat
    Results:
    In CS6, this now appends the page number, and an arbitrary number to the button name.  CS6 results are like such: "menubutton.Page 1", "menubutton.Page 21", "menubutton.Page 32", "menubutton.Page 43", etc.
    Expected results:
    The button names should become "menubutton.Page 1", "menubutton.Page 2", "menubutton.Page 2" , etc. (As in prior ID versions)
    The problem becomes a lot worse when you use combinations of master pages . . . for example:
    Master A – contains one button – menubutton
    Master B – contains one button – otherbutton
    Apply those masters to alternating pages, like below and export to PDF, this will be the crazy result:
    Page 1 (A)        “menubutton.Page 1”
    Page 2 (B)        “otherbutton.Page 2”
    Page 3 (A)        “menubutton.Page 31”
    Page 4 (B)        “otherbutton.Page 41”
    Page 5 (A)        “menubutton.Page 52”
    Page 6 (B)        “otherbutton.Page 62”
    Page 7 (A)        “menubutton.Page 73”
    Page 8 (B)        “otherbutton.Page 83”
    So, can anyone else attest to this?  It makes scripting buttons incredibly hard!

    Hi johnjohn123,
    1. I would definitely make a copy of the EnterpriseWiki.aspx page layout and make changes to that. You can then set your pages to use your custom page layout. Typically, I provision these via Visual Studio and a module for uploading them to the SharePoint
    master page gallery.
    2. For the master page, the html version is new to 2013 and is meant to simplify branding, however, it's not required. You can still work within master pages and provision those via features if you'd like. The key is to create your own master page and never
    modify the default.
    If you need code samples for any of the above, let me know and I can supply it.
    Shereen Qumsieh http://sharepointdeveloperhq.com @msshushu

  • Motion 5 won't export, keeps seizing on a random frame

    There isn't much extra to explain, I was trying to stabalize some video, and everytime that I tried to export it would randomly die on me.
    Does anyone know why? The only extra thing that I can think of that might be important is the size of the clip (it was a 20:00 1080p clip shot from a Nikon DSLR) but the frames it continued to die on were in the first minute; once only 20 seconds in and before the first spot that I was trying to stabalize.

    Take a look at this thread and see if the solution helps.
    Mavericks and Motion error -1

  • Standard FICA datasoources ate missing- Alternative solution

    Hi All,
    Our ISU system is in ECC6 with out any Ehp. CRM-2005 is connected with ISU system through middleware.
    We are missing standard FICA BW datasources( 0FC_BP_ITEMS,0FC_DUN_HEADER,0FC_DUN_ITEMS) due to unavalability of Ehp in the ISU system.
    If Ehp will be apply to ISU system, CRM system need to be upgraded to CRM7 which is not feasible in current time.
    As per BW implementation we need to use these extractors which are based on important FICA tables.As the base table for these extractors will have huge volume of data(Utilities Industry).
    Request you to help us the alternative solution for this without upgrading any Ehp in the ISU system. If we will create custom extractors performance issue may come.
    I have refered the Blogs where performance issue is mentioned for custom extractor.
    Regards,
    Asish

    You listed two of the best options possible...
    1) Upgrade ECC to EHP2 and CRM to CRM 7.0.
    2) Create generic DataSources from the source tables.
    The only other option you would have is to create a remote-enabled FM in your source ECC environment to extract data out of the source table(s) and insert into an ITAB, create an ABAP program in your BW environment that calls the remote-enabled FM and receives the extracted data ITAB and then load that data into a custom table in BW. Then create a generic DataSource on that custom table in BW. Realize, this would pretty much be the same as creating a generic DataSource on the ECC environment, but would be more easily replaced when you do eventually update and potentailly move to the standard content DataSources.

Maybe you are looking for