Unable to create Web i reports in Win 7 64 bit OS

Hi,
    I have WIN 7 64 bit installed on my Laptop. I am unable to create Web I reports in this machine. Does any one know why?
BR, Nanda

Hi Nanda Kishore,
Webi reports does not show in your local system,because webi reports acces from repository through URL,if you export your Bex Query(Universe) to repository,it is possible to see.but you local system is usefull for stand alone applications.
you can see only web intelligece rich client and Desk intelligence.
All the best
Praveen

Similar Messages

  • Unable to create web reports using WAD in BI 7.0

    We are unable to create web reports using WAD in BI 7.0 because of the missing BI metadata. Please take a look at the error below .

    didnt see the error??

  • "Unable to create web dynpro callable object implementation" - GP error

    Good day.
    I've created a GP process and transported it to the test system. But when I try to start the process I get an error on the screen: Error while processing the item; it cannot be displayed. When I look to the logs I can see the following exception:
    Unable to create web dynpro callable object implementation.
    java.lang.Exception
    at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWD.execute(COExecWD.java:294)
    at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWD.execute(InternalCOExecWD.java:171)
    at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWDInterface.execute(COExecWDInterface.java:122)
    at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface.execute(InternalCOExecWDInterface.java:134)
    at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface$External.execute(InternalCOExecWDInterface.java:249)
    at com.sap.caf.eu.gp.ui.act.container.VContainer.onPlugFromDispatcher(VContainer.java:391)
    at com.sap.caf.eu.gp.ui.act.container.wdp.InternalVContainer.wdInvokeEventHandler(InternalVContainer.java:167)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:303)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:667)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:537)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    It doesn't make any sense to me... I would appreciate for any help.

    Hello
    We are facing exact similar issue when we checked the logs.
    Could you help us as we are new to GP.
    What steps you followed to resolve this error.
    Regards
    aparna

  • Unable to create webI report??

    HI all
    I am using BO XI3.1 SP3, when I logged into infoview and click on the new webintelligence document, I see universes available and select the universe then it is showing as "PLUGIN's NOT INSTALLED" instead of showing the query panel of the report.
    Can any one please let me know exactly what plugin should I install before I start creating webI reports???

    @denis
    When I tried in mozilla it says "A plugin is needed to display content...Install plugins"
    when I click on install plugin
    firefox checks for available plugins for couple seconds and finally popus a window saying "No suitable Plugins found"
    when I click on more plugins it takes me to some another page in mozilla "plugins addons for mozzila"
    here I found "Java version 6 update 27" so I am installing this version of java.
    I don't have any admin rights...and all this is on my personal laptop, company didn't issued any laptop of their own.
    Thanks

  • Creating webi/crystal report on BEx and retrieving data, an error ocured?

    Hi Experts,
    I have a problem which many couldnt able to provide a better solution and solve it.
    Need your expert solutions.
    Installed SAP BI with BO(R/3) integration kit SP3.
    Created WEBI report on BEx report via Universe. While trying to load/ refresh/ retrieving the data for display it is throwing an error message like the mentioned below.
    Query1: UniverseOnSAPBEx2
    A database error occurred. The Database error text is: The MDX query SELECT { Measures.ZPrice } ON COLUMNS, NON EMPTY CROSSJOIN( ZVNAME.LEVEL00.MEMBERS, ZVID1.LEVEL00.MEMBERS) ON ROWS FROM $ZICTEST failed to execute with the error.
    UNKNOWN error. (WIS 10901)
    Some fields in the Cube/ BEx/ Universe/ WEBI that i have used are ZPrice, ZVendorId, ZVendorName etc.
    Regards

    looks like it could be the same issues as your other post.

  • Unable to create Web Service Model

    Hi All,
         I generated one wsdl file from Message Interfaces in Integration Repository of SAP XI.
    I am unable to create the model by using this wsdl file in Web Dynpro.
    I followed this approach
    In the NWDS > model > createModel > Import WebService Model > LocalFile System or URL > Here I am selecting wsdl file from local system.
    But the model is not created. Even it is not giving any message or error.
    Please suggest how to proceed.
    Regards
    Ashish.

    Hi Ashish,
      I think you missed something when u r creating the wsdl only.
    So do one thing check it again else create the wsdl again and try importing it. It should not be the problem else.I'm giving my wsdl file here..just check it with this. This takes the associate id as input and will give 3 outputs like email id and others as output. I dont think u can use this wsdl. You can simply compare this with ur wsdl and find out wat is the mistake..
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="http://esaTwoRfcWebservice.satyam.com" name="Soap_OutBound_MI" targetNamespace="http://esaTwoRfcWebservice.satyam.com">
        <wsdl:types>
            <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://esaTwoRfcWebservice.satyam.com" targetNamespace="http://esaTwoRfcWebservice.satyam.com">
                <xsd:element name="Soap_In_MT" type="File_In_DT" />
                <xsd:element name="Soap_Out_FromRFC_MT" type="FileFromRFC1_DT" />
                <xsd:complexType name="FileFromRFC1_DT">
                    <xsd:annotation>
                        <xsd:appinfo source="http://sap.com/xi/TextID">
                        b598f031e79611d995c8e527ac121d2b
                        </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:sequence>
                        <xsd:element name="Details" minOccurs="0" maxOccurs="unbounded">
                            <xsd:annotation>
                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                fd9f6cc0e6f511d9aa5bdfdeac121d2b
                                </xsd:appinfo>
                            </xsd:annotation>
                            <xsd:complexType>
                                <xsd:sequence>
                                    <xsd:element name="Associate_Name" type="xsd:string">
                                        <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            fd9f6cc1e6f511d9b0bddfdeac121d2b
                                            </xsd:appinfo>
                                        </xsd:annotation>
                                    </xsd:element>
                                    <xsd:element name="Associate_Mail_ID" type="xsd:string">
                                        <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            fd9f6cc2e6f511d9c314dfdeac121d2b
                                            </xsd:appinfo>
                                        </xsd:annotation>
                                    </xsd:element>
                                    <xsd:element name="From_SecondRFC_Name" type="xsd:string">
                                        <xsd:annotation>
                                            <xsd:appinfo source="http://sap.com/xi/TextID">
                                            b598f030e79611d9a6abe527ac121d2b
                                            </xsd:appinfo>
                                        </xsd:annotation>
                                    </xsd:element>
                                </xsd:sequence>
                            </xsd:complexType>
                        </xsd:element>
                    </xsd:sequence>
                </xsd:complexType>
                <xsd:complexType name="File_In_DT">
                    <xsd:annotation>
                        <xsd:appinfo source="http://sap.com/xi/TextID">
                        15c39470e79611d9b14200096bf55f9d
                        </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:sequence>
                        <xsd:element name="Associate_Id" type="xsd:string">
                            <xsd:annotation>
                                <xsd:appinfo source="http://sap.com/xi/TextID">
                                b09aa0c0e6f511d9912fdfdeac121d2b
                                </xsd:appinfo>
                            </xsd:annotation>
                        </xsd:element>
                    </xsd:sequence>
                </xsd:complexType>
            </xsd:schema>
        </wsdl:types>
        <wsdl:message name="Soap_In_MT">
            <wsdl:part name="Soap_In_MT" element="p1:Soap_In_MT" />
        </wsdl:message>
        <wsdl:message name="Soap_Out_FromRFC_MT">
            <wsdl:part name="Soap_Out_FromRFC_MT" element="p1:Soap_Out_FromRFC_MT" />
        </wsdl:message>
        <wsdl:portType name="Soap_OutBound_MI">
            <wsdl:operation name="Soap_OutBound_MI">
                <wsdl:input message="p1:Soap_In_MT" />
                <wsdl:output message="p1:Soap_Out_FromRFC_MT" />
            </wsdl:operation>
        </wsdl:portType>
        <wsdl:binding name="Soap_OutBound_MIBinding" type="p1:Soap_OutBound_MI">
            <soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http" />
            <wsdl:operation name="Soap_OutBound_MI">
                <soap:operation xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" soapAction="http://sap.com/xi/WebService/soap1.1" />
                <wsdl:input>
                    <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" />
                </wsdl:input>
                <wsdl:output>
                    <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal" />
                </wsdl:output>
            </wsdl:operation>
        </wsdl:binding>
        <wsdl:service name="Soap_OutBound_MIService">
            <wsdl:port name="Soap_OutBound_MIPort" binding="p1:Soap_OutBound_MIBinding">
                <soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://cgnsap12:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=ESA_SOAP_SERVICE&Interface=http%3A%2F%2FesaTwoRfcWebservice.satyam.com%5ESoap_OutBound_MI" />
            </wsdl:port>
        </wsdl:service>
    </wsdl:definitions>
    All the best.
    Regards,
    Sirisha.R.S

  • Unable to open web analysis reports through workspace

    Hi,
    I am connecting web analysis with MSSQL server 2000 and generating reports. I am using essbase 9.3.1 version.
    But my problem now is that I can just open these reports from web analysis studio and cannot open them from workspace. In workspace, if I right click on the report and open it from web analysis studio it does open. But it does not open by double clicking the report in workspace. It just shows a blank report on just parts of the report.
    The issue is only there for the reports that are getting data from relational db (MSSQL server 2000). The other reports that are using the cube data are fine and opening from everywhere.
    Are there any other configuration settings involved in order to open a web analysis report(that uses relational db) from workspace?
    Thanks in advance,
    John

    Hi Atul,
    Try using the in built config checker:
    http://localhost:16000/WebAnalysis/config
    This has several tests you can perform to see what's running.

  • Unable to create web app with PowerShell - An update conflict has occurred

    I am trying to create a new Web Application using PowerShell. I need to use PowerShell because I need to create the Web App using classic authentication and not Claims authentication. the first time I created the Web App, everything went great. Ever since
    the first time, I get an error and the web app creation does not complete. Just as an FYI, I can create a new Web App using Central Admin, but that creates it with Claims authentication which I cannot use.
    Here is my PowerShell script
    New-SPWebApplication -Name "SharePoint2013 (82)" -ApplicationPool "SharePoint2013-82" -AuthenticationMethod "NTLM" -ApplicationPoolAccount (Get-SPManagedAccount "GLOBAL\SP_AppPool") -Port 82 -URL "http://sharepoint2013"
    Here is the error I get in PowerShell
    New-SPWebApplication : An update conflict has occurred, and you must re-try this action. The object SPWebApplication
    Name=SharePoint2013 (82) was updated by DOMAIN\SP_Administrator, in the powershell (13020) process, on machine SPWEB01.
     View the tracing log for more information about the conflict.
    At line:1 char:1
    + New-SPWebApplication -Name "SharePoint2013 (82)" -ApplicationPool "SharePoint201 ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (Microsoft.Share...PWebApplication:SPCmdletNewSPWebApplication) [New-SPWebA
       pplication], SPUpdatedConcurrencyException
        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPWebApplicationUnknown SQL Exception 547 occurred. Additional error information from SQL Server is included below.
    The DELETE statement conflicted with the REFERENCE constraint "FK_Dependencies1_Objects". The conflict occurred in database "SP_Config", table "dbo.Dependencies", column 'ObjectId'.
    The statement has been terminated.
    I also get  this error from the trace
    Unknown SQL Exception 547 occurred. Additional error information from SQL Server is included below.
    The DELETE statement conflicted with the REFERENCE constraint "FK_Dependencies1_Objects". The conflict occurred in database "SP_Config", table "dbo.Dependencies", column 'ObjectId'.
    The statement has been terminated.
    I have tried to resolve the issue by performing the following:
    Delete the partially created web app using Central Admin or PowerShell
    Clear the file system cache on all servers in the farm (Stopping wss timer job, Saving Copy of the
    cache.ini file from C:\Documents and Settings\All Users\application data\Microsoft\SharePoint\Config folder. Clearing all the .xml files from the location except cache.ini but Edit the cache.ini to have value 1. Starting the timer job)
    Use Products Configuration Wizard (no detach, just 'upgrade') - People have said to select the option to disconnect the server from server farm and revert back again at next step (so you actually do not disconnect), but there is no next step that I have
    encountered. You select 'disconnect', hit next, and the server disconnects.
    Restart all the servers in the farm
    Run the PowerShell script again...still get the same error
    I have tried it on multiple servers in the farm too.

    Hi Michael,
    I found a similar thread for you reference:
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/9ccef7bf-87a9-4849-b086-4db2d898f1d7/cannot-create-new-web-application-wss-30?forum=sharepointadminlegacy 
    If it doesn’t work, sometimes the issue might be caused by long time keep powershell opening and generating some cache files. So please try re-opening the powershell and test the issue again.
    http://blogs.msdn.com/b/ronalg/archive/2011/06/24/mount-spcontentdatabase-errors-on-2nd-and-subsequent-attempts-of-same-database.aspx?Redirected=true 
    http://www.oakwoodinsights.com/sharepoint-powershell-surprise/
    In addition, here is an article which explains the possible reason of the SQL error:
    http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • Unable to create web app items if Proximity Search is Enabled.

    I am using BC API to create web app items because I am getting the data from a third party website and wanted to save the data into web app by using BC API. I have a web app ( Name: "Map Overview" ) and the proximity search is enabled. When I test my script I got 404 bad request error but if I disabled the Proximity Search the item is created.
    Can someone help me on this?
    Thanks

    Let me know the page you are running the API call on, I'll have a look and see what gives.
    Thanks,
    Mihai

  • Unable to create Database in Reporting Service Configuration

    Hi,
    We have SQL Server 2012 in our environment. I want to enable monitor report in Lync 2013. i have separate Lync sql instance.
    I am trying to configure new database in Reporting Service Configuration manager in report Server database Configuration wizard.
    while testing connection getting below error.
    could not connect to server:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to
    allow remote connections.(provider:Named Pipes provider,error:40-could not open a connection to SQL Server)
    kindly help to resolve issue.

    Hi Rakesh,
    Please check the below details information:
     Check the ReportServer db is present in the Database engine.
    Go and check the report server configurations (go here:Start -> All Programs -> Microsoft sql server 2012-> Configuration Tools -> Report Service Configuration Manager
    check all the connections if still not working. then create a new reporting services Database. While creating it make sure you select native mode, if you want to create a share point services then select share point integration mode.
    If the above didn't work, Please check which port is used for SQL Server database engine from SQL Server Configuration Manager.
    If we are using dynamic port, please make sure:
    SQL Server Browser service is running.
    UDP 1434 port is enabled in the firewall.
    If we are using static port, please make sure the port is enabled in the firewall.
    Below is useful link about how to troubleshoot connection issue:
    http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
    https://msdn.microsoft.com/en-us/library/ms156468.aspx?f=255&MSPPError=-2147217396
    Similar thread for your reference:
    http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
    If you have any more questions, please feel free to ask.
    Regards,
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • Unable to create master detail report

    Hi,
    I´ve two tables (Organisation and Purchases) and want to create a master-deatil with the wizard.
    At the end an error occurs:
    ORA-20001: Unable to create master detail page. ORA-06502: PL/SQL: numeric or value error: character to number conversion error
    Unable to create Master Detail pages.
    Return to application.
    Any ideas ? Any reaction will be appreciated
    Leo

    Leo,
    How are your two tables related? Do you have a foreign key constraint? It sounds like that there may be a datatype mismatch between the master table's PK and the detail table's FK - check to make sure that they are both NUMBER.
    Thanks,
    - Scott -

  • Unable to Create a QBE report based on View

    I have a view which is based on 4 tables.
    The view by itself works fine.When I create a QBE report based on that view it gives the
    ORA-01445: cannot select ROWID from a join view without a key-preserved table (WWV-11230).
    I am not able to understand what I'm doing wrong.Please help!
    Thanks,
    Hyma.
    null

    Its simple if its a view on one table, but you have a view based on 4 tables. That is what makes it complicated and the need for special set up and a little research. I don't remember what all goes into it, but I do recall that its not just as simple as creating the view.

  • Unable to create web os profile

    Just purchased Palm Pre 3. It's unlocked. I go through the set steps to create profile and end up with "checking email" then it locks. I can't even turn it off. I'm stuck.
    Post relates to: HP Pre 3 (Unlocked EU)

    Hi Nanda Kishore,
    Webi reports does not show in your local system,because webi reports acces from repository through URL,if you export your Bex Query(Universe) to repository,it is possible to see.but you local system is usefull for stand alone applications.
    you can see only web intelligece rich client and Desk intelligence.
    All the best
    Praveen

  • Unable to create web service client

    I am using NetBeans to build the the first-cup example but I have failed in all my attempts to create the web service client for first-cup web module.
    The reported error is: "
    init:
    wsimport-init:
    wsimport-client-check-DukesAgeService:
    wsimport-client-DukesAgeService:
    error: Connection timed out: connect
    unknown location
    error: java.net.ConnectException: Connection timed out: connect
    I have tried to start the sun server application but that doesn't solve the problem.
    I have strictly followed the following instructions taken from the first-cup tutorial, found at http://java.sun.com/javaee/5/docs/firstcup/doc/p8.html.
    Creating a Web Service Client for the firstcup-war Web Module
    The firstcup-war web module must consume the firstcup-dukes-age web service in order to get Duke's current age. For this to happen, you need to create a web service client for the firstcup-war web module.
    Creating a Web Service Client for the firstcup-war Web Module
    Select firstcup-war from the Project pane.
    Select File -> New File.
    Select Web Services from the Categories pane.
    Select Web Service client from the File Types pane.
    Click Next.
    Select WSDL URL.
    Into the WSDL URL field, enter the following location of the WSDL file of the web service that the web service client will consume.
    http://localhost:8080/DukesAgeService/DukesAgeService?WSDL
    Into the Package field, enter the following package where the client files will be generated.
    com.sun.firstcup.webservice
    Click Finish.
    Thank you and look forward to hearing from you all.

    Hi there.
    I don't know what the problem is with NetBeans, but if you see the local copy of the WSDL in the firstcup-war project, you will find that the name of your computer should be there as part of the URL. Change it to 'localhost' or to '127.0.0.1' and it should work.
    Example:
    <xsd:schema>
          <xsd:import namespace="http://webservice.firstcup.sun.com/" schemaLocation="http://localhost:8080/DukesAgeService/DukesAgeService/__container$publishing$subctx/WEB-INF/wsdl/DukesAgeService_schema1.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </xsd:schema>And...
    <port name="DukesAgePort" binding="tns:DukesAgePortBinding">
          <soap:address location="http://localhost:8080/DukesAgeService/DukesAgeService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </port>

  • Unable to create web service from wsdl that contains xsd as import

    I have written a WSDL and tried to create the web services by weblogic workshop.
    Prior to that I have created the war file and able to deploy them properly. Also able to access any wsdl by hitting the server.
    But when I am trying to create the web services by weblogic workshop its throwing error as "URL is not well formed" for those XSDs which I have imported in my WSDL. I have kept all my XSDs and WSDLs in the same folder.
    The WSDL has given below :
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:intf="http://soapheader.ibm.com" xmlns:impl="http://soapheader.ibm.com" xmlns:MessageContext="MessageContext" xmlns:AlertUpdateRequest="AlertUpdateRequest" xmlns:AlertFetchResponse="AlertFetchResponse" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapheader.ibm.com">
         <import namespace="MessageContext" location="http://localhost:7001/WebApplicationWeb/gss/xsd/MessageContext.xsd"/>
         <import namespace="AlertUpdateRequest" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertUpdateRequest.xsd"/>
         <import namespace="AlertFetchResponse" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertFetchResponse.xsd"/>
         <wsdl:types>
              <schema elementFormDefault="qualified" targetNamespace="http://ggg.com" xmlns="http://www.w3.org/2001/XMLSchema">
              </schema>
         </wsdl:types>
         <wsdl:message name="alertUpdateRequest">
              <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:message name="alertUpdateResponse">
              <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:message name="alertFetchRequest">
              <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:message name="alertFetchResponse">
              <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:portType name="AlertUpdateService">
              <wsdl:operation name="getAlertUpdate">
                   <wsdl:input name="alertUpdateRequest" message="intf:alertUpdateRequest"/>
                   <wsdl:output name="alertUpdateResponse" message="intf:alertUpdateResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:portType name="AlertFetchService">
              <wsdl:operation name="getAlert">
                   <wsdl:input name="alertUpdateRequest" message="intf:alertFetchRequest"/>
                   <wsdl:output name="alertUpdateResponse" message="intf:alertFetchResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="AlertUpdateServiceSoapBinding" type="intf:AlertUpdateService">
              <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="getAlertUpdate">
                   <wsdlsoap:operation/>
                   <wsdl:input>
                        <wsdlsoap:header message="intf:alertUpdateRequest" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <wsdlsoap:header message="intf:alertUpdateResponse" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:binding name="AlertFetchServiceSoapBinding" type="intf:AlertFetchService">
              <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="getAlert">
                   <wsdlsoap:operation/>
                   <wsdl:input>
                        <wsdlsoap:header message="intf:alertFetchRequest" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <wsdlsoap:header message="intf:alertFetchResponse" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="AlertUpdateServiceService">
              <wsdl:port name="AlertUpdateService" binding="intf:AlertUpdateServiceSoapBinding">
                   <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertUpdateService"/>
              </wsdl:port>
         </wsdl:service>
         <wsdl:service name="AlertFetchServiceService">
              <wsdl:port name="AlertFetchService" binding="intf:AlertFetchServiceSoapBinding">
                   <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertFetchService"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>

    Hi,
    From your description I am assuming that you are using JAX-WS, if not get back to me as I might have another bug to look at.
    The problem is that the annotation @Oneway needs to be added to the methods in java files for this to work correctly. You can either do this manually or use the PI in the code editor. I have raised bug 6266513 to track the fact this annotation is not written out properly. I have logged bug 6266556 to track the nillable=true and extranious elements you will see when you do add @Oneway.
    Thanks for the quality of your bug report, and we would of course welcome any other feedback good or bad you would like to give us.
    Gerard Davison
    JDeveloper Web Services Team

Maybe you are looking for