In my ASP.NET website I am trying to comsume a webserice and I and getting the following error:
SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://usaepay.com/soap/gate/3213EA2A/usaepay.wsdl' : failed to load external entity "https://usaepay.com/soap/gate/3213EA2A/usaepay.wsdl"
Any idea on how to resolve it.
Thanks,
Pinaz.
The certificate for the host is for www.usapay.com. If you change your soap call to point at https://www.usaepay.com/soap/gate/3213EA2A/usaepay.wsdl your call should work.
Is it because there is an HTTPS error on the WSDL?
Related
I am getting the below error when i am creating a API proxy on free Apigee cloud environment :
Fetch WSDL Error: Cannot invoke method startsWith() on null object
A similar issues was reported here
Apigee - Issue while configuring an API Proxy
I have kept the wsdl here
http://pastebin.com/tavinD2n
This got resolved . The wsdl file was named as XXX.WSDL , i changed it to XXX.wsdl and it worked. Strange isn't it? Should it be case sensitive?
I am getting the following error message: "You have requested a non-existent service "projet_rating.manager.rating" - Help please.
Two possibilities come to mind:
1) Somewhere in your application you have a controller that includes $this->container->get("projet_rating.manager.rating")
2) Somewhere in a config file you create a service that includes as an argument %"projet_rating.manager.rating"%.
If you're using an IDE that allows searching multiple files for a string, try searching for "projet_rating.manager.rating" in ...src/ or ...app/config
While trying to connect to OpenX with the following code: (asp.net, c#)
IOpenXProxy proxy = (IOpenXProxy)XmlRpcProxyGen.Create(typeof(IOpenXProxy));
proxy.Url = "http://testserver.com/OpenX/www/api/v2/xmlrpc/";
proxy.Logon("username", "password");
I am getting an error message:
Response from server does not contain valid XML. "'--' is an unexpected token. The expected token is '>'. Line 31, position 3."
Using Fiddler it's possible to find out that the response I am getting is http://testserver.com/www/admin/index.php i.e. html login page. Because of that I am getting this error message.
The question is what is wrong? Server settings?
Thank you
The link was wrong: should be "http://testserver.com/www/api/v2/xmlrpc/".
See OpenX.NET to use OpenX from a .Net application. I recommend using ISession instead of IOpenXProxy
Could any one help me in finding the solution for this error.
I have a normal web service which is working fine in intranet, when when the vendors try to access the same from internet, they get this below error.
There was an error downloading
'https://isite.corp.net/Service/Sample.asmx'.
The remote name could not be resolved:
'isite.corp.net'
Metadata contains a reference that
cannot be resolved:
'https://isite.corp.net/Service/Sample.asmx'.
There was no endpoint listening at
https://isite.corp.net/Service/Sample.asmx
that could accept the message. This is
often caused by an incorrect address
or SOAP action. See InnerException, if
present, for more details.
The remote name could not be resolved:
'isite.corp.net'
If the service is defined in the
current solution, try building the
solution and adding the service
reference again.
Does any one know the solution for this.
Thanks.
It seems like domain "isite.corp.net" (website) is not accessible from outside office network because error says "The remote name could not be resolved: 'isite.corp.net'". Please make sure your domain is public and can be accessible from outside. If it is not public, you have ask your vendor to put ipaddress mapping in host file.
While accessing a webservice which is availbale at http://recpushdata.cyndigo.com/jobs.asmx, I am getting this Exception. "Remote name could not be resolved"
Any Suggesytion..what to do..
The server error you got in the previous comment is good - it means your original problem, being unable to resolve the remote host, is solved.
As to your HTTP 500 error, check the event log for that time on the remote host. If you don't have access to it, contact its administrator.
Try using the URL:
http://216.10.246.91/jobs.asmx
If this works, whereever you are calling the web service from has a problem with DNS. If that does not work report back.