ntdll crashes with specific user

Fommo
Member Posts: 138
Hello
I have implemented an integration using MSMQ in NAV. The functionality works perfect when running the code with my user (that is administrator on the NAV Server, but NOT on the MSMQ Server).
When I run through NAS driven Job Queue on a service account it crashes. When running as the service account in the classic client it also crashes in the same way and gives the following error in the event log:
Both accounts have FULL access to the queues in MSMQ, so the only difference between the accounts is that the service account has only public access to the NAV database, not administrator. Both accounts have the SUPER role within NAV.
What could result in the application crash (NAS as well as classic client) on the service account, but not when using my own user account?
Please help, I've been debugging this for days now. ](*,)
I have implemented an integration using MSMQ in NAV. The functionality works perfect when running the code with my user (that is administrator on the NAV Server, but NOT on the MSMQ Server).
When I run through NAS driven Job Queue on a service account it crashes. When running as the service account in the classic client it also crashes in the same way and gives the following error in the event log:
Faulting application name: finsql.exe, version: 6.0.32012.0, time stamp: 0x4d030bb8 Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f Exception code: 0xc0000374 Fault offset: 0x000ce6c3 Faulting process id: 0x8fc Faulting application start time: 0x01cd080f2eb58233 Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\60\Classic\finsql.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 89738899-7402-11e1-b8f2-00505682001aBoth NAS and classic client gives the similar error in the event log. Above is the one I get from the client crash.
Both accounts have FULL access to the queues in MSMQ, so the only difference between the accounts is that the service account has only public access to the NAV database, not administrator. Both accounts have the SUPER role within NAV.
What could result in the application crash (NAS as well as classic client) on the service account, but not when using my own user account?
Please help, I've been debugging this for days now. ](*,)
0
Comments
-
Hi Fommo,
looking at your error message it looks like you are trying to print something from the NAS.
Make sure that the printers are available to the service account user!
I had the same error once and I solved it by updating the printer driver for the NAS service account.
There are other reasons that could cause this error, but try this first.
Hope this helps,
WillyFostering a homeless, abused child is the hardest yet most rewarding thing I have ever done.0 -
KYDutchie wrote:looking at your error message it looks like you are trying to print something from the NAS.
Make sure that the printers are available to the service account user!
I had the same error once and I solved it by updating the printer driver for the NAS service account.
Thanks for your answer Willy.
However, no I'm not trying to print anything. The object that makes the NAS and the open client to crash is when writing to a queue in MSMQ. It seems that I can read from it. I have tried to reinstall the Communication Components from the SDK, but there is no change. I have also tried to set the service account on the NAV Server as well as the MSMQ Server. Both my own user (where it works) and the service account have full access to the MSMQ Queues.
I'm out of ideas what to try next. ](*,) ](*,) ](*,)0 -
Hello,
found very old post, but we have very similar problem: in the NAS+MSMQ combo there is frequent NAS crash:Faulting application name: nassql.exe, version: 6.0.32012.0, time stamp: 0x4d030c18 Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f Exception code: 0xc0000374 Fault offset: 0x000ce6c3 Faulting process id: 0x734 Faulting application start time: 0x01cdb6777e0ea297 Faulting application path: C:\Program Files (x86)\Microsoft Dynamics NAV\60\Application Server\nassql.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: f1b128eb-226f-11e2-8cce-000c29bda0ee
Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: nassql.exe P2: 6.0.32012.0 P3: 4d030c18 P4: StackHash_bcaa P5: 6.1.7601.17725 P6: 4ec49b8f P7: c0000374 P8: 000ce6c3 P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_nassql.exe_c05964a2ddb58f5b78b7a262cd783f92ad49cb_115c0feb Analysis symbol: Rechecking for solution: 0 Report Id: f1b128eb-226f-11e2-8cce-000c29bda0ee
OS: Win Server 2008 Standard 64-bit
NAV: NAV 2009 R2 (build 32012)
If you solved the problem, I would be very thankful for any advice.0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions