Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 05, 2012 03:48 PM by rlubanovic
Jul 05, 2012 03:48 PM|LINK
We have been users of webservices for many years and have developed and deployed many applications successfully using web services (since .net 1.1).
That being said, we have recently developed a new application for a Windows CE 5.0 device, which is a simple C# app that will connect to a webservice. Note we are fairly new to CE development, so we could be missing something basic.
This webservice exposes certain methods, and we have developed two applications that use these methods. One is an ASP.Net app (1.1) and the other is a Pocket PC 2003 Windows Application. In our development lab, both applications run properly. However,
in production (there is only one device onsite), the ASP.Net app runs properly through (IE) the iesample browser. The Pocket PC app will not connect to the webservice and fails.
A few notes: We did not actual physically test the production device in our lab, so we can't be sure there is not something inherently wrong with the device (or OS/image/etc). We did not manipulate the OS in any way from the vendor. We believe our test
device is a duplicate of the one in production.
The IP address in the web reference was hardcoded into the app, and we tried both a server name and actual IP address. We are using a Smart Device CAB file for the deployment.
Access to the webservice is anonymous, and we have tried making calls with and without credentials.
The webservice is working fine for other applications that use its methods.
We attempted to determine if a firewall was blocking the requests. Here is what we tried:
netstat -p ip -n
When this command was run in our development lab (from the device), we could see the attempts to talk with the webservice. When this command was run onsite (by the site administrator), there was no response. Now it is possible that it ran "too fast" to
show any results, but after multiple attempts, it appears that the application is not even trying to send requests to any webservice, not even one to the wrong IP address.
At this point, we are out of ideas on how to fix our Pocket PC app, which is the one we'd like to run in production (it has some nice recovery features). Is there something that needs to be configured or checked on the actual device to get this to attempt
to talk ? Although it seems that the webservice is setup properly, is there anything about this webservice or specific network that could be configued in such a way that our app can't communicate ? Are there any basic tests that can help is determine what
to fix ?
Any help would be greatly appreciated. The alternatives and workarounds just don't quite solve the problem as well as we'd like.
Note from Microsoft:
Based on your description, I suggest you go to
Mobile and Handheld Devices , re-ask the question for better support. Here we only discuss development problem of windows mobile. Therefore, I’d move this thread to off-topic.
Thanks for your understanding and active participation in the MSDN Forum.
Elegentin Xie [MSFT] MSDN Community Support |
Feedback to us