NI instruments / Logic instruments and multi processor warning

I am running an instance of FM8 and Massive and the rest of my patches are exs and evp88 , on a macbook with 2gb ram , the memory is less than 50% and mainstage has been great up untill today when i got the "mainstage does not support multi processor 's" warning and then the second time this warning came up mainstage force quitted . Anyone experienced this yet ?

Ola Ramiro,
como estas?
I'm using Atmosphere on as a normal plug-in.
However, there have been some mates that post about here in the forum.
Try to shearch about it.
If I have any news, I'll keep you post.
adieus amigo,
Jorge

Similar Messages

  • Java multi-thread Applet and Multi-processor

    Hello,
    I have a JAVA applet which work fine on a mono-processeur machine and not fine at all on multi-processors.
    It use multi thread (for reading on socket) and some times, request are lost.
    Is that a matter of programming or a JVM bug ?
    This happens on Linux and Windows NT bi-processors.
    We hare using JAVA 1.3.0_02
    Thanks for your help
    [email protected]

    I have already have a look to javax.swing.SwingUtilities.invokeLater() but (I think) it don't work for my need.
    A graphic applet which create 2 threads : one for reading and one for writing on a socket.
    Request sent to the server are memorized in a vector, and once answer is received, the request is remove from vector and treated. Access to the list is protected by synchronize.
    Everything works fine one several plateforme (linux, windows 98/2000/NT, Solaris). The only problem is on multi-processor : request are lost !

  • Java and Multi-Processor Systems

    [This may be the wrong form, please point me to the correct one if I should redirect this!]
    Is it possible to use Java in a multiprocessing environment where Java can take advantage of the multiple processors? Naturally Threads are the obvious parallel mechanism, but I suspect there are others.
    Motivation: Basically we are trying to build an inexpensive system to do scientific and mathematical computing where the runs can take hours or days on traditional uniprocessor systems. Presumably a multiprocessor system would be the first stop, although Grid computing may be as effective.
    So any pointers for doing cpu intensive programming with Java would be appreciated!

    You need to have atleast one active thread per CPU.The domain I am looking at is "Agent Based Modeling" (ABM). In that sphere, each agent is fairly independent of all the others, making decisions based on "local knowledge". Our current simulation uses 35,000 agents.
    You may find that different architecture may limit
    the number of processors you can effectively exploit
    but you should be able to use2-4 CPUs without
    signifciant trouble.I'm not clear on how I can ask Java to use the multiprocessors I may have in my system. Do I simply assign a thread to each agent? That would be quite easy to do.
    So I think the question here is: Does Java assign threads to multiprocessors? Does it need a special compile/run flag to do so? Do I need to include special Java code to somehow promote this behavior?
    If the processing is really CPU intensive the best
    option may be to find the bottlenecks with a profiler
    and write them in C. You should be able to get a
    significant speed up this way with minimal
    conversion.That may be necessary, but in the ABM space, people are leaving C for Java due to its being fast enough and the networking support, memory management, etc just too nice to pass up!
    To use multiple threads you need to be able to
    exploit a natural parrellism in the work you are
    doing. If the task is genuinely single threaded you
    wil only every be able to use one CPU.This should be easy, see above .. due to each agent being reasonably independent.
    Thanks for the thoughtful response!

  • Oracle and multi processor

    Hi,
    Does Oracle databases manage automatically multiprocessors? If not what are the parameters to modify?
    what are the functionalities of databases which take into account multiprocessors (queries, backup/recover, etc...) and is it automatically activated?
    If not could you please give me a summary on how activating it (or a path to a document)?
    Thanks in advance.
    Fred

    Yes. No need to modify parameters.
    But what you should do is recollect system statistics
    Go to www.morganslibrary.org/library.html
    and look up system statistics

  • Multi-threads will run better on multi-Processores environment?

    Are there any proof to say that Multi-threads will run better on multi-Processores environment?
    Will Java run better on multi-Processores environment? Are there any proof?
    Thank in advance

    Are there any proof?The proof is in the pudding, so to speak. The best thing to do is to benchmark your application on single and multi-processor machines.
    It should be noted that there are reports of threading problems with Java on multi-processor machines. I haven't seen the problems myself, nor do I remember the exact problems people were seeing (and on what OS/Hardware) but if you search these forums you should be able to find out the details.

  • Kontakt 3 as a Multi-midi instrument? How? Multi-outputs?

    I am having trouble getting Kontakt to work properly as a mutlii-output instrument with multi-midi inputs.
    There are instructions in the manual and online but I seem to have some problems.
    I create an Instrument track of Kontakt 3. I select 16 stereo output mode.
    I open Kontakt 3 and create new mixer tracks to match the 16 stereo.
    Problem 1: I cannot rename these new tracks.
    Problem 2: I cannot assign outputs that seem correct. I look at config. on the mixer channel and I get "unassigned" or "plug-in output 9, 10..."
    I go to the Logic Mixer and hit the + on the Konotakt Instrument Track and create new AUX tracks alongside the Instrument Track but this does not seem to help.
    I really can't figure how to make the midi multi instrument in Logic such that I can send different midi channels to multiple instruments in Kontakt 3.
    I create a multi instrument in Environment but where to I drag that cable to connect?
    Sorry I am so lagging in understanding this but if there are some thngs I am missing please help.
    Yes I can get a Koontakt 3 Instrument track to work and sound a single instrument but I need the multi midi and multi output option to work.
    Thanks,
    Dean

    Beatfarm wrote:
    I setup my Kontakt 3 Multiple Output Instrument in Logic Pro 8 including the Logic Aux Channels.
    This way is not so good,,, (sorry don't get me wrong )
    ... I just talking about my personal experience with Logic Pro
    I Never use Multi outs workflow in my songs
    the Multi outs strategy comes from other DAWs (expacially related with ProTools) that have hystorical limited nunbers of track in the Mixer. (or you must pay a lot of "bucks" to have 200 stereo tracks in Protools)
    In Logic you have over than 500 straight tracks/Audio and instruments + 64 and maybe more Aux Busses...
    As you can see the buss are limited related to the number of track
    My personal advice is: use buss only for reverbs, Delays, and Multi grupoed tracks... and instead to use aux for multiouts instrument use single instances...
    *about Kontkt 3 and Logic Pro there are 2 different additional working strategies*
    1) using single instances (this don't ask for more CPU power resource) but the Audio Units version of NI instruments are not so stable when used as multi instances...
    SO: Export as Audio the allready completed orchestral parts.
    Using Audio track in Logic is always a good idea because Logic Pro have 255 *Stereo Audio tracks*
    2) using Kontakt 3 as Standalone allow you to use more Ram (logic stops to work with more than 2.7GB physically adressed
    SO: you can use IacBus to route Midi signal direct to Kontakt 3
    All of the sudden I'm not able to freeze my Kontakt Multi Instrument anymore (the other tracks still show the freeze function).
    The "freeze" works only on the tracks (obviously, Freeze cannot and "will never" works on AUX/BUS) this is one of the majior reasons that makes me able to suggest you to avoid Multi Outs Instruments strategy
    What can I do to get around this problem? Please help me out!
    I can only add that is not a good idea to use Logic in the same way as Protools or Cubase
    Logic Pro is different
    you need to adapt your working in progress strategy to achieve the best result
    you have more than 500 Audio and instrument tracks...
    I suggest to use it...
    I'm sure that you never will be able to use all 500 tracks in une song... BUT LOGIC can DO THAT!!!
    I suggest to stay focused to the Logic Mixer: it is a great pieace of software thecnology... it is a REAL hardware mixer that has been ported inside the best professional Audio software...
    Logic Pro is very near to a REAL HARDWARE RECORDING STUDIO Mixing consolle ENVIRONMENT! (including Cables, Inserts and AUX capabilities)
    *about 600 Stereo Audio Channels and Aux/buss are ready to be used in Logic PRO to realize your songs!*
    if you need more than 600 stereo tracks... feel free to ask me... I will try to find a way to solve your issue
    hope this helps
    Thanks
    G

  • Why do Logic instruments 'go to sleep'?

    If I make a project with lots of software instruments, and play one live via a USB keyboard or pad after it's been dormant for a while, the first note I hit will not sound right away. Instead there is a gap of maybe 50ms, then it clicks in with a faint digital pop. This is extrememly annoying as I use Logic live onstage.
    It's as if Logic decides to re-allocate that chunk of memory to other sounds. Programming in a 'mute' MIDI note or controller event on that instrument's track does not 'wake up' the instrument either. The only way to wake it up is to activate a hardware controller--so I have gotten in the habit of pressing my sustain pedal right before I go to play a part. But sometimes I forget, and my first note or chord is messed up; and it sounds like I made a mistake!
    Any clues, good Forum folks?
    (I'm using a Logic 9 on a MacBook Pro 2.3 with 4mb memory. Previously I had a pre-Intel G5 and had the same problem.)
    Thomas Dolby

    From the manual:
    Understanding Live Mode
    Live mode instruments need to stay in Live mode while the audio engine is running (when Logic Pro is in playback or record mode), because switching a software instrument track out of Live mode creates a gap (or noise) in the audio stream. Obviously, this is unacceptable.
    Software instruments that are live (ready for playing) require considerably more processing power than those that are merely playing back existing regions. If selecting a software instrument track automatically activates Live mode, switching between multiple instrument tracks would compound the problem, possibly resulting in system overloads.
    The Record button of selected software instrument tracks gives visual feedback of the current state of a software instrument:
    Switching Instruments to Software Instrument Live Mode
    When you select a software instrument track, it does not immediately switch into Live or Performance mode. You must send a MIDI event before Live mode is activated, but this takes around 100 milliseconds to engage, which is more than enough time to destroy the timing of your first played note.
    If you require perfect timing for the first played note, you need to send silent MIDI events in advance; press the sustain pedal, or make a small move of the pitch bender or modulation wheel, for example. This will turn on Live mode.

  • Cap locks key only for logic instruments?

    Had the misfortune of getting my upgrade to Logic 9 and having to take my synth in for servicing in the same week. So I have to use the Cap Lock's keyboard to play the instruments until I get my synth back. I have a curious problem though. The cap lock's keyboard will play logic instruments but not Zebra 2 or Battery 3. Is this normal?

    Maybe you need to change Octave by pressing the numeric keys on your mac keyboard(2) (changes will displayed >(1) below)
    A

  • Changing Logic instrument library path

    I changed the path of the instrument library in garagebamd recently to my external HDD. That works great! now how can i get logic to recognize this path so that i may use garagebands instrument library in addition to logics just as it would be if they were installed on the same disk?

    You said you are using the instrument insert menu, and then you ask where is it?
    Presumably, if you have to ask, you don't know where it is, and thus are likely to be not using it.
    I really recommend starting with at least the Getting Started menu, which explains what and where these things are with screenshots in a far better way than can be typed out in a forum post.
    In short, you need to have a software instrument track selected, and click-holding on the input slot (directly above the output slot) to get the instruments menu. This is different to the insert FX menu, which will only list the FX plugins you have installed (ie, not any instruments).

  • Lost all Instrument Plug-ins and Samples

    I recently Downloaded a free plugin from Native instruments website and after doing so I Lost all of my Instrument plug-ins and drum samples. I removed the native download but I still have not been able to recover my existing Logic instruments, I'm running Logic 9 any ideas?

    Presets: Save them in CS3, copy the files to CS5.
    Do NOT copy all the Adobe plugins from CS3, or you're in for a world of pain.
    Just copy the third party plugins, or better yet, reinstall them for CS5.

  • Using hyperdraw for automation of Logic instruments

    I'm pretty new to Logic and I have not figured one thing out even after browsing through these forums.
    I like the drawing mode that hyperdraw offers for automation of synth parameters and such much more than the regular automation drawing.
    Hyperdraw seems more like when drawing automation in Reason which I like very much.
    If possible at all, how can I locate and draw automation for all the buttons and sliders on the Logic instruments (and VSTs also for that matter) in hyperdraw style?
    Thanks

    Well, the Hyper Editor is really a MIDI editor, so you can create and edit MIDI data, including Control Change messages (like CC07 for volume or CC01 for modulation for example) - so it is like automation in that respect.
    As far as I can see, using track automation is the best option because all the available parameters are there ready to automate as soon as you insert the plug in - perhaps I'm missing the point of what you want to do.

  • Multi processor Solaris 2.6 and mutex locks

    hi,
    is anyone aware of any documented issues with Solaris 2.6 running
    on dual-SPARC processors (multi-processor environment) where the
    programs using "mutex locks" (multi-threaded applications), require
    some special handling, in terms of compiling and linking, to some
    special libraries.
    as far as i remember, in some OS book, maybe Peterson's, it was said
    that the mechanism for implementing mutex-locks on multi-processor
    systems is to use low-level spin-locks. this brings down performance
    on a single-processor system, making the processor doing busy-wait,
    but this happens to be the only way of mutex-locking in a multi-processor
    system. if this is so, then where is such behaviour documented in case
    of Solaris 2.6.
    i have had problems with my applications crashing (rathing hanging up)
    in a vfork() on such a system, but same application works fine, with
    100% reproducability, on a single-processor system.
    thanks for any inputs or suggestions and/or information.
    regards,
    banibrata dutta

    I am also facing similar problem. Application which written using Mulit-Threaded using Posix Mutexes. When i run on SINGLE processor manchine, i.e.
    SunOS sund4 5.7 Generic_106541-11 sun4u sparc SUNW,Ultra-5_10
    It works perfectly.
    But when try to run on dual processor machine, i.e.
    SunOS sund2 5.7 Generic_106541-11 sun4u sparc SUNW,Ultra-250
    It is blocking in the one of mutexes.
    Please inform us what is problem. Mr. B. Datta, you comes to know
    any channel, please inform me also at [email protected]
    Thanx & regards,
    -venkat

  • 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

  • IDVD 7.1.2: I am making music instrument instructional DVDs, and I want to include several audio loops in that the viewer access from the main menu to play along with

    iDVD 7.1.2: I am making music instrument instructional DVDs, and I want to include several audio loops that the viewer access from the main menu to play along with

    Export the slideshow out of iMovie via the File  ➙  Share ➙ File menu option as a 480p Quicktime movie.
    Open iDVD, select a theme and drag the exported QT movie file into the open iDVD window being careful to avoid any drop zones.
    Follow this workflow to help assure the best quality video DVD:
    Once you have the project as you want it save it as a disk image via the File ➙ Save as Disk Image  menu option. This will separate the encoding process from the burn process. 
    To check the encoding mount the disk image, launch DVD Player and play it.  If it plays OK with DVD Player the encoding is good.
    Then burn to disk with Disk Utility or Toast at the slowest speed available (2x-4x) to assure the best burn quality.  Always use top quality media:  Verbatim, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
    OT

  • Any news on new presets for Logics instruments?

    I had heard that the relatively limited presets on all of Logics instruments were going
    to be expanded upon. Is there any info on whether this has materialized or not. If
    the new EXS instruments are cool that would be great but I sure would like to see more
    presets on the other ones.
    So far I am looking forward to getting my copy. I also wonder if installing on the same machine will remove 7.2 or will it be added to rather than over it?.

    First of all, there are many new presets in most of the synths. The LP7 presets are often now found in a presets folder called "Legacy Presets" or something similar.
    I did find a site with some cool Guitar Amp Pro presets. The site also has synth presets, midi drum files, etc. They're not free, but a lot of the GAP presets do sound good. I have no affiliation with the company making them.
    http://www.macsongtools.com/MacSongTools/Tone%20Heaven%20Vol%201.html

Maybe you are looking for

  • Since upgrading to Lion I can no longer print to my network printer.

    I get the error message "/usr/libexec/cups/filter/rastertospl" via http://localhost:631/printers/Samsung - it's a Samsung ML-1510 laser. Printing works fine from a Windows machine - the printer is attached to a network router, and I connect via WiFi

  • Is this a bug in Swing?

    If anyone could provide help on this ASAP it would be greatly appreciated. I was hoping to use my Swing application in an experiment on Tuesday morning, but I seem to have run into a bug in Swing. I'm hoping I have made a mistake or there is some wor

  • Backed-up Mac Files turn into EXE

    Help please! I am have such a bad time of it here. So many archived files created on my Mac once copied onto my HD (or even showing up in their storage, i.e., old ZIP, or even new LaCie drives) have changed to EXE icons. Can't open them, can't go int

  • Memory leak puzzle

    Hello guys, I'm having a very, very difficult time debugging this memory leak on my server. I'm pretty sure it's related to berkeley DB XML, bu I just couldn't prove this in numbers. My server: Debian GNU/Linux 2.4.27-2-386 #1 Wed Aug 17 09:33:35 UTC

  • ADF BC App tomcat 5.5 Runtime error

    I have a ADF BC webapp that I am trying to deploy to tomcat 5.5, however I get the following runtime error: java.lang.NullPointerException      oracle.adf.model.BindingRequestHandler.endRequest(BindingRequestHandler.java:226) oracle.adf.model.servlet