Muse Script Errors During Startup. Also Dreamweaver and Premiere Pro Crash during Startup.

I have a brand new iMac i7 with 16gig Ram. Multiple Problems with Applications Launching Successfully.
Error: HTMLLoader failed to initialize
          at flash.html::HTMLLoader/initHTMLEngine()
          at flash.html::HTMLLoader()
          at mx.core::FlexHTMLLoader()
          at mx.core::ClassFactory/newInstance()
          at mx.controls::HTML/createChildren()
          at com.adobe.muse.widgets::MuseHTML/createChildren()
          at mx.core::UIComponent/initialize()
          at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
          at mx.core::UIComponent/addChildAt()
          at spark.components::Group/addDisplayObjectToDisplayList()
          at spark.components::Group/http://www.adobe.com/2006/flex/mx/internal::elementAdded()
          at spark.components::Group/setMXMLContent()
          at spark.components::Group/createChildren()
          at mx.core::UIComponent/initialize()
          at com.adobe.muse.widgets::BaseAttachingWidget/initialize()
          at com.adobe.pash.ui::DocumentCanvas/initialize()
          at com.adobe.pash.ui::PreviewCanvas/initialize()
          at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
          at mx.core::UIComponent/addChildAt()
          at spark.components::Group/addDisplayObjectToDisplayList()
          at spark.components::Group/http://www.adobe.com/2006/flex/mx/internal::elementAdded()
          at spark.components::Group/setMXMLContent()
          at spark.components::Group/createChildren()
          at mx.core::UIComponent/initialize()
          at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
          at mx.core::UIComponent/addChildAt()
          at spark.components::Group/addDisplayObjectToDisplayList()
          at spark.components::Group/http://www.adobe.com/2006/flex/mx/internal::elementAdded()
          at spark.components::Group/setMXMLContent()
          at spark.components::Group/createChildren()
          at mx.core::UIComponent/initialize()
          at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
          at mx.core::UIComponent/addChildAt()
          at spark.components::Group/addDisplayObjectToDisplayList()
          at spark.components::Group/http://www.adobe.com/2006/flex/mx/internal::elementAdded()
          at spark.components::Group/setMXMLContent()
          at spark.components::Group/createChildren()
          at mx.core::UIComponent/initialize()
          at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
          at mx.core::UIComponent/addChildAt()
          at spark.components::Group/addDisplayObjectToDisplayList()
          at spark.components::Group/http://www.adobe.com/2006/flex/mx/internal::elementAdded()
          at spark.components::Group/setMXMLContent()
          at spark.components::Group/set mxmlContent()
          at spark.components::SkinnableContainer/set mxmlContent()
          at spark.components::SkinnableContainer/createDeferredContent()
          at spark.components::SkinnableContainer/createContentIfNeeded()
          at spark.components::SkinnableContainer/createChildren()
          at spark.components::Application/createChildren()
          at mx.core::UIComponent/initialize()
          at spark.components::Application/initialize()
          at spark.components::WindowedApplication/initialize()
          at com.adobe.pash.air::PASHonAIRApplication/initialize()
          at MuseOnAIR/initialize()
          at mx.managers.systemClasses::ChildManager/childAdded()
          at mx.managers.systemClasses::ChildManager/initializeTopLevelWindow()
          at mx.managers::SystemManager/initializeTopLevelWindow()
          at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::kickOff()
          at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()
          at flash.events::EventDispatcher/dispatchEventFunction()
          at flash.events::EventDispatcher/dispatchEvent()
          at mx.preloaders::Preloader/timerHandler()
          at flash.utils::Timer/_timerDispatch()
          at flash.utils::Timer/tick()
AND
TypeError: Error #1009: Cannot access a property or method of a null object reference.
          at mx.controls::HTML/measure()
          at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::measureSizes()
          at mx.core::UIComponent/validateSize()
          at mx.managers::LayoutManager/validateSize()
          at mx.managers::LayoutManager/doPhasedInstantiation()
          at mx.managers::LayoutManager/doPhasedInstantiationCallback()
Please Help!

1st idea... uninstall and reinstall
Discussions of RE-installing
-http://forums.adobe.com/thread/1398961?tstart=0
-and http://helpx.adobe.com/creative-cloud/help/install-apps.html
-http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
2nd idea... ask program questions in the individual program forums
If you start at the Forums Index http://forums.adobe.com/index.jspa
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll

Similar Messages

  • After download and installation, InDesign, Flash, Dreamweaver and Premiere Pro all won't fully launch.

    After download and installation, InDesign, Flash, Dreamweaver and Premiere Pro all won't fully launch. From the Windows icon pane, I click on the program, it opens the Sign In Required pane, I sign in, it opens the Thank You pane and reverts back to Sign In pane or never opens the program.
    Acrobat also keeps giving me a popup to sign in, each time I look at a .pdf file.
    I have tried uninstalling Acrobat and then redownloading. It didn't work.
    Anyone else find a fix?

    Sign Out When Sign In http://forums.adobe.com/thread/1450581?tstart=0 may help
    -and http://helpx.adobe.com/creative-cloud/kb/unable-login-creative-cloud-248.html

  • Bootstrap.js script error during eval() "Error initializing JDF library"

    bootstrap.js script error during eval(). Everytime I open Adobe Acrobat 6.0 I recieve this error message once it loads up. I also recieve another error messeage while it is in the process of loading "There was an error while loading the plug-in "SaveAsXML.api.' This file was not found. I am wondering if this is why I cannot convert a file to PDF from word when I go to convert from file from adobe acrobat 6.0. It is vital to my business that I convert these files from Word. Even when I try to go to Adobe Distiller the error message "Error initializing JDF library"  pops up and will not allow me to convert my file to PDF  
    Thank you       

    Hello,
    I solved the problem (even if I really don't know how) :-/
    What I did :
    1. remove all the environnement variables for ORACLE : ORASID, ORACLE_SID, ORAHOME, ORACLE_HOME, ORACLE_BASE...
    (I don't know why I have so many variables...)
    2. I remove any varible of LANG (NLS_LANG, ORA_LANG...)
    3. I checked the rpm (it seems that some of the library where missing, for example libXtst.so.6)
    By the way, I installed the patch 6078836. Unzip the patch, it will create the library libdb.so.2. Move this file to /usr/lib
    4. I uninstall first the agent and the oms, then the database.
    5. I reinstalled everything and run the ConfigureGC.pl script. I had to go through the bug 7483221 (the script failed twice because of invalid login/password, ORA-01017). The procedure is described on several sites, I used this one :
    [http://www.idevelopment.info/data/Oracle/DBA_tips/Enterprise_Manager/OEM_10.shtml]
    I hope it will help you to complete the installation.
    Regards

  • Error message: "Warning: unresponsive script". Afterward, the system freezes and will then crash. Crash reports have been submitted many, many times without response. I have tried the fore-mentioned solutions with either no results or very bad results

    Error message: "Warning: unresponsive script". Afterward, the system freezes and will then crash. Crash reports have been submitted many, many times without response. I have tried the fore-mentioned solutions with either no results or very bad results which I filed a report but did not receive an answer. The application to block scripts actually worsened the problem and I could not correct the situation for a while (no response from Firefox, at all). I have also been through this procedure without any one contacting me, AT ALL.
    == URL of affected sites ==
    http://http://www.facebook.com (always) and www.YouTube.com (sometimes)

    There does appear to be any support whatsoever from mighty "non caring" FIREFOX & people are getting fed up. We may as well try another system, if they can't be bothered to provide any support for their system, we can't be bothered to use their system.
    Brianeng

  • I am getting script errors on startup - Script: chrome://global/content/bindings/browser.xml:194 WHY?

    The last couple of days I have been getting script errors on startup - Script: chrome://global/content/bindings/browser.xml:194 ,
    I am also getting shutdown errors when I power down "end program" types including sgtray.exe, hkcmd.exe, directcd.exe, msascui.exe, d3d9window.exe,
    Some of these are associated with programs I use but have not caused problems previously.

    This post can help you with your problem : https://support.mozilla.org/en-US/kb/warning-unresponsive-script
    Hope it helps :)

  • After Effects CS6 and Premiere Pro CS6 Long Startup and Application Hang

    Problem:
    After Effects and Premiere Pro CS5.5 and CS6 are very slow to start all of a sudden.  Around 5 minutes to get to/by the intro dialogue box.  For AE, the majority of the time is spent on the "initializing user interface." Then, if I can make a comp, and even a layer inside that comp, it will "Hang" if I attempt to open AE's General preferences for example (no preferences window ever comes up).  This "hang" is what the Event Viewer in windows calls it, with the faulting module being afterfx.exe.  Premiere is not much different.   It makes it to the new project window fast, but after setting project parameters and creating the first sequence, I can't get into the preferences either and the application hangs.  It is important to note that if I have another application open, like Chrome or Firefox for example at the time the application hangs, they will freeze as well.  As soon as I kill the Afterfx.exe process, they come back to life.
    I have read nearly all threads on the subject, and am struggling to find a solution:
    Deleted preferences folder under my username's appdata.
    Turned off Firewall (network traffic from dynamiclink, qtserver, etc was allowed, but what the hay)
    ran windows system file checker/malwarebytes/rkill/rootkit detection.
    checked for windows compatibility checkboxes under the file.
    Uninstalled Wacom Tablet drivers
    Disabled Aero
    Started with ctrl-alt-shift to delete pref.
    uninstalled video driver and replaced with one 6 months ago.
    uninstalled, reinstalled, and tested various quicktime versions back to version 7.69
    moved plugins folder
    moved opengl's plugin out of the folder temporarily
    Disabled all 3rd party codecs (xvid was the only one installed and for months)
    reinitialized default directshow filters
    checked for adobe font list (none found) and removed any fonts from 1 month ago to present.
    used msconfig to selective startup without other applications/services running.
    Uninstalled all adobe products, and reinstalled.
    I performed all of these in a systematic manner, trying to solve the problem.  None have fixed the problem.
    So it doesn't seem to be a network issue, a codec issue, a plugin issue, a driver issue, font issue, or conflicting application.  Any thoughts?
    System Info:
    PC Windows 7 pro 64-bit SP1
    Core i7 - 960 24GB ram
    AMD Radeon 6750  v12.10
    Adobe CS6 Master Collection

    Who's says that Microsoft can't debug?
    I used msconfig, first disabling startup items, -same result.
    Enabled all startup items, disabled all non-microsoft services - AE worked!
    I re-enabled each service in turn until AE crashed.
    The fault was related to an item for a video streaming device I have in my house.  It was Monsoon-multimedia's Vulkano Service.  Sometimes under the old name of Hava, this is an app that acts like a sling-box to send my Cable TV to my screen.  It does load a couple of virtual devices in device manager, and uses a proprietary codec.
    I uninstalled the vulkano streamer application and rebooted the external Vulkano device.  I reinstalled the Vulkano and verified it connected to the device and could stream.  Once it did, I tried AE again and IT WORKED!
    I wonder if simply rebooting the Vulkano would have fixed it.  Its like opening the garage door to turn on the refridgerator.
    Thanks for the help!
    Jim

  • Getting a U43M1D204 error when trying to update After Effects and Premiere Pro

    Getting a U43M1D204 error when trying to update After Effects and Premiere Pro. I have tried reinstalling the cloud installer and all of my programs with no luck. HELP!! I need the update because I have no direct link from Speedgrade back to Premiere Pro

    See if the following posting helps: http://forums.adobe.com/message/4629442#4629442

  • How to activate Studio 8 won't accept serial number of my previous versions of Dreamweaver and Flash Pro

    In order to complete Studio 8 activation, I was asked to provide serial numbers of older version of Dreamweaver and Flash Pro. I did but it won't accept it.
    Kindly help to resolve this issue

    Jeff A Wright wrote:
    I know that both Dreamweaver MX 2004 and Flash MX 2004 are two versions later than version 8.0.
    Other way round, Jeff - MX 2004 is one version earlier.
    MX 2004 (version 7) pre-dated Studio 8 (version 8) by two years.
    Adobe Creative Suite - Wikipedia, the free encyclopedia
    Macromedia Studio MX 2004 Released September 10, 2003, despite its name, it is internally version 7.
    Macromedia Studio 8 Released September 13, 2005, Studio 8 was the last version of Macromedia Studio.
    I have always found it odd that MX 2004 owners have been provided with non-activation serial numbers by Adobe.
    However, Studio 8 owners (later version software) have been left stranded with no non-activation serials and no way to activate their software when they re-install. What do they do?

  • PreludeCC and PRemiere Pro CC will not update  error: " log Transport 2"

    PreludeCC and PRemiere Pro CC will not update . update gets to 62% and then quits with the following error code "Log Transport 2"
    System
    OS 10.9
    MacPro 3,1
    All other apps do update.

    HI Steve & Perry,
    Have you tried restarting the machine and applying the updates again ? If yes, are you still getting the same error message ? If yes , could you please share a screen shot of the error that you get ?
    Cheers,
    Kartikay Sharma

  • Adobe Premiere CC Trial Version "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down." PLEASE HELP!

    Every time I open any project in Adobe Premiere CC Trial Version, I get the message "Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will try to save your project." I can't edit at all and am totally stuck. Please help!
    It's terrible that this is happening on the trial version as it's making me want to go straight back to FCP! Also - I've tried switching external hard drive and that also doesn't work.
    Thank you!

    So, opening a new project works?

  • Why Do Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up.

    Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up. 32 bit version of Photoshop works fine.
    Here is the problem signature when they crash.
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Photoshop.exe
      Application Version:          12.0.0.0
      Application Timestamp:          4bbc5b10
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7602
      Fault Module Timestamp:          4b980c97
      Exception Code:          c0000005
      Exception Offset:          0000000000073a92
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          7c82
      Additional Information 2:          7c821a1fc13b00b508d1bb6ee7ecaf44
      Additional Information 3:          019c
      Additional Information 4:          019cb6db15489631b8a43faf27e30830
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Adobe Premiere Pro.exe
      Application Version:          5.0.3.0
      Application Timestamp:          4ce382d1
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7449
      Fault Module Timestamp:          4b7b1af3
      Exception Code:          c0000005
      Exception Offset:          00000000000739ea
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          889a
      Additional Information 2:          889afed61eb6ddf1c1c3419adc6026b6
      Additional Information 3:          8235
      Additional Information 4:          823549a371dff618695395cc0a8514ee
    Both are referencing cooltype.dll. I ran Font Doctor on all system and non-system fonts and found no errors. Booted without Extensis Suitcase loading. Nothing works. All 32 bit programs work fine. Any clues would be appreciated.

    It does not necessarily mean a "corrupt" font, but can be a font that PrPro, and PS, cannot handle.
    Though I have read that changes have been made, Open Office's DejaVu font would crash PrPro's Titler - every time. There are quite a few others. Font Dr, and similar utilities, will not see the font(s) as corrupt, but they are so poorly designed, that PrPro and PS cannot deal with them.
    Though it can be a long, drawn out process, one can often zero in on the problem font(s), with a little work. This is accomplished by first defining the "System Fonts," and not touching them. Then, uninstall half of the remaining fonts, and testing PrPro and PS. If they launch fine, you know that somewhere in that list of fonts, the problem exists. If there is still a failure to launch, chances are good that the problem font(s) reside in that half, that are still installed. Note: because the problem still exists, does not guarantee that there are NOT problem fonts in that uninstalled group, so keep that in mind.
    Repeat the proces, by uninstalling half of the remaining fonts and testing.
    If necessary, repeat by removing half of the now remaining fonts and testing.
    When you get to a point, where you are no longer getting problems, reinstall fonts, in small groups, testing in between. The smaller the groups, the easier it will be to pinpoint the problem font(s).
    Keep notes on which fonts you are uninstalling and reinstalling, until you narrow it down to the problem font(s).
    I would start by uninstalling any "free fonts," and then commercial, 3rd party fonts. A lot of free fonts are just poorly designed, and can cause issues, though they might work fine in some other programs.
    I use a font manager, so that I only have ~ 350 fonts installed at one time, and then dynamically install fonts, as needed for Projects. That keeps my machine clean, and if, upon installation, I get a crash/hang, I know that at least one font in that Set is causing it. This helps, as my workstation has ~ 19,000 fonts on it, and some are free fonts, and many are from 3rd parties. Some are also very, very old.
    Good luck,
    Hunt
    PS - one common cause for hangs on loading PrPro can be from VST's, used in Audio-editing. If you also have a lot of VST's, you could have two issues with two separate programs, i..e. PS hanging on fonts, and PrPro hanging on VST's. The results would be the same, but the causes could be different. That leads to even more work. For PrPro, also see this ARTICLE. If you get PS launching, but PrPro is still not functioning, drop by the PrPro Forum, and someone can help you there.

  • Another: a serious error has occurred that requires Adobe Premiere Pro to shut down

    I know a few people have had the same notification:
    sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project
    I have tried a whole series of things to fix it and no luck. Here are all the computer stats... does anyone have any ideas???
    Premiere Pro
    Version number: CS5, with most recent update
    Installation language: English
    Updates applied: Most recent… installed AFTER problem started
    Project/sequence settings… NA
    Operating System
    Name: Windows 7, 64bt
    Update/patch level: Service Pack 1
    Installed language: English
    Display resolution and color depth. 1920x1080; 32bit color
    CPU type and speed Core i7 950
    Amount of memory (RAM) 12GB
    Video card 
    Manufacturer: Nvidia
    Model: FX3800
    Driver version: Latest (installed after errors started)
    Number of monitors (displays): in use 2 (with one disabled for testing)
    Audio card
    Manufacturer Gigabyte Technology 82801J HD Audio Controller
    Model
    Driver version: 6.1.7601.17514 (latest version)
    Each hard drive's capacity and space remaining Disk setup (partitions used, raid configuration, what is where for OS/projects/media/scratch/audio)
    C and D, no partitions. D is raided, controlled by hardware controller. All software on C. Media kept on D.
    Hardware capture device NA
    Manufacturer
    Model
    Driver version number
    Capture software NA
    Name
    Company
    Version
    Comprehensive list of third-party plug-ins you installed.
      None for Premiere I don’t think. A couple for After Effects. Have been installed for a while with no recent updates.
    Exact text of any error messages
    sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project
    Explain clearly what you want to do, what you are doing and what the result is
      Open Premiere to do some work 
    Be sure to mention if it is something that worked before using the same procedure
    Nothing has changed on the PC prior to program failure.
    Very importantly: Post details of troubleshooting you have already done to avoid "did that" reponses to questions people ask when trying to help.
    Tried:
    Reinstalling
    Reducing to one screen.
    Holding Shift when starting until first screen (New/ Open Existing/ Help)
    Holding Ctrl, Shift Alt when starting until first screen (New/ Open Existing/ Help)
    Programme crashed regardless of clicking directly on loading icon and opening New or Existing via first load screen, or via clicking directly from a project file.
    Removed all fonts installed since last opened.
    Restarting.
    Updated Graphics Driver.
    Updated Premiere

    Hi guys; I thought I would share my experience and how I managed to fix this problem. It might help someone.
    In my case I kept receiving this message; eventually after re-launching Premiere, I actually paid close attention to the "software loading" information and saw that it got stuck on my installed "Colorista ii" which is a colour grading software.
    Now the red bulb came on my head ping!
    I recently just upgraded my Mac to the OS X Yosemite & that affected pretty much any non-updated application, which in my case was that and many more of the Red Giant Pacakge; so I searched for the upgrade via Red giant Link, and low and behold I found it and did so. Immediately everything loaded up perfectly fine.. and now can't even do the work, cos I'm so exhausted from an 'almost heartattack'; so going to sleep and commence later in the day I guess..
    Now, you might probably want to check if any application on your system needs upgrading to whatever is the operating system on your Mac or PC at this very time. It might help.
    Always back-up.
    I hope I helped someone :-)
    @ToleXElijah
    Extreme Studio Manager

  • 'Sorry a serious error has occured that requires Adobe Premiere Pro to shut down. We will attempt to save your current project'. What is the solution? (Mac)

    There is an error that says when I am open my project: 'Sorry a serious error has occured that requires Adobe Premiere Pro to shut down. We will attempt to save your current project'. What is the solution? (mac)

    This happens to me all the time too. When I attempt to reopen, it makes a "copy of" my project. This is frustrating and happiness often.

  • Sorry, a serious error has occured that requires adobe premiere pro to shut down

    Every time I start premiere pro, i get this message
    Sorry, a serious error has occurred that requires adobe premiere pro to shut down. We will attempt to save your current project.
    I have no idea why this is happening because the program has been working fine for nearly 7 months.
    My ram is 2gb, I have a c2d processor and a powerful psu and a gfx card.
    Any ideas as what I can do, I have already reinstalled, removed vst plugins and reset all sorts of preferences and caches.
    THank you

    Head to the Adobe site's 'knowledgebase', type optimise CS3 for (Windows XP, if that's what your using) and following the instructions there, house clean. I find doing this helps clean out those nasty messages

  • "A Serious Error Has Occurred That Requires Adobe Premiere Pro to Shut Down"

    "A Serious Error Has Occurred That Requires Adobe Premiere Pro to Shut Down" Pops up every time I export a video.. I have 2 TB of space where i'm exporting so thats not the issue... I'm using RED Giant Pluraleyes to match multiple cameras but other then that, there are no other 3rd party plug ins being used...
    This is very frustrating. I'm using updated CC and have tried shutting down the computer (iMac) and tried exporting to different locations on and off my HDD.
    What am I supposed to do?

    So, opening a new project works?

Maybe you are looking for