Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K 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
- 317 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.6K 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
Control add-in error
TimoBo
Member Posts: 31
Hi,
I have a problem with control add-ins in a new on-prem BC23 NZ installation with db upgraded from BC17.
Some of the control add-ins don't work. The weird thing is that it's specifying public key token a4af7ee0f073bc1a instead of 31bf3856ad364e35
Also the OAuthIntegration Control add-in is not working
The control add-ins have been set up
I tried removing them, adding them via PS, adding them via company initialization, nothing worked.
The add-in files are in the correct add-ins folder on the server. The files are not blocked and the files have the correct permissions.
We have already tried re-installing the web client and service tier.
Does anybody have a clue how to solve this?
I have a problem with control add-ins in a new on-prem BC23 NZ installation with db upgraded from BC17.
Some of the control add-ins don't work. The weird thing is that it's specifying public key token a4af7ee0f073bc1a instead of 31bf3856ad364e35
Also the OAuthIntegration Control add-in is not working
The control add-ins have been set up
I tried removing them, adding them via PS, adding them via company initialization, nothing worked.
The add-in files are in the correct add-ins folder on the server. The files are not blocked and the files have the correct permissions.
We have already tried re-installing the web client and service tier.
Does anybody have a clue how to solve this?
0
Best Answer
-
TimoBo
Member Posts: 31
It was magically fixed by re-doing the db upgrade from BC17 to BC23. We will probably never know the real cause.0
Answers