Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6023439
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T04:00:20+00:00 2026-05-23T04:00:20+00:00

I have successfully created an ASP.net website to make calls to a Soap Web

  • 0

I have successfully created an ASP.net website to make calls to a Soap Web service.

Now I need to turn it into a Class Library that I can call via Com from Classic ASP.

This post on Consume web service in asp.net app from a class library says that I need to add the web service as use “Add Service Reference” instead of “Add Web Reference” to add a reference to the Webservice.

When I try to do that I get an error:

Metadata contains a reference that
cannot be resolved:
‘http://theURL.com:8008/asmx/publicServiceAddress.asmx?wsdl‘.
There was an error downloading
‘http://theURL.com:8008/asmx/publicServiceAddress.asmx?wsdl‘.
Unable to connect to the remote server
A connection attempt failed because
the connected party did not properly
respond after a period of time, or
established connection failed because
connected host has failed to respond
77.95.80.35:8008 Metadata contains a reference that cannot be resolved:
‘http://theURL.com/asmx/publicServiceAddress.asmx‘.
Metadata contains a reference that
cannot be resolved:
‘http://theURL.com/asmx/publicServiceAddress.asmx‘.
If the service is defined in the
current solution, try building the
solution and adding the service
reference again.

…but when I click on advanced and then add then “Add Web Reference” I can add it fine.

Questions:

1) Is it necessary to use “Add Service Reference” instead of “Add Web Reference”?
2) Why, what’s the difference?
3) What are potential causes of this error, and how can I figure this out, for instance I don’t know why it’s going to port 8080 to look for the WSDL http://theURL.com:8008/asmx/reguspublic.asmx?wsdl when it should go to http://theURL.com/asmx/reguspublic.asmx?wsdl

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T04:00:21+00:00Added an answer on May 23, 2026 at 4:00 am

    Service Reference is for Windows Communication Foundation (WCF) services and WCF Data Services where as Web Reference is used when using ‘legacy’ or asmx web services.

    So for ‘asmx’ you should use web reference and not service reference.

    http://alexduggleby.com/2008/08/24/add-web-reference-instead-of-service-reference-in-visual-studio-2008/

    Regarding the error:
    WCF services expose Metadata that enables them to interact with different kinds of endpoints and data. .NET 2.0 asmx webservices only have one endpoint @SOAP. So ‘asmx’ web services does not expose any metadata due to which the error occurs.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the following scenario. I have created an ASP.NET web application (framework 3.5)
I have created a C# web service, a web client, and successfully debugged the
I have an ASP.NET website on a Windows 2003 Server, that needs to access
I have an ASP.NET website (in C#) that takes in user data and then
I have an old .net 2005 web site that has some asp pages and
I have been researching for a while and have actually created a prototype ASP.NET
I have an IIS7.5 web-site, on Windows Server 2008, with an ASP.NET MVC2 web-site
Coding Platform: ASP.NET 4.0 WebForms with C# We have a website with the existing
I've implemented this AJAX countdown timer successfully: - http://forums.asp.net/t/1085601.aspx I created these 3 labels:
Yesterday I began learning WCF by porting an existing ASP.NET Web Service. Creating the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.