Web Service migration question

[=?Utf-8?B?ZG91Zw==?=]

I built a ws locally takes in a request object and returns a response object.
The ws reads in a good sized xml file and the request oject has elements
used to create an xml subset and returns it as a response object. Use
XSD.EXE to create proxy classes. I built WSDL and it is stored same location
as ws asmx file. WS runs fine locally. It is using SOAP. I get userid and
authentication TRUE on local testing. Client gets good response object.

I had some issues using server side. Client reached it (my server side
logging says it fired ws up). But it can't detect UserId or isAuthenticated
settings and it says XML doc has problems. So I rebuilt XSD, proxy classes,
and wsdl on the server.

There is an error in XML document (0, 0).

[Steven Cheng[MSFT]]

Hi Doug,

From your description, you have an ASP.NET based webservice that will
accept and return some custom defined class objects(follow your own xml
schema), the webservice can be consumed correctly locally, but fail when
accessing remotely, correct?

As for the "UserId or isAuthenticated" is it any IIS or ASP.NET specific
authentication or your own custom authentication in the webservice request
schema definition? So far I'm still not very clear about your webservice's
detailed code logic and deployment scenario. Would you provide some further
info on this?

** Your webservice's code logic(such as soap message schema)
** your webservice's deployment scenario(security ...)
** How to consume the webservice through remote client and any different
from the approach you visit it locally

Also, please feel free to let me know if there is anything I misunderstand.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[=?Utf-8?B?ZG91Zw==?=]

I'm using lots of defaults/provided features. I don't actually see any
"soap" headers, but I turned off Soap12 and issued requests from test client
using both Soap11 and Soap12 and Soap11 worked and Soap12 failed - couldn't
parse it.

Custom classes built from XSD. Early binding seems to be behaving fine on
both WS and Client sides using these objects.

When I run WS locally (invoked from within instance of IDE) and then invoke
Test Client (invoked from within second instance of IDE) this all works.

When running on IIS server, I can bring up WS to get the default
ServiceDescription page. Looks okay.

When I invoke Test aspx page on server it gets error back. I create an
instance of the Request object and prior to invoking WS I save request to XML
file and it looks fine.

I will try to answer your questions:
** Your webservice's code logic(such as soap message schema)
<WebMethod(Description:="Returns one or more deposit rates based
upon request values", EnableSession:=False)_
Public Function getRates(ByVal Request As RequestObject.RATEDOC) As
ResponseObject.RATEDOC

sUser = Me.User.Identity.Name ' This is empty when run from test server
If Me.User.Identity.IsAuthenticated Then ' this is false when run from
test server

[Steven Cheng[MSFT]]

Thanks for your reply Doug,

So the problem is after you deploy the WS into IIS virtual dir. So far I
haven't any definite clues on what could cause this problem. But I think
you can try the following things also:

1.add a very simple and typical webservice endpoint in y our WS project and
consume it in both development environment(IDE) and IIS host to see whether
it suffer the same problem.

2.Use some http or tcp trace utility to capture the soap request/response
message(raw xml) and compare the one in development environment with in IIS
host scenario to see whether there is any difference.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[Steven Cheng[MSFT]]

Hi Doug,

How are you doing on this issue, have you got any progress? Please feel
free to post here if there is still anything we can help.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.