Hello,
I am trying to access my repository which was working recently,
but I get the Error shown in down pic.I need a help.
Hello,
I am trying to access my repository which was working recently,
but I get the Error shown in down pic.I need a help.
Your installation is not licensed. You need to reactivate.
Since a case has already been opened for this issue, you need communicate with LF Support through case system. If you have difficulty reactivating or obtaining a new license, then please let us know there.
Have you checked the license on the server itself? If you bring up the Admin console, select the "servername" node on the left hand side of the screen, the right hand pane will give you a license summary. Does it show the "License type", "Full Repository named user" count and "Retrieval user" count?
What does the application log say? If your license is expired, it will show there too.
If your license is expired, you will need to reactivate and replace the old license.
Cruz thx for reply and useful info.
look what I get in Admin console,
Your installation is not licensed. You need to reactivate.
Since a case has already been opened for this issue, you need communicate with LF Support through case system. If you have difficulty reactivating or obtaining a new license, then please let us know there.
FYI. A case has already been opened for this issue. We will let everyone know the outcome once it has been resolved.
Hi Gentil,
Is this your VAR kit? If so has the license expired?
Also is the SQL server this repository is looking at running and functioning correctly?
Hello Chris,
Thank you for reply.
*This is my VAR kit,
*About the licence our LSAP was experied on 25 February 2015 but we have paid for LSAP activation.I think activation should do be automatic.
*SQL server is running correctly.
Thanks
Hi Gentil,
No the license renewal isn't automatic. Sounds like your license has expired.
You need to run the Activationtool.exe located in the server directory (C:\program files\laserfiche\server). You will need your activation key which you can get from the support site.
Like Raymond says you might find some more detailed info on the error in the application logs.
Good luck!