most likely ..you webservice is having permissons problem.
try running it under different app pool ..remember to change the identity in
the app pool to a user who has correct rights.
also change the account your service is running under in directory security
in IIS.
Thanks
Siddharth
"Louis Kwong" wrote:

> Hi,
>
>
> I am trying to consume web services via SOAP ports on another machine
> running Windows Server 2003. I currently run BizTalk on a Win XP
> machine.
>
>
> I get the following error messages in order from event viewer after I
> dump a XML file into the receive location.
>
>
> -------------------------
> The adapter "SOAP" raised an error message. Details "Exception has been
>
> thrown by the target of an invocation.".
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> -------------------------
> The adapter "SOAP" raised an error message. Details "Server was unable
> to process request. --> Login failed for user 'NICTA\NICTA-ESE1-VM$'.".
>
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> -------------------------
> The adapter failed to transmit message going to send port
> "http://203.143.168.110/AddNewCarCustomer/AddNewCarCustomer.asmx". It
> will be retransmitted after the retry interval specified for this Send
> Port. Details:"Server was unable to process request. --> Login failed
> for user 'NICTA\NICTA-ESE1-VM$'.".
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> --------------------------
>
>
> I have ensure that IIS running on the Windows Server 2003 have user
> ASPNET and my normal Windows Server login. I made sure that "Anomymous
> Access" is enabled on the web services I want.
>
>
> Also, I have gone in to the Send Port inside my orchestration to try
> changing the SOAP Send Port's credentials to see if it will solve the
> problem but failed.
>
>
> What is interesting is NICTA-ESE1-VM is not a login name on any
> machine. It is actually a machine name for the Windows Server 2003.
>
>
> Can anyone help me out?? Thanks!
>
>

[ Post a follow-up to this message ]