Problem porting PTracker to production server

DanEssin posted on Monday, February 12, 2007

I have PTServiceClient working on my development machine. I have set up corresponding virtual directories on my production server for PTWebService and WebServicesHost. On the production server I can browse the WSDL and click invoke but then all I get is a 500 error.

I was trying to include log4net in an attempt to get some information about exactly what isn't right. The logging calls that I put in PTWebService generate output but the ones that I included in the PtrackerLibrary do not.

I would be happy to solve the first problem and skip the second and would appreciate some input about what to do next, either to get the web service working or to get logging working.

Thanks,
Dan Essin

RockfordLhotka replied on Monday, February 12, 2007

You are almost certainly running into some sort of security issue on your production server. Either at the virtual root or file system level.

Regarding log4net - I love log4net, but it is a serious pain in the @@$ to get it working on a web server. Mostly, again, due to security issues...

DanEssin replied on Monday, February 12, 2007

Following your suggestion I have narrowed down the server-side problem.
I just don't know how to fix it.
The problem is that if I set the db connection strings for integrated
security, access to the db fails. If I hard code a user id and password,
then the web service works as expected.

For the production server I have created a domain user called IUSR_WS. I
have made this user the user for anonymous access to the web service and
have given this user permission on all of the stored procedures. None of
this has any beneficial effect.

On the development machine everything works because the database knows
that I am logged on and have permission. It lets me in for no reason
having anything to do with the web service's request.

If you have any pointers for how to resolve this I would appreciate them.

Dan

RockfordLhotka wrote:
>
> You are almost certainly running into some sort of security issue on
> your production server. Either at the virtual root or file system level.
>
> Regarding log4net - I love log4net, but it is a serious pain in the
> @@$ to get it working on a web server. Mostly, again, due to security
> issues...
>
>
>
>

DanEssin replied on Tuesday, February 13, 2007

The latest version of this problem is as follows:

IF the machine on which the PTServiceClient is running has a proxy server enabled in IE
THEN the calls to the web service on the remote server fail with an HTTP 417 - Expectation Failed

Of course, everything always works if the client app and the web service are on the same box.

Any ideas?

Dan

RockfordLhotka wrote:

You are almost certainly running into some sort of security issue on your production server. Either at the virtual root or file system level.

Regarding log4net - I love log4net, but it is a serious pain in the @@$ to get it working on a web server. Mostly, again, due to security issues...

RockfordLhotka replied on Tuesday, February 13, 2007

DanEssin replied on Tuesday, February 13, 2007

Thank you.

It turns out that the answer is to add the following to the App.config file:
    <system.net>
        <defaultProxy>
            <bypasslist>
                <add address="IP Address of my Web Server"/>
            </bypasslist>
        </defaultProxy>
    </system.net>


Rockford Lhotka wrote:

Eliminate complexity: try creating a basic, trivial web service – like something returning Hello World – and a client that talks to it. Get the basic IIS/ASP.NET/web service security out of the way, then move on.

 

Rocky

 

From: Daniel Essin [mailto:cslanet@lhotka.net]
Sent: Tuesday, February 13, 2007 5:21 PM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] Problem porting PTracker to production server

 

The latest version of this problem is as follows:

IF the machine on which the PTServiceClient is running has a proxy server enabled in IE
THEN the calls to the web service on the remote server fail with an HTTP 417 - Expectation Failed

Of course, everything always works if the client app and the web service are on the same box.

Any ideas?

Dan

RockfordLhotka wrote:

You are almost certainly running into some sort of security issue on your production server. Either at the virtual root or file system level.

Regarding log4net - I love log4net, but it is a serious pain in the @@$ to get it working on a web server. Mostly, again, due to security issues...