Skip to main content
jot64467005
Participant
August 18, 2015
質問

Has anybody ever had a random window "Microsoft Visual C++ Runtime Library" pop up stating a vulcanjs.node error? It doesn't stop me using photoshop CC but randomly occurs at least once per day. How do I fix this error?

  • August 18, 2015
  • 返信数 9.
  • 39383 ビュー

    このトピックへの返信は締め切られました。

    返信数 9

    Participant
    February 12, 2021

    **SOLUTION****

     

    GO TO:

    local disk/program files/adobe/adobe creative cloud experience/libs/ node

    rename to node.off

     

    Restart computer.

     

    Participant
    May 21, 2021

    Thanks brother...😊

    June 18, 2017

    Thanks for pointing me in (hopefully) right direction!

    Since I don't intend to use the CC Libraries functionalities, I'm trying to fix this the good old dirty way...

    I have located these files:

    CCLibrary.exe
    in C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCLibrary

    and

    CCXProcess.exe

    C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCXProcess

    I have closed them via Windows Task Manager and I renamed them to CCLibrary.exe.off and CCXProcess.exe.off respectively to prevent them from running automatically again.

    The applications themselves (Photoshop, Illustrator, InDesign) seem to be running fine so far.

    I will update if I see the error again (or confirm if it doesn't pop up in next few days - it was popping like 10 times a day, so I guess I will find out quite quickly if this helped)

    Participant
    March 13, 2020

    Thanks, now everything working fine!

    March 31, 2016

    Is adobe comming with a fix for this problem?

    We tried reinstalling Visualc++ but this did not resolve anything.

    We are running Win7 and problem occurs on 3 pc's.

    Participant
    February 26, 2016

    Hi, i reinstall all Visual C++, but nothing

    CVB_Josh
    Participant
    February 17, 2016

    Same issue here. I'll try the suggested C++ repair and the link provided by Akash.

    Participant
    November 30, 2015

    It´s just three days ago that I´m having the same problem. How will I have to fix it? When will we get a solution?

    Thais W
    Participant
    August 19, 2015

    An user here at the office is having the exact same error message, while working on random applications and it also happens once a day.

    I've found that vulcanjs.node resides on %PROGRAMFILES%\Adobe\Adobe Creative Cloud\CCLibrary\js\node_modules\node-vulcanjs\build\Release

    But why is it happening, what it is impacting and how to stop it?

    jot64467005, did the suggestion from Akash Sharma worked for you?

    Thank you.

    Terri Stevens
    Legend
    August 18, 2015

    I think this relates to the server used to provide the functionality for the new Library Panel features in Photoshop 2015. So you probably won't see anything wrong if you are not using the library when the error occurs. You could try closing the Library panel for a couple of days and see if the runtime error goes away.

    Terri

    Akash Sharma
    Legend
    August 18, 2015

    Hi,


    Please Remove/Repair all the Microsoft Visual C++ Redistributable from the control panel


    below is the screenshot how they will look

    then reinstall the Microsoft Visual C++ Redistributable for 2012 and others

    from the below mentioned link

    Download Visual C++ Redistributable Packages for Visual Studio 2013 from Official Microsoft Download Center

    ~Akash

    Participating Frequently
    October 6, 2015

    We're having the same exact issue as the OP on one of our workstations.  I first attempted a repair of all C++ installations with no success.  Then I uninstalled all C++ installations.  Oddly, prior to reinstalling, I could still open Photoshop and still had the same error message.  I've since reinstalled C++ 2012, 2013, and 2015 and still get the error message.  Would a reinstallation of Photoshop be the next step or does somebody else have another suggestion?

    MissTake - for what it's worth, the the library panel isn't open (for any user on the machine - we've tested with a couple of different users in case it was a profile issue).  This error is appearing immediately upon loading the application.