Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 310 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Control AddIn public key corrupted
Maria-S
Member Posts: 90
Good day,
Setup:
NAV2018; Several AL Extension with several Control Add-In
Problem:
My Control add-in stops working sometimes when I deploy the new version of my extension.
It shows the errror "Control add in with public key XXXX cannot be found."
Investigation:
I found out, that after deployment (via Publish-NavApp from specified path), in the table NAV App Tenant Add-In, the correct public keys for all Control Add-In are replaced with the key of first Control Addin in the list.
Changing back Public Keys in this table back to correct values works.
But how to avoid this to happen in future, and what might be the reason for that?
Any suggestion is greatly appreciated.
Setup:
NAV2018; Several AL Extension with several Control Add-In
Problem:
My Control add-in stops working sometimes when I deploy the new version of my extension.
It shows the errror "Control add in with public key XXXX cannot be found."
Investigation:
I found out, that after deployment (via Publish-NavApp from specified path), in the table NAV App Tenant Add-In, the correct public keys for all Control Add-In are replaced with the key of first Control Addin in the list.
Changing back Public Keys in this table back to correct values works.
But how to avoid this to happen in future, and what might be the reason for that?
Any suggestion is greatly appreciated.
0
Answers
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!