Run Script Error | Expected: )

[karandeepk49962287]

Every time I open Premiere Pro, I get the message of Run Script Error - Expected: )

I can't seem to find the solution! Does anyone have an idea about this issue and a possible solution?

[Bruce Bullis]

I've run into that several times; most often, when I have a typo in the .jsx of my panel's ExtendScript. 

Have any panels installed? 

[karandeepk49962287]

I did a fresh install of premiere pro, and have been getting this error since I first opened the application

[Bruce Bullis]

Some script is being run, upon launch. Usually, scripts are run from within third party extensions. Do you have any installed?

[karandeepk49962287]

I haven't installed any. Is there any folder, where I can go and fix it?

[Bruce Bullis]

Windows:    C:\Program Files (x86)\Common Files\Adobe\CEP\extensions
Mac:        /Library/Application Support/Adobe/CEP/extensions

Let me know (screenshot?) what folders you see in those directories. 

Are you perhaps launching PPro from a Windows shortcut?

[karandeepk49962287]

I don't see any folder named CEP, Below is the reference for directories.

[Bruce Bullis]

That listing is within \Program Files; could you check in \Program Files (x86)?

[karandeepk49962287]

Here is the directory!

[MPoczynek]

I just did an upgrade to Windows 10 to allow me to use Adobe CC as it would not allow me to install Premiere Pro under Windows 7 and I have the same error with PP and AE.

[Bruce Bullis · Accepted solution]

PPro and AE haven't supported Windows 7 for some time.

When you say "I have the same error with PP and AE", does error mean the run script error (start of this discussion), or does error mean you can't install onto Windows 7?

[MPoczynek]

I have Windows 10 on an i7.  I called Adobe and they said it was my video card and to go to the Adobe site and see whats video cards were compatible.  Which I think is so silly considering I can run everything else on my $1000 video card.  Granted it is old, but should still be able to be used.  I am not happy.  Especially considering I also had to upgrade to Windows 10 as well.  No wonder people are using macs although I much prefer a PC.  Works fine on my iMac.

[countcardboard · Accepted solution]

does this occur when u just open the program or when u r opening a project?

cause i had this error when trying to apply specific effects to footage. the fix was to avoid apostrophes or other special characters / glyphs in both the project (file) name and any footage file name.

[MPoczynek]

It happens when the program opens and I have go through and hit the OK button 6 or so times when the program starts.

[countcardboard]

mh... so u can't fix it by avoiding special characters?... bummer...

[MPoczynek]

No and not impressed with Adobe's answer.  

[Bruce Bullis]

We haven't heard of this issue before; I'm not clear on why avoiding special characters won't work for you? I think MPoczynek's theory is correct, and that whatever script(?) is having problems parsing what it's passed. 

[MPoczynek]

I have never created a project on this program ever.

It is a new install on a computer that has never had PP installed.  

I did Google the issue and there are a number of people reporting this with no resolution.  

After Effects; just installed as well gives me the same error 5 times.  Here is the screenshot:

Adobe Tech Support was quick to tell me it was my video card.  Here are my system specs and PP error clip:

[iamkiddnick]

Mine say's the same im not really sure what to do... Adobe isnt realy giving me any answer's and also whenever i try to speed ramp my footage it like glitches or like skips frames. Is there a solution to this?

[MPoczynek]

Adobe said to me to replace my video card with one they have on their "approved" list.  Found here:  https://helpx.adobe.com/in/premiere-pro/system-requirements.html#gpu-acceleration

[Naflan]

Fix : watch this video to understand the issue and fix it.

https://youtu.be/C2X8581tmDE

[Bruce Bullis]

I don't understand how that video would apply. 

The run script error likely had to do with the panel code being executed, when bringing in media from the panel.