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
- 302 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
Inconsequent System.Xml.XmlDocument.Save error
rjmvdven
Member Posts: 22
I hope someone can point me in the right direction. Sometimes a user gets one of the attached error messages when either calling a webservice of exporting a payment file. The last one is standard Dutch NAV functionality, so no customizations.
It is also not a consequent message, since the user performs these tasks multiple times a day and the message does not appear always. Also when the user tries it a second time it performs the functionality, or the user has to restart NAV and then it works again. Really weird.
Until now we only have 2 users that have this problem, but the DotNet objects are run on the server, so I do not think it is related to the PC's of those users.
I hope someone has experienced this issue before, but google is not really helpful in giving me a solution.
We are running NAV 2016.
It is also not a consequent message, since the user performs these tasks multiple times a day and the message does not appear always. Also when the user tries it a second time it performs the functionality, or the user has to restart NAV and then it works again. Really weird.
Until now we only have 2 users that have this problem, but the DotNet objects are run on the server, so I do not think it is related to the PC's of those users.
I hope someone has experienced this issue before, but google is not really helpful in giving me a solution.
We are running NAV 2016.
Best Regards,
Remco van de Ven
Remco van de Ven
0
Answers
Problems like these immediately make me think: "NST Bug".
Before investigating further I would make 100% sure that there is not a CU that addresses this issue.
/Wisa
I would assume that as well, except we have been running the same NST's for the last 2 years. And only recently the error occured. I will look into the release notes of the CU's that have been released after the one that we have installed. Thanks for the reply.
Remco van de Ven