HTTPS - Unable to load WSDL

(I'm using Flex Builder 3)
Hi... I'm building a flex application that has asp.net web
service as a backend. I've put this webservice on the https
protocol with a self-signed certificate. My problem is that my Flex
app can't access this web service over https, unless I manually
direct load the web service page and import the certificate into
browser. This happens with all browsers IE, Opera, Firefox and
Safari.
I get this message:
quote:
[RPC Fault faultString="HTTP request error"
faultCode="Server.Error.Request" faultDetail="Unable to load WSDL.
If currently online, please verify the URI and/or format of the
WSDL (https://localhost/myApp/Service1.asmx?wsdl)"]
at
mx.rpc.wsdl::WSDLLoader/faultHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\ws dl\WSDLLoader.as:98]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()[E:\dev\3.0.x\frameworks\pro jects\rpc\src\mx\rpc\AbstractInvoker.as:168
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\3.0.x\frameworks\project s\rpc\src\mx\rpc\AbstractInvoker.as:220
at
mx.rpc::Responder/fault()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\Responder.as:49 ]
at
mx.rpc::AsyncRequest/fault()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\AsyncRequest .as:103]
at
DirectHTTPMessageResponder/errorHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\mes saging\channels\DirectHTTPChannel.as:343]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/redirectEvent()
It's still in development and I load flex app through http
(not https)... And it will probably stay that way cause I want flex
app to be hosted on one server (http) and have my web service on
totally another server (https).
So, is it possible to have this combination with swf on http
and backend on https?
Thank You

Similar Messages

WebService "Unable to load WSDL" error

I need some help with this strange problem
I have a web service that i call from Flex 3
<mx:WebService id="dataTowns" wsdl="
http://localhost:2008/SqlData.asmx?WSDL"
result="objectTowns(event)" fault="faultHandler(event)"
showBusyCursor="true"/>
Not every time but 40% of the time i would get an error. Web
services are running on my local machine and i run web service
using Visual Studio 2005. Funny thing is that even if i get this
error data still loads in flex. So when i run application from flex
i sometime get an error and some time i don't and works fine. Some
times after the error i restart the webservices and works fine
again. I run Windows Vista i don't know if that has anything to do
with this.
Here is the error :
[RPC Fault faultString="HTTP request error"
faultCode="Server.Error.Request" faultDetail="Unable to load WSDL.
If currently online, please verify the URI and/or format of the
WSDL (
http://localhost:2008/SqlData.asmx?WSDL)"
at
mx.rpc.wsdl::WSDLLoader/faultHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\ws dl\WSDLLoader.as:98]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()[E:\dev\3.0.x\frameworks\pro jects\rpc\src\mx\rpc\AbstractInvoker.as:168
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\3.0.x\frameworks\project s\rpc\src\mx\rpc\AbstractInvoker.as:220
at
mx.rpc::Responder/fault()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\Responder.as:49 ]
at
mx.rpc::AsyncRequest/fault()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\AsyncRequest .as:103]
at
DirectHTTPMessageResponder/errorHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\mes saging\channels\DirectHTTPChannel.as:343]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/redirectEvent()
Thank you

I'm not sure if you have found what you are looking for. But
if you still need complete code using web services let me know i
have no problem giving you this. If you want give me you email i
will send you a complete code via email.

Security error accessing url (Unable to load WSDL)

Hi folks.
I have a Flex project that use a WCF webservice. In my localhost everything is allright, but I want to upload my flex project to a web host (http://www.dorj.ir) and upload my WCF webservice to a server that has a valid IP...
After going to http://www.dorj.ir, you can see this error
Security error accessing url
Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL (http://ip/service.svc?wsdl)
I put the crossdomain.xml file in the root of my server:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="http://www.dorj.ir" />
<allow-http-request-headers-from domain="http://www.dorj.ir" headers="SOAPAction"/>
</cross-domain-policy>
But I have the same error, yet...!
what should I do?!

Have you seen this blog
"Crossdomain.xml" in ABAP Web AS Server cache

Unable to load wsdl. if currently online please verify the uri and or format of the wsdl

Hi,
i have one aspx page in which i have embeded an swf object,
which calls webservice to load data,
it works fine on localhost,
but when uploaded it gives the error no 2032 stream error ,
i added the crossdomain.xml in the root project then that error was gone and found the following error,
"unable to load wsdl. if currently online please verify the uri and or format of the wsdl"
Can anybody help me with this?
Any elp or suggestion will be appriciated.
Thank You.
Bhavika

I had the same error message and I believe I added the -use-network=true to the additional compiler arguments to fix the problem. The default value for this should be true.
Sorry if this doesn't help...It's just a guess.

Flex encounters "Security error accessing url.Unable to load WSDL"

i have created a flex application which connects to SAP via web service.
when i try to run my flex application i encounter the following error.
"Security error accessing url.Unable to load WSDL"
i went through various posts relating a BSP application and crossdomain.xml
i have created the crossdomain.xml file in the application and
i tried those options and still not able to figure out the problem.
the security error is because of the absence of the crossdomain.xml file, and in which path should i be saving the file?
Kindly help me solve the problem.
Thanks in advance.

Have you seen this blog
"Crossdomain.xml" in ABAP Web AS Server cache

Unable to load WSDL

I am trying to consume the 3rd party WSDL below from my BizTalk project in Visual Studio. I am using BizTalk 2010 and Visual Studio 2010.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:appoutcome="http://xxxx/applicationOutcomeService/xxx/schema/messages/v1"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:tns="http://xxxx/xxxx/applicationOutcomeService/xxx/v1"
xmlns:notif="http://xxxx/xxx/xxxx/1.0"
targetNamespace="http://xxx/xxxx/applicationOutcomeService/xxx/v1"
name="applicationOutcomeService"
>
<wsdl:documentation>Version ${project.version}</wsdl:documentation>
<wsdl:types>
  <xs:schema targetNamespace="http://xxxx/applicationOutcomeService/xxx/schema/messages/v1">
   <xs:include schemaLocation="../messages/application-outcome-service-messages.xsd" />
  </xs:schema>
  <xs:schema targetNamespace="http://xxxx/xxx/xxxx/1.0">
   <xs:include schemaLocation="../../../../../schema/deliverynotification/xxxx-v1.0.xsd" />
  </xs:schema>
</wsdl:types>
<wsdl:message name="From">
  <wsdl:part element="wsa:From" name="from" />
</wsdl:message>
<wsdl:message name="MessageID">
  <wsdl:part element="wsa:MessageID" name="messageID" />
</wsdl:message>
<wsdl:message name="RelatesTo">
  <wsdl:part element="wsa:RelatesTo" name="relatesTo" />
</wsdl:message>
<wsdl:message name="To">
  <wsdl:part element="wsa:To" name="to" />
</wsdl:message>
<wsdl:message name="Action">
  <wsdl:part element="wsa:Action" name="action" />
</wsdl:message>
<wsdl:message name="FaultTo">
  <wsdl:part element="wsa:FaultTo" name="faultTo" />
</wsdl:message>
<wsdl:message name="ReplyTo">
  <wsdl:part element="wsa:ReplyTo" name="replyTo" />
</wsdl:message>
<wsdl:message name="ApplicationOutcomeUpdate">
  <wsdl:part element="appoutcome:ApplicationOutcomeUpdate" name="ApplicationOutcomeUpdate" />
</wsdl:message>
<wsdl:message name="ApplicationOutcomeResult">
  <wsdl:part element="appoutcome:ApplicationOutcomeResult" name="ApplicationOutcomeResult" />
</wsdl:message>
<wsdl:message name="ApplicationOutcomeUpdateError">
  <wsdl:part element="appoutcome:ApplicationOutcomeUpdateError" name="ApplicationOutcomeUpdateError" />
</wsdl:message>
<wsdl:message name="ApplicationOutcomeResultError">
  <wsdl:part element="appoutcome:ApplicationOutcomeResultError" name="ApplicationOutcomeResultError" />
</wsdl:message>
<wsdl:message name="DeliveryNotification">
  <wsdl:part element="notif:DeliveryNotification" name="DeliveryNotification"/>
</wsdl:message>
<wsdl:portType name="ApplicationOutcomeServiceProducerPortType">
  <wsdl:operation name="ApplicationOutcomeUpdate">
   <wsdl:input message="tns:ApplicationOutcomeUpdate" name="ApplicationOutcomeUpdate" />
   <wsdl:output message="tns:DeliveryNotification" name="DeliveryNotification" />
  </wsdl:operation>
  <wsdl:operation name="ApplicationOutcomeResult">
   <wsdl:input message="tns:ApplicationOutcomeResult" name="ApplicationOutcomeResult" />
   <wsdl:output message="tns:DeliveryNotification" name="DeliveryNotification" />
  </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="ApplicationOutcomeServiceConsumerPortType">
  <wsdl:operation name="ApplicationOutcomeUpdateError">
   <wsdl:input message="tns:ApplicationOutcomeUpdateError" name="ApplicationOutcomeUpdateError" />
   <wsdl:output message="tns:DeliveryNotification" name="DeliveryNotification" />
  </wsdl:operation>
  <wsdl:operation name="ApplicationOutcomeResultError">
   <wsdl:input message="tns:ApplicationOutcomeResultError" name="ApplicationOutcomeResultError" />
   <wsdl:output message="tns:DeliveryNotification" name="DeliveryNotification" />
  </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ApplicationOutcomeServiceProducerSoapBinding" type="tns:ApplicationOutcomeServiceProducerPortType">
  <wsp:PolicyReference URI="#SSBPolicy"/>
  <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
  <wsdl:operation name="ApplicationOutcomeUpdate">
   <soap12:operation style="document" />
   <wsdl:input>
    <soap12:body parts="ApplicationOutcomeUpdate" use="literal" />
    <soap12:header message="tns:From" part="From" use="literal"/>
                <soap12:header message="tns:MessageID" part="MessageID" use="literal"/>
                <soap12:header message="tns:To" part="To" use="literal"/>
                <soap12:header message="tns:Action" part="Action" use="literal"/>
                <soap12:header message="tns:ReplyTo" part="ReplyTo" use="literal"/>
   </wsdl:input>
   <wsdl:output>
    <soap12:body parts="DeliveryNotification" use="literal" />
   </wsdl:output>
  </wsdl:operation>
  <wsdl:operation name="ApplicationOutcomeResult">
   <soap12:operation style="document" />
   <wsdl:input>
    <soap12:body parts="ApplicationOutcomeResult" use="literal" />
    <soap12:header message="tns:From" part="From" use="literal"/>
                <soap12:header message="tns:MessageID" part="MessageID" use="literal"/>
                <soap12:header message="tns:To" part="To" use="literal"/>
                <soap12:header message="tns:Action" part="Action" use="literal"/>
                <soap12:header message="tns:ReplyTo" part="ReplyTo" use="literal"/>
   </wsdl:input>
   <wsdl:output>
    <soap12:body parts="DeliveryNotification" use="literal" />
   </wsdl:output>
  </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="ApplicationOutcomeServiceConsumerSoapBinding" type="tns:ApplicationOutcomeServiceConsumerPortType">
  <wsp:PolicyReference URI="#SSBPolicy"/>
  <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
  <wsdl:operation name="ApplicationOutcomeUpdateError">
   <soap12:operation style="document" />
   <wsdl:input>
    <soap12:body parts="ApplicationOutcomeUpdateError" use="literal" />
    <soap12:header message="tns:RelatesTo" part="relatesTo" use="literal" />
    <soap12:header message="tns:From" part="From" use="literal"/>
                <soap12:header message="tns:MessageID" part="MessageID" use="literal"/>
                <soap12:header message="tns:To" part="To" use="literal"/>
                <soap12:header message="tns:Action" part="Action" use="literal"/>
                <soap12:header message="tns:ReplyTo" part="ReplyTo" use="literal"/>
   </wsdl:input>
   <wsdl:output>
    <soap12:body parts="DeliveryNotification" use="literal" />
   </wsdl:output>
  </wsdl:operation>
  <wsdl:operation name="ApplicationOutcomeResultError">
   <soap12:operation style="document" />
   <wsdl:input>
    <soap12:body parts="ApplicationOutcomeResultError" use="literal" />
    <soap12:header message="tns:RelatesTo" part="relatesTo" use="literal" />
    <soap12:header message="tns:From" part="From" use="literal"/>
                <soap12:header message="tns:MessageID" part="MessageID" use="literal"/>
                <soap12:header message="tns:To" part="To" use="literal"/>
                <soap12:header message="tns:Action" part="Action" use="literal"/>
                <soap12:header message="tns:ReplyTo" part="ReplyTo" use="literal"/>
   </wsdl:input>
   <wsdl:output>
    <soap12:body parts="DeliveryNotification" use="literal" />
   </wsdl:output>
  </wsdl:operation>
</wsdl:binding>
<wsdl:service name="ApplicationOutcomeServiceProducer">
  <wsdl:port name="ApplicationOutcomeServiceProducerPort" binding="tns:ApplicationOutcomeServiceProducerSoapBinding">
   <soap12:address location="http://TBD"/>
  </wsdl:port>
</wsdl:service>
<wsdl:service name="ApplicationOutcomeServiceConsumer">
  <wsdl:port name="ApplicationOutcomeServiceConsumerPort" binding="tns:ApplicationOutcomeServiceConsumerSoapBinding">
   <soap12:address location="http://TBD"/>
  </wsdl:port>
</wsdl:service>
<wsp:Policy wsu:Id="SSBPolicy">
  <wsp:ExactlyOne>
   <wsp:All>
    <wsoma:OptimizedMimeSerialization/>
   </wsp:All>
  </wsp:ExactlyOne>
</wsp:Policy>
</wsdl:definitions>
I have commented out sensitive names in the namespaces and I cannot provide the XSDs as these are also sensitive but I guess you could replace the imported XSDs with your own simple ones.
I am not getting the binding files complete with the information to create the ports, this is what I get for the custom binding...
<?xml version="1.0" encoding="utf-8"?>
<BindingInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xmlns:xsd="http://www.w3.org/2001/XMLSchema"
             Assembly="Microsoft.BizTalk.Adapter.Wcf.Consuming, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
             Version="3.5.1.0">
<Timestamp>2014-06-12T18:38:44.5868862+01:00</Timestamp>
<SendPortCollection />
</BindingInfo>
I also get strange Port Types in the Orchestration.
Can anyone through some light on why the WSDL is behaving in this way, thanks?

It looks like these are all document operations, meaning you send/receive entire Xml instances instead of parameters.
If that's the case and the message schemas are correctly added to the project, recreating everything else, Orchestration and Physical Ports is not terribly difficult. The Wizard doesn't do anything special or outside what you can do in the UI.

Unable to load WSDL after moving to Air 2.6

I have an AIR app that works fine in 2.5, but fails after moving to FB 4.5 & SDK 4.5.1 & Air 2.6!
It fails to load a WSDL file if the host address is in a separate network.
My box is in 10.0.1.202, and the following wsdls load fine:
- http://localhost:8080/wsdl
- http://10.0.1.202:8080/wsdl
- http://10.0.1.8:8080/wsdl (another box)
But any other address out of the 10.0.1 subnet fails to load, I get a Client.Error.RequestTimeout fault.
If I try http://192.168.10.100/wsdl (a box on a VPN network I have access to) it fails. Mind you that before issuing a loadWSDL(), the same app does a URLLoad from http://192.168.10.20 and that work fine (it call that address to look for updates).
So the addresses are all valid and do return a valid wsdl.
The 2.5 version, built with FB 4 & sdk 4.1 works flawlessly. So this must be something with either FB 4.5 or Air 2.6.
Maybe something related to security. I have no clue as to what might be causing this.
Oh, in time, I have generic crossdomain.xml in all sites (those are test sites).
Thanks for any pointers.
cheers,
julio

Hi Julio,
Could you log this as a bug over at bugbase.adobe.com? Also, have you tried this on AIR 2.7?
Thanks,
Chris

Security error accessing ur unable to load wsdl

HI
I am using a webservice(.net webservice) that is on my
localhost and using it in flex application that is also on my
system. Means both the webservice and flex application are on the
same system.
But when i gives the reference of the webservice using the
system ip and run the application by the flex builder it generates
the error as:
mx.messaging.messages::ErrorMessage)#0
body = (Object)#1
clientId = "DirectHTTPChannel0"
correlationId = "24CD6542-F141-1A05-BA35-00A108CB30A0"
destination = ""
extendedData = (null)
faultCode = "Channel.Security.Error"
faultDetail = "Destination: DefaultHTTP"
faultString = "Security error accessing url"
headers = (Object)#2
messageId = "CC123DF0-0E6C-05FF-7894-00A109676283"
rootCause = (flash.events::SecurityErrorEvent)#3
bubbles = false
cancelable = false
currentTarget = (flash.net::URLLoader)#4
bytesLoaded = 0
bytesTotal = 0
data = (null)
dataFormat = "text"
eventPhase = 2
target = (flash.net::URLLoader)#4
text = "Error #2170: Security sandbox violation:
http://localhost:3000/MYCIMS/flex_bin/Design.swf
cannot send HTTP headers to
http://myip/MyServer/AdminWS.asmx."
type = "securityError"
timestamp = 0
timeToLive = 0
I have put crossdomain.xml file in the root of the localhost
and made every changes possible in the crossdomain.xml file but the
application is not running.
Please somebody provide an effective solution, I have spend
lots of time to resolve the problem but its not being....
Thanks in advance
Gopi Saini

Have you seen this blog
"Crossdomain.xml" in ABAP Web AS Server cache

"Unable to load URL" error when importing VS2008 created WSDL

One of my developers created a simple web service in Visual Studio 2008 that queries a database on our SQL Server 2005. I can view the web service results in a web browser with no problems. I can also pull up the WSDL in the web browser with no problems (http://<ip address>/Service.asmx?WSDL). However, when I try to load WSDL into a Web Service Connection in Xcelsius 2008, I get the "Unable to load URL" error.
I've also tried to use the web service as a data source in Crystal Reports 2008, but I get another error:
Logon failed.
Details: Schema file is invalid
error: src-resolve: element 'schema@http://www.w3.org/2001/XMLSchema' not found
I've seen a post in which it looked like Crystal acknowledged this as a bug in the XML driver used by Crystal products, but it should be fixed in a service pack update. I've got the latest service packs and fix packs installed for both Xcelsius 2008 and Crystal Reports 2008.
I scanned the information being sent/returned to Xcelsius using Fiddler and it looks like the request is getting through and the actual WSDL file is being returned to Xcelsius, so it shouldn't be an authentication issue. It seems like Xcelsius doesn't like the WSDL file for some reason. However, it is automatically generated by Visual Studio 2008.
Any ideas as to how I can get Xcelsius to use this test web service?

Having the same issues here also.
I can see the wsdl file being accessed successfully in the web access log, but Xcelsius v5.3 return "unable to load URL"
Only thing I can guess is that the schema is "untyped"
So, nobody in SAP has a solution?

Error loading wsdl from the OSB in the SOA Suite over https

Hi,
We are running SOA Suite 11G R1 PS2. I have created a webservice in the OSB which runs on https://soa-test.myfirm.com/schedule/service/v1. This service works fine. I can test it in the OSB and using SoapUI. Now I want to make use of it in a bpel proces in the SOA Suite so I added the webservice as external reference and pointed it to the the above url. This works...it sees the porttype and all the bindings. But when I want to deploy it, it doesnt compiles and i get the following issue:
Error(19,30): Load of wsdl "https://soa-test.myfirm.com/schedule/service/v1?wsdl" failed
Error(29,89): Cannot find Port Type "{http://www.myfirm.com/wsdl/schedule/service}ScheduleServicePortType" for "ScheduleService" in WSDL Manager
So it seems it cannot load the wsdl. I saw it might be a proxy issue but I dont use a proxy. I can see the wsdl using my browser without proxy settings.
Does anyone know why it cannot load my wsdl?
best regards,
H
Edited by: 860367 on 20-May-2011 05:32

The issue changed to an certificate issue now.
I get the error:
javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:784)
     at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:234)
     at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:105)
     at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:464)
     ... 156 more
Caused by: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:227)
     at oracle.j2ee.ws.common.transport.HttpTransport.transmit(HttpTransport.java:75)
     at oracle.j2ee.ws.common.async.MessageSender.call(MessageSender.java:64)
     at oracle.j2ee.ws.common.async.Transmitter.transmitSync(Transmitter.java:134)
     at oracle.j2ee.ws.common.async.Transmitter.transmit(Transmitter.java:90)
     at oracle.j2ee.ws.common.async.RequestorImpl.transmit(RequestorImpl.java:273)
     at oracle.j2ee.ws.common.async.RequestorImpl.invoke(RequestorImpl.java:94)
     at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:741)
I looked in the forum and this could be solved by adding the root CA to the trust keystore of the server. My OSB Managed Server and SOA Managed Server are on the same machine (https://sontprs201.myfirm.com:8888). This machine has a certificate of GoDaddy so i have added the GoDaddy-root and GoDaddy-intermediate as trusted certificates to my certs.jks
In the weblogic console I set both the managed servers to point to my certs.jks with the correct password and in OSB managed server i setup the SSL with the correct private key alias.
When i call the OSB service from SoapUI i get the correct 3 certificates back (GD-root, GD-intermediate, sontprs201.myfirm.com), but when I call the OSB service from BPEL I still get the error: Unable to access the following endpoint(s): https://sontprs201.myfirm.com:8888/schedule/service/v1. Unable to find valid certification path.
Does anybody know what I'm missing or how I can debug this?
Thanks in advance!

Why do I get the error message "unable to load page (HTTP 502) when I try to open Mobile Web?

I have an LG Octane 3 basic phone.   Does everything I need, phone and text, and I never was interested in web or e-mail capabilities until I recently upgraded our plan to the "More Everything" and was able to use data and check e-mail and access the internet.   Whenever I try to open Mobile Web, I get the error message "unable to load page (HTTP 502)".    As of March 31, 2015, all of us basic phone users lose the "Mobile Email" app on our phones, and will have to access web versions of our e-mail via the web. Which is currently unavailable and doesn't work.
Over a week ago, did a chat session with a tech support rep, and she indicated that either she or an engineer would contact me with how to fix the problem.   Have not heard anything from anybody, and the deadline is approaching quickly.   Have no need of all the excess features of a smart phone, nor do I wish to be forced to jettison a perfectly working phone for my needs and buy something I don't want to be able to do 2 simple things.............check e-mail to see if there's something that needs to be answered right away, and to check traffic reports when I'm on the road, or find something in an area with which I'm not familiar.     Not really too much to ask, you would think....   )
Has anyone else had this same problem, and if so, how do we fix it....??? My next move is a phone call, but those haven't always been very productive.
If any of you have any ideas why this error keeps coming up and the web can't load, and some on how to fix it, I would really appreciate some advice.
Thanks in advance.
Karen

Since the chat session got no reply, I contacted Verizon by phone and a very nice level 2 tech created a trouble ticket and sent it up the food chain. Got a call back, maybe 2 days later, and had a nice, although very long session with a higher level tech. They had determined that the browser for the LG Octane is an old one and no longer supported by Verizon.    We tried everything we could to download the Opera browser, but since I was totally unable to get Mobile Web to work, couldn't do it.   The only other possible "fix" was to totally reset the phone to factory specs and try it again.   That would mean a lot of work on my part to move anything I didn't want to disappear off the phone, and find a place to forward texts that had to be saved.   Caught our tenants lying about why the rent was late (again), and need that for when I put them back on a lease....
Long story short is that unless we try this total reset, which isn't a sure fix, either, anyone who isn't able to access the Mobile Web with the LG Octane will have to change their plan to avoid paying for data that you can't access using any method.
I ran a test with an app that I knew was no longer valid.....that was sending photos to PixPlace.   Got the exact same error message as when trying to access Mobile Web to get the web version of my e-mail.   That just verified that the 502 error is, at least in the LG Octane, for an app that no longer works.   After today, we'll get the same thing when we try to access Mobile E-Mail.
Have to admit, it's a real ****-off, but this shouldn't surprise me, since Verizon won't repair older copper phone lines if you are in an area where FIOS is offered.
I am going to immediately change my husband's and my cell phone plan to one without data, and see what I can find that will still give unlimited calls and text. The way my luck runs, they won't offer one for a decent price. The other half has some very long-winded friends and he was always running over minutes, and some months are very text-heavy and I'd go over my limit.   Absolutely HATE touch screens, and am not looking forward to having to get a new phone.

Firefox unable to load https sites

Since Monday I have been unable to load up any secure site (e.g. that starts with "https://....") in Firefox.
It says it's loading, but sits there for a few seconds and then comes up with a "Problem loading page" screen.
The same sites open fine in IE.
These sites worked fine in FF until this week. I haven't changed any FF settings, I have cleared all cache, done a complete reinstall of FF - all to no avail.
I have no addons, and all plugins are disabled.
I am running Windows 7 Professional.
Help!
== Operating system ==
Windows 7 Professional

PS. There are no firewall / proxy settings blocking HTTPS sites.

Error "Unable to Load URL" in Dashboard Design 4.1 SP2 while create web service connection

Hello Experts,
I am using SAP BO Dashboard Design 4.1 SP2.
I have create one web Intelligence report and from it i create web services url using of publish data feature.
when I use this url to create Web service(Qaaws) connection in dashboard It is showing me error " Unable to Load URL "
URL is working fine in browser in server system where i install SAP BO 4.2 but it is not working in my system where i installed dashboard design.
Please suggest how do i make connection using of this URL in dashboard.
Do i miss something or doing wrong ? then guide me.
Thanks and Regards,
Dhaval Dave

Hi Dave,
Please check the below link,
How to create Xcelsius Dashboard based of BI Web Service ( BIWS )
Using Webservice in Dashboard
Webservices in Dashboard - Issue
Also change your original link here and try to load
(sample link)
From:
http://BOE:8080/dswsbobje/qaawsservice/bisw?def=1&cuid=xxxxxxxxxx
To:
http://BOE:8080/dswsbobje/qaawsservice/bisw?wsdl=1&cuid=xxxxxxxxxx
or else can you post your url here.
Hope this helps.
--SumanT

QAAWS : Import URL failed : Unable to load URL

Hi everybody,
I have a problem with QAAWS . I created a QAAWS and copied URL ( I clicked "To Clipboard" but nothing happened so I clicked the URL, and a web browser appeared, then I copied this URL) .
my URL : http://boxi31:8080/dswsbobje/qaawsservices/biws?def=1&cuid=AXP8AcnBLFVClPYIcK5jUGE
Next, I opened Xcelsius \ Clicked Manage Connections \ Add QAAWS \ named this connection \ pasted the URL copied above to the blank of " WSDL URL" . After that, I clicked "Import" but an Error dispalyed : Unable to load URL.
I don't know why it happened like that . Maybe I made mistakes somewhere???
Pls, Help me to solve this problem.

Hi All,
I was having the same problem in BI4.0 SP2 Patch 16. Even external WSDLs gave the error so the issue wasn't with the BOBJ Server or the QaaWS URL syntax.
I'm on a machine that also had Client tools, CRE, CR 2008 and CR 2011 installed. I forget the install order. I uninstalled the Xcelsius patch, then the base SP2, and re-installed them both.
This fixed the issue.
So maybe one of the other installs messed with Xcelsius. If you're having this error, and the URL is displaying fine in a browser, then maybe try from another install of Xcelsius.

Please : WWC-43273 - ContainerException: Unable to load resource bundle

Please Help :(
Development Environment:
Application : Hello World Portlet
OAS : 10.1.2.0.2 Installed on LocalHost
Development Tool : JDeveloper 10.1.3.2.0
Portal Server : 10.1.4 Installed on LocalHost
I have followed following Tutorial for the same : http://www.oracle.com/technology/obe/obe1014portal/standards_portlets/stdsplts.htm
My EAR WSDL (http://localhost/HelloWorld/portlets?WSDL) in OAS is working perfectly fine yeilding following output :
<?xml version = '1.0' encoding = 'UTF-8'?>
<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl">
<import namespace="urn:oasis:names:tc:wsrp:v1:bind" location="http://www.oasis-open.org/committees/wsrp/specifications/version1/wsrp_v1_bindings.wsdl"/>
<wsdl:service name="WSRPService">
<wsdl:port binding="bind:WSRP_v1_Markup_Binding_SOAP" name="WSRPBaseService">
<soap:address location="http://infra:80/HelloWorld/portlets/WSRPBaseService"/>
</wsdl:port>
<wsdl:port binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService">
<soap:address location="http://infra:80/HelloWorld/portlets/WSRPServiceDescriptionService"/>
</wsdl:port>
<wsdl:port binding="bind:WSRP_v1_Registration_Binding_SOAP" name="WSRPRegistrationService">
<soap:address location="http://infra:80/HelloWorld/portlets/WSRPRegistrationService"/>
</wsdl:port>
<wsdl:port binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
<soap:address location="http://infra:80/HelloWorld/portlets/WSRPPortletManagementService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
However when i try to access the same via Register Provider wizard in Portal Server 10.1.4 i get this exception.
An error occurred during the call to the WSRP Provider: Java stack trace from root exception:
java.rmi.ServerException: Internal Server Error (java.lang.RuntimeException: oracle.webdb.wsrp.server.ContainerException: Unable to load resource bundle "portlet.resource.CHelloWorldBundle")
at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:384)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:245)
at oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown Source)

Found the solution:
I needed to choose the Servlet 2.3/JSP 1.2 (J2EE 1.3) when creating my JSR268 Portlet.
Also the second change I needed to make was to use J2SE ver. 1.4.2_12. To do this change the default j2se ver. of JDeveloper(i.e ver. 1.5) from project properties > libraries node > edit/change j2se definitions screen and select java.exe from j2se1.4.2_12/bin

HTTPS - Unable to load WSDL

Similar Messages

Maybe you are looking for