Skip to main content
darshanp09
Participant
October 18, 2018
Answered

A low-level exception occurred in: Adobe Scopes (Transmit::CreateInstance)

  • October 18, 2018
  • 24 replies
  • 142236 views

I got the Adobe Premiere Pro 2019, and after 2 days, this issue came up. I have not been able to use Premiere since then. I re-installed the program, but the issue is still there. What can I do?

    This topic has been closed for replies.
    Correct answer Sumeet Kumar Choubey

    Hi darshanp2386254,

    Sorry to hear that you are facing this issue. Please try to reset Premiere Pro preferences (FAQ: How to reset (trash) preferences in Premiere Pro?) and clear cache (FAQ: How to clean (delete or trash) media cache files? ) to isolate any issues caused due to the corruption of cache or preferences. Hope you find it useful, let us know if you have any questions.

    Regards,

    Sumeet Kumar Choubey

    24 replies

    Mandrila Films
    Participating Frequently
    March 18, 2020

    WORKED! Thanks.

     

    Participating Frequently
    October 24, 2019

    To anyone whose problem isn't permanently solved by resetting preferences: Try deleting your saved Workspace files (they can be found under "Documents/Adobe/Premiere Pro/13.0/[User-Profile]" in the "Layouts" and "ArchivedLayouts" folders). I had this issue for months and kept resetting my preferences only to have the problem come back, but when I deleted my Workspace files, everything returned to proper working order, and I haven't had any issues since the beginning of September, so fingers crossed.

     

    It may be a bit of a pain, having to rebuild your workspaces, but significantly less painful than rebuilding your preferences every week to every day.

    Kevin-Monahan
    Community Manager
    Community Manager
    October 25, 2019

    Thanks, Paul.

    Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
    Participating Frequently
    January 1, 2020

    I've tried every suggestion in this and other threads and nothing is fixing this problem.

    Kevin perhaps you can answer a question:  How is this still a thing?  These threads go back years, how does Adobe send out new releases without fixing this problem first?  This was not a problem for me until i updated a few months ago.  I have to reboot every time this happens, then my file is corrupt as it freezes at the same place in the timeline. Shutting off mercury playback is not a solution as I spent a fortune on graphics cards specifically for use in Premier.  There are so many new bugs in the latest Adobe release of everything - unbelievable.

    So what exactly is being done at Adobe to solve this specific problem....?

    What exactly is "a low level exception.." ?

    Inspiring
    August 10, 2019

    I have not been able to using Adobe Premiere Pro for any length of time without getting this issue. The Program Monitor eventually turns white every single time, wasting time and corrupting the project. I have tried every suggested solution many times to no avail.

    I experienc this on two different systems with two completely different setups.  The only solution I have found is too start completely over in Adobe Premiere 2018.

    Thanks for this Adobe.  FYI, I'm now building an Avid system thanks to 8 months of this nonsense. If we don't pay our subsciption fees, Adobe shuts us down. They can't fix something, and they just keep pushing it out.

    ColbyFulton
    Known Participant
    May 25, 2019

    Resetting my preferences on the Mac by holding down option on startup worked.

    Dear Adobe: please fix the way preference files are saved so they don't become so easily corrupted. This has been an issue for decades.

    Participant
    December 16, 2019

    Hi there,

    what happens to the project I'm working on currently on timeline. Do I loose it or it's safe even after resetting through the preferences?

    pls help

    Participating Frequently
    December 16, 2019

    Resetting your preferences (or deleting your workspace files, as I recommend elsewhere in this thread for a more permanent solution), has no effect on project files, and thus your work. As long as you save regularly, your progress should be (fittingly) safe.

    Participant
    May 6, 2019

    I've reset my preference every other day now and I am still getting this aggravating error. Not to mention the application crashing for any number of other reasons.

    Participant
    April 5, 2019

    I keep having this problem at least once a week. I reset the preferences and it will work well for a few days and then it happens again and freezes premiere.

    Participant
    April 5, 2019

    I wonder where your preferences files are being stored - mine were in a Cloud - iCloud, where it was filling up to capacity and then after I got under the capacity limit again by moving and deleting unused files, I was able to have it work for weeks.

    Participant
    March 14, 2019

    Just relaunched Premiere while holding the option key and I reset my preferences. It looks like it's working now.

    Participant
    March 14, 2019

    The same exact thing for me. I'm Running 2019 ver 13.0.3 on a MacPro running Mojave Ver 10.14.3 when I get the error at first and my source window and preview window are unable to load a single frame. All of my source files are indexed and loaded fine, I just can preview anything. Even the older version of 13.0.2 does the same. The it usually freezes and I have to force quit.

    Twelvizm
    Participating Frequently
    March 13, 2019

    I'm also having this problem on my Mac Pro 6,1.  It's a freshly wiped computer with a fresh install of the CC Suite.  Premiere crashed as soon as I opened my first project.  I cleared the cache on program launch and the program froze after the "clear" prompt.  After force quitting I reopened the app normally, and it gives the "low level error: scopes blah blah" error, hangs and freezes.

    Completely frustrating.

    Additionally I've started a new project, and imported the previous project into it: same issues.

    Finally, I've also moved all the files to the local drive from my RAID 5 Thunderbolt drive: same issues.

    Participant
    March 13, 2019

    I just had this error begin - I've had this computer and software at work since late October 2018

    I can't say I've had a single problem that wasn't a user config issue until now (audio hardware choices not set or iCloud folder as the storage and then iCloud ran out of space, that sort of thing)

    Mac Pro Late 2013 3.5 GHz 6-core INtel Xeon E5, 64 GB 1866 DDR3 with Graphics: AMD FirePro D700 6144 MB

    OS: Mojave 10.14.3

    So far I haven't seen if there was an update in either macOS or Adobe CC that has contributed to this problem, it just didn't want to play the timeline all of a sudden.

    Participant
    February 11, 2019

    hello,

    my solution was to create a new project, with only one image as a reference of the same folder of the original project, putting another name to the project, save in a different location to the folders of auto-saved, Audio Preview of the original project and close, then I opened the original project, everything was fine for me. Then you can delete the project that you created with that image since it only refers to the root of the folders of the images,

    I hope this solution works for you and that you adobe fix this quickly.