Xquery document initialization failed

i have an integration application called "IntApp". I added a jar called "Schemas1.jar" that is generated from a schemas project to "IntApp" libraries. Then I added a schema project called "Schemas2" to "InApp". When i open previusly written xquery transformation files the editor says "xquery document initialization failed. Design view unavailable." But whenever i pack all of my schemas into a single schema project i can use transformation editor.
How can i use an application with an external schemas1.jar and and a schema project? Thus finally i have two schema jar binaries.

Hi Ezra,
Could you please post your query on the
weblogic.developer.interest.integration newsgroup?
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.develope
r.interest.integration&utag=
Regards,
Anurag
"enigmah" <[email protected]> wrote in message
news:[email protected]..
Hi All,
Hopefully somebody can help me out with the following:
The XQuery transformation tool inconsistently produces the following error
When reopening an already existing and working xquery (.xq)transformation:
>
"XQuery Document Initialization failed.
Design View unavailable."
This makes the transformation uneditable, as even closing and reopeningboth
editor and application does not solve the problem. The xquerytransformation
continues to work correctly from a process in the test browser.
What is the cause and resolution for this?
Any help is greatly appreciated. Thanks.
rgds,
Ezra Kahimbaara
S.E.
BEA Solutions Africa

Similar Messages

  • Document control failed due to error in [DOCMGR-CANCEL], return code = [OTH

    Hi,
    When i tried using the cancel PO API, it resulted in the following error.
    Document control failed due to error in [DOCMGR-CANCEL], return code = [OTHER]
    I searched the metalink and found out that it was a bug as p_doc_num variable was a number and in PO_HEADERS_ALL segment1 is VARCHAR2. But now the bug is fixed.
    I tried both ways, with and without quotes but it is still giving this error. Please suggest.
    I used the API in the following way.
    DECLARE
    l_return_status VARCHAR2(1);
    BEGIN
    fnd_global.apps_initialize(4480,20707,201);
    --call the Cancel API
    PO_Document_Control_PUB.control_document (
    p_api_version=>1.0, -- p_api_version
    p_init_msg_list=>FND_API.G_TRUE, -- p_init_msg_list
    p_commit=>FND_API.G_TRUE, -- p_commit
    x_return_status=>l_return_status,-- x_return_status
    p_doc_type=>'PO', -- p_doc_type
    p_doc_subtype=>'STANDARD', -- p_doc_subtype
    p_doc_id=>34, -- p_doc_id
    p_doc_num=>null, -- p_doc_num
    p_release_id=>null, -- p_release_id
    p_release_num=>null, -- p_release_num
    p_doc_line_id=>null, -- p_doc_line_id
    p_doc_line_num=>null, -- p_doc_line_num
    p_doc_line_loc_id=>null, -- p_doc_line_loc_id
    p_doc_shipment_num=>null, -- p_doc_shipment_num
    p_action=>'CANCEL', -- p_action
    p_action_date=>SYSDATE, -- p_action_date
    p_cancel_reason=>null, -- p_cancel_reason
    p_cancel_reqs_flag=>'N', -- p_cancel_reqs_flag
    p_print_flag=>null, -- p_print_flag
    p_note_to_vendor=>null ); -- p_note_to_vendor
    commit;
    -- Get any messages returned by the Cancel API
    FOR i IN 1..FND_MSG_PUB.count_msg
    LOOP
    DBMS_OUTPUT.put_line(FND_MSG_PUB.Get(p_msg_index => i,
    p_encoded => 'F'));
    END LOOP;
    END;
    /

    first you have to assign org_id to the program,like fnd_client_info.set_org_context('167');
    you also have to initialize,like this
    fnd_global.initialize(session_id => l_session_id
    ,user_id => 2613
    ,resp_id => 50459
    ,resp_appl_id => 201
    ,security_group_id => 0
    ,site_id => -1
    ,login_id => 1102144
    , --can't be -1,or else will be wrong
    conc_login_id => 1102144
    ,prog_appl_id => -1
    ,conc_program_id => -1
    ,conc_request_id => -1
    ,conc_priority_request => NULL);

  • NOT POSSIBLE TO START ESSBASE WHEN SSO INITIALIZATION FAILS

    Version is 11.1.1.3. My Essbase is not starting. Issues from the logs and what I have attempted are as follows. I have highlighted the relevant areas in bold.
    When Starting Essbase from products/Essbase/bin/start.bat:
    C:\Hyperion\products\Essbase\bin>start.bat
    C:\Hyperion\products\Essbase\bin>REM eis
    C:\Hyperion\products\Essbase\bin>net start "Hyperion Integration Services"
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    C:\Hyperion\products\Essbase\bin>REM APS
    C:\Hyperion\products\Essbase\bin>call C:\Hyperion\products\Essbase\aps\bin\start.bat
    C:\Hyperion\products\Essbase\bin>REM aps
    C:\Hyperion\products\Essbase\bin>net start HyS9aps
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    C:\Hyperion\products\Essbase\bin>REM EAS
    C:\Hyperion\products\Essbase\bin>call C:\Hyperion\products\Essbase\eas\bin\start.bat
    C:\Hyperion\products\Essbase\bin>REM eas
    C:\Hyperion\products\Essbase\bin>net start HyS9eas
    The requested service has already been started.
    More help is available by typing NET HELPMSG 2182.
    C:\Hyperion\products\Essbase\bin>REM EssbaseAgent
    C:\Hyperion\products\Essbase\bin>net start hypservice_1
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    C:\Hyperion\products\Essbase\bin>REM EssbaseStudio
    C:\Hyperion\products\Essbase\bin>C:\Hyperion\products\Essbase\EssbaseStudio\Server\startServer.bat
    C:\Hyperion\products\Essbase\bin>setlocal
    C:\Hyperion\products\Essbase\bin>set CONFIGTOOL_HOME="C:\Hyperion\common\config\9.5.0.0"
    C:\Hyperion\products\Essbase\bin>call ""C:\Hyperion\common\config\9.5.0.0"\setJavaRuntime.bat"
    Logging configuration file is not found. Expected filename is C:\Hyperion\products\Essbase\bin\.\server.properties
    Log file location is:
    C:\Hyperion\logs\esbstudio\server.log
    13:23:09 11/01/11 INFO Starting up
    13:23:09 11/01/11 INFO Oracle Essbase Studio Server. Version 11.1.1.3.00, Bui
    ld 090, June 25 2009
    13:23:16 11/01/11 (system) WARNING Failed to load driver for sap
    13:23:16 11/01/11 (system) SEVERE Cannot load Teradata connector
    13:23:16 11/01/11 (system) WARNING Failed to load driver for teradata
    13:23:16 11/01/11 (system) WARNING Failed to load driver for mysql
    13:23:16 11/01/11 (system) WARNING Failed to load driver for netezza
    Essbase.log:
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Error(1051223)
    Single Sign On function call [css_init] failed with error [CSS Error: CSS method invocation error: com.hyperion.css.CSSSystem.<init>]
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Info(1051198)
    Single Sign-On Initialization Failed !
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Info(1051232)
    Using English_UnitedStates.Latin1@Binary as the Essbase Locale
    [Tue Oct 25 11:26:31 2011]Local/ESSBASE0///Error(1051527)
    In Shared Services Security mode it is not possible to start Essbase when single sign on initialization fails.
    AND
    C:\Hyperion\logs\essbase\SharedServices_Security_Client.log com.hyperion.css.CSSSystem.<init>(Unknown Source)
    2011-10-25 11:26:11,039 INFO [main] Configure CSS with registry com.hyperion.css.CSSSystem.initCSSSystem(Unknown Source)
    2011-10-25 11:26:11,039 INFO [main] Initializing CSS from Registry. com.hyperion.css.common.configuration.CSSConfigurationManager.getConfiguration(Unknown Source)
    2011-10-25 11:26:11,085 INFO [main] Trying to get Registry Instance com.hyperion.css.registry.RegistryManager.<init>(Unknown Source)
    2011-10-25 11:26:31,023 ERROR [main] 20:1092:Failed to initialize EPM System registry. *[Root Cause: java.sql.SQLException: [Hyperion][SQLServer JDBC Driver]Error establishing socket to host and port: machinex:1433. Reason: Connection refused: connect ] com.hyperion.css.registry.RegistryManager.<init>(Unknown Source)*
    *2011-10-25 11:26:31,023 ERROR [main] Arguments: param1={}, param2=null, param3=C:\Hyperion\logs\essbase\,* com.hyperion.css.CSSSystem.initCSSSystem(Unknown Source)
    2011-10-25 11:26:31,023 INFO [main] CSS system intialization failed. : [21484 ms] com.hyperion.css.CSSSystem.initCSSSystem(Unknown Source)
    What I have attempted:
    - Attempted to connect to Shared Services, Workspace url's - YES
    - Checked openLDAP & my Database is running - YES
    - Added following to Configuration File :
    SharedServicesLocation machinex 28080
    AUTHENTICATIONMODULE CSS http://machinex:28080/interop/framework/getCSSConfigFile YES, but same error
    - Changed essbase.bak to essbase.sec YES but same error
    - netstat -an to check for 1423. Port 1423 is not listening, although ALL TCP Ports have been enabled. So YES but same error.
    - Read Knowledgebase article # 954322.1 - the suggested things in there don't seem to apply to my case, unless I am missing something.
    At this point does anybody have any suggestions ?

    An update: Just for kicks, I tried restarting Essbase using Start->Programs-EPMSystem->Essbase->EssbaseServer->Essbase.bat and apparently now Essbase is started.
    EAS, Studio and Planning however are down.
    Excerpt from the HyS9eas-sysout.log:
    [ERROR] RegistryUtils - SQL Exception when trying to create a new connection [Hyperion][SQLServer JDBC Driver]Error establishing socket to host and port: machinex:1433. Reason: Connection refused: connect
    * CRITICAL ERROR: Common Security Services initialization failed. Please *
    * make sure that a valid entry is provided for SECURITY_CONFIGURATION in *
    * OlapAdmin.properties. This is required if Shared Services is enabled. *
    * Please restart the server after the changes. *
    Stopping DAO factory!
    HBR Configuration has not been initialized. Make sure you have logged in sucessfully and there are no exceptions in the HBR log file.
    java.lang.ExceptionInInitializerError
    .... bunch of java code.
    This is really strange. There is NOTHING that I changed, started or stopped which could have caused Essbase to start magically all of a sudden.
    Any insights into the cause of all this ?

  • Error -32810 occurred at The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi

    I have two cFP-2120 RT controller. They both have NI-Serial RT2.5.6, DataSocket for LV RT4.2, NI-VISA 3.6, FP Drivers 5.1.0, FP VI Manager 3.1.0 LV RT 7.1.1 installed. But one same vi can run on one controller but not another.
    the error message got when it runs on another controller is "Error -32810 occurred at  The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi"
    I wonder by what it is caused?
    Thanks

    Hi Matthew,
    As mentioned previously, this KnowledgeBase article may be of some help. Also, if your code is being run on an embedded controller and then a network controller (not embedded), you will need to run the program differently. On the embedded controller, you should deploy your VI in a Project Explorer or programmatically (as described here.) However, you do not need to deploy the program to a network controller, but simply run the VI.
    I would also suggest creating a new .IAK file. Do you still see the same error? Also, double-check that the software installed on the controller matches the software installed on the host PC. If you have any file paths associated with one FieldPoint controller, ensure that you are changing them to match the second controller.
    Please keep us posted on your troubleshooting steps. Have a great day!
    Amanda Howard
    Americas Services and Support Recruiting Manager
    National Instruments

  • Window server 2008 r2 error show "stop :- c00002e3 security account manager initialization failed because of the for A DIVICE ATTACHED to the system is not funcation"

    Hi All
    Please help
    my server not working showing display error window server 2008 r2  error show "stop :- c00002e3 security account manager initialization failed because of the for A DIVICE ATTACHED to the system is not funcation"
    Please help me how to resolve this issue ???
    thnaks !!!

    Hi,
    If there is any external device plug into your computer, please unplug it and restart the Server.
    You can also test the issue in Safe mode.
    If it can boot into Safe mode, please update any driver has yellow warning on it, also check if the dump file is existing under %SystemRoot%\, if so, please help to post back for our research.
    Kate Li
    TechNet Community Support

  • Document control failed due to error in [DOCMGR-CANCEL] with a return code

    i am getting this error while calceling the purchase order "Document control failed due to error in [DOCMGR-CANCEL] with a return code of [OTHER]. "
    I am doing the calcel like this
    Nav: buyer work centre --> order
    searche the po and then
    select order --> cancel then click GO button
    i gave the Reason as Cancel
    communication method: email
    Cancel Requisition: Yes
    Please help on this, its urgent.
    Thanks,
    Vijay.

    Hi Vijay,
    Check this MOS note.
    Cancelling A Standard Purchase Order In Buyer Work Center Results In Error [Docmgr-Cancel] With A Return Code [ID 1338826.1]
    Thanks
    -Arif.

  • File Adapter: Initialization error: Conversion initialization failed

    Hi all,
    I'm trying to establish a file adapter (FTP, File Content Conversion).
    In the adapter monitor I' ve got the following error:
    Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
    Configured at 14:49:34 2005-08-29
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
    My content conversion parameters are:
    BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
    20,50,50,1,10,50,10,50,5,20,20,15,15
    BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
    HouseNo,PhoneNumber,Fax,BankId,BankAccount
    BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
    trim
    BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
    ignore
    What could be the error or where I have to look for it?
    Thanks,
    Fabian

    Yes,
    Recordset name: BP_BusinessPartnerMasterData_IncomingData
    Recordset structure: BP_BusinessPartnerMasterData_IncomingData
    The corresponding Message Type:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
         <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
         <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   f323a4b018a911da9fd9000bcd69ce64
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Number">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8500fe111da89f2d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Id from Sender for BP
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name2">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8510fe111dacfd7d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Last name or Company name
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name1">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8520fe111da94bad1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             First name or Company name 2
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Gender">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8530fe111da99add1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             m or f or blank
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Birthdate">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8540fe111dab156d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="City">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8550fe111daa58cd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Postcode">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8560fe111dac0c2d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Street">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8570fe111dabbd3d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="HouseNo">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8580fe111dab63fd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PhoneNumber">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8590fe111dac782d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Fax">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85a0fe111daa9ebd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankId">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85b0fe111dace1ed1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankAccount">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85c0fe111da8801d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • Failed to open XML document. Failed to retrieve Public ID

    I have a client posting to Weblogic 6.1 server with the help of Apache
    SOAP 2.2. The posting works fine if the contents of the SOAP message
    is small. But when the contents of SOAP reached more than 11KB, the
    following error occurs:
    Error: Failed to open XML document. Failed to retrieve PUBLIC id or
    SYSTEM id from the document. Decrease the number of char between the
    beginning of the document and its root element.
    The SOAP document looks like:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
    <mn:sMethodName xmlns:mn="sMethodURI">
    <batch appid="1">
    <employee>
    <name>...</name>
    <address>...</address>
    </employee>
    <employee>
    <name>...</name>
    <address>...</address>
    </employee>
    </batch>
    </mn:sMethodName>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    The Max Post Size in Weblogic is set to (-1).
    The program is able to handle less than 50 items of
    <employee>.....</employee>. The error occurs when more than 50 items
    are used. The problem is that our application should be able to handle
    more than 1000 items of <employee>....</employee>.
    My questions are:
    1. How should I configure weblogic to solve the problem?
    2. How should I configure the deployment of Apache SOAP to solve the
    problem?
    Pls advise. Thanks.

    One can deduce from the error message that the parser is looking for the
    <?XML...?> portion of the document because that is where the SYSTEM and
    PUBLIC ids are found in the document.
    Peace,
    Cameron Purdy
    Tangosol Inc.
    Tangosol Coherence: Clustered Coherent Cache for J2EE
    Information at http://www.tangosol.com/
    "Grace" <[email protected]> wrote in message
    news:[email protected]...
    >
    Sorry, but I didn't get what you mean. I thought that was handled by theApache
    SOAP API already? And if it couldn't see the XML document header, then whydoes
    this only happens when the document size is large? It doesn't haveproblems whenever
    the document size is small.
    "Cameron Purdy" <[email protected]> wrote:
    It's looking for the XML document header "<?XML" ....
    Peace,
    Cameron Purdy
    Tangosol Inc.
    Tangosol Coherence: Clustered Coherent Cache for J2EE
    Information at http://www.tangosol.com/
    "Grace" <[email protected]> wrote in message
    news:[email protected]...
    I have a client posting to Weblogic 6.1 server with the help of Apache
    SOAP 2.2. The posting works fine if the contents of the SOAP message
    is small. But when the contents of SOAP reached more than 11KB, the
    following error occurs:
    Error: Failed to open XML document. Failed to retrieve PUBLIC id or
    SYSTEM id from the document. Decrease the number of char between the
    beginning of the document and its root element.
    The SOAP document looks like:
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
    <mn:sMethodName xmlns:mn="sMethodURI">
    <batch appid="1">
    <employee>
    <name>...</name>
    <address>...</address>
    </employee>
    <employee>
    <name>...</name>
    <address>...</address>
    </employee>
    </batch>
    </mn:sMethodName>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    The Max Post Size in Weblogic is set to (-1).
    The program is able to handle less than 50 items of
    <employee>.....</employee>. The error occurs when more than 50 items
    are used. The problem is that our application should be able to handle
    more than 1000 items of <employee>....</employee>.
    My questions are:
    1. How should I configure weblogic to solve the problem?
    2. How should I configure the deployment of Apache SOAP to solve the
    problem?
    Pls advise. Thanks.

  • Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured

    Today I tried to configure JAVA APM on a CentOS 6.4 server with tomcat6 installed through the normal RPM package. Adding this server to SCOM was no problem and it shows itself as a 'Deep Monitored Configuration'. The last part of enabling
    JAVA APM fails. I have followed the following process:
    1. Imported the JAVA APM MP's
    2. Extracted the JAVA APM Files
    3. Copied those files to my CentOS server
    4. Added the JAVA_OPTS to my tomcat configuration file
    5. Restarted Tomcat
    When I look for the log file which needs to be created through the installation of the APM agent it cannot be find. When I look into my Catalina.out file I see the following errors:
    Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
    SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
    com.microsoft.ManagementServices.APMAgent.Exception.ApmException: SEAgent.config.xml does not have a valid event sender configured
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            ... 15 more
    Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            ... 15 more
    Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
            ... 19 more
    Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
            at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:601)
            at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
            at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
    Caused by: java.lang.InstantiationException: Monitor initialization failed: SEAgent.config.xml does not have a valid event sender configured
            at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
            ... 12 more
    Does anyone have seen this error before? Can someone help me with this one?
    Thnx,

    I'm running tomcat on a CentOS release 6.4 (Final) server. I installed Tomcat 6 through an RPM from the CentOS sources. I have installed Apache Tomcat/6.0.24 wit JVM version 1.7.0_09-icedtea-mockbuild_2013_01_16_18_52-b00, the JVM Vendor is Oracle Corporation.
    My tomcat configuration needs to be done in '/etc/tomcat6/tomcat6.conf'
    I installed the APM Agent in the path '/opt/apm/' with the rights  40755 (root/root). The files have the following rights:
    -rw-rw-r-- 1 root tomcat  32046 Mar  3 15:38 apm_facade.jar
    -rw-rw-r-- 1 root tomcat 244819 Mar  3 15:38 apm_monitor.jar
    -rw-rw-r-- 1 root tomcat  38110 Mar  3 15:38 apm_producers.jar
    -rw-rw-r-- 1 root tomcat 207006 Mar  3 15:38 asm-all-3.3.1.jar
    -rw-rw-r-- 1 root tomcat   4157 Mar  3 15:38 ASM_Third_Party_Notices.txt
    -rw-rw-r-- 1 root tomcat 241368 Mar  3 15:38 DispatcherStub.dll
    -rw-rw-r-- 1 root tomcat  36880 Mar  3 15:38 pmonitor.config.xml
    -rw-rw-r-- 1 root tomcat   2625 Mar  3 15:38 SEAgent.config.xml
    -rw-rw-r-- 1 root tomcat    830 Mar  5 15:19 Starter.properties
    The above rights are equal to the /etc/tomcat6 directory with the tomcat configuration files.
    In the tomcat6.conf I have added the following entries:
    #Microsoft SCOM APM
    JAVA_OPTS="${JAVA_OPTS} -Djava.library.path=/opt/apm"
    JAVA_OPTS="${JAVA_OPTS} -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar"
    When I look into the running tomcat process I see the following:
    tomcat   17401     1  0 Mar05 ?        00:00:39 /usr/lib/jvm/jre/bin/java -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar
    -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
    -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat6/temp
    -Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
    My Starter.Properties looks like this:
    # Jars to load by inner classloader.
    # Use semicolons to separate the JAR entries
    ClassPath=apm_monitor.jar;asm-all-3.3.1.jar;apm_producers.jar
    # Path to pmonitor.config
    MonitorConfigFileName=pmonitor.config.xml
    # Path to SEAgent.config
    AgentConfigFileName=SEAgent.config.xml
    # Log file name
    # Example for full-path location:
    #                  LogFileName=c:\\tracelog\\apm-java-agent.log
    # Example for relative path (to agent jar files):
    #                  LogFileName=apm-java-agent.log
    LogFileName=apm-java-agent.log
    # Log level (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST)
    # A level of FINER or FINEST may expose Personally identifiable
    # information (PII) in the log file.  The levels below INFO are
    # intended for debugging and diagnostic use only.
    LogLevel=FINEST
    The 'apm-java-agent.log' is not created on the system. The only logging is done in the catalina.out. When restarting tomcat I see the following entries in te log file:
    INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading succeeded (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger warning
    WARNING: Failed registering the COUNTER MBean
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
    SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
    Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
    INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
    Hope this gives your some more background around my problem, I double checked the permissions..

  • J2EE Engine start error: Database initialization failed!

    My J2EE engine now fails to start - jcontrol stays yellow.  I've followed Troubleshooting pages from help.sap.com Admin manual topic "starting J2EE Engine".
    Background:
    I was running through JDI Scenario 2+ on a fresh installed WebAS 6.40 at SP9.  Using NWDevStudio2.09, I attempted to load a DC, but servers stopped responding.  So I downed everything (in MMC) including offlining the DB, then put DB back online and restart the J2E engine, and now jcontrol stays yellow. 
    I find this in the file log_bootstrap_ID0014430.0.log:
    Apr 7, 2005 3:10:23 PM  ] Bootstrap MODE:
    [Apr 7, 2005 3:10:23 PM  ] <INSTANCE GLOBALS>
    [Apr 7, 2005 3:10:23 PM  ]  determined by parameter [ID0014430].
    [Apr 7, 2005 3:10:23 PM  ] -
    [Apr 7, 2005 3:10:26 PM  ] Exception occured:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
         at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
         at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
         at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
    .........a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:344)
    ............ a few lines cut out here..........
         at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://PHI21811/J2E [Cannot connect to host PHI21811 [Connection refused: connect], -813.].
         at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:183)
         at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:219)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:570)
         at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:263)
         at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:294)
         ... 14 more
    [Apr 7, 2005 3:10:26 PM  ] [Bootstrap module]> Problem occured while performing synchronization.
    [Apr 7, 2005 3:22:24 PM  ] -
    ANYONE HAVE ANY SUGGESTIONS?????

    Using the Database Administration section of the help.sap.com library, I found the location of SAPDB/MySQL log files.  They are in C:\sapdb\data\wrk\J2E.  In 'knldiag' I found entries complaining of Log files being full and tasks put in suspension.
    So I figured out to do a full back up of the DB and/or backup the log files.  The log file bar (in MMC) still showed 100% full, but I figured out to refresh the view and voila it was empty (so one of the backups emptied it, not sure which one).
    After that the DB comes up fine and now my J2E WebAS goes all green.
    Message was edited by: Michael W Rains

  • Eclipse XQuery expression validation failed: The current configuration is out of sync with the XQuery resource in the repository.

    I created a wsdl based on a dbadapter in jdeveloper, imported into eclipse and created the biz and the proxy and uploaded to oracle service bus, it works fine,
    but happens now that i need to have a xsd and wsdl with business names and not table names, invented to create a xsd and wsdl file in jdeveloper
    and then went to eclipse and tried t xquery tranformation, but when i add the replace in the message flow in the filed in Variable : body and Expression i look for the xquery and in the binding trying to put
    $body/input parameter, get the following error [RouteNode1, Replace action] XQuery expression validation failed: The current configuration is out of sync with the XQuery resource in the repository.
    what im doing wrong or its configuration
    thanks in advance sonia

    thanks
    ok have created a table with only in column varchar2(1)
    then the type object and the procedure to insert it works the proxy in the osb if i test it inserts
    now in jdeveloper i created an xml file with
    <?xml version="1.0" encoding="windows-1252" ?>
    <vessel>
    <barco>a</barco>
    </vessel>
    then i created a xsd based on this xml, and a wsdl based on the xsd
    in eclipse created a xquery transformation and selected source as the xsd created in adf and target the xsd input parameter, dont know why in the purple ball of the input parameter it puts a ?, an a f.
    then in the proxy xpath not writing anything in variable body and in the expression select the xquery and in binding select the parameter

  • Exchange Management Console, Initialization Failed

    Hi,
    Today when i open the Exchange 2010sp1 EMC it gave me this error
    The following error occurred while attempting to connect to the specified Exchange Server HUBC01.contoso.int
    The attempt to connect to
    http://HUBC01.contoso.int/powershell using "kerberos" authentication failed: connection to remote server failed with following error message: The WinRM client cannot process the request because the server name cannot be resolved. for more information see
    the about_remote-troubleshooting help topic
    Your quick response really appriciated,
    Dilshan

    Hi Dilshan,
    Any updates?
    Please check whether "WinRM IIS Extension" is installed in the Server Manager->Feature. If not, please install it.
    Please also try to use another member of Organization Management to log on to Exchange to open EMC to test.
    Frank Wang
    I came across this thread when troubleshootinga a similiar problem.  I login to Exchange this morning and I'm unable to open EMC and get an Initialization Failed error message.  It states
    The attempt to connect to http://exchange2010server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: Access is denied.
    I'm curious if the proposed solution to this thread would solve my problem.  I'm a little stumped as to what could cause this, other than the fact a colleague of mine installed the Exchange management tools on his Win7 workstation.  That really
    is the only change that has taken place in the last week.
    Any thoughts?

  • "Software Usage Metrics initialize failed" error when open Report Manager, after moving ReportServer from SSRS 2008 to SSRS 2012 (Native Mode)

    I've asked this question in SQL Server Upgrade forume, I'm asking here as well:
    Your help is highly appreciated!
    After migrating ReportServer db from 2008 to 2012, when access Report Manager throughhttp://myserver:80/Reports, I got the error below:
    ui!ReportManager_0-3!11d8!02/04/2013-15:19:12:: e ERROR: Software Usage Metrics initialize failed
    The process is below:
    •I successfully installed SQL Server 2012 (64-bit) Enterprise as a Native Mode on a server who runs Windows 7 Enterprise SP1 (64-bit).
    •I restored "ReportServer2008To2012" and "ReportServer2008To2012TempDB" in SSRS 2012 from the db files backed up in SQL 2008. In SSRS 2008, I have SSRS Model, ad-hoc reports based on model, and I also have canned reports built through BIDS
    report server project.
    •I reconfigured both databases' Compatibility level to SQL Server 2012(110) from SQL Server 2008(100).
    •I configured SSRS through Reporting Services Configuration Manager as below:
      > I chosen "Use built-in account:" as Service Account
    > In "Database" tab, I selected "Choose an existing report server database" and choose "ReportServer2008To2012" db, I used "Windows Authentication" (my login has the System Administrator priviledge). I got all 4 parts
    success: Verifying database sku = Success; Generating rights scripts = Success; Applying connection rights = Success; Setting DSN = Success.
    > I went to "Scale-out Deployment" to check if the initializing succeed, I found nothing there.
    Here are what I did from different approaches:
    A •I went to "Encryption Keys" and restored the key I backed up from SSRS 2008, after retoring, I got two initialized instances: One is on my current server (SSRS 2012), the other one is from the old server (SSRS 2008).
       I deleted the old one(SSRS 2008) through "Remove Server" action and kept the one on my current server(SSRS 2012).
       After I restart SSRS service, and tried to connect Report Manager, I got "An internal error occurred on the report server. See the error log for more details."
       I checked the log file, the error is actually "ERROR: Software Usage Metrics initialize failed"
    B •I also tried to "Delete Encrypted Content" and did see the SSRS was initialized through checking it on "Scale-out Deployment", however when I tried to open Report Manager, I got the same error.
    Anyone had the same issue? Any solution? Thanks in advance!

    Your help is highly appreciated!
    After migrating ReportServer db from 2008 to 2012, when access Report Manager through
    http://myserver:80/Reports, I got the error below:
    ui!ReportManager_0-3!11d8!02/04/2013-15:19:12:: e ERROR: Software Usage Metrics initialize failed
    The process is below:
    •I successfully installed SQL Server 2012 (64-bit) Enterprise as a Native Mode on a server who runs Windows 7 Enterprise SP1 (64-bit).
    •I restored "ReportServer2008To2012" and "ReportServer2008To2012TempDB" in SSRS 2012 from the db files backed up in SQL 2008. In SSRS 2008, I have SSRS Model, ad-hoc reports based on model, and I also have canned reports built through BIDS
    report server project.
    •I reconfigured both databases' Compatibility level to SQL Server 2012(110) from SQL Server 2008(100).
    •I configured SSRS through Reporting Services Configuration Manager as below:
     > I chosen "Use built-in account:" as Service Account
     > In "Database" tab, I selected "Choose an existing report server database" and choose "ReportServer2008To2012" db, I used "Windows Authentication" (my login has the System Administrator priviledge). I got all
    4 parts success: Verifying database sku = Success; Generating rights scripts = Success; Applying connection rights = Success; Setting DSN = Success.
     > I went to "Scale-out Deployment" to check if the initializing succeed, I found nothing there.
    Here are what I did from different approaches:
    A •I went to "Encryption Keys" and restored the key I backed up from SSRS 2008, after retoring, I got two initialized instances: One is on my current server (SSRS 2012), the other one is from the old server (SSRS 2008).
       I deleted the old one(SSRS 2008) through "Remove Server" action and kept the one on my current server(SSRS 2012).
       After I restart SSRS service, and tried to connect Report Manager, I got "An internal error occurred on the report server. See the error log for more details."
       I checked the log file, the error is actually "ERROR: Software Usage Metrics initialize failed"
    B •I also tried to "Delete Encrypted Content" and did see the SSRS was initialized through checking it on "Scale-out Deployment", however when I tried to open Report Manager, I got the same error.
    Anyone had the same issue? Any solution? Thanks in advance!

  • AcroDist.exe-DLL Initialization Failed on logoff/shutdown in XP x64

    Acrobat 9 Pro
    Windows XP Professional x64 Edition
    Intel Pentium Dual CPU E2160 1,8GHz
    2GB of memory.
    The title of the window of error is "AcroDist.exe - DLL Initialization Failed" and the message is "The application failed to initialize because the window station is shutting down." Behind the window is "Ending AcroTrayIcon". These messages occur when you logoff/shutdown and log into the system the first message reappears.
    If I close the process acrotray.exe before you logoff, the error does not occur.
    I am grateful for the help.

    Hi,
    I have  removed the SMD command lines from config tool, i have restarted the Instance  now  i am  facing the new error one .
    Sandbox is copied from Instance DBW and all services are pointing to DBW... even the message server also. please suggst where i have to change these settings..
    Thr 59500] Mon Jul 07 14:12:27 2008
    [Thr 59500] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 59500] ***LOG Q0I=> NiPGetServByName2: service 'sapmsDBW' not found: getservbyname_r [ninti.c 530]
    [Thr 59500] *** ERROR => LgIGroupX: NiServToNo(sapmsDBW) failed, (rc=NIESERV_UNKNOWN) [lgxx.c       4168]
    [Thr 59500] *** ERROR => JRFC> Error jrfc_lg LgGroup failed(-102) [jrfclg.c     344]
    [Thr 59500] *** ERROR =>       mshost: nbcddsabw10, msserv: sapmsDBW, r_group: TICDEV [jrfclg.c     345]
    [Thr 59860] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 59860] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 59860] JLaunchCloseProgram: good bye (exitcode = -11113)
    Thanks,
    Subhash.G

  • Oracle Windows Sevice does not start (ORA-12640: Authentication adapter initialization failed)

    I converted a physical windows 2003 machine to a virtual hyperv machine.
    The following error occurs in oradim.log when I try to start the Oracle Windows Service on the virtual server:
    ORA-12640: Authentication adapter initialization failed
    I recreated the service and the password file but with no luck.
    I also tried to change sqlnet.ora with the following: (Replaced NTS to NONE)
    SQLNET.AUTHENTICATION_SERVICES= (NONE)
    In this case the service was started but when I tried to connect as sysdba using sqlplus "/ as sysdba" the "ORA-01031: insufficient privileges" error occurs. If you connect using the password then it connects fine. But I would like to be able to connect without a password because I have some scripts that I do not want to hardcode the sysdba password.
    I also removed and readded the administrator password from ORA_DBA group but again with no luck.

    Have you seen this:
    Oracle Database Service on Windows 2000 in AutoStart Mode with Logon as SYSTEM
    (Bug 1397927) If you have installed an Oracle database service on Windows 2000, when logging in as SYSTEM user (Local System), with startup mode set to Automatic, it is possible that the Oracle database service starts but the database does not start automatically. The following error message is written to the ORADIM.LOG file in the ORACLE_BASE\ORACLE_HOME\DATABASE directory.
    ORA-12640: Authentication adapter initialization failed
    It has also been observed that the services like Oracle Enterprise Management Agent, Oracle Enterprise Manager Management Server and Oracle Internet Directory may also fail for the same reason because they cannot connect to the database.
    The workarounds for this problem are:
    Remove the line sqlnet.authentication_services=(NTS) from SQLNET.ORA or set sqlnet.authentication_services=(NONE) in SQLNET.ORA.
    Start the database manually after the Oracle database service has started using SQL*Plus connecting as user name INTERNAL. Note that the INTERNAL user name will not be available after release 8.1.7.
    Start the service as a specific user:
    Choose Start > Settings > Control Panel > Services. The Services dialog box appears.
    Select the service you want to start.
    Click the Startup button. The Service dialog box appears.
    Click This account and specify the user name and corresponding password.

Maybe you are looking for