Wscompile error : duplicate

environment: JAX-RPC Standard Implementation (1.1.2_01, build R40)
Server: Sun Application Server 8.0
Problem Statement:
We have two schemas suppose abc.xsd and cde.xsd which refer to one another i.e. abc.xsd imports cde.xsd and vice-versa (circular referencing).
There is a WSDL that imports in the type definition another schema say A.xsd which in turn imports abc.xsd. config-wsdl.xml refers to this WSDL.
On running the following command to generate server side artifacts:
wscompile -gen:server -d build -classpath build -mapping mapping.xml config-wsdl.xml
we get the following error:
error: modeler error: duplicate "element" entity
Is there any mechanism (like setting a flag/using some option )by which wscompile should include definitions of the schemas only once or some other solution to overcome this duplicate element entity error. Since there is no control over xsd's, we cannot modify the schema.
Thanks in advance
Regards
anjali

Hi,
I have a duplicate error of another reason. I try to generate client stubs on a WSDL which has many identical type names but in different namespaces.
- Is there any way to tell wscompile to map the different namspaces automatically to different packagenames?
There will be more and more such webservices with identical types in different namespaces in it. I have to use them and I wan't have the possibility to write for each single webservice explicit namspace / packagename mappings in the config files.
- Does somebody know a solution?

Similar Messages

  • Wscompile error with PayPalSvc.wsdl

    Hi,
    I am trying to use wscompile to generate the client artifacts for the PaypalSvc.wsdl file.
    The error is: error: modeler error: duplicate "complexType" entity: "AmountType"
    The link to the wsdl file is: http://www.sandbox.paypal.com/wsdl/PayPalSvc.wsdl
    My version of wscompile is: JAX-RPC Standard Implementation (1.1.2_04, build R45)
    Thanks,
    Jim

    We are having the same problem with the case changes in WSDL generation, preventing us from upgrading, too.  Haven't heard a peep from Adobe on it.
    - http://forums.adobe.com/message/1053957
    Wish I could help more.
    Fred

  • RFC Connection error duplicate conversation id

    Hello everybody !
    I started getting a weird error on my XI RFC Connections, because of this I can't connect to my SLD.
    When testing the RFC connection "AI_DIRECTORY_JCOSERVER", “Ai_RUNTIME_JCOSERVER”, “LCRSAPRFC” and “SAPSLDAPI” (trans sm59) I get the following error:
    ERROR duplicate conversation id 34212218 from localhost/sapgw01 and   calhost/  pgw00
    COMPONENT CPIC (TCP/IP) with Unicode
    COUNTER 87
    MODULE r3cpic.c
    LINE 5432
    RETURN CODE 736
    SUBRC 0
    RELEASE 640
    TIME Tue Dec 07 12:43:22 2004
    VERSION 3
    Does anybody have any idea/clues on this? thanx!
    Martial

    Hello !
    I have the same problem you had ...
    Do you solve your problem and how ?
    Thanks in advance
    Martial

  • Calendar and Adressbook error: Duplicate records found for GUID

    Hi all,
    i have a Mountaion Lion Server running on a mac mini and everything was working well.
    This morning one user of mine is unable to connect to his calendar and adressbook.... i found this error in the log files:
    2013-06-30 15:19:50+0200 [-] [caldav-1]  [-] [twistedcaldav.directory.appleopendirectory.OpenDirectoryService#error] Duplicate records found for GUID ****USER_GUID****:
    2013-06-30 15:19:50+0200 [-] [caldav-1]  [-] [twistedcaldav.directory.appleopendirectory.OpenDirectoryService#error] Duplicate: ***USER_Shortname***
    Apperetnly there is a duplicate match in the database. how can i fix this issue?
    In Server App this user is only listed once.
    Mail and other services for this user are working correctly.
    Thanks for any advice!

    Hi Samuel,
    You may try:
    select code,count(code)
    from [dbo\].[@XTSD_XA_CMD\]
    group by code having count(code) > 1
    What is the result?
    Thanks,
    Gordon

  • JWSDP1.5: wscompile error: "(should not happen): tie.generator.002

    Hi all,
    I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
    error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
    Cheers,
    --Tim West
    Full output (from wscompile Ant task) - added linebreaks for readability
    Buildfile: C:\common\eclipse-projects\thp\build.xml
    wscompile-init:
    ANEW-generate-server-binding:
    [wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
    -features:documentliteral,wsi -g -gen:server -keep -verbose \
    C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
    [wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: userDefinedBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdHeader]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestAckHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyResponseChoiceHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusQueryHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: statusStructure]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseHdr]
    [wscompile] error: generator error: internal error (should not happen): tie.generator.002
    BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
    Total time: 2 seconds

    Hi again,
    The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
    Thanks again,
    -Tim West
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
        name="TentativeHold"
        targetNamespace="http://www.w3.org/2001/08/thp/definitions"
        xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
        xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns="http://schemas.xmlsoap.org/wsdl/">
      <types>
        <schema xmlns="http://www.w3.org/2001/XMLSchema"
            xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
            targetNamespace="http://www.w3.org/2001/08/thp/schemas">
          <!-- =================================================================== -->
          <!-- Item - holdHeader -->
          <!-- Note - This information is required in all the Tentative Hold Protocol
                      communications. -->
          <!-- Fields- holdID - UUID. -->
          <!--             customerID - account number or other identifier -->
          <!--             replyTo - could be a unique locator such as a URI or an
                              email address depending on the communication protocol
                              to be used. -->
          <!-- comment - space for trading partner defined info. -->
          <!-- =================================================================== -->
          <complexType name="holdHeader">
            <sequence>
              <element name="holdID" type="int"/>
              <element name="customerID" type="string"/>
              <element name="replyTo" type="string"/>
              <element name="comment" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - userDefinedBody -->
          <!-- Note - This will carry any domain-specific information  (e.g., product
                ID and quantity). An implementation shall probably have many
                different userDefinedBody's (one for holdRequest, holdRequestAck,
                ...). This body is used in all messages. -->
          <!-- Fields - Trading partner to trading partner specific or an agreed
             - standard (e.g., RosettaNet PIP). -->
          <!-- =================================================================== -->
            <!-- TIM: Just junk here for now, must fix later -->
          <complexType name="userDefinedBody">
            <sequence>
              <element name="someRequestField" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestHdr -->
          <!-- Note - Specifies the Tentative Hold Protocol header for messages
             - requesting a tentative hold. -->
          <!-- Fields - Same as holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdRequestHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestAckHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + timeUntilResponse - a indication of the time it
             - will take the resource provider to process the request. -->
          <!-- =================================================================== -->
          <complexType name="holdRequestAckHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="timeUntilResponse" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdGrantHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdDuration" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the
             - denial. The implementation may choose to use reason codes or just
             - textual descriptions. -->
          <!-- =================================================================== -->
          <complexType name="holdDenialHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="reason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdModifyRequestHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdModifyGrantHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the denial.
             - The implementation may choose to use reason codes or just textual
             - descriptions.-->
          <!-- =================================================================== -->
          <complexType name="holdModifyDenialHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyResponseChoiceHdr -->
          <!-- Note - The use of a single type for this response was to facilitate a
             - synchronous request/response for the modify request without preventing
             - asynchronous.-->
          <!-- Fields - Either holdModifyGrantHdr or holdModifyDenialHdr -->
          <!-- =================================================================== -->
          <!-- TIM: JWSDP does not support xsd:choice, so I'm turning this into a sequence.
             -      The implementor is now responsible for ensuring exactly one of these
                    is present.
            -->
          <complexType name="holdModifyResponseChoiceHdr">
            <sequence>
              <element name="grant" type="holdSchema:holdModifyGrantHdr"/>
              <element name="deny" type="holdSchema:holdModifyDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + customerReason - a description of or a code for
             - the reason why the hold is being cancelled. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationRequestHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="customerReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationResponseHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationNotificationHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + cancellationReason - a description of or a code
             -for the reason the vendor is cancelling the hold. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationNotificationHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="cancellationReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusQueryHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusQueryHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - statusStructure -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdState - a description of the state of the hold.
             - Possible values currently defined are: responding, in process, active,
             - and inactive. The definition is left open (not restricted) for future or
             - user refinement of the useful values. -->
          <!-- =================================================================== -->
          <complexType name="statusStructure">
            <sequence>
              <element name="itemHeader" type="holdSchema:holdHeader"/>
              <element name="holdState" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseBody -->
          <!-- Note - -->
          <!-- Fields - holdItemsCount - the number of holds matching the holdStatusQuery. -->
          <!--             itemList - The header and state of the holds that match the query. -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseBody">
            <sequence>
              <element name="holdItemsCount" type="int"/>
              <element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdErrorHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <!-- TIM: Combined old "holdErrorHdr" and "holdErrorBody" as a fault must
             - have only a single part (see WSDL sec 3.6).
            -->
          <complexType name="holdError">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdErrorType" type="int"/>
              <element name="holdErrorDesc" type="string"/>
            </sequence>
          </complexType>
          <!-- TIM: To use doc/lit, we need <element> tags here to reference from WSDL -->
          <element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
          <element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
          <element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
          <element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
          <element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
          <element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
          <element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
          <element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
          <element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
          <element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
          <element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
          <element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
          <element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
          <element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
          <element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
          <element name="holdError" type="holdSchema:holdError"/>
        </schema>
      </types>
      <message name="HoldRequest">
        <part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
        <part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldRequestAck">
        <part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
        <part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldGrantResponse">
        <part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
        <part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldDenialResponse">
        <part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
        <part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyRequest">
        <part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
        <part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyResponse">
        <part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
        <part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationRequest">
        <part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
        <part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationResponse">
        <part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
        <part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationNotification">
        <part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
        <part name="body" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusQueryRequest">
        <part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
        <part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusResponse">
        <part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
        <part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
      </message>
      <message name="HoldErrorResponse">
        <!-- TIM: altered to be consistent with updated schema - the
           - fault body must have only one part
          -->
        <part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
      </message>
      <portType name="TentativeHoldServicePortType">
        <operation name="InitiateHold">
          <input message="tns:HoldRequest"/>
          <output message="tns:HoldRequestAck"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldModify">
          <input message="tns:HoldModifyRequest"/>
          <output message="tns:HoldModifyResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldCancellation">
          <input message="tns:HoldCancellationRequest"/>
          <output message="tns:HoldCancellationResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateStatusQuery">
          <input message="tns:HoldStatusQueryRequest"/>
          <output message="tns:HoldStatusResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
      </portType>
      <portType name="TentativeHoldNotificationServicePortType">
        <operation name="NotifyHoldGranted">
          <output message="tns:HoldGrantResponse"/>
        </operation>
        <operation name="NotifyHoldDenied">
          <output message="tns:HoldDenialResponse"/>
        </operation>
        <operation name="NotifyServerHoldCancellation">
          <output message="tns:HoldCancellationNotification"/>
        </operation>
      </portType>
      <binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
          <operation name="InitiateHold">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldModify">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldCancellation">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateStatusQuery">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
      </binding>
      <service name="TentativeHoldService">
        <documentation> Mythical Tentative Hold Web service</documentation>
        <port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHold/"/>
        </port>
      </service>
      <service name="TentativeHoldNotificationService">
        <port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHoldNotification"/>
        </port>
      </service>
    </definitions>

  • NDS error: duplicate value (-614) on Generic LDAP Export to NetIQ eDirectory

    Dear community,
    using the Generic LDAP Agent, the latest eDirectory (8.8.SP8 (20806.01) and FIM Version (4.1.3627.0)) I encounter the following problem in very special situations (namely when the value in eDirectory only differs from the FIM value by different upper/lower
    case letters:
    NDS error: duplicate value (-614)
    DirectoryOperationException: (0) 0 Server Message: The attribute exists or the value has been assigned.

    I don't see that as a Problem, when it is in fact doing string comparison.  You may need to write an advanced flow rule to simply say something like this
    CSHARP Snippet.  (if not equal, case does not matter)
    if !(csentry["co"].ToUpper().Equals(mventry["co"].ToUpper()))
     csentry["co"].Value =mventry["co"].Value ;
    Nosh Mernacaj, Identity Management Specialist

  • 46C Migration Oracle/HP-UX to MAXDB/SLE10 error: Duplicate value QCMT066

    To migrate a productive system from 46C to ECC600 I got an system copy export from our business partner.
    The source system is running on HPUX/Oracle. The target system should be MAXDB/SLE10.
    I run the import with R3setup and got error: Duplicate value QCMT066.
    To try to continue the import I set in DBMIG.R3S:
    [DBR3LOADEXEC_IND_ADA]
    from STATUS=ERROR to STATUS=OK
    [DBR3LOADVIEW_IND_ADA]
    from STATUS=ERROR to STATUS=OK
    [DBR3LICENSECREATE_IND_ADA]
    STATUS=ERROR to STATUS=OK
    [DBR3START_IND_ADA]
    from STATUS=ERROR to STATUS=OK
    Tthe system is coming up, but get: in SAPGUI: GEN_TABLE_NOT_EXISTS .. Table VSEOPARENT does not exist.
    I believe that I have to run the import again. How can I solve the duplicate value QCMT066 problem?
    Edited by: Trieu Chi Phung on Aug 4, 2009 4:01 PM

    Answer of SAP:
    Did you skip the error? because there errors in both SAPVIEW.log and
    SAPAPPL1.log
    The SAPVIEW is having error because the table VBKD was not imported yet, and this table belongs to package SAPAPPL1, so, you have to finish
    import the SAPAPPL1 in the first place.
    You have the error "Duplicate key in index" for table QCMT066
    One of the most important things to do before a migration starts is to
    look at the consistency between Database and ABAP DDIC (/DB02 > checks>
    button Database<> ABAP/4 DDIC) and to look after QCM-Tables from pre-
    viously failed table-conversions These temporary objects are used duringconversion (see attached note # 9385 this note is for 3.0F but explains
    the situation).
    I would like you to proceed as follows:
    1. In the source-system check SE14 > Extras > Invalid Temp.
    Tables and remove all entries from there
    2. Switch to use sidadm create a new temp-directory and run 'R3ldct
    without any parameters
    3. Check the STR-files created and grep for entries starting with
    QCM
    4. For those objects use function module 'DD_NAMETAB_DELETE' and
    remove them from the nametab
    5. repeat the export from scratch
    If you want a workaround on this, you can modify the <package>.STR file
    and remove the entry QCMT066 and restart the import to continue.
    However, this maybe tedious if you and lots of this kind of object.

  • Facebook installation gives an error ''duplicate provider authority''

    Hi everybody this is my first ever post I hope i will get an answer quickley from this forum,
    My question is I have this LENOVO S860 smartphone with 4.4 android, It came as preinstalled Facebook which has an older version of facebook which I don't like much when i go to playstore and try to download Facebook it downloads smoothly but when the installation process comes up it gives an error ''duplicate provider authority'' I can't even uninstall the default Facebook and neither can update it as there is no update button in Play Store, Please help me out
    thanks

    1.Have you try  go to  Settings-System Settings -Apps select the Facebook app to  uninstalled it .   It could be uninstalled by user.   
    2.what's  the default Facebook version in your phone? is it 3.7?
    You can get it from Settings-System Settings -Apps select the Facebook app.  Could you take a screenshot about the Facebook app info to give me
    3.what's your Build number version ,You can go to Settings-System Settings-About phone--Version information -Build number.  Could you take a screenshot about the Version infomation to give me.

  • Content generation error. [Error: Duplicate overlay IDs are not allowed]

    Has anyone else experienced this? I'm creating a hidden navigation menu that has buttons for showing and hiding it. When the menu is on, there are a number of buttons grouped together in one of the states. It works when I preview with the preview tool, but when I try to preview through Folio Builder I get the error message: Content generation error. [Error: Duplicate overlay IDs are not allowed]
    All of my multi-state objects have unique names, as do buttons and layers and I still get this error. Any ideas?
    Thanks,
    Christopher

    Attached are screenshots of my layers palette, object states and buttons. I noticed in the layers palette, after I've made the menu into a multi-state object there's a sub-group called "normal" that's showing up in my layers palette. Could this be it?

  • Intellisync error "Duplicate records found"

    I am trying to sync my BB 8300 with Outlook 2007.  I am using Blackberry Desk Manager 4.2.2.14.
    I was able to sync before but now it get this error "Duplicate records found in the device" and it won't sync.
    Any ideas to fix this problem?
    I tried to un-install and re-install DM.
    I also tried to delete Intellisync folder
    Thanks! 

    JJKD wrote:
    I am trying to sync my BB 8300 with Outlook 2007.  I am using Blackberry Desk Manager 4.2.2.14.
    I was able to sync before but now it get this error "Duplicate records found in the device" and it won't sync.
    Any ideas to fix this problem?
    I tried to un-install and re-install DM.
    I also tried to delete Intellisync folder
    Thanks! 
    Hi JJKD;
    What is your email application?
    Backup your device.
    Review the BB KB Here...
    There are a couple of approaches to this. If your not needing to complete a two way sync, you can clear the calendar on the BB Handheld by going to BACKUP / ADVANCED and clearing the calendar on right side of the Advanced GUI. Then just try a regular sync.
    This can also work by clearing
    If you do need to complete a two way sync you can BACKUP the device and clear the Calendar (edit), then RESTORE just the the calendar in BACKUP / ADVANCED by menu'ing the backup you created and complete a restore of the calendar. By backing up and then clearing and then restoring, this will clear any issues with the calendar DB and reindex the data. Then try a regular sync and see if the symptom is taken care of.
    Good luck and let us know how your doing...
    Message Edited by hmeister on 10-10-2008 09:48 PM
    +++++++++++++++++++++++++++++++++++++++++++++++++
    If successful in helping you, please give me kudos in my post.
    Please mark the post that solved it for you!
    Thank you!
    Best Regards
    hmeister

  • Had to replace Xserve RAID controller and now I get Xsan Admin: ERROR: duplicate LUN label RAID1-Left1

    I need some help, I had one of my five Xserve RAID boxes fail. The upper controller card needed to be replaced and so we replaced it. But now only one of my volumes is loading and I am seeing the following error in my Console.
    7/18/12 9:23:18.550 AM Xsan Admin: ERROR: duplicate LUN label RAID1-Left1
    This raid box holds three LUNs. the left is split into two with one being the metadata / Journal for the main volume and the 2nd being the same for my secondary volume. The right side of this box is the second volume while the remaining 4 RAID boxes are my main volume. Here is the rub, the main volume is using the left1 LUN and the secondary is left2. The left2 is the one that is not working and when I go into the LUN info the WWN number does not match the actual id on the raid box.
    HELP!!!!
    Thanks,
    Kevin Rosenthal

    Did you try turning it off and on again? I mean, the full SAN shutdown/startup: http://support.apple.com/kb/HT4027
    You're probably seeing "duplicate LUN labels" because the MDC has seen two LUNs with the same label but different serial numbers since it has been online. The serial number (which I think is based off the WWN) would have changed when the RAID controller changed. A reboot should fix that specific error message.
    If the volume still doesn't start after rebooting, then you would want to check the cvlog for that volume.

  • DTP Error: Duplicate data record detected

    Hi experts,
    I have a problem with loading data from DataSource to standart DSO.
    In DS there are master data attr. which have a key  containing id_field.
    In End routine I make some operations which multiple lines in result package and fill new date field - defined in DSO ( and also in result_package definition )
    I.E.
    Result_package before End routine:
    __ Id_field ____ attra1 ____  attr_b  ...___   attr_x ____ date_field
       ____1________ a1______ b1_________ x1         
       ____2________ a2______ b2_________ x2       
    Result_package after End routine:
    __ Id_field ____ attra1 ____  attr_b  ..___   attr_x ____ date_field
       ____1________ a1______ b1_________ x1______d1         
       ____2________ a1______ b1_________ x1______d2    
       ____3________ a2______ b2_________ x2______d1         
       ____4________ a2______ b2_________ x2______d2   
    The  date_field (date type)  is in a key fields in DSO
    When I execute DTP I have an error in section Update to DataStore Object: "Duplicate data record detected "
    "During loading, there was a key violation. You tried to save more than one data record with the same semantic key."
    As I know the result_package key contains all fields except fields type i, p, f.
    In simulate mode (debuging) everything is correct and the status is green.
    In DSO I have uncheched checkbox "Unique Data Records"
    Any ideas?
    Thanks in advance.
    MG

    Hi,
          In the end routine, try giving
    DELETE ADJACENT DUPLICATES FROM RESULT_PACKAGE COMPARING  XXX  YYY.
    Here XXX and YYY are keys so that you can eliminate the extra duplicate record.
    Or you can even try giving
        SORT itab_XXX BY field1 field2  field3 ASCENDING.
        DELETE ADJACENT DUPLICATES FROM itab_XXX COMPARING field1 field2  field3.
    this can be given before you loop your internal table (in case you are using internal table and loops)  itab_xxx is the internal table.
    field1, field2 and field 3 may vary depending on your requirement.
    By using the above lines, you can get rid of duplicates coming through the end routine.
    Regards
    Sunil
    Edited by: Sunny84 on Aug 7, 2009 1:13 PM

  • Sharepoint 2013 (Danish): Deploying site from a custom template fails with error "Duplicate content type"

    I cannot create a site-template in my own language (danish) and deploy a site based on the template.
    I created a template from a "fresh" SharePoint project site with no tampering.
    When trying to deploy a new site based on the templat I get the following error:
    In Danish:
    Beklager, men noget gik galt
    Det blev fundet et navn på en dubletindholdstype "billede".
    Tekniske oplysninger
    Fejlfinding af problemer med Microsoft SharePoint Foundation.
    Korrelations-id: 96646c9c-3213-a088-c6c4-537b0815313c
    Dato og klokkeslæt: 21-06-2014 10:23:36
    In English:
    Sorry, something went wrong
    A duplicate content type name "billede" was found.
    Technical Details
    Troubleshoot issues with Microsoft SharePoint Foundation.
    Correlation ID: 0b656c9c-52ee-a088-c6c4-5132070e3c4e
    Date and Time: 21-06-2014 10:31:35

    Need details from ULS logs about Correlation ID: 0b656c9c-52ee-a088-c6c4-5132070e3c4e
    Check below:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/e955e737-e12e-4afa-b446-bb6e0f05e9b1/duplicated-content-type-error-creating-a-sharepoint-2010-site-from-a-custom-site-template?forum=sharepointgeneralprevious
    http://aramacciotti.wordpress.com/2012/04/04/the-case-of-the-duplicated-contenttype/
    http://community.office365.com/en-us/f/154/t/69416.aspx
    If this helped you resolve your issue, please mark it Answered

  • Creation and checkout errors, duplicate transactions using iPhoto print projects?

    My fiance and I have been using iPhoto to create calendars to give away as gifts for a couple years. I have had multiple problems with the latest iPhoto. They occurred on two Macbooks on two different wireless networks (an old white MB from 2006 running Snow Leopard, and the other an MBP running Lion), both with the latest iPhoto. Apple Support told me I should have used Time Capsule to avoid the first two of these errors (which, I was told, are documented bugs in their software). I was bummed because I initially spent around over 8 hours building the print book project!
    - Fonts changing when opening journal print book projects (fixed by completely restarting an 80 page book :-/ )
    - Pages cannot be rearranged in print books - they actually swap rather than drag and drop (fixed by again, completely restarting the project!)
    - When checking out, in calendars have an unspecified error and I have to cancel and fix individual photos (fixed by canceling
    - Photos randomly become blank icons and I have to reupload the photos
    - Photos that are dragged and dropped into a calendar don't show up in a random spot in the project and I have to go find them
    - When ordering calendars for this holiday season, errors when uploading have resulted in 16 duplicate transactions on my debit card resulting in over $400 of pending transactions that have been unable to be resolved by Apple Support
    Has anyone else experienced these problems? Any real fixes?

    If you're using iPhoto 5 as you say then, yes, 24k photos is heading close to the Limit of 25k. iPhoto 6 is good for 250,000 images, iPhoto 11 is good for 1,000,000.
    I'm going to guess that's a typo and that you have iPhoto 9.5.
    I've simply never heard of "too many photos" causing the problem you describe. You don't need more memory. You don't need to break up the Library. "Flushing Memory" is a non-isssue. One of the big improvements in 10.9 is in memory management.
    There are a couple of ways to break up a Library while preserving everything. It's dead easy with Aperture - export projects as Library - you can do it with iPhoto simply by duplicating the Library and deleting from the two libraries or use iPhoto Library Manager.
    But, as I say, 24k is a small Library. My main library is more than twice the size of that.
    Are Aperture and iPhoto using the same Library?
    As a Test:
    Hold down the option (or alt) key and launch iPhoto. From the resulting menu select 'Create Library'
    Import a few pics into this new, blank library. Is the Problem repeated there?
    Post back with the result.

  • XML Parsing Error: duplicate attribute in Firefox

    Hello,
    I recently switched from a JSF 1.2 RI nightly build from March to the 1.2_01 SNAPSHOT from 5/5/06 available in the maven repository:
    https://maven-repository.dev.java.net/repository/javax.faces/jars/
    Upon doing so, Firefox stopped rendering certain pages complaining of dupicate attributes (IE doesn't seem to care). The duplicate attributes are onclick attributes of <h:commandButton/> generated <input/> tags.
    The background is that we have a number of <h:commandButton> tags that once submitted forms as part of JSF actions, but were modified to call JavaScript (non-JSF integrated) instead (type="button" onclick="someJavaScriptFunc()"). As this is the case, the problem has been easily avoided by changing the <h:commandButton/> tags to regular html <input/> tags.
    My question is whether the rendering of two onclick attributes per <h:commandButton type="button"/> tags is a bug that should be reported, or a result of user error.
    I am also using Facelets 1.1.4 in JBoss AS 4.0.3sp1.
    Thanks for the help,
    Jonn

    No, my expectations are not unmet. Being new to JSF 1.2 RI, I thought it best to ask about possible user error before reporting a bug.
    Not surprised that the same error appears in app server 9 as it looks like it contains a JSF snapshot from a few days before the one I'm using.
    I just tested the nightly from 6-2-2006 and the duplicate attribute problem appears fixed, so no need to open an issue. tromanow, you might want to grab these jars from the jsf java.net site:
    https://javaserverfaces.dev.java.net/servlets/ProjectDocumentList?folderID=1703&expandFolder=1703&folderID=5420
    ...as long as you're not using Seam, as Seam variable resolving appears to be broken using the 6-2 nightly.

Maybe you are looking for

  • I cannot access or connect to my app store on macbook pro

    I am unable to connect to my app store with my mac book pro.  When I open the app it flashes a lot, I have tried going into 'store'  on the tool bar and signing into my account but it comes up "connection failed'. We have tried using wifi and etherne

  • How does expert day work?

    how does this expert day work? 

  • Dual Network Issues

    I have set up a n network using a new airport extreme base station and have a g band running alongside it using my old base station. After a lot of resets and trying different things, everything appears to be working. However, when I try to have my M

  • My USB Tascam US-200 audio soundcard can't be found in System Preferences, but can be found in application? (Screenshots inside)

    I'm having some issues with my audio since I upgraded to Yosemite 10.10.1. This is currently what the sound section in my system preferences shows: Before I upgraded to Yosemite 10.10.1, I had an option for "US-200" on the list to select. I use music

  • Best hardware but worst times

    We are testing a "fastest" hardware to put in production soon. To test the machine we use our quality server which is a clone of production server. When we make the test, we have noticed that: When we access from Abap to the database the time of the