License has expired

Hi Jonathan,

Has the license expired in reality?
If not, make sure you are using the correct license.

To do this:
1) Tools | License | Change (just for testing purposes, this will reset to your current license which gives the error when you close client.
2) Test that the license is working correctly.
3) If it is, go to Tools | License and press import and then change.
4) If the error still occurs, I suggest you contact your partner.

As an answer to your question, I have never heard of anyone where this has occurred.

Regards

Jonathan2708 wrote:

Hi,

Today a developer reported that they got the message 'Your program license has expired.' The odd thing is this reportedly happened during trying to post a general journal. Whenever I have seen this error previously it's always been when NAV has been first run or an attempt to open a database with an old license installed, never after having already successfully opened a database. The database in use has a current active license.

Anybody else had this happen?

Jonathan

bbrown wrote:

Are you an end-user (client) or a partner (NSC)? Client licenses do not expire. Only partner licenses do.

Well yes, client licenses may never expire, but if they purchased new granules or allocated more objects, a new license will be required for the customer.

bbrown wrote:

infonote wrote:

bbrown wrote:

Are you an end-user (client) or a partner (NSC)? Client licenses do not expire. Only partner licenses do.

Well yes, client licenses may never expire, but if they purchased new granules or allocated more objects, a new license will be required for the customer.

Yes, that is true. But has no bearing on the situation. The old license still remains valid. Just does not have access to new features.

I have seen resellers put a 'time bomb' in some installations (CU 1 I guess?) to ensure they pay their annual support renewal. Bit dodgy! :-k

Jonathan2708 wrote:

Hi,

Today a developer reported that they got the message 'Your program license has expired.' The odd thing is this reportedly happened during trying to post a general journal. Whenever I have seen this error previously it's always been when NAV has been first run or an attempt to open a database with an old license installed, never after having already successfully opened a database. The database in use has a current active license.

Anybody else had this happen?

Jonathan

Just replace the fin.flf file on your local computer. NAV checks the flf file on the local computer first before going out to the network to find the server.