dbForge Ent. 5.4.275 Requires Reactivation

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
hobiedave
Posts: 16
Joined: Thu 01 Nov 2012 13:39

dbForge Ent. 5.4.275 Requires Reactivation

Post by hobiedave » Sun 04 Jun 2017 18:53

Every week or so, I am forced to reenter by software license key. Why? Just happened today and also last week.

alexa

Re: dbForge Ent. 5.4.275 Requires Reactivation

Post by alexa » Mon 05 Jun 2017 09:07

We will fix this issue in the next product build that should be released this week.

The problem, in fact, happens when leaving SSMS or VS with installed dbForge SQL Complete overnight. To avoid this, you have to close SSMS/VS before leaving the PC overnight.

vital3d
Posts: 1
Joined: Wed 07 Jun 2017 12:00

Re: dbForge Ent. 5.4.275 Requires Reactivation

Post by vital3d » Wed 07 Jun 2017 12:05

Running Standard 5.6.158 and this happens every day. Is your fix going to resolve that for Standard as well?

alexa

Re: dbForge Ent. 5.4.275 Requires Reactivation

Post by alexa » Wed 07 Jun 2017 15:32

We would like to let you know that we have released dbForge SQL Complete, v5.6.162 where the issue you reported is fixed https://www.devart.com/dbforge/sql/sqlc ... nload.html

Thank you for your help in improving dbForge SQL Complete.

sbsdevelop
Posts: 1
Joined: Wed 07 Jun 2017 23:50

Re: dbForge Ent. 5.4.275 Requires Reactivation

Post by sbsdevelop » Wed 07 Jun 2017 23:57

The past couple editions switched me to trial period after performing an 'upgrade', the latest version 5.6.162 did also.
Is this by design? It is a bit of a drag to re-activate it after each installation (I have 3 licences to keep track of where they are installed).

alexa

Re: dbForge Ent. 5.4.275 Requires Reactivation

Post by alexa » Thu 08 Jun 2017 05:20

We have fixed this issue in the latest product build 5.6.162 that has been released yesterday.

Please install the latest version and activate it once again. It shouldn't ask you for activation in the future.

Sorry for the inconvenience.

Post Reply