Inspiring

Answered

Cannot execute script in target engine 'main'! (#1116) Can't start debug session.

19 replies
13567 views
Translate

Hi,

This is probably more for staff, but I am getting the above error. I checked the forums and noticed that it can be resolved by resetting system clock, however I am unable to do that as I am on a business machine, so without going through IT, I cannot reset the clock.

Has anyone got alternative solutions?

Many Thanks,

Dale

Actions and scripting

This topic is closed to new replies. Start a new post to keep the conversation going.

Tom RuarkCorrect answer

Inspiring

1. Open the file(Mac): "/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx"

2. Search for the value: 604800000 (line reads bt.timeout = 604800000)

3. Replace that value with 604800 and save

4. Quit ExtendScript Toolkit and relaunch.

[ more info in Extendscript Toolkit: Error Message "(#1116) Can't start debug session." by moderator ]

ryan_edwards

Inspiring

I am using cc 2019 and had a similar issue.... I tried modifying the number mentioned here - no fix.

Then reverted to the initial number and restarted my computer, opened illustrator and ESTK and all seems normal now *phew*

Restarting seems to fix it... my issue was probably leaving my machine on for over a week (aka the time out session)

once I rebooted I believe my session restarted and thus enabled me to run my scripts from ESTK.

I would try this before trying to monkey around with system clock like others are mentioning above.

Translate

C

camjocotem

Participant

This worked for me! I'm honestly quite surprised.

Translate

H

Hoochalaffa

Participant

I am finding that the fix for value: 604800000 is not working as expected. When I run any script from extendscript, the script executes, in my case Illustrator, and then extendscript toolkit is unresponsive. no GUI elements are clickable and commands like ctl + K to stop result in a dialog box to end debugging but doesn't really do anything except cause another dialog box to appear. Is there something I am missing to get estk to be responsive after running a script? I will provide a video if this helps explain what I am seeing.

thanks.

Translate

V

varDale_undefinedAuthor

Inspiring

Worked on my home MBP so, I will get IT at work to solve on the work machine.

Cheers

Translate

Lara_seven

Known Participant

Hi Tom,

I get the same error Snapshot for your refrence:

Translate

Lara_seven

Known Participant

@Tom Winkelmann

Looping with Tom

Translate

Tom RuarkCorrect answer

Inspiring

1. Open the file(Mac): "/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx"

2. Search for the value: 604800000 (line reads bt.timeout = 604800000)

3. Replace that value with 604800 and save

4. Quit ExtendScript Toolkit and relaunch.

[ more info in Extendscript Toolkit: Error Message "(#1116) Can't start debug session." by moderator ]

Translate

V

varDale_undefinedAuthor

Inspiring

Hi Tom,

I get the below error:

Translate

Tom Winkelmann

Inspiring

Because you edit the file with ESTK (which uses the 11BTBackend.jsx)

You can edit the file with ESTK, but you have to save it with a different filename or to an other location. Then close ESTK and delete/rename the original jsx and replace it with the new one or rename the new one with the original name.

You can also edit the file with another editor (but you have to close ESTK in the meantime).

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.