Edit to tape - timecode mismatch between timeline & output tape (Digi Beta)

I'm trying to edit to tape (insert) a programme. The clock drops in on exactly the right frame but by the time I get to the end of part there's a 2 frame difference between my timeline TC and the master tape's TC. In other words my timeline ends at 11.30.00 but when I play back the recorded tape the same frame is now 11.30.02. Is there a) an explanation for this and b) a solution? I need frame accuracy as I'm exporting my audio to OMF for the dub. Any advice hugely appreciated. Thanks. J
Digi Beta - Uncompressed 8 Bit - PAL.
Dual 2.7 G5   Mac OS X (10.4)   Blackmagic HD Link
Dual 2.7 G5   Mac OS X (10.4)  

Jeremy,
Wish I could offer more help other than to say Blackmagic is usually pretty quick with a fix once they identify there is a problem. We're in Sydney, and had some problems with dropped frames a couple of years ago, and they did some very quick testing and realised that they hadn't tested there new drivers with Batch digitise - point is, they issued a fix (updated driver) extremely quickly.
Go through your supplier and see if you can get their ear, especially if you can identify the problem happening consistently.
Tim

Similar Messages

  • Can I output to Digi beta on 4 channels of audio discreet?

    Network requires program on digibeta with stereo on 1 and 2 / mono split track on 3 and 4. Will FCP allow me to do this in one pass?
    Normally I would have to print my stereo tracks with the video on one pass
    then go back and insert discreet tracks on 3 and 4 as a second pass.

    Hi. I had to learn how to do this under pressure recently. It wasn't as intuitive as I would have hoped, I haven't had the repetitions necessary to know it by heart, and I'm not near a system that is connected to a deck.
    What I do remember though is Command-Zero for current sequence settings, Audio Outputs tab, select four channel audio in the drop down menu. Make output channels 3 and 4 mono.
    It is important to remember that you are setting these output tracks for you current sequence only. If you want to make a reusable output setting go to Final Cut Pro > User Settings then the Audio Output tab.
    In your timeline right click on your audio tracks (different from output channels - very important distinction) and assign where the track will play out. Right click near the lock but not on it, on the left side.
    I went to Help>Final Cut Pro User Manual, then typed "edit to tape" and read everything. I learned a lot and avoided many, many traps. Probably saved me hours and hours of time in the long run.
    Best of luck.
    Tom

  • Digi beta PAL editing on i Mac

    Hi all. I am a film editor who has recently bought fcp and is eager to do my first professional job on it. An opportunity has arisen and I'm thinking of doing it at home on my imac (2.8 Intel Core Duo with 2Gb RAM). I'm unsure whether Pro Res 422 clips from the original Digibeta rushes will run smoothly on my machine. I am asking because I will be digitising the footage at an edit house and then bringing the files back home on a drive. so I need to know the maximum res my machine can cope with before digitising.

    You might get away with uncompressed 8 bit on a FireWire 800 external drive. Do a small test first.
    A few years ago I had to edit a long form project on a G4 from digi beta material. I captured through another companies machine with a Black Magic card to DV, retaining original timecode and edited at home.
    Obviously, this was only to edit. I then went back and batch captured the finished version at full res to do color grading and titles.

  • Output mismatch between BEx query output and WebI Report output

    Hi All,
    I have a BEx query in which there are only characteristics placed in rows.
    There are combinations of the values of the characteristics giving different records in the query output.
    Date is one of the characterisctics in the query output.
    There is an output mismatch between the query output and the WebI report output in the following case:
    When there are 'Not Assigned' or '#' or blank values, there are additional entries(rows) in the WebI report, giving repeating or wrong entries in the Date field. This is incorrect data.
    Is this because of the  'Not Assigned' or '#' or blank values of the Characteristics or is there any other reason?
    How do I fix this?
    Please helo me with this.
    Thanks and Regards,
    Srilakshmi B

    Hi Rajesh,
    I need to verify the WebI report output for records with # and 'Not assigned' values for the cHracteristics in the report.
    So I cannot check the WebI report by hiding the # or Not assigned values.
    The problem is that in the Query output the records are like these shown below:
    Char1                    CHar2                          CHar3                       Date field
    A                             B                                 C                                Date1
    #(Not assgined)      #(Not assgined)      #(Not assgined)             No value
    Where as the WebI report output is as below:
    Char1                    CHar2                          CHar3                       Date field
    A                             B                                 C                                Date1
    #(Not assgined)      #(Not assgined)      #(Not assgined)            Date1
    As shown here, there are wrong/repeating entries for the Date field in the WebI report output.
    Please check this and let me know what could be the issue and how do I fix it.
    Thanks and Regards,
    Srilakshmi B

  • I'm using a Canon HV20 video camera that uses digital tape. After importing to my Events Library in Final Cut X, there are some timecode breaks between clips resulting also in gaps between the clips. Is there a way to avoid this?

    I'm using a Canon HV20 video camera that uses digital tape. After importing to my Events Library in Final Cut X, there are some timecode breaks between clips resulting also in gaps between the clips. Is there a way to avoid this?

    Thanks Russ.  I'm a beginner but Lynda.com has a video on making an archive, so I'll follow her video to try this method.

  • Timeline output to external monitor

    Hi - I'd like to see the timeline output on an external monitor (TV set with composite in) while editing. I'm told the only way to do this is to purchase an input-output card and one of the most reasonably priced ones seems to be the Pinnacle Movie Box. Does anyone know if this compatible with Premiere Pro CS3? Will it do what I want it to? If not, what is the best solution?
    Thanks in advance...

    For the moment, neither SD nor HD, but just simple DV :) But I'd like to buy something that can handle HDV, as I'll be editing a project soon. The output need not be great - after all, it's going to an ordinary TV set, not a precision reference monitor. The purpose of this additional monitor is to screen unfinished portions of the film to other people. I might have people come in to give their comments during the editing, so it's useful to be able to output the timeline.
    Pinnacle lists four products on their site: Studio MovieBox Plus, Studio MovieBox Ultimate, Studio MovieBoard and Studio MovieBoard Ultimate. Do they all work? Which of them would you recommend? Or would you suggest someting else altogether?
    Thanks very much.

  • Fatal error C1900: Il mismatch between 'P1' version '20080116' and 'P2' version '20070207'

    Hi all,
    I have a Team Foundation Build Agent that has Visual Studio Team System 2008 Test Edition installed. One of the solutions that I compile with that Build Agent gives me the following errors:
      VCBUILD : fatal error C1047: The object or library file '.\bin\Release\main.obj' was created with an older compiler than other objects; rebuild old objects and libraries
      LINK : fatal error LNK1257: code generation failed
      VCBUILD : fatal error C1900: Il mismatch between 'P1' version '20080116' and 'P2' version '20070207'
      LINK : fatal error LNK1257: code generation failed
    I've searched online and found that other people have experienced the same problem:
    http://software.intel.com/en-us/forums/intel-c-compiler/topic/62516/
    http://nuicode.com/issues/266
    In the second posting one states "I had the same Error! After installing Service Pack1 for VS2008 it worked!". Thats great for him but I don't see any such update for the Test Edition of Visual Studio Team System 2008 - Test Edition.
    What can I do to get rid of that problem?
    Thanks!

    Hello ACKH
    I once handled a similar case in newsgroups. That case exhibit a almost same symptom. Please check out my summary below:
    Problem
    In that case, the customer has a DLL project that you had built on a machine where VS 2008 SP1 was installed. You then attempted to rebuild that project on a machine without SP1, and got a fatal compiler error C1900 “IL mismatch between ‘P1’ version ‘20080116’ and ‘P2’ version ‘20070207’”, and then LNK1257 “Code generation failed”. He found that rebuilding your static library alleviated the errors, but cannot accept this as a workaround because your clients will not have the ability to rebuild the libraries you distribute before they use them.
    Cause
    You had built the static library with the /GL (Whole Program Optimization) compiler switch, which requires Link Time Code Generation (/LTCG) when the static library is subsequently linked. These features require that all linked modules be built by the same version of the compiler. In fact, if precompiled headers are used, the same machine must build and link all the involved object code. Therefore, it is highly recommended that static libraries not be built with the /GL switch, since their intended use is quite frequently to support reuse by others.
    Solution
    You rebuilt the static library on your VS2008 SP1 machine without the /GL switch, and you no longer encounter this problem.
    Please let me know if this info is helpful to you or not.
    Regards,
    Jialiang Ge
    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact [email protected]
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

  • Mismatch between availability and marker

    I have run the following command:
    /repvfy -detail -fix -pwd password
    and am seeing a section called "Mismatch between availabiltiy and marker". What does this mean? I know there is a bug out from Note: 735957 against 10.2.04 and that patch 6951116 is available. I also know this bug is fixed in 10.2.0.5. But I don't know what exactly this section is telling me. Here is the output I am seeing:
    6. Mismatches between availability and marker
    TARGET_GUID TARGET_NAME TARGET_TYPE MARKER_AVAIL_STATUS MARKER_TIME CURRENT_STATUS START_TIME
    9CB8EE19415C3C6B55954BF3346C1106 ssan-Internal Concurrent Manager oracle_apps_icm 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:22
    1B21AAEF5AC63DD44FE339B7852EA1EE ssan-Report Server_ssan_devstar2 oracle_apps_reports 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:13
    F5EAD749526EC1116A70157771E3D011 ssan-Oracle Workflow Agent Listener oracle_apps_wfalsnr 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:29
    CD32714673BC508CDBF85BF191A5A1B7 ssan-Workflow Background Engine oracle_apps_wfbg 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:26
    FADA1D6BF4DFD0E8AA1739A6666BA210 SSAN oracle_database 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:40
    0BE2ACE2EDC7271744DA1A249E30C9A5 APPS_ssan oracle_listener 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:12
    89D241EEEF24821E30AD66741BC3D433 devstar2.rtd-denver.com oracle_listener 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:20
    F40BAF501645A5957A498E7A270AEA47 ssan-Apps Listener_ssan_devstar2 oracle_listener 6 09-JUN-2009 10:41:50 1 28-MAY-2009 14:25:28
    8 rows selected.

    Various provision like Freight, transport etc .
    these should go to separate GL accounts. if you give wrong account assignment value will be passed to GRIR. then difference will happen
    sunoj

  • Mismatch between the patch version

    Version 2.18, next step, next issue. Got through the 'Do Setup' step on "9-Apply DBA CUP and related patches" with a bug workaround that was provided. Now went to the next step of 'Do Execute' and it is failing with the message below. I've done some inital searching and haven't found an answer. There was one note on MOS about a very similar issue but it was resolved in 2.16. Posting here whild I spend more time researching and trying to figure out the reason. I also reviewed my notes from when I did this upgrade manually and these mereged patches were not applied in preinstall mode as the message is saying has to be done. Any help would be appreicated. Thanks!.
    patchit12.sh - is exiting with no actions. ie. Patch patchfile_ad17089s not applied.
    There is a mismatch between the patch version specified and the release
    version obtained from your Applications environment. In order to apply
    Release 12 patches to previous Applications versions, the patch must be
    applied in preinstall mode.This can be done by passing the appropriate
    value to the preinstall parameter of eof_patch12.sh.
    INFO: Not starting patch alert monitor, to start: Login Engineer, User Admin, Update Profile
    Version in scripts/COMMON
    # $Header: patchit12.sh 1.32 2009/09/15 16:00:00 vpickard $
    Edited by: user649511 on Mar 2, 2011 2:24 PM

    You can change following in patchit12.sh under ./eof/scripts/COMMON. Please change it back before executing any other steps.
    From
    Check_Release()
    #Check if the releasenr is OK
    if [ "${preinstall}" = "y" ];then
    RELEASE=12
    echo
    echo "patchit12.sh is installing: $patch in preinstall=y mode."
    else
    REL=`Get_Release`
    RELEASE=`echo $REL | awk '{print substr($1,1,2)}'`
    echo
    echo "Found release REL=$REL from fnd_product_groups."
    fi
    to
    Check_Release()
    #Check if the releasenr is OK
    if [ "${preinstall}" = "y" ];then
    RELEASE=12
    echo
    echo "patchit12.sh is installing: $patch in preinstall=y mode."
    else
    REL=`Get_Release`
    #RELEASE=`echo $REL | awk '{print substr($1,1,2)}'`
    RELEASE=12
    echo
    echo "Found release REL=$REL from fnd_product_groups."
    fi

  • SSIS 2008 package conversion to SSIS 2012 using SQL Data Tools generating warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWra

    I am seeing the following warning is a SSIS C# script and receive a SSIS abort when I attempt to run the package.
    The SSIS log indicates the package is failing at about this same step in the process.  
    I have also included the file SSQLDUMPER_ERRORLOG.log that SSIS generates when it aborts below.
    My SSIS package has been set to 64-bit and I only have 64-bit SQL Server 2012 installed on the box.
    I migrated the package using the latest version of Data Tools that came out around mid July 2014.
    I edited all connection manager strings to point to 64-bit SQL Server and I run using the following command
    I edited the run string to point to the new 64 bit DTExec and attempted to run.
    C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /Rep V /F PkgMigration.dtsx .........................
    A significant amount of work does occur as reflected by the log steps prior to DTEXEC aborting but the log does just quit in mid sentence so not sure if it might have actually got a bit further.
    Any help on understanding what is happening here would be most appreciated.
    Warning               1              There was a mismatch between the processor
    architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=11.0.0.0, Culture=Neutral, PublicKeyToken=89845dcd8080cc91", "x86". This mismatch may
    cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a
    processor architecture that matches the targeted processor architecture of your project.                C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets             
    1605       5                sc_5756696d96034309a51afe69fed2eb44
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 6100
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00A8B770
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6100
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00A8B770
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0007.mdmp
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1CBC:1808) 08/14/14 10:36:47, ACTION,                DTExec.exe, Watson Invoke: No
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 10124
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0012B770
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 10124
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0012B770
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0008.mdmp
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2724:2488) 08/14/14 10:43:09, ACTION,                DTExec.exe, Watson Invoke: No
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8716
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 0072B770
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8716
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0072B770
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0009.mdmp
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2240:89C) 08/14/14 10:51:56, ACTION,                DTExec.exe, Watson Invoke: No
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8856
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 009AB770
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8856
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x009AB770
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0010.mdmp
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (7B8:1E68) 08/14/14 11:01:36, ACTION,                DTExec.exe, Watson Invoke: No
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 1292
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00BFB770
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1292
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00BFB770
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0011.mdmp
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (229C:1CD8) 08/14/14 11:45:45, ACTION,                DTExec.exe, Watson Invoke: No
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 4220
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0019B770
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4220
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0019B770
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0012.mdmp
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2520:2624) 08/14/14 12:05:47, ACTION,                DTExec.exe, Watson Invoke: No
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 8408
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00000000003ECC18
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8408
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000003ECC18
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0001.mdmp
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1B5C:20C0) 08/18/14 14:21:50, ACTION,                DTExec.exe, Watson Invoke: No

    Hi GaryAMiller,
    It seesm this is a know ssue. Please take a look at the following simialr issue at Microsoft Connect site:
    MSB3270: Mismatch between the processor architecture:
    https://connect.microsoft.com/VisualStudio/feedback/details/804933/msb3270-mismatch-between-the-processor-architecture-fakes-framework
    If this issue still persists, I would suggest
    opening a case with Microsoft Customer Support Services (CSS)(http://support.microsoft.com), so that a dedicated Support Professional can assist you in a more efficient manner.
    If you have any feedback on our support, please click
    here.
    Elvis Long
    TechNet Community Support

  • PdfA1b -  Subject Mismatch between Document Info and XMP metadata

    As far as I can tell, when generating PdfA-1b files I am completely compliant with the spec. Yet when I try to preflight verify my output I get the following error: "Subject mismatch between Document Info and XMP metadata".
    Here is my Document Info:
       /Title (Title)
       /Author (Author)
       /Subject (Subject)
       /Keywords (Key Words)
       /Creator (Creator)
       /Producer (Producer)
       /CreationDate (D:00010101000000)
       /ModDate (D:00010101000000)
    Here is my XMP Stream:
        Key Words
        Producer
        Title
        Subject
            Author
        Creator
        0001-01-01T00:00:00.0011111
        0001-01-01T00:00:00.0022222
        1
        B
    Am I missing something?
        Subject
    vs
       /Subject (Subject)
    It seems like it should be fine.
    -Rick

    You have a disconnect with regard to how Document Info fields are to be mapped to XMP Dublin Core (dc) data fields:
    - Document Info Subject -> dc:description
    [nobody claims this is intuitive, but it is indeed specified reasonably well]]
    The following is not required in your case, but for your info I include it anyway:
    - Document Info Keywords -> dc:subject
    Your best source for this is the actual PDF/A-1 standard (ISO 19005-1, can be purchased form www.iso.org).
    A very good companion for such type of topics are the TechNotes from the PDF/A Competence Center (see www.pdfa.org), downloadable free of charge.
    HTH.
    Olaf Drümmer

  • Contrast mismatch between Organizer and Editor

    I can edit an image in Editor to where it looks great, to include the contrast, brightness, shadows, etc.  When I send it back to the Organizer, it look much too contrasty and dark.  When I use the same images in a slideshow originating in Organizer, they still look too contrasty.  Is there a way to correct this?  I'm using PSE 10 on a Windows 7 -64 bit machine. Thanks for any ideas.

    Thanks for your quick response.  I just checked out the settings in both the Editor and Organizer and they're both set on "let me decide".  I'm not sure what to do on that one.  I could go with optimizing the computer screen with sRGB, or the Adobe RGB for the printer, or no management, or decide on the fly.  If I go with the computer, I guess I'd have to change it when I print a photo out, and vice versa.  Have any suggestions for me? Thanks again. 
    New update.  I have a Dell color laser printer, and I just checked the manual.  It offers both sRGB and AdobeRGB.  My priority is really to have a good printout.   If I check sRGB I should be safe for either print or computer, but I'm wondering if I'd get as good a printout with sRGB as with AdobeRGB.  The easiest might be to see what the printer is curently set on, and then set PSE Organizer and Editor to match it.  I'll do that, and then see if that helps the mismatch between Organizer and Editor. 

  • HDV timeline output to DVCPRO master

    So I have an HDV project that I digitized via firewire and edited in HDV. I now have to make a DVCPRO master. I need to export a DVCPRO Quicktime to take to a dub house that is going to make my masters. I'm trying to figure out the best workflow to get the best quality.
    I've been dropping the HDV sequence into a DVCPRO sequence then rendering. The problem is when I do this, the HDV footage is wider than the canvas that is created by a sequence made with a DVCPRO easy setup. If I set the aspect ratio under the distort settings to 12 it seems to fit the video to the canvas size.
    Am I doing this right? Should I just set easy setup to DVCPRO, then create a new sequence and leave the default sequence settings? Also, I've been dragging my HDV sequence to the DVCPRO sequence. I read on another forum someone say they just changed the sequence setting of the HDV sequence then re-rendered that. Or is copying and pasting the timeline the way to go?
    Anyone who has done this successfully and would help me out, I would appreciate it.
    Thanks in advance,
    Keith
    Dual 2.0 G5   Mac OS X (10.4.3)   Final Cut 5 Decklink Extreme

    Still stuck on this attempt to record HDV from an HDV timeline. To Sharon...yes. Last thing I check is that Easy Setup has not reverted to 'custom' before Print to Video.
    Here are some more puzzling anomalies: The color bars and tone do get recorded on tape, but when the program material comes up, the tape actually stops. Toward the end of the clips (using 60 seconds of clips for this testing) the recorder will restart and capture the last 2 seconds of the clips. I think this happens after the timeline program in the computer has finished. I'm guessing there's a cache that's recording this last couple of seconds.
    I've trashed all FCP prefs, rebooted the computing machine, reset all deck settings, etc., but still failing to accomplish this simple task.
    A question for anyone: should my program material be able to pass through the deck to a monitor in HDV, as was always done when working in DV? Program video just doesn't seem to be getting to the deck.
    HOWEVER, a few days ago, I did record this timeline to tape. It recorded without audio, and attempting to re-record, in order to include audio, has led me down this sticky path.
    The original material was captured as HDV, and some simple editing done in the same format. So I believe the timeline has the correct sequence presets. Now just wanting to send that back out to an HDV tape again.
    Dale

  • There is a mismatch between order type and GL accountu201D.

    Hello
    Can any one help me to know why I am getting this error message.
    Here  I am giving the steps carried out.
    Step1. Using transaction code: FB60 I have posted a vendor invoice to a Machinery account GL account against a internal order.
    Step2. A down payment using transaction code FBA7. using a special indicator M to a bank account.
    Step3. When I am trying to clear the open item  (by selecting above both documents) for the vendor using transaction F-44 system is giving an error message u201CThere is a mismatch between order type and GL accountu201D. System is prompting to correct the down payment entry, where I dint use any Cost centre, internal order.
    Checked the Internal order profile, AUC settlement profile etc and no able to find an error message.
    Can any one explain me why this error is coming and what need to be check in order to rectify it.
    Regards
    RS.

    Hi It looks that the field status of the Order Type and GL Account field status is being mistmatching with each other. You can check the field status group given on GL Account and the fields status in Order Type.

  • Hi Folks,  I am using FCPX 10.0.8 on a MPB 10.8.2 with a multi in/out audio device RME Fireface 400.  I recorded a timecode track through in 11 and routed it to out 3.  Initially it worked, although it did also play timecode through the main outputs 1

    Hi Folks,
    I am using FCPX 10.0.8 on a MPB 10.8.2 with a multi in/out audio device RME Fireface 400.
    I recorded a timecode track through in 11 and routed it to out 3.
    Initially it worked, although it did also play timecode through the main outputs 1&2 !!!
    Now it has stopped playing TC through output 3.
    Is FCPX capable of working with professional audio?
    Regards
    Donagh Long.

    You welcome

Maybe you are looking for

  • Loading Flat File and Temporary Table question

    I am new to ODI. Is there a method to load a flat file directly in to the target table and not have ODI create a temporary file? I am asking this in trying to find out how efficient ODI is in bulk loading a very large set of data.

  • How do I re-arrange order of songs in a playlist in itunes 10.3.1?

    Just had a technician tune up my iMac yesterday and apparently he upgraded itunes to version 10.3.1. I just tried to re-arrange a playlist song order and I couldn't do it by trying to drag a song to a different order slot in the list. Can anyone expl

  • Change behaviour of Expand/collapse icon in JTree

    Want to change the behaviour of Expand/collapse icon in a JTree. Need help with the same. Thanks.

  • Dynamic customizng for ganttChart

    Hi all, we want create a dynamic customizng for gantt chart. For example we need to set the minimum and maximal value for time axis dynamicly. Does someone have expirience in these or exists a good guidline for dynamic programming with Web Dynpro ABA

  • -adobe-helvetica-medium-r-normal--*-100-*-*-*-*-iso8859-1

    Hi! I have the following installed font in the solaris environment and I want to use it in my Swing application. (1.4.2.) -adobe-helvetica-medium-r-normal---100----*-iso8859-1 I listed all available fonts from java, but I do not find the above one. D