Two NSTs for same database, but one with partner license

John_Reinhold

Hello my clever friends :-)

Is it possible to have two NSTs (NAV2018) running on the same server and database, to have different licenses? The reason for my question is the need of running special developer environments or tools on customers installation. I short, I need to start the customer’s NAV windows client with the partner license active. Uploading the license to the SQL server would do the trick for me. But as I see it, I would need to restart the NST. And of course, the customer would also be running on partner license which is a no-go.

So is the idea of creating a secondary NST ‘DynamicsNAV110Dev’ for developer use only possible?


In the old classic-days, you would just choose ‘change license’ in the client (finsql.exe) :-)

Any inputs on the problem are welcome.

/John

RemkoD

Uploading the partner license into the NAV database doesn't mean the customer is instantly using the partner license. Only after restarting the user NSTs they would use the partner license.

So if you do this: (assuming all NSTs are running on the customer license)

1. Upload partner license (into NAV DB)
2. Restart DynamicsNAV110Dev NST
3. Upload customer license (into NAV DB)

You would have the partner license only active on the Dev NST. The customer NSTs are still running on the customer license and stay on the customer license after NST restart.
Until the DEV service tier is restarted you would have the partner license active.

If you need to do it often you could make a powershell script that will do this for you. The downside is indeed.. you need to restart the DEV NST.

Duikmeester

Use separate Program Files folders and replace the Cronus.flf file in those folders with the development/customer license should do the trick.

RemkoD

Uploading the partner license into the NAV database doesn't mean the customer is instantly using the partner license. Only after restarting the user NSTs they would use the partner license.

So if you do this: (assuming all NSTs are running on the customer license)

1. Upload partner license (into NAV DB)
2. Restart DynamicsNAV110Dev NST
3. Upload customer license (into NAV DB)

You would have the partner license only active on the Dev NST. The customer NSTs are still running on the customer license and stay on the customer license after NST restart.
Until the DEV service tier is restarted you would have the partner license active.

If you need to do it often you could make a powershell script that will do this for you. The downside is indeed.. you need to restart the DEV NST.

John_Reinhold

Thanks RemkoD and Duikmeester for your posts. I'll try the approach restarting NST "DynamicsNAVDev" right after license upload. In that manner I'll also can have webservice and more running on partner-license. And now I have an excuse to use PowerShell.
In fact, I did suspect that this would be the answer, but it's great to be assisted by experienced people anyways.