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
- 304 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
Web service "locks" when run from some machines
Shaggs
Member Posts: 36
I am having a problem with web services in NAV 2009R2. This particular web service is being used by wireless devices. The wireless deviceses work when we first log them in. they are able to run a number of functions (using the webservice) just fine. But when a particular function is called, it seems to "lock" the service. After that, no more functions on the webservice work from the handheld device. The service is still running, and there are no errors in any event logs.
At this point, if I check the web service, from a machine other than the server it is running on (http://192.168.0.1:7047/DynamicsNAV/WS/ ... erviceName) it does not work. If I go to the machine the service is running on, and run this from a browser http://localhost:7047/DynamicsNAV/WS/Co ... erviceName, it *does* work. And now everything else works - putting in the address from the other machine, and calling it from the handheld device.
I created a test app (winforms), that calls some of the functions that the wireless devices call. I ran this on both the server, and another machine. The results were very similar. Running that particular function on a non-server machine "broke" the service. But running *any* function on the server machine fixed it again.
I should point out at this point that in all cases, the same user/password/domain is being used in all cases.
When it failed on a non-server machine, I got the following error message:
"The login failed when connecting to SQL Server SQLSVR\INSTANCE"
I don’t know if it is worth mentioning, but the actual SQL Server is on another machine.
We have a very similar environment, using the same version of executables, working in our office. The only significant difference I can see is that the SQL Server is running on the same machine as the NAVService on this envoronment.
Can anyone suggest anything? Any ideas as to why this is happening?
At this point, if I check the web service, from a machine other than the server it is running on (http://192.168.0.1:7047/DynamicsNAV/WS/ ... erviceName) it does not work. If I go to the machine the service is running on, and run this from a browser http://localhost:7047/DynamicsNAV/WS/Co ... erviceName, it *does* work. And now everything else works - putting in the address from the other machine, and calling it from the handheld device.
I created a test app (winforms), that calls some of the functions that the wireless devices call. I ran this on both the server, and another machine. The results were very similar. Running that particular function on a non-server machine "broke" the service. But running *any* function on the server machine fixed it again.
I should point out at this point that in all cases, the same user/password/domain is being used in all cases.
When it failed on a non-server machine, I got the following error message:
"The login failed when connecting to SQL Server SQLSVR\INSTANCE"
I don’t know if it is worth mentioning, but the actual SQL Server is on another machine.
We have a very similar environment, using the same version of executables, working in our office. The only significant difference I can see is that the SQL Server is running on the same machine as the NAVService on this envoronment.
Can anyone suggest anything? Any ideas as to why this is happening?
0