Corona version mismatch.

[zules]

Corona version mismatch. Slave version: 1.6 (hotfix 3), Master version: 1.7
The image may come out wrong (e.g. darker or missing objects) because of this.   

I reinstalled 2 times Corona on this specific node, still the same log.

[Frood]

Do you have multiple Max versions installed on that node?


Good Luck

[zules]

Nothing like that... just a simple node : 1 max 1 Corona

[pokoy]

I had this happen often after installing a new version on the DR nodes. However, it's something that resolved itself magically... maybe you need to restart the machines after installing Corona?

[zules]

Yes I will ty this !

Also, some node wait the render to start forever... when the other render correctly. Weird...

[maru]

Try this:
1. Uninstall Corona from the Windows "Programs and Features" list
2. Restart PC
3. Install 1.7 again

[zules]

I ill try that asap thank you !

[hrvojezg00]

I ill try that asap thank you !

Working?

[zules]

On it !

[zules]

Try this:
1. Uninstall Corona from the Windows "Programs and Features" list
2. Restart PC
3. Install 1.7 again

Solved ! :)

Thank you for this dummy question !

[maru]

That's not a dummy question. I have just saved this in our internal bug tracker.
It seems that sometimes 1.7 is installed incorrectly over an old installation of 1.6.
I can imagine this could cause some other issues.

[pokoy]

That's not a dummy question. I have just saved this in our internal bug tracker.
It seems that sometimes 1.7 is installed incorrectly over an old installation of 1.6.
I can imagine this could cause some other issues.

FYI, I had this happen with 1.5 and 1.6 dailies, too, not only 1.7 over 1.6. DR slaves would always report a version mismatch even if all the files were on new versions when checked manually. Not on all DR servers, though, which makes it a bit more mysterious.

[hrvojezg00]

That's not a dummy question. I have just saved this in our internal bug tracker.
It seems that sometimes 1.7 is installed incorrectly over an old installation of 1.6.
I can imagine this could cause some other issues.

FYI, I had this happen with 1.5 and 1.6 dailies, too, not only 1.7 over 1.6. DR slaves would always report a version mismatch even if all the files were on new versions when checked manually. Not on all DR servers, though, which makes it a bit more mysterious.

Did this issue affect render nodes speed in any way?

[pokoy]

That's not a dummy question. I have just saved this in our internal bug tracker.
It seems that sometimes 1.7 is installed incorrectly over an old installation of 1.6.
I can imagine this could cause some other issues.

FYI, I had this happen with 1.5 and 1.6 dailies, too, not only 1.7 over 1.6. DR slaves would always report a version mismatch even if all the files were on new versions when checked manually. Not on all DR servers, though, which makes it a bit more mysterious.

Did this issue affect render nodes speed in any way?

Didn't look like it did.

[zules]

That's not a dummy question. I have just saved this in our internal bug tracker.
It seems that sometimes 1.7 is installed incorrectly over an old installation of 1.6.
I can imagine this could cause some other issues.

FYI, I had this happen with 1.5 and 1.6 dailies, too, not only 1.7 over 1.6. DR slaves would always report a version mismatch even if all the files were on new versions when checked manually. Not on all DR servers, though, which makes it a bit more mysterious.

Same same
Did this issue affect render nodes speed in any way?

Didn't look like it did.

[Luis.Goncalves]

I've ad this issue on one of the render farm machines. Funny enough we have 9 PCs that in theory are the same but only one of them ad this issue. (I also fixed it by uninstalling and reinstalling corona).

Edit:I've just checked and i'm having this in all of them (just ad to check the log). I'm wondering if this is happening because it's a scene created in 1.6.. I'll do some tests tomorrow

Edit2: I've reseted Corona settings on my maxstartup file and on ongoing projects, and I've also manually uninstalled corona from all of the machines and reinstalled them (and apparently that fixed the problem)