Ben, I haven't seen the error but I am wondering if it might be related to the other errors you are seeing with interop. Monday morning when I was catching up on e-mails there was a message about WSAS not supporting MSEC. Could this be the cause of the problem (since .NET uses MSEC by default)? Also could someone comment on the MSEC support. Is this something that is planned but has not been implemented yet or is there a technical reason why this cannot be implemented?
Scott Golightly -----Original Message----- From: Ben Dewey [mailto:[email protected]] Sent: Tuesday, April 21, 2009 3:16 PM To: '[email protected]' Subject: Error Sending to .NET OPS from PHP and WSAS I'm also getting an error sending to .NET from both PHP and WSAS. I presume that they are the same issue. I was able to find a message in the wsf_php_client.log The error message says: [Tue Apr 21 15:35:31 2009] [debug] wsf_xml_msg_recv.c(1205) [wsf_service] setting fault reason The message with Action 'SubmitOrderOnePhase' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None). The .NET IOrderProcessor doesn't seem to have an action with the suffix 'OnePhase', All I see is this contract: [OperationContract(Action = "SubmitOrder", IsOneWay = true)] void SubmitOrder(OrderDataModel order); Has anyone seen this error message before? Ben Dewey
