I can hit the wsdl from both boxes, 1 browser on each.  
im sure I could open another one, but I don't think that would help :)

tw

-----Original Message-----
From: Alexander Sherwood [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 09, 2004 9:35 AM
To: CF-Talk
Subject: Re: axis error...can anyone help explain?

At 09:17 AM 6/9/2004, you wrote:
>works from one webserver, not from the other, both have same settings,
etc..
>
>I can hit the wsdl from the server, through a browser...it looks like its
>telling me im
>no authorized to do something, but if I can hit the wsdl from both boxes,
>and the code is the
>same between the boxes...any ideas why it would be erroring?

You mean you hit the WSDL file from 2 different browsers on 2 different
servers, or you have the same WSDL file on 2 different servers setup with
identical permissions?

>Diagnostics:
>Could not perform web service invocation "CreateLead" because AxisFault
>faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server faultSubcode:
>faultString: Server was unable to process request. --> The request failed
>with HTTP status 401: Unauthorized. faultActor: faultNode: faultDetail:
>{http://xml.apache.org/axis/}stackTrace: AxisFault faultCode:
>{http://schemas.xmlsoap.org/soap/envelope/}Server faultSubcode:
faultString:
>Server was unable to process request. --> The request failed with HTTP
>status 401: Unauthorized. faultActor: faultNode: faultDetail: Server was
>unable to process request. --> The request failed with HTTP status 401:
>Unauthorized. at
>org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:
2
>60) at
>org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:1
6
>9) at
>org.apache.axis.encoding.DeserializationContextImpl.endElement(Deserializat
i
>onContextImpl.java:1015) at
>org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1675) at
>org.apache.crimson.pars...
>The error occurred on line 199.
>
>thanks :)
>
>...tony
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to