R11 License Server & SNHookClass

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 08/02/2010 at 10:12, xxxxxxxx wrote:

Ah and another question, although that has already been answered I guess but if regdate is invalid and WriteRegInfo is not suitable to be used in conjunction with the SNHook class, then it seems that it´s impossible to provide customers with a demo. So the customer would require a seperate single c4d license to test a plugin before he can buy a license for a license server environment right?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/02/2010 at 03:44, xxxxxxxx wrote:

However, shouldn´t this rather say that this is a unique ID passed to the serial hook object´s Register() function? Otherwise it would seem impossible to register several plugins within one library (.cdl) for a license server environment. Can somebody confirm this just to make sure?

Yes, a unique ID has to be passed because all SNHookClass is doing is to establish a hook into the Personalize dialog.

Btw. is there ANY way to test this? Is there a license server demo?

We are currently thinking about ways to provide developers with license server NFR versions.

Also I´d like to know something else (as regdate is invalid). WriteRegInfo(), on which machine is this written to (assuming it is called from within SNCheck())? On the individual client machines or on the machine the license server is installed? I assume the former but I´d like to make sure I get this correctly.

Yes, it's written to the client machine.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/02/2010 at 03:46, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Ah and another question, although that has already been answered I guess but if regdate is invalid and WriteRegInfo is not suitable to be used in conjunction with the SNHook class, then it seems that it´s impossible to provide customers with a demo. So the customer would require a seperate single c4d license to test a plugin before he can buy a license for a license server environment right?

This seems to be an oversight on our side. I forwarded this as feature request / bug report.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 09/02/2010 at 05:47, xxxxxxxx wrote:

thanks Matthias for clearing this. An NFR version would definetly be super helpful.
Ok, for now I´ll tell my LS customers that there´s no demo possible. Maybe they wait. :)

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 10/02/2010 at 08:19, xxxxxxxx wrote:

Note that 11.5 and up now allow you to manually enter a serial number for a plugin using SNCheck if it's not provided by the License Server.

I'm happy to test license server compatibility here at MAXON USA for anyone who can't get their hands on it. Just send me a PM.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 10/02/2010 at 09:16, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Note that 11.5 and up now allow you to manually enter a serial number for a plugin using SNCheck if it's not provided by the License Server.

Hi Rick,

could you elaborate on this? I am not sure I fully understand this. Thanks

Originally posted by xxxxxxxx

I'm happy to test license server compatibility here at MAXON USA for anyone who can't get their hands on it. Just send me a PM.

Superb. Thanks for the support. I´ll probably get in touch with you on this directly next week then.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/02/2010 at 06:54, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Riptide Pro [11-0-1022532] _<__>
...the XOXO partwould be replaced by a 16 character generated license key

Just to make sure, the XOXO part does not explicitly need to be 16 characters in length right? It could also be more or less and may contain digits and characters right?

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 23/02/2010 at 02:25, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Originally posted by xxxxxxxx

Riptide Pro [11-0-1022532] <<RipPro12345-XOXOXOXOXOXOXOXO>>

...the XOXO partwould be replaced by a 16 character generated license key

Just to make sure, the XOXO part does not explicitly need to be 16 characters in length right? It could also be more or less and may contain digits and characters right?

As far as I know, your statement above is correct (within reason)... my license keys just happen to be 16 characters. I'm not sure if there's a fixed / practical upper limit on the length though.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/07/2010 at 08:30, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Originally posted by xxxxxxxx

Ah and another question, although that has already been answered I guess but if regdate is invalid and WriteRegInfo is not suitable to be used in conjunction with the SNHook class, then it seems that it´s impossible to provide customers with a demo. So the customer would require a seperate single c4d license to test a plugin before he can buy a license for a license server environment right?

This seems to be an oversight on our side. I forwarded this as feature request / bug report.cheers,Matthias

Hi Matthias,

Do you know if this issue (can't provide evaluation/demo plugins for License Server use) was ever addressed? I am currently working with a client and trying to determine some means of them purchasing a single test/evaluation copy, before they make the big purchase.

Thanks,

Keith

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 08/07/2010 at 03:06, xxxxxxxx wrote:

I am not aware of any changes regarding this issue I am afraid. In any case I am not allowed to speak about future development, sorry.

cheers,
Matthias