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
NAS and SQL Server
jeffb_r4
Member Posts: 34
Hi.
We have created a warehouse app that we are attempting to deploy. We have a test box running native database that we can successfully connect handhelds to. Both us and the client have a SQL server box that we cannot connect to.
We have checked all of the obvious things like having NAS running etc.
The NAV version is 5.0 SP1 and the SQL server version is 2000 running on a W2k3 server.
Does anybody have any suggestions as to what we can look at?
Any suggestions would be welcome at this point. ](*,)
Thanks.
We have created a warehouse app that we are attempting to deploy. We have a test box running native database that we can successfully connect handhelds to. Both us and the client have a SQL server box that we cannot connect to.
We have checked all of the obvious things like having NAS running etc.
The NAV version is 5.0 SP1 and the SQL server version is 2000 running on a W2k3 server.
Does anybody have any suggestions as to what we can look at?
Any suggestions would be welcome at this point. ](*,)
Thanks.
0
Comments
I would try upgrading to SQL 2005 for a start, I don't think 5 will run very well on 2000. 2000 does not support VSIFT properly, so performance will be really bad.
NIEM THAI
what error do you get? Did you check the application log?
Are you using ADCS? If so, there can be multiple issues that can block the scanners from working:
1. have you checked the firewall to make sure port 6666 is not blocked?
2. Is there a virus protection running that blocks telnet?
3. The accounts that are running the VT100 and the NAS, do they have telnet enabled in their profile?
4. Does the NAS user have sufficient rights?
5. Do you see the VT100 and NAS startup correctly? Those messages should be in the application log.
All these things should be checked.
Hope this helps.
Regards,
Willy
The application doesn't use ADCS. It sends xml files to and from the handheld.
The problem ended up not being related to SQL server at all. I initially thought it was as our application ran on a native database that we had set up for testing, but not at the client's which had SQL server.
The problem was eventually fixed by applying update 1 to 5.0 SP1 (or at least the part that related to NAS). This update fixed some problems with NAS, including, apparently, the problem that we had.
Anyways, I'm posting this information here to highlight that this update is out there and fixed this problem.