Problem connectiin​g to web services server

I've been trying to download the latest software/firmware updates for my All-in-one HP Photosmart Prem C310a.
I cannot get Product updates nor enable Web Services because it always gives me the error message " problem connectiing to web services server". 
I have attempted everything in the trouble shooting section on HPs website including connecting through WPS -unsucessfully. 
This question was solved.
View Solution.

I understand you are getting unable to connect to server error message on your printer. I would first unplug router and printer for about 1 minute. I would plug router up first then printer. I would then try to enable web services. If not successful and you get same error message. I would follow these steps.
1. Obtain your printer's IP address
a. This can be done by pressing the wireless icon on printer.
2. Enter the printer's IP address in a browser.
3. Select the network tab at the top of the page.
4. On the left select networking.
5. Select Network Address (IP)
6. Select Manual DNS Server
a. Manual Preferred DNS should read 8.8.8.8
b. Alternate DNS Server should read. 8.8.4.4
7. Select apply you might get a warning just select okay.

Similar Messages

  • Problem connecting to Web Services server

    Hello,
    I've had my printer running perfectly since I installed it 3 days ago but today I am nolonger able to use eprint. I can still scan and print from my home PC and laptop but I am unable to send emails directly to the printer now. This was working fine and I used the feature fairly often without error but today no emails arrived. When I logged on to the eprint web site using my google account {Personal Information Removed} the status of the printer said disconnected. I've tried deleting the printer and re-attaching it (which had no effect) and I've now tried disabling web services on the printer then re-enabling it. When I try this I now receive the following error: Problem connecting to Web Services server.
    The printer model is a HP Photosmart Premium C310a with the lastest software update. The printer is connected to my network via Wifi and is reachable and usable from all my PC's.
    It seems to me that there is something wrong with the software configuration on the printer, the reason I think this is because the screen interface slows down to a crawl after some use and when this happens it is not possible to switch the printer off via the power button. The only solution is to pull the power cable! This is something new and didn't happen before, is there a way to reset to factory default, the option in the menu doesn't seem to reset everything?
    Please advise ASAP.
    Thanks in advance,
    Stuart {Personal Information Removed}

    Greetings,
    The ePrint Service has been having some issues after the upgrade. The server team has found and fixed a bug in the latest release that affected connectivity. If you're having problems, please unregister your product (from the Web Services menu, select "Remove Web Services"), then register again (from the Web Services menu, select "Enable Web Services).
    After reregistering, I have been very successful using both ePrint and the Print Apps using my HP LaserJet CM1415. It has been staying connected, and promptly printing jobs I send to it. It has also been reconnecting after I powercycle. I sincerely hope you have the same experience. We had an ePrintCenter outage a few minutes ago that may have affected connectivity, but I am able to use ePrint and the Print Apps again as of 5:15 Mountain Time.

  • A problem with building a web service with netbeans

    always a problem occurs when i try to build a web service server side.
    build is perfect .but when i said run the project there is an error occurs:
    "Deployment error:null. See the server log file for details."
    error link goes me to this row in the build-impl.xml file of the project:
    <nbdeploy forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" debugmode="false"/>
    i am waiting for your help.

    Being a total novice on the https/SSL configuration side of things, I've finally managed to dig down to the fact that our external partner of course needs to have a certificate installed in order to run https.
    I guess the browser did not prompt and ask for acceptance of this, because it was already verified through one of the standard issuers - VeriSign.
    So was then able to export the certificate through IE's Properties>Certificate>Details>Copy To File...
    Will then try to import this into the correct domain on the WebLogic server.
    (A quick test of the web service from the EM console worked fine. Strange then that executing the service through a partner link in bpel does not work, but I guess it may have to do with a local bpel being exposed as a web service in itself, and that security on both sides is called for... maybe... :-) )
    -Haakon-

  • Is there an issue connecting to the web services server currently?

    Keep getting an errror, "problem connecting to web services server" This used to work fine. I tried turning off web services and it allowed me to, but now I can't re-enable them.

    Hi Pirmin87,
    There was a known brief outage a few days ago that could have resulted in this.
    - http://status.businesscatalyst.com/
    However at the moment everything should be connecting fine.  If still an on-going issue please reach BC direct chat support for further investigation. 
    - http://helpx.adobe.com/contact.html?product=business-catalyst
    Kind regards,
    -Sidney

  • Web services server side uses C dll (native calls)

    Hi,
    I developed a web service using JAX-RPC. My implementation class uses native c function calls. Dose anybody know where I should put my C dlls and their dependentcy files on Web service server side (tomcat)? If they should be in the .war file, what kind of path in the war would be?
    I have an exception ocurred, like this
    [java] java.rmi.ServerException: Missing port information
    [java] at com.sun.xml.rpc.client.StreamingSender._raiseFault (StreamingSender.java:357)
    [java] at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:228)
    I think probably it is because of native call problem, since I could get something back if not using native call.
    Anybody has similar experience when developing web service using JAX-RPC and calling native c api functions on server side?
    Thanx in advance!

    Yes, I just tried it again (comment all native call out and just call the method that doesn't use native call, it works).
    So your web service application using jax-rpc and c native dlls works already?
    Can you tell me where you put all the native C DLLs and where I can set java.library.path in tomcat?
    Thank you!

  • Problem while Introspecting a Web-Service in OBPM 10GR3 studio

    I get the following problem while Introspecting a Web-Service in OBPM 10GR3 studio:-
    Introspecting...
    downloading /test-ws/testc?wsdl [Error] Instrospection exception: Web Service WSDL parse exception: HTTPS hostname wrong: should be <test-01.test.net>...
    Any idea why?
    It runs well in a browser, eclipse and SOAP UI?

    have you create the destination?
    do  you use the wizard to generate code?
    usually there is catch clause for this line of code
    wdContext.currentRequest_SERVICE_MDM_LOOKUPElement().modelObject().execute();
    Edited by: John Wu on Dec 16, 2010 11:51 PM

  • Safari cannot open the page ~ The error was: "There was a problem communicating with the web proxy server (HTTP)

    Help!  I was cruzing along just fine and went out tonight only to receive the message above:
    Cannot open Page
    Safari cannot open the page
    The error was: "There was a problem communicating with the web proxy server (HTTP)."
    I have had all the Apple iPhone phone.  Have never encountered anything like this. 
    All systems are GO as soon as I log on to wifi. 
    Can anyone help, please. 

    I am also fixed.  I also loaded Onavo, but that was the other day ... this is what I did with the help of online chat with AT&T ...
    I went to:
    Settings
    Wifi
    I selected the network I was working on by hitting the blue arrow located on right side
    At the detail page of that network I scolled down to the bottom to find HTTP Proxy boxes
    I was on Off and changed it to Auto and it worked! 
    I was soo jazzed!!
    Instructions said if it was already on AUTO, to change it to Manual and make your Port = 80 but I didn't have to do that!
    YIPPIE!!  I'm a new man!!
    Go to settings -----> WI-FI  -----> select the network you're using  ------> hit the blue arrow located on the right-side of the network name (ie: show details of that network), this takes you to another page.  
    --------> at the bottom of the page you'll see "HTTP Proxy" boxes (located below the "renew lease" button) ---------------> change the proxy to AUTO.   Note: if you're already at AUTO, change it to "Manual" and make your Port = 80.

  • OWSM how can i get user credentials from gateway in web service server

    I need username in web service server. Gateway has option like "Insert WSBASIC Credentials" and service definition in gateway has "forwardcredentials" option. how can i use these options? has some any idea or sample code.

    Hi Surya,
    You asked whether there are any other solutions other than JavaBean.
    There are ..
    It is a round about way. But should work good on WEB. This is particular to MS things.
    As you know you can use vb scripting to invoke all of this Ms things on WEB. So the trick is have a dynamic page called with your actual doc name as a parameter. Script and do whatever you want in this Dynamic method. And from within Forms call this Dynamic page using WEB.show_document( remember within Forms I can call any WEB viewable doc ). It should do the job.
    But ( And that is a big but...)..
    You need to take care of lot many things here.
    You must have a app server which would support scripting like VB. And you must have MS OFFICE in the server . I understand this works best with 2000.
    So finally it boils down to what I need and what I have. And Yes It requires a good effort.
    Great going??? :))
    Good Luck
    Vijay

  • Envy100_Problem connecting to Web Services Server

    WIreless printing functions working well.  But I cannot get the Envy 100 to connect with the Web Services server.  Suggestions?

    Have you enabled web services and gotten a printout that says its email address?
    What brand/model router?
    Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
    I am employed by HP

  • Client in Visualbasic/C  to  JavaTM Web Services server

    Hi
    can I use client written in Visualbasic or C to access to JavaTM Web Services server.
    If yes does someone have source code for me?
    Thanks

    Hi,
    I've got a VB (6.0) client that talks to a Java Web Service.
    It's a simple VB program and a simple server, but the messages flow.
    Also check out:
    1) http://www.scottnichol.com/soap.htm
    2) http://www.scottnichol.com/vbclienthiapachesoap.htm
    3) http://www.scottnichol.com/vbclientapachesoap.htm
    You will also need the latest SOAP libraries from M$.
    How can I get code to you?
    I found the TcpTunnelGui most helpful (I think it's in the Apache file: soap-bin-2.3.1.zip).

  • Problem about Calling SQLplus Web Service on Aspen Watch Server

    Hi all,
    We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
    According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
                                                                                    Server A / Server B / Error, if applicable
    .Net Framework installed on MII server:                                 1.1, 2.0 /      1.1, 2.0     
    .Net Binding:                                                                          1.1 /               2.0
    IIS version on MII server:                                                 6 /                 6     
    From MII server broser to Server A web service:                 Yes /      Yes     
    From MII server browser to Server B web service:                 No /     No /      Return on web "The test form is only available for requests from the local machine"
    From localhost browser to Server A web service:                 n/a //     Yes     
    From localhost browser to Server B web service:                 Yes //     n/a     
    From PC browser to Server B web service:                                No /        Yes /     Return on web "The test form is only available for requests from the local machine"
    Credentials required to run web service:                                 No /     Yes /     
    The following are the SOAP generated:
    Server A
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      <s:element name="string" nillable="true" type="s:string" />
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpGet">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpGetIn" />
      <wsdl:output message="tns:ExecuteSQLHttpGetOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpPost">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpPostIn" />
      <wsdl:output message="tns:ExecuteSQLHttpPostOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
      <http:binding verb="GET" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <http:urlEncoded />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
      <http:binding verb="POST" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <mime:content type="application/x-www-form-urlencoded" />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Server B
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
    Best regards,
    Lawrence
    Edited by: UMeng Lai on Feb 6, 2009 4:07 PM

    Hi all,
    We're using MII 11.5 and trying to call a web service from a Aspen Watch server through the web service block in transaction. The web service enclosed a function call ExecuteSQL which will accept a sql query function and return a set of Data. Now, using the same web service on two different servers, we got a success(server A) and a failure(Server B). On the failed call, right in the first page of enter a URL, it will return a "SOAP Service could not be loaded: The element type 'META' must be terminated by the machine end-tag '</META>'" error.
    According to the admin of the web server, the web service on both servers can be called correctly when he created two simple ASP pages. After serious testing, he thought that the only reason should be MII may not be compatible with .Net 2.0 binding web service. The following is some comparison we made to the two servers.
                                                                                    Server A / Server B / Error, if applicable
    .Net Framework installed on MII server:                                 1.1, 2.0 /      1.1, 2.0     
    .Net Binding:                                                                          1.1 /               2.0
    IIS version on MII server:                                                 6 /                 6     
    From MII server broser to Server A web service:                 Yes /      Yes     
    From MII server browser to Server B web service:                 No /     No /      Return on web "The test form is only available for requests from the local machine"
    From localhost browser to Server A web service:                 n/a //     Yes     
    From localhost browser to Server B web service:                 Yes //     n/a     
    From PC browser to Server B web service:                                No /        Yes /     Return on web "The test form is only available for requests from the local machine"
    Credentials required to run web service:                                 No /     Yes /     
    The following are the SOAP generated:
    Server A
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      <s:element name="string" nillable="true" type="s:string" />
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostIn">
      <wsdl:part name="command" type="s:string" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpGet">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpGetIn" />
      <wsdl:output message="tns:ExecuteSQLHttpGetOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:portType name="SQLplusWebServiceHttpPost">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLHttpPostIn" />
      <wsdl:output message="tns:ExecuteSQLHttpPostOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpGet" type="tns:SQLplusWebServiceHttpGet">
      <http:binding verb="GET" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <http:urlEncoded />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceHttpPost" type="tns:SQLplusWebServiceHttpPost">
      <http:binding verb="POST" />
    - <wsdl:operation name="ExecuteSQL">
      <http:operation location="/ExecuteSQL" />
    - <wsdl:input>
      <mime:content type="application/x-www-form-urlencoded" />
      </wsdl:input>
    - <wsdl:output>
      <mime:mimeXml part="Body" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://clkaspenwatch:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpGet" binding="tns:SQLplusWebServiceHttpGet">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceHttpPost" binding="tns:SQLplusWebServiceHttpPost">
      <http:address location="http://servera:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Server B
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.aspentech.com/SQLplus.WebService/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://www.aspentech.com/SQLplus.WebService/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    - <wsdl:types>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.aspentech.com/SQLplus.WebService/">
    - <s:element name="ExecuteSQL">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="command" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
    - <s:element name="ExecuteSQLResponse">
    - <s:complexType>
    - <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="ExecuteSQLResult" type="s:string" />
      </s:sequence>
      </s:complexType>
      </s:element>
      </s:schema>
      </wsdl:types>
    - <wsdl:message name="ExecuteSQLSoapIn">
      <wsdl:part name="parameters" element="tns:ExecuteSQL" />
      </wsdl:message>
    - <wsdl:message name="ExecuteSQLSoapOut">
      <wsdl:part name="parameters" element="tns:ExecuteSQLResponse" />
      </wsdl:message>
    - <wsdl:portType name="SQLplusWebServiceSoap">
    - <wsdl:operation name="ExecuteSQL">
      <wsdl:input message="tns:ExecuteSQLSoapIn" />
      <wsdl:output message="tns:ExecuteSQLSoapOut" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="SQLplusWebServiceSoap" type="tns:SQLplusWebServiceSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:binding name="SQLplusWebServiceSoap12" type="tns:SQLplusWebServiceSoap">
      <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ExecuteSQL">
      <soap12:operation soapAction="http://www.aspentech.com/SQLplus.WebService/ExecuteSQL" style="document" />
    - <wsdl:input>
      <soap12:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap12:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="SQLplusWebService">
    - <wsdl:port name="SQLplusWebServiceSoap" binding="tns:SQLplusWebServiceSoap">
      <soap:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
    - <wsdl:port name="SQLplusWebServiceSoap12" binding="tns:SQLplusWebServiceSoap12">
      <soap12:address location="http://serverb:13080/sqlpluswebservice/sqlpluswebservice.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    Please advise me on how to fix the probelm. And please let me know any additional information is needed. Greatly appreciated~
    Best regards,
    Lawrence
    Edited by: UMeng Lai on Feb 6, 2009 4:07 PM

  • Problem in deploying a web service

    hi all,
    i am creating java files out of a wsdl and tring to deploy them. but there is some problem because when i try to deploy the java files it throws following exception:
    E:\eclipse\workspace\AvailRqOTAToTH\com\tourico\webservices>java org.apache.axis
    .client.AdminClient deploy.wsdd
    Processing file deploy.wsdd
    Exception: AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: java.lang.reflect.InvocationTargetException
    faultActor:
    faultNode:
    faultDetail:
    {http://xml.apache.org/axis/}stackTrace:java.lang.reflect.InvocationTarg
    etException
    at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder
    .java:221)
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.
    java:128)
    at org.apache.axis.encoding.DeserializationContext.endElement(Deserializ
    ationContext.java:1087)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endEleme
    nt(AbstractSAXParser.java:585)
    at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan
    EndElement(XMLNSDocumentScannerImpl.java:560)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
    l$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1555)
    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp
    l.scanDocument(XMLDocumentFragmentScannerImpl.java:341)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X
    ML11Configuration.java:828)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X
    ML11Configuration.java:758)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.
    java:148)
    at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Ab
    stractSAXParser.java:1178)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at org.apache.axis.encoding.DeserializationContext.parse(Deserialization
    Context.java:227)
    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
    at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnders
    tandChecker.java:62)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
    at org.apache.axis.client.Call.invoke(Call.java:2748)
    at org.apache.axis.client.Call.invoke(Call.java:1784)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
    at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
    at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
    {http://xml.apache.org/axis/}hostname:ff-930b52be034f
    here is the snippet of the wsdl:
    <wsdl:portType name="HotelsServiceSoap">
    <wsdl:operation name="BookHotel">
    <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Create reservation(s) for selected rooms. Separate reservation created for each room</documentation>
    <wsdl:input message="tns:BookHotelSoapIn"/>
    <wsdl:output message="tns:BookHotelSoapOut"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="HotelsServiceSoap" type="tns:HotelsServiceSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <wsdl:operation name="BookHotel">
    <soap:operation soapAction="http://tourico.com/webservices/BookHotel" style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    <soap:header message="tns:BookHotelLoginHeader" part="LoginHeader" use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="HotelsService">
    <wsdl:port name="HotelsServiceSoap" binding="tns:HotelsServiceSoap">
    <soap:address location="http://localhost:7070/axis/services/HotelsServiceSoap"/>
    </wsdl:port>
    </wsdl:service>
    where as i am using one more web service and able to deploy the java file of this web successfully.
    the snippet of 2nd web service is:
    <wsdl:portType name="TouricoRequest">
    <wsdl:operation name="BookHotelRq">
    <documentation xmlns="http://schemas.xmlsoap.org/wsdl/"> middleware method for "book
    hotel" request from OTA to TH conversion </documentation>
    <wsdl:input message="ws:BookHotelRqSoapIn"/>
    <wsdl:output message="ws:BookHotelRqSoapOut"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="TouricoRequestSoapBinding" type="ws:TouricoRequest">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
    <wsdl:operation name="BookHotelRq">
    <soap:operation soapAction="" style="rpc"/>
    <wsdl:input>
    <soap:body use="encoded" encodingStyle="soap-enc"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="encoded" encodingStyle="soap-enc"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="TouricoHotelRequestServiceMiddleware">
    <wsdl:port name="TouricoRequest" binding="ws:TouricoRequestSoapBinding">
    <soap:address location="http://localhost:7070/axis/services/TouricoRequest"/>
    </wsdl:port>
    </wsdl:service>
    i am using tomcat 5.0.30 and axis 1.1 RC2
    please help in solving the problem.
    thanx
    sandeep

    Try to include port number in the command line after org.apache.axis.client.AdminClient
    like this
    % java org.apache.axis.client.AdminClient -p 80 deploy.wsdd
    Please try this amd let me know. I know you should have solved it by now, but sitll to make sure I am posting htis message
    Thanks
    Meena

  • Problem with accessing a web service from outside world

    Hello SAP experts
    I have a custom BAPI for which I have created a webservice.
    If I login as an admin to the BOX where I have installed this SAP server and open an internet explorer window and give the URL, I can access the web service without any problem. This is just a simple BAPI that searches for some data from a table based.
    However, when I give the same URL from a different PC, it can open the web service and in the fields if I give the data and click on send button, it fails with an error '500 Internal Server Error '.
    I looked for the details of this error on internet and it says that this is some general error and solutions that it suggested doesn't help my scenario.
    Has anyone seen this problem before? Any help will be highly appreciated.
    Tks
    Ram

    i have tried the stack trace in the catch but as i said on the statement where i made the object for the service the program just exits. it didn't return any exception or any output.
    thanx for refering me any answer.......

  • Problem with Deployments of web service Project as EAR in weblogic console

    Hi All :-)
    I was facing the problem with the Deployments of web service(java class) as EAR.I created the one web project associated with EAR project. After my development i exported this project as EAR and deployed the same on the weblogic console.....But time it will work fine and sometime it Deployments status will not become active (its running status) and failed after activate the changes.
    Can any body tell me the real problem with weblogic console for Deployments?
    Please tell me the solution...it?s urgent for me...If you know the answer please mail me on [email protected] or reply here on forum
    Thank you very much for your time.
    Rgds
    Ranjit

    I received the same message and resolved it by adding the following jars to the classpath. All these jars came from the weblogic92 directory:
    server/lib/ant/ant.jar
    common/lib/apache_xbean.jar
    server/lib/jsafe.jar
    server/lib/weblogic.jar
    server/lib/webservices.jar
    server/lib/webserviceclient.jar
    server/lib/webserviceclient+ssl.jar
    server/lib/schema/weblogic-container-binding.jar
    server/lib/xbean.jar
    hth,
    John

  • Problems - WLS 10.0 web service client

    I'm having a few issues with WLS 10.0 web service client.
              I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
              1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
              2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
              3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
              Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
              Thanks,
              [email protected]

    Thank you for the reply..
    But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
    ---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
    LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
    return lagerServiceServant;
    Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
    Or could there be some different fundemental thingy I have forgotten ??
    thanks
    Aqoi

Maybe you are looking for