v2.5.2875 Actipro invalid license error

[Arnold Wolfe]

Anyone else getting this?

Client side exception:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Windows.Markup.XamlParseException: The invocation of the constructor on type 'Raven.Studio.Features.Indexes.EditIndexView' that matches the specified binding constraints threw an exception. [Line: 9 Position: 27] ---> System.Windows.Markup.XamlParseException: The invocation of the constructor on type 'Raven.Studio.Controls.Editors.LinqEditor' that matches the specified binding constraints threw an exception. [Line: 842 Position: 50] ---> ActiproSoftware.Compatibility.LicenseException: The type 'Raven.Studio.Controls.Editors.LinqEditor' could not be created because a valid license for its usage was not found.  See the 'Licensing' documentation topic for details on registering a license.

Error: The licensee or license key that was entered is invalid.

Please contact Actipro Software for assistance.

LICENSE DETAIL

Product: SyntaxEditor 14.1.0171 (Full)

License Type: Full

Licensee: Hibernating Rhinos

[Matthew Sharpe]

Yes, I'm getting the same. Just got the server from nu-get and was confronted with this. Not the best initial experience...

[jdecicco]

Yes. Glad to see I'm not alone. :-)

[Kijana Woodard]

This seems to happen from time to time with release builds. Not sure why the license fill gets out of whack like this. Someone from Hibernating Rhinos will fix it soon, no doubt.

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Cosmin Constantin Lazar]

I get this one in the studio after i updated to 2.5.2875

Client side exception:

System.Windows.Markup.XamlParseException: [Parser_CreateInstance_ConstructorInvocation]

Arguments: Raven.Studio.Controls.Editors.JsonEditor

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20513.0&File=System.Windows.dll&Key=Parser_CreateInstance_ConstructorInvocation [Line: 158 Position: 55] ---> ActiproSoftware.Compatibility.LicenseException: The type 'Raven.Studio.Controls.Editors.JsonEditor' could not be created because a valid license for its usage was not found.  See the 'Licensing' documentation topic for details on registering a license.

Error: The licensee or license key that was entered is invalid.

Please contact Actipro Software for assistance.

LICENSE DETAIL

Product: SyntaxEditor 14.1.0171 (Full)

License Type: Full

Licensee: Hibernating Rhinos

Licensee Key: SIL132-H6K2W-XYGL0 (Truncated for security)

Platform: Silverlight

ID: 5550

Error Code: 101

   at ActiproSoftware.Products.ActiproLicenseValidator.ValidateLicense(AssemblyInfo assemblyInfo, Type controlType)

   at ActiproSoftware.Windows.Controls.SyntaxEditor.SyntaxEditor..ctor()

   at Raven.Studio.Controls.Editors.EditorBase..ctor()

   at Raven.Studio.Controls.Editors.JsonEditor..ctor()

   --- End of inner exception stack trace ---

   at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)

   at Raven.Studio.Features.Documents.DocumentPadView.InitializeComponent()

   at Raven.Studio.Features.Documents.DocumentPadLayer.HandleLoaded(Object sender, RoutedEventArgs e)

   at MS.Internal.CoreInvokeHandler.InvokeEventHandler(UInt32 typeIndex, Delegate handlerDelegate, Object sender, Object args)

   at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTyp

[Chris Marisic]

All of us needs to write Actipro and tell them how horrible of an experience they provide 3rd parties who are using their licensed controls. Their license validation scheme is horribly broken, it should never just error like this. 

[Cosmin Constantin Lazar]

Well, the blame goes both ways...

But indeed they could have sent an email to Hibernating Rhinos saying "hey your license will expire in 30 days, would you like to renew?", on the other hand, maybe Hibernating Rhinos should monitor the licenses they acquired and make sure they get notified when they are about to expire...

[Chris Marisic]

to: sa...@actiprosoftware.com

Subject: Bad Product behavior!

I have been a user of RavenDB for nearly 4 years. For a large portion of this time Hibernating Rhinos has licensed your components to be used in their software. Throughout the years numerous threads occur on RavenDB’s forums similar to https://groups.google.com/forum/#!topic/ravendb/nIgduQjsxtk

Error Code: 101

   at ActiproSoftware.Products.ActiproLicenseValidator.ValidateLicense(AssemblyInfo assemblyInfo, Type controlType)

   at ActiproSoftware.Windows.Controls.SyntaxEditor.SyntaxEditor..ctor()

This is an absolutely horrible experience you provide to 3^rd parties who are using your paid for commercial components! Honestly I’ve told Hibernating Rhinos on several occasions they should drop your software and purchase someone else’s products who do not treat their users so terribly.

These horrible activation schemes do nothing to prevent malicious users in avoiding paying for your software. They only punish innocent bystanders who get caught in your crossfire. 

[Bill Henning]

Hello all, Chris just wrote us expressing his frustration with the licensing exception and I replied right back.  To summarize, our licensing scheme is such that our customer (RavenDB) just calls a single line of code at app startup to register their license info.  That is pretty much industry standard.  In this case, I can tell based on the information that was posted for the exception that they registered a v2013.2 license key (it starts with SIL132-), but then went and used the 2014.1 version in their app.  If they want to use the newer version they need to register a 2014.1 license key instead.  That would solve the problem.

I'm sorry for the problems this has caused you, their customers.  We don't have any sort of activation or "phone home" functionality in our licensing so we wouldn't know if situations like this happen to end users.  It's up to our customers (like RavenDB) to test their product and ensure they follow our Licensing documentation to ensure that this situation never occurs.  We are always happy to assist our customers if they have problems getting the licensing set up.

Hopefully somebody can pass this info onto their support so that they can get everything up and running for you again.

[Cosmin Constantin Lazar]

It is really nice Bill stepped up and clarified the things (thumbs up)

The faulty commit is https://github.com/ravendb/ravendb/commit/5f6ae0c421daba0b4ca8de9ff74b6da30a8d2c28

I just hope they fix it tomorrow...

[Oren Eini (Ayende Rahien)]

Hi Guys,

Yesterday was Independence Day, so we weren't working. 

A new release will go out shortly.

Oren Eini

CEO

Mobile: + 972-52-548-6969

Office:  + 972-4-674-7811

Fax:      + 972-153-4622-7811

--

[Fitzchak Yitzchaki]

http://hibernatingrhinos.com/builds/RavenDB-Stable/2878

Best Regards,

Fitzchak Yitzchaki

Hibernating Rhinos Core Team

Tel: +972-4-6227811

Fax: +972-153-4-6227811