ExtendScript won't launch: Photoshop CC 2015.5 provides no engine for debugging

[Dval]

I get the following error:

Cannot execute script. Target Adobe Photoshop CC 2015.5 provides no engine for debugging.

It was fine 3 days ago, when I last ran the script.

Is there any way to get a debugging engine for the current Photoshop CC 2015.5?

Message was edited by: Dylan Valentine Updated Title to be more descriptive.

[KanikaS]

Moving to Photoshop General Discussion​

[JJMack]

Perhaps if you post the script someone here that knows ExtendScript can help.  Some here use EsxtendScript. It does not look like ExtendScript has had an uodate in years.  Pehaps some external thing is need to support CC 2015.5.  I do noy use ExtendScript but, if I start it I see CC 2015.5 in its pulldown menu.

I also get an error starting it but it does start.

[rechmbrs]

If on Windows, try running by administrator on both Photoshop and Extendscript.

RONC

[xbytor2]

FWIW, I just launched ESTK (4.0.0.1, 4.5.5, 6.2.2), loaded a .jsx, and selected 2015.5 as jjmack showed in his post. PSCC 2015.5 fired up just fine. Make sure you have the most recent version of ESTK or find the version of ESTK that I'm using and try that. I have several versions of ESTK because I have a lot of versions of PS some of which require specific versions of ESTK.

-X

[Dale_]

instead of using the dropdown.

Does just using

#target Photoshop

in the first line of your script help?

[rechmbrs]

My note above about admin rights is for a brand new PC install. Windows

just keep changing! ESDK is not a signed product either.

RONC

[Dval]

Dale, thanks. My script does have that line at the top. And I guess the answer is just use the SDK, instead of the Scripting interface. Adobe seems to have stopped linking to info for the ESTK after CC 2015.  So, trying to get support in CC 2015.5 and beyond is most likely hopeless.

I will focus my efforts else where. Thanks to all those who replied.

[Davide_Barranca]

Dval,

ESTK is erratic, to say the least. Mac is known to be worse than Windows. From time to time, it may fire that error (or refuse to run a script, even if the play button icon says it's running). Usually stopping the execution, going back from PS to ESTK a couple of times and waiting few secs solve the issue. Was your problem constantly repeatable or just once in a while?

Davide