Announcement

Collapse
No announcement yet.

DR locking up and wscommctr1.exe

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DR locking up and wscommctr1.exe

    Problem with DR locking up and wscommctr1.exe

    I haven't been able to tie it down to an actual cause/effect to make a real bug report, but i am running into an issue here where DR works for 1-2 hours, and then fails.. Restarting max/spawner service fixes it for a while.

    Looking at the servers, there ends up being a few wscommctr1.exe's tying up a full CPU each, These are the 'communication center' for max.

    the error in the log is:
    warning: Could not connect to host ipaddress: No connection could be made because the target machine actively refused it.
    Anyone else running into similar problems at all? or know how i can get rid of/disable the communication center on a slave machine.
    Dave Buchhofer. // Vsaiwrk

  • #2
    yep; have ran into this exact same problem.
    seems to be the autodesk communication centre as you point out.

    Currently not sure how to get rid of it.

    Comment


    • #3
      http://tech-artists.org/forum/showthread.php?t=222

      Post 3 here has how to disable the communication center, I'm giving it a try, so far its working, but haven't been going with it long enough to make a real argument either way yet.

      Seems to have become a real problem lately, i think in conjunction with tightening of the firewall security.
      Dave Buchhofer. // Vsaiwrk

      Comment


      • #4
        You could try using the "Restart slaves on render end" option in V-Ray 1.5 SP3 and see if it makes things any better.

        Best regards,
        Vlado
        I only act like I know everything, Rogers.

        Comment


        • #5
          I'm getting a similar bug. i noticed the DR will show this message if i cancel a render. all renders that i will send after that won't use the DR, and i will have to restart vrayspawner on all slaves.

          Comment


          • #6

            I just tried what was outlined in post 3 and max 2009x64 now crashes on startup. fun.
            Chris Jackson
            Shiftmedia
            www.shiftmedia.sydney

            Comment


            • #7
              Really? Its still working fine here.. May not have been the same issue? When you have a lockup on the slave machine, and view the task manager, are you seeing 4-5 wscommctr1.exe's in the list?
              Dave Buchhofer. // Vsaiwrk

              Comment

              Working...
              X