Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
Options
Import License bug in NAV 2013 R2 multi-tenant w\ multi-SQL
benr
Member Posts: 11
Hi All,
In my multi-tenant development environment I've got an Application Database on a SQL 2008 R2 box (SQL1). Tenants that are mounted to this app db are located on both SQL1 and another SQL 2012 box (SQL2). I've discovered that when I try to Import a license into a Tenant the Import always fails for the tenants on SQL2 with the error "Invalid object name 'TenantDBName.dbo.$ndo$tenantproperty'.". I ran SQL Profiler and it turns out it is looking for the Tenant on SQL1 to import the license into even though the Tenant is mounted to SQL2! It seems like it is assuming all tenants are mounted on the same SQL Server as the app db.
Fortunately our prod multi-tenant environments don't have multiple SQL Servers so this is just a development issue for now. Has anyone else come across this behavior?
Ben
In my multi-tenant development environment I've got an Application Database on a SQL 2008 R2 box (SQL1). Tenants that are mounted to this app db are located on both SQL1 and another SQL 2012 box (SQL2). I've discovered that when I try to Import a license into a Tenant the Import always fails for the tenants on SQL2 with the error "Invalid object name 'TenantDBName.dbo.$ndo$tenantproperty'.". I ran SQL Profiler and it turns out it is looking for the Tenant on SQL1 to import the license into even though the Tenant is mounted to SQL2! It seems like it is assuming all tenants are mounted on the same SQL Server as the app db.
Fortunately our prod multi-tenant environments don't have multiple SQL Servers so this is just a development issue for now. Has anyone else come across this behavior?
Ben
0
Comments
Import-NAVServerLicense : The following SQL error was unexpected.
Invalid object name 'database.dbo.$ndo$tenantproperty'.
No solution at the moment.
Another workaround is to have 1 tenant on your app SQL Server and load the license there. Then use TSQL to join your tenant SQL server to your app SQL server via a linked server and update the $ndo$tenantproperty.license column that way. Again you have to dismount\remount for it to take effect (or restart the entire service of course).
Neither workaround is fun, but we only have this setup in our development environment so it hasn't caused us too much grief.
Ben