Latest post Thu, Mar 23 2017 9:49 PM by Vadym. 8 replies.
Page 1 of 1 (9 items)
Sort Posts: Previous Next
  • Thu, Mar 23 2017 3:54 PM

    An unexpected error occurred checking in asset

    Can somebody see what my unexpected error is?

    I was following the guide located here.

    http://localhost/docs/Interplay_WS_Reference_Guide.html#ref_assetsService_checkInAAF

     

    I am attempting to execute the following command. I replaced the huge base64 encoded string to keep the message at a readable length

    <x:Envelope xmlns:x="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://avid.com/interplay/ws/assets/types">

       <x:Header>

          <typ:UserCredentials>

    {my credenitals, that work fine}

          </typ:UserCredentials>

       </x:Header>

       <x:Body>

         <typ:CheckInAAF>

            <typ:InterplayURI>interplay://EvertzWorkgroup/Projects/JEFFK/</typ:InterplayURI>

            <typ:AAF>{VALID base64encoded AAF File string}</typ:AAF>

            </typ:CheckInAAF>

      </x:Body>

    </x:Envelope>

    ------------------------------------------------------------------------

    Comes back with an unexpected error about being unable to checkin, but if I drag the same file into the same interplay access project folder it works fine. I am pretty sure the base64 content is ok because I got error parsing XMLStream when it wasnt encoded to base64.

    ------------------------------------------------------------------------- 

    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

       <soap:Body>

          <soap:Fault>

             <faultcode>soap:Server</faultcode>

             <faultstring>An unexpected error occurred checking in asset to interplay://EvertzWorkgroup/Projects/JEFFK/  null.</faultstring>

             <detail>

                <AssetsFaultType Code="OTHER_ERROR" xmlns="http://avid.com/interplay/ws/assets/types">

                   <Message>An unexpected error occurred checking in asset to interplay://EvertzWorkgroup/Projects/JEFFK/  null.</Message>

                   <Details>An unexpected error occurred checking in asset to interplay://EvertzWorkgroup/Projects/JEFFK/  null.</Details>

                </AssetsFaultType>

             </detail>

          </soap:Fault>

       </soap:Body>

    </soap:Envelope>

  • Thu, Mar 23 2017 7:11 PM In reply to

    Re: An unexpected error occurred checking in asset

    I should mention that when there is a SOAP syntax error soapUI comes back almost right away. But this message takes a while to come back, so that too in addition to the message makes me think the server accepts the request and my format is correct but something is going wrong while checking in.

  • Thu, Mar 23 2017 8:26 PM In reply to

    • Vadym
    • Not Ranked
    • Joined on Thu, Apr 17 2014
    • Posts 127
    • Points 1,600
    • Avid Developer Moderator
      Avid Employee

    Re: An unexpected error occurred checking in asset

    please share the aaf

    dragging an aaf to Inteprlay Access will create a binary database object. A white/any other non asset icon means that the file is stored as is and is not a valid asset.

    import AAF is a debug feature of Interplay Access and is not enabled by default

  • Thu, Mar 23 2017 8:34 PM In reply to

    Re: An unexpected error occurred checking in asset

    I had to rename it with .txt so you need to rename it to .aaf

  • Thu, Mar 23 2017 8:53 PM In reply to

    Re: An unexpected error occurred checking in asset

    1. What is the best way to look at the content of an aaf file to see what I am dealing with?

    2. Can I use AMT with a linux GNU C++ compiler?

  • Thu, Mar 23 2017 9:13 PM In reply to

    • Vadym
    • Not Ranked
    • Joined on Thu, Apr 17 2014
    • Posts 127
    • Points 1,600
    • Avid Developer Moderator
      Avid Employee

    Re: An unexpected error occurred checking in asset

    You can use the freely available AAF Toolkit to parse the contents of an AAF file. Please note that only AAF created by Avid tools are fully supported.

    AMT is shipped and tested only with some Visual Studio and Xcode versions. We recommend the compiler AMT is build with going forward. There are succesfull implementations with different compilers and languages that support C++ library imports.

    The earlier attached AAF imports successfully into our lab environment as TestSequence1 that references Heli_Cam masterclip.

    You can see the result of the MTOM request below.


  • Thu, Mar 23 2017 9:35 PM In reply to

    Re: An unexpected error occurred checking in asset

    really helpful, yes i can see that it works fine on your avid. I think that means I just need to figure out how to turn on imports as you suggested.

  • Thu, Mar 23 2017 9:36 PM In reply to

    Re: An unexpected error occurred checking in asset

    in your test there how did you know what cid to put. the Content ID listed below is a filename.

     

    Oh I see you can just look at the raw but mine still just says the filename

  • Thu, Mar 23 2017 9:49 PM In reply to

    • Vadym
    • Not Ranked
    • Joined on Thu, Apr 17 2014
    • Posts 127
    • Points 1,600
    • Avid Developer Moderator
      Avid Employee

    Re: An unexpected error occurred checking in asset

    CID in the message matches attachment Part number. CID in the attachment is the filename. If thats what you're asking.

    SoapUI will encode and inline the attachment automatically that is visiblein the Raw view

Page 1 of 1 (9 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller