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
- 262 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
DotNet and NAS
mikhael
Member Posts: 19
Hi experts
I have a codeunit which uses my own DLL to fetch invoices from web service. I had to use C# and pack the code to DLL because the web service uses tls1.2 encryption and I didn’t get that working with pure C/AL.
Everything worked fine until it came time to automatize the process. When I try to run the codeunit over NAS it gives me client callback error.
Is it possible at all to use Dotnet variables / selfmade DLL:s with NAS? If not, is there any feasible workarounds?
Mikhael
I have a codeunit which uses my own DLL to fetch invoices from web service. I had to use C# and pack the code to DLL because the web service uses tls1.2 encryption and I didn’t get that working with pure C/AL.
Everything worked fine until it came time to automatize the process. When I try to run the codeunit over NAS it gives me client callback error.
Is it possible at all to use Dotnet variables / selfmade DLL:s with NAS? If not, is there any feasible workarounds?
Mikhael
0
Best Answer
-
Options
Kishorm
Member Posts: 921
Have you set the DotNet variable to run server side instead of client side (RunOnClient = No)?5
Answers
I went through all my DotNet variables, I had one else variable which was RunOnClient = TRUE. I turned it also FALSE and it seems working now over NAS! It was just weird that the client callback error message was referring to my own DLL which was RunOnClient = FALSE all the time.