Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 298 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Conflict of licenses
aleix1979
Member Posts: 213
Hi,
I have an odd case. I have in the same server, two databases with their 2020 granule "one license per database" which cannot be separated with respect to license. If I upload one license to one, the other also gets updated and likewise the other war around.
The funny thing is that that does not happen with other databases in the same server which also have different licenses.
Both databases are 5.0 SP1. Any idea anyone?
I have an odd case. I have in the same server, two databases with their 2020 granule "one license per database" which cannot be separated with respect to license. If I upload one license to one, the other also gets updated and likewise the other war around.
The funny thing is that that does not happen with other databases in the same server which also have different licenses.
Both databases are 5.0 SP1. Any idea anyone?
Navision Developer
0
Comments
Check the option 'Save license in database'. If this option is not set, the database uses the license that is saved on the SQL Server Instance.