Horrible pixelation that should not happen

I am running Final Cut Pro 5 and when I have video without any transitions, effects, or LiveType Titles the resolution is high and high when I render it. But when I add one of these elements it cuts the resolution down to about 1/4 of the original pixels.
It is obviously not just the preview playback in FCP, but something else because when I just look at the individual frames it happens. It also happens when I do a quick export to quicktime, or a full export to quick time in any format.
I am worried that it will do this when I print to tape as well. I have a 1' project due tomorrow for my high school's broadcasting class and that is where I will upload to MiniDV.
I need the titles and transitions, and I want this pixilation to go away. It's not just with this one movie, it has done it for every other movie I have edited.
I am running a PowerBook G4 w/ 1.5 GHz 512MB RAM and 64MB Video. I am not editing in HD.
Why is it doing this and how can I fix it? I need to know tonight... any help would be greatly appreciated. Thanks.

right now, I cannot monitor externally, by any means. I am just busy. I did not have access to the broadcasting room today, because I had an AP test. There is no computer that isn't a laptop at the house I stay at during the week, so no external monitor. I can get access to the monitor for my desktop this weekend. And the only video camera at this house is a Sony Handycam, a rather old one, and it doesn't have support for FireWire, only USB.
It hasn't always been like this, as I may have said. I was looking at some older videos. and the first two I did are loaded with tons of effects. And no pixelation. http://www.webbschool.com/%7Eicady/Goat.mov That's a link to the first thing I ever edited in Final Cut. You can see that there is no pixelation and that it is loaded with effects.
I am wondering if maybe it is the amount of HDD space I have. Because, when I first did that video, the computer was brand new. I also do photography, and without an external HDD (besides my iPod), they are taking up quite a bit of space. I have 7.5 GB free.
One of the last things I did for my class didn't pixelate until a certain point of effects. And the new one pixelates even with a crossfade or a fade to/from black.
Could this be a problem? And is there someway to reset the settings to default?
Also, something else to note. The Goat movie I did, I imported with iMovie, because I hadn't figured out FCP yet. Could that have something to do with it?

Similar Messages

  • 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>

  • Update should not happen in the name of WF-BATCH

    Hi All,
    I have a requirement to change the WF-BATCH to the other user id.
    The task completion or update should not happen in the name of WF-BATCH, instead it should happen with the name of the other user id.
    Please can anybody suggest on this..
    Thanks and Best Regards,
    Sushmitha

    Hello Sushmitha,
    Like I said, it is only working if a previous step was a dialog step for the same user.
    Then when all steps have advance with dialog it will automatically execute the "background" step (which is now dialog).
    If the "background" step is the first to be executed then this scenario does not work.
    It will only work if the agent has a previous work item AND is the one you want as the changed_by user.
    A work around would be to either
    a) check what the method does. If it executes a FM and if that FM has a parameter for changed by you can create a new method where you pass the changed_by user
    b) check if a bapi/fm exists which allows you to change the user
    c) create a program to execute the same logic as the method. Now you must create a new method where you can schedule this program as a background job with another user as the person who executes it.
    Kind regards, Rob Dielemans

  • My mac mini is running slow.  Bought it in 2009.  Activity monitor shows nothing running that should not be.  Someone suggested it might be my operating system?  Check for software updates, and I am current.  Suggestions?

    My mac mini is running slow.  Bought it in 2009.  Activity monitor shows nothing running that should not be.  Someone suggested it might be my operating system?  Check for software updates, and I am current.  Suggestions?

    Open Activity Monitor, Show:>All Processes, sort on CPU%, see if anything using too much CPU% when this happens, click on Memory tab, do you have many Pageouts?
    Open Console in Utilities & see if there are any clues or repeating messages when this happens.
    Check the S.M.A.R.T. status of the drive in Disk Utilty by highlighting the Drive & looking at the bottom of the window.

  • Should not happen unless default context failed to deploy

              Can somebody please throw some light on this error?
              <Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP> <HttpServer5173817,null
              default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
              HTTP/1.0". This should not happen unless the default context failed
              to deploy.>
              Myself and lot of other people in my team are getting this error
              when using beans in a cluster.
              I am getting this error consistently whenever I make some code
              changes in my bean class (not interface changes) and redeploy it
              and try to lookup through a stand-alone client.
              The only way I could find to overcome this problem is:
              1) edit config.xml to remove the Application element completely
              corresponding to the bean
              2) remove jar files from the applications directory
              3) re-deploy and run the client again.
              Thanks a lot
              Kiran Ganuthula
              

    Partly it could be WLS problem also. Under any circumstances default webapp should be able
              to deploy. I have seen somebody else also reported the same problem. The current problem is
              if you delete anything from apps dir, the corresponding entry is not being deleted from config.xml
              So next time when you boot the server, it tries to deploy the webapp and eventually it fails.
              I 'm not sure if this is the situation in your case.
              In anycase somehow Targets tag is not being picking up. That's why i asked you add
              "WebServers" tag. I think we have done some major changes in SP1, to make sure that
              default webapp deploys all the times.
              If you still have problems, post it to servlet or management group, we will discuss there.
              Kumar
              Kiran G wrote:
              > I edited the config.xml ONLY after getting this error. And, it worked.
              >
              > BTW, can you please be more specific about the changes to config.xml
              > to solve the problem?
              > If possible, can you give pertinent portion(s) of config.xml, highlighting
              > the changes.
              >
              > Thanks
              > Kiran G
              >
              > Kumar Allamraju <[email protected]> wrote:
              > >
              > >
              > >It appears your "default webapp" failed to deploy.
              > >Did you messed up with the config.xml?.
              > >
              > >Add the following to your default webapp tag?
              > >
              > ><Application
              > > Deployed="true"
              > > Name="DefaultWebApp_vindev1"
              > > Path="./config/vindev1/applications"
              > > >
              > > <WebAppComponent
              > > Name="DefaultWebApp_vindev1"
              > > Targets="vindev1"
              > > WebServers="vindev1"
              > > URI="DefaultWebApp_vindev1"
              > > />
              > > </Application>
              > >
              > >
              > >Here vindev1 is my domain's name..
              > >
              > >BTW, this is not a clustering question. So you better
              > >post it to servlet newsgroup where you get much
              > >better answers..
              > >
              > >Kiran G wrote:
              > >
              > >> I forgot to give these details about the problem.
              > >> I am running this cluster using WebLogic 6.0 on a SUN
              > >sparc machine.
              > >>
              > >> The error text given in my original posting appears
              > >in the managed
              > >> weblogic server's log. The exception that the client
              > >receives while
              > >> lookup is :
              > >>
              > >> javax.naming.CommunicationException. Root exception
              > >is java.rmi.UnmarshalException:
              > >> failed to unmarshal class java.lang.Object; nested exception
              > >is:
              > >> java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
              > >> java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
              > >>
              > >> "Kiran G" <[email protected]> wrote:
              > >> >
              > >> >Can somebody please throw some light on this error?
              > >> >
              > >> ><Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP> <HttpServer5173817,null
              > >> >default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
              > >> >HTTP/1.0". This should not happen unless the default
              > >context
              > >> >failed
              > >> >to deploy.>
              > >> >
              > >> >Myself and lot of other people in my team are getting
              > >> >this error
              > >> >when using beans in a cluster.
              > >> >
              > >> >I am getting this error consistently whenever I make
              > >some
              > >> >code
              > >> >changes in my bean class (not interface changes) and
              > >redeploy
              > >> >it
              > >> >and try to lookup through a stand-alone client.
              > >> >
              > >> >The only way I could find to overcome this problem
              > >is:
              > >> >1) edit config.xml to remove the Application element
              > >completely
              > >> >corresponding to the bean
              > >> >2) remove jar files from the applications directory
              > >> >3) re-deploy and run the client again.
              > >> >
              > >> >Thanks a lot
              > >> >Kiran Ganuthula
              > >> >
              > >> >
              > >> >
              > >> >
              > >> >
              > >
              > >
              > ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
              > ><html>
              > >It appears your "default webapp" failed to deploy.
              > ><br>Did you messed up with the config.xml?.
              > ><p>Add the following to your default webapp tag?
              > ><p><Application
              > ><br> Deployed="true"
              > ><br> Name="DefaultWebApp_vindev1"
              > ><br> Path="./config/vindev1/applications"
              > ><br> >
              > ><br> <WebAppComponent
              > ><br> Name="DefaultWebApp_vindev1"
              > ><br> Targets="vindev1"
              > ><br> <b><font color="#CC0000">
              > >WebServers="vindev1"</font></b>
              > ><br> URI="DefaultWebApp_vindev1"
              > ><br> />
              > ><br> </Application>
              > ><br>
              > ><p>Here vindev1 is my domain's name..
              > ><br><br>
              > >BTW, this is not a clustering question. So you better
              > >post it to servlet
              > >newsgroup where you get much
              > ><br>better answers..
              > ><p>Kiran G wrote:
              > ><blockquote TYPE=CITE>I forgot to give these details about
              > >the problem.
              > ><br>I am running this cluster using WebLogic 6.0 on a
              > >SUN sparc machine.
              > ><p>The error text given in my original posting appears
              > >in the managed
              > ><br>weblogic server's log. The exception that the client
              > >receives while
              > ><br>lookup is :
              > ><p>javax.naming.CommunicationException. Root exception
              > >is java.rmi.UnmarshalException:
              > ><br>failed to unmarshal class java.lang.Object; nested
              > >exception is:
              > ><br> java.lang.ClassNotFoundException:
              > >RingoutSessionBeanHomeImpl_WLStub
              > ><br>java.lang.ClassNotFoundException: RingoutSessionBeanHomeImpl_WLStub
              > ><p>"Kiran G" <[email protected]> wrote:
              > ><br>>
              > ><br>>Can somebody please throw some light on this error?
              > ><br>>
              > ><br>><Mar 5, 2001 10:07:26 AM EST> <Error> <HTTP>
              > ><HttpServer5173817,null
              > ><br>>default ctx,POSDev01) found no context for "GET /classes/ringout_statelessSession3@/RingoutSessionBeanHomeImpl_WLStub.class
              > ><br>>HTTP/1.0". This should not happen unless the default
              > >context
              > ><br>>failed
              > ><br>>to deploy.>
              > ><br>>
              > ><br>>Myself and lot of other people in my team are getting
              > ><br>>this error
              > ><br>>when using beans in a cluster.
              > ><br>>
              > ><br>>I am getting this error consistently whenever I make
              > >some
              > ><br>>code
              > ><br>>changes in my bean class (not interface changes)
              > >and redeploy
              > ><br>>it
              > ><br>>and try to lookup through a stand-alone client.
              > ><br>>
              > ><br>>The only way I could find to overcome this problem
              > >is:
              > ><br>>1) edit config.xml to remove the Application element
              > >completely
              > ><br>>corresponding to the bean
              > ><br>>2) remove jar files from the applications directory
              > ><br>>3) re-deploy and run the client again.
              > ><br>>
              > ><br>>Thanks a lot
              > ><br>>Kiran Ganuthula
              > ><br>>
              > ><br>>
              > ><br>>
              > ><br>>
              > ><br>></blockquote>
              > ></html>
              > >
              > >
              [att1.html]
              

  • Order is showing in T code# VKM3, which should not happen.

    Client using automatic credit check. Customer maintained credit master data for which system is doing credit check.  As per client requirement the future orders created for this customer system should not do a credit check.
    For this we have created a new risk category and in the T code #ova8 , unchecked all the settings for this combination of credit control area,  risk category  and credit group. We maintained the new risk category in the credit master data of that customer, and created a new order and found that the system is not doing any credit check and system is allowing for the billing. However when but this order is showing in T code# VKM3, which should not happen.

    Hi- SAP always shows orders in VKM3 even though they do not have credit hold... SAP lists all orders which have item cat deliver or billing relevant..
    Reg
    Siva

  • I lost power to my MacBook Pro before I had saved anything that I was working on...usually I plug my computer it and power it back on and the documents pop right back up when the computer turns on. That did not happen this time.How can I recover this data

    I lost power to my MacBook Pro before I had saved anything that I was working on...usually I plug my computer it and power it back on and the documents pop right back up when the computer turns on. That did not happen this time. How can I recover my documents?

    If you never saved, auto save does not kick in.
    Peter

  • PR to PO conversion should not happen in case of expired pricing condition in Info Record

    Hi All,
    Issue – PR to PO conversion should not happen in case of expired pricing condition in Info Record.
    In case of creation of PR/ PO, the Price is pulled out from the Info Record of the material. In our case if the Price in the Info Record is expired, it should give the Error Message & should pick the Price from the last PO created for the same combination of Plant, Vendor, Company code.
    Request you to please let us know if there is any way out.
    Regards,
    Karthick.V

    Hi,
    As per your requirement if info record price is not valid and in auto PO creation from PR, price should get picked from last PO, this is standard behavior and it will happen.
    If you check in customization MM - Purchasing - Environment Data - Define Default Values for Buyers -Settings for default values
    Default values if you check under price adoption , it has to be Always copy ( copying of conditions from last PO) . Pls check

  • Reversal of a reversed document should not happen

    Dears
    In our system, user is able to reverse an already reversed document, which should not happen.
    In the Message Control F5 361, nothing has been changed to make this warning or information.
    Hence the standard is 'error'. But why the system is allowing the reversal of  a reversed document then ?
    Could you please provide inputs ?

    Hello Nikitha,
    Please create one validation according to your requirement. PFB the relevant T codes to create validation.
    GGB0 - Create Validation
    OB28 - Activation of FI validations
    GCT9 - Transport: Validations
    Please let us know do you still require any more information
    Thanks & Regards,
    Lakshmi S

  • HOW WE CAN VALIDATE A FIELD THAT SHOULD NOT BE SPECIAL CHARACTER?

    HOW WE CAN VALIDATE A FIELD THAT SHOULD NOT BE SPECIAL CHARACTER?

    data : v_abcde like sy-abcde,
             v_num like '0123456789',
              v_data(60) type c.
    start-of-selection.
    v_abcde = sy-abcde.
    concatenate v_abcde v_num into v_data.
    if ur field co v_data
    else.
    message.
    endif.

  • Purchase order printout should not happen without release of PO

    I have made all the settings for PO release strategy and printout settings. But printout can be taken even before final release. I checked the settings and this printout should not happen before release. Please help me out.
    Thanks in advance.

    Hi,
    Thank ypu for your reply. PO was not released. Printout wa snot able to be taken in ME9F. But Printout can be taken using Print preview in Tcode ME22N. Can we avoid such printing using Print preview option.
    Thank you in advance

  • I am not able to play videos from YoyTube, or videow posted on my blog. That does not happens with explorer, where videos are playing normal

    I am not able to play videos from YouTube, or videow posted on my blog, when I use Fire Fox. That did not happened before the 3.6.14 and allthouhg you informed us that with the 3.6.15 the problem will dissapear, it does not happen. Take into consideration that, with explorer, everything is running fine. I am a long time user o firefox and I donnot want to change. Please give me advise how to solve thiw problem. Tanhks in advance

    Hi, My computer shuts down when I try to do any thing with graphics, ie, watching streamed video or looking at my photo's. this is a recent problem, anyone got any idea's

  • I have started to get the 150:30 error in Photoshop Elements. I am using English so that should not

    I am getting the 150:30 error in Photoshop Elements. I am using English as my language so that should not be an issue. I have restarted the computer but to no avail. I am furious at Adobe for letting this go on so long. I see posts with this same issue from October 2009. You would think that the Adobe engineers could have found a way to resolve this issue by now. There seem to be a lot of people with this problem and it is inexcusable.

    Have you already ran the workarounds/solutions mentioned in the link below? try the LicenseRecovery toolkit and see if that helps?
    http://kb2.adobe.com/cps/512/cpsid_51260.html
    Regards,
    Ankush

  • I keep getting this message and PSCC will not open:Unable to start your subscription for Adobe Photoshop CC.  I keep trying again with no results.  I am on automatic pay system.  This should not happen.

    I keep getting this message and PSCC will not open:Unable to start your subscription for Adobe Photoshop CC.  I keep trying again with no results.  I am on automatic pay system.  This should not happen.
    I had it open a few minutes ago.  Closed it and went to reopen to no avail. How can I open and continue to work?

    Does your Cloud subscription properly show on your account page?
    If you have more than one email, are you sure you are using the correct Adobe ID?
    https://www.adobe.com/account.html for subscriptions on your Adobe page
    If yes
    Some general information for a Cloud subscription
    Cloud programs do not use serial numbers... you log in to your paid Cloud account to download & install & activate... you MAY need to log out of the Cloud and restart your computer and log back in to the Cloud for things to work
    Log out of your Cloud account... Restart your computer... Log in to your paid Cloud account
    -Sign in help http://helpx.adobe.com/x-productkb/policy-pricing/account-password-sign-faq.html
    -http://helpx.adobe.com/creative-cloud/kb/sign-in-out-creative-cloud-desktop-app.html
    -http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
    -http://helpx.adobe.com/creative-suite/kb/trial--1-launch.html
    -ID help https://helpx.adobe.com/contact.html?step=ZNA_id-signing_stillNeedHelp
    If no
    This is an open forum, not Adobe support... you need Adobe staff to help
    Adobe contact information - http://helpx.adobe.com/contact.html
    -Select your product and what you need help with
    -Click on the blue box "Still need help? Contact us"

  • How to compare two dates that should not exceed morethan 3 years

    hi all,
    can you please tell me how to compare two dates( basically dates are string type)
    that should not exceed more than 3 years? in JAVASCRIPT
    Thanks in Advance.

    This is not a JavaScript forum.
    [*Google* JavaScript Forum|http://www.google.co.uk/search?q=JavaScript+Forum&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a]
    Good luck.

Maybe you are looking for

  • HT4907 Password Issue when attempting to enable Back to My Mac in iCloud Preferences - HELP?

    Since upgrading to Mountain Lion, I have a problem enabling Back to My Mac. When I try and enable B2MM in the iCloud preferences window, I am asked to enter my Apple ID password. It says the password is incorrect, even though it IS 100% correct. I've

  • How create a carrosel photo gallery with Adobe Muse widgets?

    I use Adobe Muse 3.2 build 2, and I need create a photo gallery with many photos (around 60) like a carrosel (with photos and thumbnails that slides both from left to right). There is some way to create or insert a widget of this kind in Muse? If pos

  • Parallel query clarification

    Hi, I am working on Oracle 10.2.0.4 2 node RAC database(Solaris 10, SPARC). I have a table containing around 10 million rows occupying 10G storage. To test the benefits of partitioning I created a partitioned table and then tried inserting all the re

  • Memory & Export & Media Encoder

    Problem 1: Is there in CS4 a way to export a standard DV AVI file (standard DV 4:3 source material) without having to use Media Encoder?   In older versions of Premiere (CS2 for example) all I had to do was "Export to Movie" which created an AVI file

  • Annotations in Mail

    I just moved to Mail from Eudora. There I had the possibility to annotate received messages - which I did a lot, comments, actions to take etc. There doesn't seem to be such a function in Mail. Is there a way aroud this limitation?