Maybe check your setenv.bat? It might not be pointing to the right license server.
And if you're not sure what the setenv.bat is, I recommend you have a look at the Setup Guide. It might help you find the source of the problem.
Thanks,
Christine
-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Chris
Posted At: Wednesday, May 10, 2006 2:49 PM
Posted To: xsi
Conversation: Re[2]: 1 licence for two different versions
Subject: Re[2]: 1 licence for two different versions
To all: Alright I read all your answers and I understand it. First I never was going to run (2) XSI versions at the same time. Second why do I get the error:
Error: there is no interactive licence to run XSI
And i'm not running 4.2 & 5.1 at the same time. I'm just loading up
5.1 with no 4.2 running. What am I doing wrong, when under new licence for 5.1, version 4.2 loads up fine. When I try to run *just*
5.1 I get this error ?
Christopher
Wednesday, May 10, 2006, 7:41:19 AM, you wrote:
> If you've payed to upgrade to 5, you've still only got a license to
> run
> 1 XSI, no matter which version that is.
> If you bought a brand new copy of 5, then clearly you could still run
> one 4.2 and also your new version 5 at the same time.
> Personally, I'm not sure where the confusion is?
> Tim Leydecker wrote:
>> (this isn´t my thread, it´s Chris´)
>>
>> Thanks for the details about the consequences of the licensing
>> scheme, I had assumed SPM and FlexLM to work identical, e.g. I could
>> run two 4.5 Maya licenses here using one 4.5 and 6.0 if my licenses
>> wouldn´t be nodelocked anyway but floating :-)
>>
>> Good to know this wouldn´t work with XSI, e.g.you had upgraded a
>> licensefile and explicitely get one interactive license granted in
>> that.
>> Counting per machine but made to block different builds to run in a
>> simultaneous session from one interactive license.
>>
>> This isn´t ideal as it would obviously be desireable to have both
>> builds open when transfering things from old>new for fixing
>> inconveniences introduced through new functionality or changed featuresets.
>>
>> tim
>>
>> P.S: I´d find it building customer relationship to allow *build up*
>> of licenses but I can understand it would be commercially stressing...
>>
>> ----- Original Message ----- From: "kim aldis" <kim(at)cg-soup.com>
>> To: <XSI(at)Softimage.COM>
>> Sent: Wednesday, May 10, 2006 12:07 PM
>> Subject: RE: 1 licence for two different versions
>>
>>
>>> The rules are that one user/machine combination only takes one
>>> token, no matter how many instances of xsi you use. However, it does
>>> seem that the rule doesn't cross version boundaries and running 5.1
>>> alongside 4.2 won't work if you have a single token. With that
>>> caveat, old versions of xsi will run from newer tokens, so 4.2 will
>>> run from a 5.1 token provided 5.1 isn't running. Which is annoying.
>>>
>>> Except on linux where a second xsi will crash the prior version.
>>> That's a
>>> bug, though.
>>>
>>>> -----Original Message-----
>>>> From: owner-xsi(at)Softimage.COM
>>>> [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Sandy E. Sutherland
>>>> Sent: 10-May-2006 10:49
>>>> To: XSI(at)Softimage.COM
>>>> Subject: RE: 1 licence for two different versions
>>>>
>>>> Don't know about this - If you BOUGHT 4.2 and then BOUGHT
>>>> 5.01 - then you can get Softimage to generate you a key with both
>>>> in - but if you bought 4.2 and UPGRADED it to 5.01 - then you can
>>>> run only 1 seat at a time - unless of course this is on 1 machine -
>>>> where you should be able to run 2 or more XSI at the same time -
>>>> THIS IS ON THE SAME MACHINE!!!!
>>>> I am presuming this, as I do not run 2 XSIs at the same time
>>>> - do not work that way!!
>>>>
>>>> S.
>>>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
> unsubscribe xsi
--
Best regards,
Chris mailto:walksfar(at)netscape.ca
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
