Rendering license : checkout problem

   2612   3   0
User Avatar
Member
301 posts
Joined: July 2005
Offline
Hi,

I have installed the recent versions of H13 (13.0.729) and H14 (14.0.291) using local licensing for ease of administration.

I have been using local licensing for about 1 year now.

Whilst the application works (licensing wise), I have not been able to render with Mantra

hkey tells me I have 1 render token for each H13 and H14

when I render in either version, I get

“No licenses could be found to run this application.
Please check for a valid license server host”

Has there been recent changes to how Mantra is retrieving licenses ?

Cheers
Nicholas Yue
User Avatar
Member
301 posts
Joined: July 2005
Offline
I noticed that if I were to run “mantra” from $HFS there is no license issue.

If mantra is run from somewhere else, I get that license error.
Nicholas Yue
User Avatar
Member
301 posts
Joined: July 2005
Offline
Solved!

I had a stale copy of Licensing.opt in the $HOME directory and I was firing up Houdini from my $HOME.

I was reorganising my directories due to disk space and had left a copy of Licensing.opt in $HOME that points to a non-existent license location.

I did have an updated and correct copy of Licensing.opt in $HFS/houdini

I started houdini in $HOME, it works fine I guess because houdini looks for licensing configuration in $HFS/houdini so that works fine.

Whereas for mantra, the search order is different (I discover this through strace), mantra found a Licensing.opt (stale) in the current directory ($HOME) and used that instead of $HFS/houdini

I guess mantra search order needs to take into account farm/network rendering requirement.

I thought I write this up as it might benefit others.

Cheers
Nicholas Yue
User Avatar
Member
1 posts
Joined: April 2015
Offline
Has there been recent changes to how Mantra is retrieving licenses ?
dolii
  • Quick Links