License Issue

nverma

We have a client, and he just bought few user sessions a while ago. We loaded the new license file in the Live database and worked perfectly. I exported the license file from the live database and uploaded it into the development database, but the no of Licensed session did not change. It is still display the old licensed sessions.

What did I miss.

I exported copy of the license (from live database) and moved it to a computer that is running the development database. The copied license file is in classic, rtc, services folder. Why wont the no. of licensed session update.

I tried saving the license in database, tried uploading the license, tried restarting the services.

I am kinda out of ideas. ](*,)

Any ideas or suggestions?

geordie

I think you should import the license with "Import" function.

vaprog

At the client's site, you probably uploaded the license to the SQL Server, or copied it to the native server install folder, so it takes effect when you connect to the server. Export, however, gets you a copy of the license that is installed in your client's install folder.

nverma

I tried using Import function and still the same no. of licensed sessions appears.

I didnt do the initial setup/uploading of license so I am not sure how it was done (i.e. whether it was uploaded to SQL Server or whether it was copied to the native server install folder)

rjmvdven

nverma wrote:

We have a client, and he just bought few user sessions a while ago. We loaded the new license file in the Live database and worked perfectly. I exported the license file from the live database and uploaded it into the development database, but the no of Licensed session did not change. It is still display the old licensed sessions.

What did I miss.

I exported copy of the license (from live database) and moved it to a computer that is running the development database. The copied license file is in classic, rtc, services folder. Why wont the no. of licensed session update.

I tried saving the license in database, tried uploading the license, tried restarting the services.

I am kinda out of ideas. ](*,)

Any ideas or suggestions?

Did you use the Export button on the License screen? If so, this will export the license from the NAV directory of the machine that you use and it will not export the license from the SQL server. So in order to have the latest license in the development database, you have to use the Upload function and select the correct license. Then restart the client and you are using the latest license.

nverma

I was able to get my hands on the license file that was uploaded on the Live Database. I uploaded the same file in the Development database and was able to resolved the problem.

Just out of curiosity, why did microsoft built it this way? What is the benefit of having it this way. All it does is creates confusion.

When we run/open nav, which license file does the system load by default? SQL Server one or locally installed one? (I am going to guess, it runs nav using the license in the local system)

When the license file is modified with new granules, do I need to just Import the updated copy of the license (which will create/update the copy of license in classic, rtc, and service folder)? Or is there more to it.

vaprog

What I tried to tell you in my former post is:

• I you use the same license in your development environment that is installed on the your client's server (i.e.the customer's), you will have the same number of licensed sessions.
• You will not export the license that is installed on the server when you use the export function. You will get the one installd in NAV Client program folder, in other words, the one you imported, not the one you uploaded.

I know, it's confusing, especially if the dialog shows you the license on the server and export from that very dialog gives you some other license.

vaprog

nverma wrote:

When we run/open nav, which license file does the system load by default? SQL Server one or locally installed one? (I am going to guess, it runs nav using the license in the local system)

NAV uses the local license if you open a .fdb file directly. It uses whatever license is installd on the server (or database, if you stored it in the database) if you connect to a server. You can then override the server's license by using the Change button in the License Information window.
That part is very logical. Only the Export part is what usually gives unexpected results.

rocatis

nverma wrote:

When we run/open nav, which license file does the system load by default? SQL Server one or locally installed one? (I am going to guess, it runs nav using the license in the local system)

It starts off using the fin.flf located in the NAV program folder. If that file does not exist, it uses an "internal" CRONUS (demo) license.

It then reestablishes the last server connection used (if any) and pulls the license from the SQL database.

A license cannot be exported from the SQL database (at least not in an easy way). Trying to using the Export function will merely export the locally stored license.