Skip to main content
tristanra
tristanra
Participant
April 12, 2016
Answered

Node.js: Server-side JavaScript has stopped working.

  • April 12, 2016
  • 34 replies
  • 95400 views

Hello Everyone,

After the last Adobe Creative Cloud update. I receive this error every second that takes me out of the program I am currently in. (Indesign, Premiere, Aftereffects, Photoshop). I am currently at a stand still, where a similar problem happened less than a month ago with Error: "Evented I/O for V8 JavaScript has stopped working" .

How many problems can you cause with every update Adobe? Can you fix these before updating and how do I fix this one now since I literally slowed to a snails pace with this issue.

Thanks.

This topic has been closed for replies.
Correct answer atjain

Hi Tristan,

          We are terribly sorry for making you have to go through this. Here are some steps that should help solving the issue:

  • Open Start > Control Panel
  • Click on Programs
  • In the programs and features section click on 'Turn Windows Features on or off'
  • Make sure that Microsoft .NET Framework 3.5.1 is not unchecked (A check as well as a blue box as in the screenshot below is ok)

Please reply back to this thread in case you still face issues.

Thanks,

Atishay

Adobe CC Libraries Engineering

34 replies

Show previous replies
R
russellk19203185
Participant
April 17, 2016

Same issue here but deleting node.exe didn't resolve the issue (though node.exe is what is referenced in the details of the error).  Any other thoughts out there?  I tried stopping the creative cloud app from starting at login but that didn't help.

tristanra
tristanraAuthor
Participant
April 18, 2016

I have deleted the node.exe and the error comes up less often, but still comes up.

    H
    Helen Subiaco
    Participant
    May 6, 2016

    I got rid of the evented I/O problem and now this is destroying my processing time. Why is it occuring? why does adobe not

    fix it when they see re all frustrated? Helen

      DMarcos
      DMarcos
      Participant
      April 13, 2016

      Windows 10 is apparently immune, Windows 7 SP1 is affected and I don't know about Windows 8

        DMarcos
        DMarcos
        Participant
        April 13, 2016

        WORKAROUND: Backup and delete C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCLibrary\libs\node.exe

        This is not recommended but will free you to go through this stupid error all the time

          Blue Bear
          Blue Bear
          Participating Frequently
          April 13, 2016

          Other than the obvious workaround benefit, what gets affected by deleting node.exe?

            DMarcos
            DMarcos
            Participant
            April 13, 2016

            I couldn't tell you, for now didn't notice any difference but it is certain that even before deleting it the node.exe wasn't being any helpful because of this error

            Blue Bear
            Blue Bear
            Participating Frequently
            April 13, 2016

            I have the exact same issue.... this is absolutely ridiculous!

              Terms & ConditionsAccessibility statement
              Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices