Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I'm facing an issue that drive me crazy, I hope I can find the answer among all you experts. :)
We are running NAV2009R2 with a Navision Application server that run as a windows service.
When we do import documents via NAS, sometimes, the import just freeze in the job queue with status "In progress", to solve that, we do restart the NAS windows service and then the import continues. When I restart the service, I get "Error 109, The Pipe has been ended".
Added some log lines in the code to see where it stopps. I can see it always stopps at "rRequest.Data.CREATEOUTSTREAM(RequestOutStream)"
Along with the import, we do a SOAP request in a separate codeunit where the code execution freezes.
Dlg.Update(4, 'Create SOAP request...');
btSoapEnvelope.ADDTEXT('<?xml version="1.0" encoding="utf-8"?>');
xmlhttp.setRequestHeader('Content-Type', 'text/xml; charset=utf-8');
xmlhttp.setRequestHeader('SoapAction', rType."Soap Action");
Dlg.Update(4, 'Wait for an answer...');
xmldomResponse4 := xmlhttp.responseXML;
The strange thing is there are two companies in the same database. And the problem occurs only in one of them.
The problem occurs usually along with heavy import. There is no problem with few documents but when NAS import too many documents, the probability is much higher that the problem will occur.
What I tried:* Uninstall NAS service and reinstall it.* Create a new service user and changed the user running the NAS service.* Checked any deadlocks in the database. Using extended events and SQL profiler.* Followed the SOAP request using Wireshark and Fiddler.* Used Process monitor to see if there are any thread block.* Checked Event Viewer.
None of the above showed any hint where is the problem.
Googled a lot and the most similar case is here: forum.mibuso.com/.../nas-getting-stuck-when-ran-as-serviceThe common thing is that the user has proxy settings in internet options.
Any ideas, hints?
Sounds like you have already tried many things! Maybe this can help if you have not seen it already: forum.mibuso.com/.../how-to-debug-nas
Also, make sure you are using the latest build of NAV 2009 R2, i.e. build 39038. This was the latest and most stable build of NAV 2009 R2 released by Microsoft back in Dec 2014.
Hope that helps.
The problem is NAS does not crash rather hangs. I'll give it a shot though.
Anyone at any time may need a service like https://askboosters.com/ which specializes in increasing ratings in top video games and is not expensive at all.
Business Applications communities