Manoj Manohar

Hi

We have deployed our WCF service in IIS and it worked fine with BASICHttpBinding for some time.

I create a windows client using vb.net to consume the web service. its working fine for some time

Suddenly i got this following error message

"The request channel timed out while waiting for a reply after 00:00:59.9687500. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout."

Hence i Increased my Timeout values in the app.config & server side also but i still got the error message. so i opened a new project and tried to bind the WCF Service. I am getting the following error mesage

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\svcutil.exe /noLogo /s /ct:"System.ComponentModel.BindingList`1,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /d:"C:\Documents and Settings\Manoj\Local Settings\Temp\bmceoibz.rtv" /config:"C:\Documents and Settings\Manoj\Local Settings\Temp\bmceoibz.rtv\newapp.config" /mergeConfig /out:"WebReference.vb" /language:vb /n:*,_WebReference "http://ServerMachineIP: port Number/Service.svc"

Attempting to download metadata from 'http://ServerMachineIP: port Number/Service.svc' using WS-Metadata Exchange or DISCO.

Microsoft (R) Service Model Metadata Tool

[Microsoft (R) Windows (R) Communication Foundation, Version 3.0.4506.30]

Copyright (c) Microsoft Corporation. All rights reserved.

Error: Cannot obtain Metadata from http://ServerMachineIP: port Number/Service.svc

If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at http://go.microsoft.com/fwlink/ LinkId=65455.

WS-Metadata Exchange Error

URI: http://ServerMachineIP: port Number/Service.svc

Metadata contains a reference that cannot be resolved: 'http://ServerMachineIP: port Number/Service.svc'.

The request channel timed out while waiting for a reply after 00:03:18.5625000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

The remote server returned an error: (504) Gateway Timeout.

HTTP GET Error

URI: http://ServerMachineIP: port Number/Service.svc

There was an error downloading 'http://ServerMachineIP: port Number/Service.svc'.

The operation has timed out

If you would like more help, type "svcutil / "

or

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\svcutil.exe /noLogo /s /ct:"System.ComponentModel.BindingList`1,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /d:"C:\Documents and Settings\Manoj\Local Settings\Temp\nq152c2g.ib5" /config:"C:\Documents and Settings\Manoj\Local Settings\Temp\nq152c2g.ib5\newapp.config" /mergeConfig /out:"11.75.75.65.vb" /language:vb /n:*,_11_75_75_65 "http://11.75.75.65:5004/Service.svc"

Attempting to download metadata from 'http://11.75.75.65:5004/Service.svc' using WS-Metadata Exchange or DISCO.

Case 1 :

We testing by hosting the Service in the IIS and opened a new windows project and clicked Project --> Add Service Reference

its working fine.

case 2 :

we tried with a wcf client from a system connected in a LAN but the it gave the same error

When ever we try to bind the WCF service it gives a message "Microsoft Visual Studio is busy"

The Wcf service opens in IE and we are able to browse it

Please help us in this issue





Re: Windows Communication Foundation (Indigo) Unable to Bind WCF Service

Manoj Manohar

Any Body There

Please Help me





Re: Windows Communication Foundation (Indigo) Unable to Bind WCF Service

BenK

Looks like my previous reply has not been received

'http://11.75.75.65:5004/Service.svc' is not an end point , have a look in your config file .

It should be something like http://11.75.75.65:5004/Myservice.

If you are using not http make sure you enable a mex end point.

Regards,

Ben





Re: Windows Communication Foundation (Indigo) Unable to Bind WCF Service

Manoj Manohar

Sorrry

This was my first post actually no reply came for 2 days so i reposted it on 6th august in proper heading

Since the wcf service is from third party and since i m posting from India there is some time mismatch going on i will recreate the scenerio and will let u know the information

Thanks & Regards