WSDL URL is invalid or the WSDL file is not valid or incorrect

Hi All,
I am using Oracle Soa Suite 11g. I have got Oracle database, Oracle weblogic admin server, Oracle SOA server all installed on my laptop.
I have deployed a sample BPEL process. When I am trying to test the process it is giving an error
"Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://KSNPavan-PC:8001/soa-infra/services/default/MyHumanWorkFlowSample1Project/vacationrequestprocess_client_ep?WSDL", caused by: java.net.ConnectException. : java.net.ConnectException: Connection refused: connect "
Now, when I change the url address to
"http://localhost:8001/soa-infra/services/default/MyHumanWorkFlowSample1Project/vacationrequestprocess_client_ep?WSDL"
(Please note the difference in host name from KSNPavan-PC to localhost.)
and click parse wsdl it is working well. I mean the test page is opening successfully and I am able to test the service.
Testing the service from admin console is fine. Now I want to use this BPEL process service in another BPEL process. So, when I am piciking this service wsdl in JDeveloper it is throwing me the same error and I am unable to go ahead.
Can anyone please tell me whetherI have to set property in the admin server console so that it always take local host in all the wsdl urls and solve my problem.
Thank you,
KSN Pavan.

Hi All,
My problem has got solved with the help of my colleagues. Actually the problem was that the host name KSNPavan-PC is not there in the C:\Windows\System32\Drivers\etc\hosts file. I Added the host name in the file with the IP same as that of local host and everything isworking well now.
Thank you,
KSN Pavan

Similar Messages

Either the WSDL URL is invalid or the WSDL file is not valid or incorrect.

Hi ,
i deployed one bpel process in weblogic.
when i am click on test below is error is coming. ( its on oracle soa 11)
below is coming for all the process. previously it is working fine.
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://xxxx:8001/soa-infra/services/default/ReadJMS/readtraxjms_client_ep?WSDL: HTTP connection error code is 503
Please help me how it is resolved.
Regards
jan

Hi Jan,
We had the same issue in 11.1.1.3 and we used to restart the server to fix it. Hopefully before going to PROD we upgraded to 11.1.1.5 and next time we saw this issue was only when there was some problem with the OHS (it was down etc.).
Which version you're on?
Regards,
Neeraj Sehgal

RD Client and RDWeb 2012 - RDP file is not valid when run from chrome browser on Android

After signing into the RDWeb using Android Chrome, I see the published remoteapp. If I click to
run remoteapp, it tries to open the RDP file with the installed RD Client but I got this error "Import Error - The RDP file is not valid. Notify your network administrator."
I have google about this error. One of the forum suggest to use RD client remote resources tab to access the apps but in our environment our user want to use their
own web browser to access the apps. Is there any way we can solve this issue?.

Hi,
I’m afraid that we have to configure Remote Resource.
Thanks for your understanding.
Jeremy Wu
TechNet Community Support

Invoking a WS from BPEL - WS URL is hardcoded in the WSDL

I have published a PL/SQL package as a webservice and deployed it successfully to a development instance (say DEV).
I created a BPEL process and used a Partner Link to invoke the above web service. When I deploy the BPEL process to the DEV instance, it works fine. However when I deployed the above WS and BPEL process to another instance (say TEST), the BPEL process still calls the WS in the original (DEV) instance. I verified by invoking the WS in the TEST instance and it is working fine.
When I created the partner link in the BPEL process, I had to provide the actual WS url from the DEV instance and it created the WSDL for me. This probably is causing the issue as the DEV WS url is hardcoded in the WSDL. However I do not know how to provide the WSDL in the partner link so that url/server name is not hardcoded.
Any help with this is greatly appreciated.
JDev - 10.1.3.4
SOA Suite - 10.1.3.4
Thanks.
Edited by: user13163442 on Jul 21, 2011 1:10 PM

Naren,
Thanks for looking into this.
Yes, the web service is calling a packaged procedure which is available in both the environments. This web service is independent and may be used by other BPEL processes or other applications too.
I developed the WS & BPEL process in the dev environment and then deployed to the TEST environment. I did not make any changes to the BPEL & WS before deploying to TEST. The only change I did after deploying the WS to the TEST environment is to map the jndi.
I am not calling the package directly -- I want to consume the WS.
I am not sure about the Composite? Is this something in SOA 11g? I am still on SOA 10.1.3.4
Is this helpful? Did I answer your questions correctly?
Thanks again.

"there was a problem connecting to the server. URLS with the type 'file' are not supported"

i have a new macbook pro 13" and every 6 minutes or so it pops up a window that says "there was a problem connecting to the server. URLS with the type 'file' are not supported". it never seems to cause any problems but is supremely annoying. how can i make this come to an end?

I tried someone's solution of taking another external disc and plugging it in, then when it showed up and time machine asked if I wanted to use it or that someone might be trying to trick me, I chose not use it. Then I shut down my computer, plugged in the original Lacie, and rebooted the computer and all seems to work fine now-- the Lacie appears on my desktop and all seeems to be in working order. Who knows why or anything else,- as weird as it gets- but for now things seemed fixed--- maybe others can try this too-- it worked for me so far.

"There was a problem connecting to the server. URLs with the type "file:" are not supported. Why? What can be done to eliminate it?

After upgrading to Mountain Lion, I repeatedly get this message: "There was a problem connecting to the server. URLs with the type "file:" are not supported.
Why?
What can be done to eliminate it?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Message - There was a problem connecting to the server. URLs with the type "file:" are not supported

new macbook pro receving this message: There was a problem connecting to the server. URLs with the type "file:" are not supported. What is causing this and how do

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

There was a problem connecting to the server. URLs with the type "file:" are not supported. OK

I have just upgraded to Mountain Lion from Leopard, but now I keep getting this message when I open some web-pages and every time I wake the Mac up after going to sleep. For some odd reason I get it in Swedish sometimes (installed language) and some times in English...
There was a problem connecting to the server.
URLs with the type "file:" are not supported.
OK
What is this and how can I get rid of it. I use Firefox and have updated to latest version.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

A Davey1 wrote:
Not a nice answer!
Posting "Check the 'More like this'" area and not simply providing the answer is a great way to make these groups worthless.
You're ignoring context. On the old Apple Discussion Groups I never posted replies like that, instead giving people relatively detailed answers. The new Apple Support Communities made things worse by introducing certain inefficiencies. Then came Lion. The flood of messages that came with Lion required a painful choice for any of the people who had been helping here: (1) Give quality responses to a few questions and ignore the rest. (2) When applicable, give a brief answer such as the one that you found objectionable. (3) Give up all the other normal activities of life and spend full time trying to answer questions here.
People who needed help with Lion problems seemed to have trouble discovering existing message threads that described how to solve their problems. I never posted the suggestion of "Check the 'More like this' area" without verifying that the help that the poster needed could be found there. Even doing that, what I posted saved me time that I could use to help someone else.
The people helping here are all volunteers. None of them is being paid for the time they spend here. They all have a life outside of Apple Support Communities. It's arrogant of you to demand that people helping here spend more time than they already do.

I'm being shown an error pop-up message periodically saying "There was a problem connecting to the server. URLs with the type 'file:' are not supported." I have a brand new MacBook Pro, and at no time am I actually having trouble connecting to the server.

I'm being shown an error pop-up message periodically saying "There was a problem connecting to the server. URLs with the type 'file:' are not supported." I have a brand new MacBook Pro, and at no time am I actually having trouble connecting to the server, but this message continues to pop-up several times a day at random intervals. Is there something I'm doing wrong? Or is my computer just having a glitch? Other than that, and a mildly sticking caps lock button, it's working perfectly.
Thank you!

Alright it didn't solve it. Any other suggestions?
I haven't suggested a solution yet. I want to know whether you still get the messages while Time Machine is disabled. Do you? If so, try any or all of the solutions proposed in this thread:
There was a Problem connecting to the...: Apple Support Communities

I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported." Can someone help me get rid of it.

I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported" Can someone help me locate and get rid of this error.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off .

My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off and continue working.

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Since updating to mountain line, error message "There was a problem connecting to the server. URLs with the type "file:" are not supported" keeps popping up

Since updating to Mountain Lion in the last week, an error message keeps popping up. The graphic is the button with 3 stick men holding hands and the message is "There was a problem connecting to the server. URLs with the type "file:" are not supported". Any solutions found?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

After loading lion, I get an error message "There was a problem connecting with the server. URL's with the type "file" are not supported."

After loading Lion, I have been getting an error message "There was a problem connecting to the server. URLs with the type "file:" are not supported." There does not seem to be any actual problem with internet connectivity, but it is persistent and annoying. Any idea of its cause and treatment?

Take a look at this link, https://discussions.apple.com/message/16156214#16156214

Error message: URL's with the type "file:" are not supported. I get this pop-up twice each time I enter Safari and Mail.

Everytime I go into Mail and/or Safari, I receive a pop-up the states "There was a problem connecting to the server. URL's with the type "File:" are not supported. The pop-up comes up twice each time and I have to click "ok" to close them. Only started after install of OS Lion 10.7. Any one else have this and is there a solution. It is just plain irrating that is does this each time I check my mail or go on the internet. Thanks!

That's interesting. I bet that helps other Safari users!

WSDL URL is invalid or the WSDL file is not valid or incorrect

Similar Messages

Maybe you are looking for