Not able to browse the service url. RRS feed

  • Question

  • Hello All,

    i have a wcf service which i have deployed on the development server.

    on the server itself when i browse to the service it gets browsed.

    but when i am trying to browse it from the local machine it's not getting browsed.

    i have tried to add the reference from the visual studio but it's throwing the error as

    the metadata contains a reference that cannot be resolved.

    i have hosted the service on the different port rather than default port.

    Monday, January 16, 2017 6:51 AM

All replies

  • Hi EmpAnsar,

    >> when i am trying to browse it from the local machine it's not getting browsed.

    What error did you get when you browse it from local machine web browser? Could you share us your urls in development server and local machine?

    You need to use ip address or computer name instead of localhost, in addition, you need to add port number which you configured for your wcf service in iis to url.

    Here is a simple.

    http://computer name:81/WCFSample/Service1.svc
    http://IPv4 Address:81/WCFSample/Service1.svc

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Tuesday, January 17, 2017 2:43 AM
  • Hello EmpAnsar,

    Because you are getting the error "metadata contains a reference that cannot be resolved", it sounds like the issue is server-side (guessing) as you are most likely able to access the service from the client and the correct handler (WCF) is being used to return the error.

    So, it sounds like access or configuration.  Have a look at what app pool the service is running and if the service has access to the windows temp directory and running directory:  

    Also, config could be an issue:

    Also, check the different pages of the wsdl of the service browsing on the service to see if the error is reported.  This should be the case but it is good to verify the issue is server-side.

    Cheers, Jeff

    Tuesday, January 17, 2017 7:03 PM