Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 295 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Lock problem with NAS
FMR
Member Posts: 3
Hi,
We have installed Navision Application Server to use bar code reader devices that update NAV (4.03) database (data interchange is made using 'Microsoft XML, v3.0' Automation). Our problem is that when two o more users are using the terminals, the NAS user (Windows/NAS) locks the table "Warehouse Activity Line" (Message: Windows/NAS user has locked "Warehouse Activity Line"...), and no one can keep working with that table (neither manually nor using reader devices). So we have to kill Windows/NAS session in NAV and re-start Navision Application Server. Any idea??
Thanks a lot!!
We have installed Navision Application Server to use bar code reader devices that update NAV (4.03) database (data interchange is made using 'Microsoft XML, v3.0' Automation). Our problem is that when two o more users are using the terminals, the NAS user (Windows/NAS) locks the table "Warehouse Activity Line" (Message: Windows/NAS user has locked "Warehouse Activity Line"...), and no one can keep working with that table (neither manually nor using reader devices). So we have to kill Windows/NAS session in NAV and re-start Navision Application Server. Any idea??
Thanks a lot!!
0
Comments
You will have to check with the debugger where something is done by the NAS and then put a COMMIT in the correct place(s).
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Finally, as we are working with Navision Server (instead of SQL Server) I replaced FINDFIRST and FINDLAST by FIND('-') and FIND('+') and it worked!! I think that those functions lock the table and it causes problems with NAS. Anyway, I'm sure that a COMMIT would have worked too.
Thank you kriki!