C # ASP.NET - Web service works on Win 7 but not on Win 2012 Server

0

I did a development in C # ASPX on a Win 7 platform and in this the web services (REST) work perfectly. I recently deployed in a Win 2012 Server and I have a special WS that brings the dollar change (TRM) from Banco de la República (Colombia). It works without problems in the development platform, but in the Win 2012 server it generates the following error:

  

Source Error:

     

An unhandled exception was generated during the execution of the   current web request. Information about the origin and location of   The exception can be identified using the exception stack trace below.

     

Stack Trace:

     

[WebException: The remote server returned an error: (404) Not Found.]   System.Net.HttpWebRequest.GetResponse () +8442708
  System.ServiceModel.Channels.HttpChannelRequest.WaitForReply (TimeSpan   timeout) +234

     

[EndpointNotFoundException: There was no endpoint listening at    link that could accept the message. Este   is often caused by an incorrect address or SOAP action. See   InnerException, if present, for more details.]
  System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage (IMessage   reqMsg, IMessage retMsg) +14581778
  System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (MessageData &   msgData, Int32 type) +622
  WebApplication1.ref_trm_ban_rep.trm_ban_repSoap.trm () +0
  WebApplication1.master.Page_Load (Object sender, EventArgs e) +126
  System.Web.UI.Control.LoadRecursive () +71
  System.Web.UI.Control.LoadRecursive () +190
  System.Web.UI.Control.LoadRecursive () +190
  System.Web.UI.Page.ProcessRequestMain (Boolean   includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   +3178

I want to emphasize that this WS works perfectly on my Win 7 platform.

My question is: Possibly, is it a configuration issue of the server, ports or the firewall?

Thank you for your kind time.

    
asked by Alexander Pachón 15.03.2017 в 15:50
source

3 answers

1

At the moment you send this error:

  

[EndpointNotFoundException: There was no endpoint listening at link

It means that your new service is looking for a route in localhost , that's why it works locally without problem.

In the web.config file of your server, change the address of your EndPoint to the one where it is published, something like this: p>

<endpoint address="http://URLDeTuServicio/trm_ban_rep.asmx"/>
    
answered by 15.03.2017 / 17:06
source
0

I think you may be missing some features of IIS on the server. I would start by comparing the features that are enabled in the local environment and compare them with those of the server.

    
answered by 15.03.2017 в 15:54
0

Dear, that error comes when the service you are trying to invoke, is not available, this may be because the server is not up or because if you are invoking a service you are developing is not running. If your service is in the local IIS, I recommend that you go to the administrator of IIS and restart the server or by console with administrator persids (Press the windows key, type cmd, right click on the icon, execute as administrator), execute The following command iisreset . Greetings.

    
answered by 15.03.2017 в 19:36