At the same time developer's licensing tricks strongly complicates life of the system integrators and supporters because of constrains on architecturing and many 'license not found' or 'access denied' issues.
1. License file
In MS Dynamics NAV you brought license files, those with .flf extension specify certain components and futures you'll be able to use. Short brief of included options in human readable form you can find in first section of license file (open it in Notepad, for example).
With installation disk your get a demo license file - Cronus.flf:
This informartion you can lately find in "License information" menu of Dynamics NAV client.
2. License search order
From Technet forum:
- in current database (if corresponding granule was purchased)
- in master database
- base folder
- program folder
3. NAV license file in SQL server
License tables in SQL server 'master' database will be created duning NAV setup procedure or on first classic client connection. License files can be easily managed by classic client: http://technet.microsoft.com/en-us/subscriptions/dd338774.aspx
But if you a little paranoic and don't want to allow 'master'-database-write-access via NAV, you can place the license file manually:
- in 'master' database create table '$ndo$srvproperty' with varbinary 'license' column:
- insert data from license file:
شركة مكافحة حشرات بجدة
ReplyDeleteشركة مكافحة حشرات بخميس مشيط
شركة مكافحة حشرات بابها