maslan Posted September 13, 2014 Share Posted September 13, 2014 Hi, I am trying to render on Amazon Cloud but after pre flight I get an error saying: WindowsError: [Error 32] The process cannot access the file because it is being used by another process Do you have any idea about it. I removed the antivirus software to be sure. Restarted the computer and reinstalled houdini too but no luck. Windows 7 Houdini Indıe 13.0.509 I hope someone has an idea Thank you. Quote Link to comment Share on other sites More sharing options...
Guest mantragora Posted September 13, 2014 Share Posted September 13, 2014 Try this. Quote Link to comment Share on other sites More sharing options...
maslan Posted September 13, 2014 Author Share Posted September 13, 2014 (edited) Thank you but it doesn't show anything other than hindie process for the scene handle And also a new empty scene with "balls, cam and lights" don't give that error and send to the cloud. But I get an error saying "Error: Invalid .hip file header" and job failes. Thank you Edited September 13, 2014 by maslan Quote Link to comment Share on other sites More sharing options...
maslan Posted September 14, 2014 Author Share Posted September 14, 2014 If anyone have that issue, I managed to solve windows error with process explorer linked by mantragora by killing the handle to the file and also killing hython from task manager. But amazon cloud instance failes the jobs. Even just with a ball and light. First (choose Houdini version) failed and then (submit cloud render) failed. Error message is: Error: Invalid .hip file header Quote Link to comment Share on other sites More sharing options...
kev2 Posted September 24, 2014 Share Posted September 24, 2014 After similar problems yesterday, I contacted support who's working on it. They said: "Our developers agree that this could be a versioning issue. We will update the cloud version this week. For future reference, if a job fails on the cloud, you can find out why by clicking on the View HQueue Jobs link on the cloud web page. Then keep clicking/diving into the failed Child Jobs until you reach the lowest job. The Command Output text area should show the error that caused the failure. You can also download the output to see the full log." Cheers, Kevin Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.