I am a bit confused about this error because as you can see from my server web.config - All of the maximum quotas are much higher than the error states:
I have tried increasing similar parameters in the WP7 code as follows but the error still appears:
service.Service1Client serviceClient = new service.Service1Client();
serviceClient.InnerChannel.OperationTimeout = new System.TimeSpan(0, 5, 0);
serviceClient.Endpoint.Binding.CloseTimeout = new System.TimeSpan(10, 0, 0);
serviceClient.Endpoint.Binding.OpenTimeout = new System.TimeSpan(10, 0, 0);
serviceClient.Endpoint.Binding.ReceiveTimeout = new System.TimeSpan(10, 0, 0);
serviceClient.Endpoint.Binding.SendTimeout = new System.TimeSpan(10, 0, 0);
Any advice would be greatly appreciated.
Thanks,
Jason
Jason NesbittPosted Jul 11, 2011, 1:08 PM
I've managed to get past that error but now I get the following:
"Could not find default endpoint element that references contract 'PSSLiveServiceReference.IService1' in the ServiceModel client configuration section."
These are my end points on both the application and the server:
If I change the contract to be "PSSLiveServiceReference.IService1" then I get the following, probably most confusing, error:
The content type multipart/related; type="application/xop+xml";start="";boundary="uuid:cc46e713-c87d-4657-960f-47cedae89d5b+id=1";start-info="text/xml" of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 773 bytes of the response were: '
--uuid:cc46e713-c87d-4657-960f-47cedae89d5b+id=1
Content-ID:
Content-Transfer-Encoding: 8bit
Content-Type: application/xop+xml;charset=utf-8;type="text/xml"
Cheers,
Jason
Jason NesbittPosted Jul 11, 2011, 6:47 AM
I'm using Windows Phone 7 which doesn't have a client app.config or web.config file but I'll have a look through that link and see if any of the things mentioned help.
Cheers
Suthish NairPosted Jul 11, 2011, 6:37 AM
Jason NesbittPosted Jul 11, 2011, 4:38 AM
That did sound promising but now I get the following error when the web service is initialized
(service.Service1Client serviceClient = new service.Service1Client();)
Below is the error:
Could not find default endpoint element that references contract 'service.IService1' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.
Cheers,
Jason
Suthish NairPosted Jul 8, 2011, 5:11 PM
to and try