ConvertPDF.exe flags

Hello,
Does anyone know what the flags/options are for the ConvertPDF.exe that shipped with Designer 7.0?
I see that in 7.1 the flags are explicit when you try to run it with no arguments, but in Designer 7.0 it says "for flags, see documentation"
Where is this documentation?
Thanks,
Evan

Hi Beast of Burden,
I have tested the reg flags in my Windows 7 32 bit Enterprise and it can run well .
Please note that the REG FLAGS can only be appiled to the "HKLM\Software"[\SubKey].Have you verified that the subkey existed in the 32 bit machine ?We can try the other subkey to have a check for example the "classes" subkey.
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
I understand about the HKLM\Software restriction and I have limited my testing to that key (and sub keys). As I said, when I enter a valid key it does nothing but show me the syntax screen.  Generally while I am testing I am using the REG FLAGS <key>
QUERY command. 
When I am on a machine where the command is working correctly, I will either see the flags for the eky specified or a message saying that the key was invalid (should I intensionally try a bad key).   On machines where it is
not working I always see the syntax screen regardless if the key existed or not. 
I am wondering if there is a patch or registry key that controls this behaviour.

Similar Messages

  • Reg.exe FLAGS command not working in 32bit environments

    I am trying to run the command REG FLAGS "hklm\Software\SomeKey" SET DONT_VIRTUALIZE and each time I run it on a 32bit version of windows 7 in our environment I get the help screen. Even if I put in a bad path instead of getting a message
    that the path was wrong I get the help screen.   When I run it on my computer (Windows 7 64bit) it works as expected.
    It does the same thing when I try REG FLAGS "hklm\Software\SomeKey" QUERY.  Its like the 32 bit version doesn't know what FLAGS is although it is present in the help screen.
    Ideas?  Suggestions?  Recipie ideas?

    Hi Beast of Burden,
    I have tested the reg flags in my Windows 7 32 bit Enterprise and it can run well .
    Please note that the REG FLAGS can only be appiled to the "HKLM\Software"[\SubKey].Have you verified that the subkey existed in the 32 bit machine ?We can try the other subkey to have a check for example the "classes" subkey.
    Best regards
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    I understand about the HKLM\Software restriction and I have limited my testing to that key (and sub keys). As I said, when I enter a valid key it does nothing but show me the syntax screen.  Generally while I am testing I am using the REG FLAGS <key>
    QUERY command. 
    When I am on a machine where the command is working correctly, I will either see the flags for the eky specified or a message saying that the key was invalid (should I intensionally try a bad key).   On machines where it is
    not working I always see the syntax screen regardless if the key existed or not. 
    I am wondering if there is a patch or registry key that controls this behaviour.

  • Open With my program doesn't work

    I have Java program which runs on PCs and saves files with a special extension. When I double click on a saved file, I would like it to open with my program. This worked before when my program was stored on the C drive. But now I store it more appropriately in the Program Files folder, and it does not work anymore.
    If I try to say Open With and browse to my program, it does not show up in the list, so I cannot choose it. Or if I go to Default Programs in the Start menu, click on Associate a file type or protocol with a specific program, select my extension, click on Change program, and browse to my program, again it does not show up in the list, so I still cannot choose it.
    I am using Windows Vista, and I am able to make associations with other programs, but not with my program.
    How can I make it work? Thanks for your time!

    Sorry to bother you with this. Yes, this was a Windows problem, not a Java problem.
    The solution was to use the Registry Editor. Just for the record, let me post my solution:
    For being able to open files with my extension, I had to create a registry in
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts,
    including the subkey of the program name in the subfolder OpenWithList
    and the subkey of the program id in the subfolder OpenWithProgIds.
    And for the program id I had to create another registry entry in HKEY_CLASSES_ROOT,
    including the subfolders Shell, Open, and Command, where I placed the
    subkey of the directory of my program.
    I did all this with my installation program Inno Setup (www.jrsoftware.org). Here is
    the code I created with Inno Setup for recognizing my ".ac" extension:
    [Registry]
    Root: HKCU; Subkey: "Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ac"; Flags: uninsdeletekeyifempty
    Root: HKCU; Subkey: "Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ac\OpenWithList"; Flags: uninsdeletekeyifempty
    Root: HKCU; Subkey: "Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ac\OpenWithList"; ValueType: string; ValueName: "a"; ValueData: "Ananya.exe"; Flags: uninsdeletekey
    Root: HKCU; Subkey: "Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ac\OpenWithProgIds"; Flags: uninsdeletekeyifempty
    Root: HKCU; Subkey: "Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ac\OpenWithProgIds"; ValueType: binary; ValueName: "AnanyaCurves"; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves"; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves"; ValueType: string; ValueData: "AnanyaCurves"; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves\Shell"; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves\Shell"; ValueType: string; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves\Shell\Open"; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves\Shell\Open"; ValueType: string; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves\Shell\Open\Command"; Flags: uninsdeletekey
    Root: HKCR; Subkey: "AnanyaCurves\Shell\Open\Command"; ValueType: string; ValueData: """C:\Program Files\AnanyaCurves\Ananya.exe""""%1"""; Flags: uninsdeletekey
    Now my program even shows up in the Recommended Programs!
    And, by the way, this only worked if I put my extension key in
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts.
    It did not work if I tried to put my extension key in HKEY_CLASSES_ROOT.

  • SQLDumper Error

    While troubleshooting another problem I discovered this error.
    Any thoughts on this?
    Thank you
    Fault bucket 90349650291, type 5
    Event Name: SQLException64
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: ReportingServicesService.exe
    P2: 2011.110.5058.0
    P3: 00000000537423EB
    P4: SQLDUMPER_UNKNOWN_MODULE.DLL
    P5: 0.0.0.0
    P6: 0000000000000000
    P7: 17068
    P8: FFFFFFFFC677081B
    P9: FFFFFFFFF6612D81
    P10:
    Attached files:
    C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0009.mdmp
    C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0009.log
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_ReportingService_47a692227a878eaa4b1f0793dd4e4fc6d5e4ee8_00000000_26fb9ce8
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 19601fe0-bea5-11e4-80da-005056af00c4
    Report Status: 0
    Hashed bucket: e989e80431dbd4f011e34543c9c3844d
    Contents of the mini dump -
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 4932
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000587E6448
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4932
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000587E6448
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (FA4:C9C) 09/18/14 15:55:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0001.mdmp
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (FA4:C9C) 09/18/14 15:56:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (FA4:C9C) 09/18/14 15:56:01, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (FA4:C9C) 09/18/14 15:56:01, ACTION, ReportingServicesService.exe, Created the report.
    (FA4:C9C) 09/18/14 15:56:01, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (FA4:C9C) 09/18/14 15:56:01, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (FA4:C9C) 09/18/14 15:56:01, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 9952
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000616A6448
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 9952
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000616A6448
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (1924:2510) 02/25/15 16:58:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0002.mdmp
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (1924:2510) 02/25/15 16:58:38, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (1924:2510) 02/25/15 16:58:38, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (1924:2510) 02/25/15 16:58:38, ACTION, ReportingServicesService.exe, Created the report.
    (1924:2510) 02/25/15 16:58:38, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (1924:2510) 02/25/15 16:58:38, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (1924:2510) 02/25/15 16:58:38, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 9952
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000616A6448
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 9952
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000616A6448
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2048:21F4) 02/25/15 17:16:12, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0003.mdmp
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2048:21F4) 02/25/15 17:16:16, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2048:21F4) 02/25/15 17:16:16, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (2048:21F4) 02/25/15 17:16:16, ACTION, ReportingServicesService.exe, Created the report.
    (2048:21F4) 02/25/15 17:16:16, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (2048:21F4) 02/25/15 17:16:16, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (2048:21F4) 02/25/15 17:16:16, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 1188
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000627A6448
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1188
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000627A6448
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (F28:F2C) 02/25/15 17:33:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0004.mdmp
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (F28:F2C) 02/25/15 17:33:04, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (F28:F2C) 02/25/15 17:33:04, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (F28:F2C) 02/25/15 17:33:04, ACTION, ReportingServicesService.exe, Created the report.
    (F28:F2C) 02/25/15 17:33:04, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (F28:F2C) 02/25/15 17:33:04, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (F28:F2C) 02/25/15 17:33:04, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 6340
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000627A6448
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6340
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000627A6448
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (20A4:2060) 02/26/15 11:56:25, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0005.mdmp
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (20A4:2060) 02/26/15 11:56:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (20A4:2060) 02/26/15 11:56:28, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (20A4:2060) 02/26/15 11:56:28, ACTION, ReportingServicesService.exe, Created the report.
    (20A4:2060) 02/26/15 11:56:28, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (20A4:2060) 02/26/15 11:56:28, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (20A4:2060) 02/26/15 11:56:28, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 6340
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000627A6448
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6340
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000627A6448
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (B10:FD4) 02/26/15 12:16:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0006.mdmp
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (B10:FD4) 02/26/15 12:16:54, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (B10:FD4) 02/26/15 12:16:54, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (B10:FD4) 02/26/15 12:16:54, ACTION, ReportingServicesService.exe, Created the report.
    (B10:FD4) 02/26/15 12:16:54, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (B10:FD4) 02/26/15 12:16:54, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (B10:FD4) 02/26/15 12:16:54, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 5000
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000627A6448
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 5000
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000627A6448
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (754:FC8) 02/26/15 12:32:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0007.mdmp
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (754:FC8) 02/26/15 12:32:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (754:FC8) 02/26/15 12:32:56, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (754:FC8) 02/26/15 12:32:56, ACTION, ReportingServicesService.exe, Created the report.
    (754:FC8) 02/26/15 12:32:56, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (754:FC8) 02/26/15 12:32:56, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (754:FC8) 02/26/15 12:32:56, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 1140
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 0000000068E36448
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1140
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0000000068E36448
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (91C:6E4) 02/26/15 15:09:14, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0008.mdmp
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (91C:6E4) 02/26/15 15:09:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (91C:6E4) 02/26/15 15:09:19, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (91C:6E4) 02/26/15 15:09:19, ACTION, ReportingServicesService.exe, Created the report.
    (91C:6E4) 02/26/15 15:09:19, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (91C:6E4) 02/26/15 15:09:19, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (91C:6E4) 02/26/15 15:09:19, ACTION, ReportingServicesService.exe, Submitted report asynchronously.
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 6888
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 00000000552D6448
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6888
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000552D6448
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (2AB0:29E8) 02/27/15 09:21:39, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\Logfiles\SQLDmpr0009.mdmp
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, ReportingServicesService.exe, Watson Invoke: Yes
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, ReportingServicesService.exe, Created the report.
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, ReportingServicesService.exe, WerReportAddFile Mini Dump succeeded.
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, ReportingServicesService.exe, WerReportAddFile Log Tail File succeeded.
    (2AB0:29E8) 02/27/15 09:21:44, ACTION, ReportingServicesService.exe, Submitted report asynchronously.

    The dump file is used for debugging the problem. If you open a bug at
    http://connect and include the log and dump, it is possible the issue would be understandable and the bug may get fixed in a future release. You can also supply the dump to Customer support, it will help them understand the issue too.
    Brad Syputa, Microsoft Power BI This posting is provided "AS IS" with no warranties.

  • 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

  • Fuzzy Lookup SQLDUMP when run in 32 bit

    I'm running a SSIS package on a 64 bit machine that has to run in 32 bit runtime as several data sources are from excel.
    After I've loaded the source data into SQLServer EE [64 bit] I run a fuzzy lookup to match & append some columns. The data flow runs fine independently when I set Run64BitRuntime to True but fails when I run the whole package in 32 bit.
    There are no telling error messages in BIDS and I enabled full logging to sysssislog. The data flow reads all of the oledb source records but the fuzzy lookup remains yellow before SQLDUMPER_ERRORLOG.log runs and the package fails.
    The Log reads:
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 1: 4772
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 2: 0
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 3: 0:0
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,  Parameter 4: 008CD608
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4772
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x008CD608
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\ErrorDumps\SQLDmpr0021.mdmp
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\dbghelp.dll'
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE'
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '2007.100:1600.22'
    (F7C:16C0) 07/21/10 11:24:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '10.0:1600.22'
    (F7C:16C0) 07/21/10 11:24:37, ACTION,          DtsDebugHost.exe, Watson Invoke: No
    Is there anyway fix the above error and to run my package with this fuzzy lookup within a 32 bit runtime on a 64 bit machine?
    Thanks in advance!

    Hi,
    It's easy to reproduce, this seems to be a problem with the x64 fuzzy lookup task:
    https://connect.microsoft.com/SQLServer/feedback/details/488387/fuzzy-lookup-triggers-sqldumper-even-with-very-small-dataset-with-run64bitruntime-set-to-false
    You can use a single package for your 32Bit dataflow. In your 64Bit package use the "Execute Process Task" to execute your 32Bit package with the dtexec.exe located in the folder "C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\".
    Under "Process" you can use following settings:
    Executable: C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
    Arguments: /F "COMPLETE PATH TO YOUR 32BIT PACKAGE"
    Tillmann

  • LMS 3.1 processes unable to start

    Hi!
    I have had LMS 3.1 installed for more than one year - and it has been working as expected.
    After a reboot of the server (Windows 2003 R2) the solution stops working.
    When browsing the syslog.log file i see messages like:
    Apr 20 08:28:28 127.0.0.1 100: <30>   dmgt[7668]: 3001(I):Using port: tcp/42340.
    Apr 20 08:28:28 127.0.0.1 100: <30>   dmgt[7668]: 3007(I):Started application(Tomcat) "SERVICE " pid=4612.
    Apr 20 08:28:34 127.0.0.1 100: <28>   dmgt[7668]: 2095(W):Internal Error: The daemon manager cannot run application TomcatMonitor.
    This message appears for each application that tries to start up. I'm enclosing a copy of the content in the syslog.log file.
    I have tried to install the sw on another server (new), and applying the license to this. The same errors occur here.
    Does anyone have a clue on what's going on here ?
    Thanks,
    Pål

    Filesize:
    C:\Documents and Settings\admin>dir "\Program Files\CSCOpx\lib\jre\bin\java.exe
    Volume in drive C has no label.
    Volume Serial Number is E0CE-F473
    Directory of C:\Program Files\CSCOpx\lib\jre\bin
    10.11.2006  13:28            49 248 java.exe
                   1 File(s)         49 248 bytes
                   0 Dir(s)  21 417 316 352 bytes free
    pdreg:
    C:\Documents and Settings\admin>pdreg -l NameServer
            Process      = NameServer
            Path         = C:\PROGRA~1\CSCOpx\lib\jre\bin\java.exe
            Flags        =  -classpath C:\PROGRA~1\CSCOpx,C:\PROGRA~1\CSCOpx\lib\cla
    sspath,C:\PROGRA~1\CSCOpx\www\classpath org.jacorb.naming.NameServer -DOAPort=42
    342
            Startup      = Started automatically at boot.
            Dependencies = Not applicable
    Files attached.

  • ALC-UTIL-001-001: Unexpected exception while resolving a new connection to an Adobe Service

    Hi,
    I am getting the following exception while invoking ConvertPdfService
    ERROR [STDERR] (ProcessResource@46e269ca(name=convertpdf.exe,pid=0) Error Reader) /e2/jboss-5.1.0/server/pdf/svcnative/ConvertPdfService/bin/convertpdf: error while loading shared libraries: libX11.so.6: wrong ELF class: ELFCLASS64
    WARN  [com.adobe.service.ProcessResource] (ProcessResource@46e269ca(name=convertpdf.exe,pid=0) Error Reader) ALC-BMC-001-024: Service ConvertPdfService: Process ProcessResource@46e269ca(name=convertpdf.exe,pid=0) terminated abnormally with error code {3}
    INFO  [com.adobe.service.ProcessResource] (http-0.0.0.0-8080-10) ALC-BMC-001-505: Service ConvertPdfService: Starting native process with command line "/e2/jboss-5.1.0/server/pdf/svcnative/ConvertPdfService/bin/convertpdf.exe" -MyPath /e2/jboss-5.1.0/server/pdf/svcnative/ConvertPdfService -IOR IOR:000000000000002249444C3A636F6D2F61646F62652F736572766963652F4D616E616765723A312E30000 000000000020000000000000104000102000000000D31302E37382E3135322E383500000DC8000000193732363 33332353935312F42522D32302F0100000000000000000000000000050000000000000008000000004A4143000 000000100000020000000000501000100000001000100010001010900000002050100010001010000000021000 0007000000000000000010000000000000024000000200000007E00000000000000010000000D31302E37382E3 135322E383500000DC900400000000000080606678102010101000000170401000806066781020101010000000 764656661756C7400000000000000000000000000000000000000002000000004000000000000001F000000040 0000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003   -AppServer jboss
    ERROR [com.adobe.util.ConnectionFactoryReflectionWrapper] (http-0.0.0.0-8080-10) ALC-UTIL-001-001: Unexpected exception while resolving a new connection to an Adobe Service
    java.lang.reflect.InvocationTargetException
    Thanks in Advance

    Hi,
    May be of use
    1. Open the visual admin at <installdrive>:\usr\sap\J2E\JC00\j2ee\admin\go.bat
    2. Login is Administrator + admin-password you defined during installation.
    3. Under the Server 0... node select Services->Deploy
    4. Select the "Application" radio button at the bottom.
    5. Check if there exists an application sap.com/tcwdtools
    And the following applications are running
    sap.com/tcwdcorecomp
    sap.com/tcwddispwda
    sap.com/tcwdtools.
    Last thing was their any errors in the installation.
    Regards
    Ayyapparaj

  • Cannot Connect to ANIserver

    Hi.
    I'm after a reboot on LMS 2.6 server, the CM home page started showing the following message: "Cannot connect to ANI Server since it is down". I followed the procedures as in the thread "Ciscoworks ANI server cannot connect, Joe Clark please help", but, in the end, after I restarted yhe Damon Manager, all seervices came up, except for the ANI database engine. After I started this serrvice manually, it came up, but the ANI.log file reappeared and the message on the CM home became "Please wait... ANIServer is still initializing."
    The result for the pdreg command is below:
    C:\>pdreg -l ANIDbEngine
            Process      = ANIDbEngine
            Path         = C:\PROGRA~1\CSCOpx\objects\db\win32\dbsrv9.exe
            Flags        =
            Startup      = Started automatically at boot.
            Dependencies = Not applicable
    The result for the pdshow command is attached.
    Hope Joe Clark or anyone can help me to.
    Thanks in advance.

    Before your last message, I've disabled all DFM polling and SNMP trap receiving. After that, the RME home started working normally and I was able to manage jobs once again. You were right, the server coudn't handle all the traps and the polling, but even after disabling those,  the CM home still shows the JRM down message. I tried stopping and restarting the JRM, like you suggested, but the problem persisted.
    The system is a Windows 2003 on a VMWare ESXi. The hardware is a dual Xeon with 4GB of dedicated RAM to the LMS server. I don't have the clock informations now, but I can provide it tomorrow.
    P.S.: Is there any clean way to prevent DFM from processing SNMP traps? For test purpooses, I changed the SNMP port, but it makes Windows to generate lots of ICMP port  unreachable packets and I don't intend to leave it this way.

  • JRM Service could be down. Check whether JRM services are running

    I keep seeing this message when ever I open RME
    LMS 2.6 on A Windows 2003 platform
    3.0.5 common services
    4.0.6 campus manager
    6.1.5 Ciscoview
    2.0.6 DFM
    2.6.0 IPM
    4.0.5 RME
    pdshow against CTMJrmServer - waiting to initialize, then it will become administratively shutdown
    JRM and the other dependencies are up and working
    Under CTMJrmServer.log - I keep seeing what looks like authentication errors
    Error in execPOST: Server returned HTTP response code: 403 for URL: http://localhost:1741/CSCOnm/servlet/com.cisco.nm.cmf.servlet.SecretManagerServlet?command=put&alias=admin&secret=R2Dc7YpBXJLzlQ%3D%3D
    1:11 GMT 2010 ],INFO ,[main],com.cisco.nm.rmeng.jrmwrapper.server.JobManagerExt,getJRM,217,Retrying 0
    [ Wed Jan 13  10:31:21 GMT 2010 ],FATAL,[main],com.cisco.nm.rmeng.jrmwrapper.server.JobManagerExt,getJRM,207,Error during authentication:5,null
    [ Wed Jan 13  10:31:21 GMT 2010 ],INFO ,[main],com.cisco.nm.rmeng.jrmwrapper.server.JobManagerExt,getJRM,217,Retrying 1
    [ Wed Jan 13  10:31:31 GMT 2010 ],FATAL,[main],com.cisco.nm.rmeng.jrmwrapper.server.JobManagerExt,getJRM,207,Error during authentication:5,null
    [ Wed Jan 13  10:31:31 GMT 2010 ],INFO ,[main],com.cisco.nm.rmeng.jrmwrapper.server.JobManagerExt,getJRM,217,Retrying 2
    [ Wed Jan 13  10:31:41 GMT 2010 ],FATAL,[main],com.cisco.nm.rmeng.jrmwrapper.server.JobManagerExt,getJRM,234,Unable to obtain session. Terminating
    [ Wed Jan 13  10:31:41 GMT 2010 ],ERROR,[main],com.cisco.nm.rmeng.jrmwrapper.server.CTMJobManagerServer,<init>,66,Null JRM. Exiting
    Any help with this would be very much appreciated
    Simon

    hostname - sm01ms002
    C:\\>pdreg -l CTMJrmServer
            Process      = CTMJrmServer
            Path         = d:\\PROGRA~1\\CSCOpx\\bin\\cwjava.exe
            Flags        = -cw d:\\PROGRA~1\\CSCOpx -cw:jre lib/jre -cp:p MDC/tomcat/webapps/rme/WEB-INF/classes,MDC/tomcat/webapps/rme/WEB-INF/lib/ctm.jar,MDC/tomcat\/webapps/rme/WEB-INF/lib/log4j.jar com.cisco.nm.rmeng.jrmwrapper.server.CTMJobManagerServer sm01ms002
            Startup      = Started automatically at boot.
            Dependencies = RMEDbMonitor jrm TomcatMonitor RMECSTMServer
    \f1 NMSROOT=d:/PROGRA~1/CSCOpx\
    PX_BINDIR=d:/PROGRA~1/CSCOpx/bin\
    PX_CGIDIR=d:/PROGRA~1/CSCOpx/cgi-bin\
    PX_LOGDIR=d:/PROGRA~1/CSCOpx/log\
    PX_TMPDIR=d:/PROGRA~1/CSCOpx/temp\
    PX_DATADIR=d:/PROGRA~1/CSCOpx/files\
    PX_DOCDIR=d:/PROGRA~1/CSCOpx/htdocs\
    PX_CLASSDIR=d:/PROGRA~1/CSCOpx/www/classpath\
    PX_CGIURL=/cgi-bin\
    PX_DOCURL=/\
    PX_CLASSURL=/CSCOnm/classpath\
    PX_SCLASSDIR=d:/PROGRA~1/CSCOpx/lib/classpath\
    PX_DATASTORE=DSN=rme\
    PX_CLASSPATH=d:/PROGRA~1/CSCOpx/lib/classpath;d:/PROGRA~1/CSCOpx/www/classpath;d:/PROGRA~1/CSCOpx/campus/www/classpath;d:/PROGRA~1/CSCOpx/campus/lib/classpath\
    PX_APPDIR=d:/PROGRA~1/CSCOpx/objects\
    PX_CONFDIR=d:/PROGRA~1/CSCOpx/conf\
    PX_CTRBDIR=d:/PROGRA~1/CSCOpx/contrib\
    PX_HLPDIR=d:/PROGRA~1/CSCOpx/help\
    PX_LIBDIR=d:/PROGRA~1/CSCOpx/lib\
    PX_USER=casuser\
    PX_GROUP=casusers\
    PX_STOP_DELAY=3000\
    PX_SYS_CHECK=1\
    PX_OSA_PORT=42342\
    OSAGENT_PORT=42342\
    PX_HOST=sm01ms002\
    PX_FQDN=sm01ms002\
    ASANY=d:/PROGRA~1/CSCOpx/objects/db\
    SQLANY=d:/PROGRA~1/CSCOpx/objects/db\
    CORE_SECURE_PORT=443\
    CORE_NONSECURE_PORT=1741\
    PX_PROTOCOL=http\
    PX_PORT=1741\
    PX_WEB_PORT=1741\
    MAX_RAM=2048\
    MAX_SWAP=4096\
    MAX_CPU=1600\
    PX_ANI_PORT=42344\
    SYS_NO_OF_CPUS=4\
    SYS_RAM=4094\
    SYS_CPU=2666\
    SYS_SWAP=4092\
    \f0\

  • Auth Failure Traps

    After i changed snmp strings on our network devices , I see a list of devices with Auth Failure Traps on Syslog server.
    Ive check the snmp credential strings on CW for each device and they're correct.
    This is the error message on my syslog server:
    mm-dd-yyyy    11:23:16    Local0.Info    10.1.1.1    10.1.1.2.150 4 0  Authentication failure 10.1.1.254(CiscoWorks) 1 10.1.1.254(CiscoWorks)
    This message wasnt there before i re-new the snmp community string. After I chnage the snmp string on my routers and switches, I a lots of traps on my syslog server.
    How can I stop this?
    Thank you for your help
    Thanks

    Hi Joe,
    The root cause of authentication failure messages was due to dfmserver. When I stop it, the message disappeared.
    Process:
    DfmServer
    Path:
    C:\PROGRA~1\CSCOpx\objects\smarts\bin\CS_sm_server.exe
    Flags:
    Startup:
    Started automatically at boot.
    Dependencies:
    DfmBroker
    Before applying the patch, when I shutdown dfmserver, I could still see the polling. After applying the patch, the polling stop.
    There are only 2 patches for DFM. I have also applied fix CSCta56151.
    Patches installed
    Patch Name
    Version
    Installed Date
    CSCtb87449-0
    0
    02 Mar 2010, 11:28:07 WST
    CSCta56151-0
    0
    04 Mar 2010, 14:18:46 WST
    Any more tips Joe?

  • Apache web server not start

    Hi. I had to reload my server with 2008 server R2 for a maintenance. but now apache web server on my LMS 4.0 no start. I tried stop and restart daemon manager but nothing. apache is stoped.

    Hi ,
    Try the below steps and see how it works :
    On the command Prompt run this commad to check the Dependency of the Apache :
    C:\PROGRA~2\CSCOpx\MDC\Apache\bin>pdreg -l Apache
             Process      = Apache
             Path         = C:\PROGRA~2\CSCOpx\MDC\Apache\bin\Apache.exe
             Flags        = -d C:\PROGRA~2\CSCOpx\MDC\Apache -D SSL
             Startup      = y
             Dependencies = Tomcat
    Now Unregister the Apache with below commad :
    pdreg -u Apache
    To Registered the Apache:
    Note :You need to check the Apache.exe location  ,so anyone of the below  will work for you  :
    C:\PROGRA~2\CSCOpx\MDC\Apache\bin>pdreg -r Apache -e "C:\PROGRA~2\CSCOpx\MDC\Apache\bin\Apache.exe" -f "-d C:\PROGRA~2\CSCOpx\MDC\Apache -D SSL" -d Tomcat
    (used your NMSROOT Location )
    C:\PROGRA~2\CSCOpx\MDC\Apache\bin>pdreg -r Apache -e "C:\PROGRA~2\CSCOpx\MDC\Apache\Apache.exe" -f "-d C:\PROGRA~2\CSCOpx\MDC\Apache -D SSL" -d Tomcat
    Now re-check the Apache Registration :
    C:\PROGRA~2\CSCOpx\MDC\Apache\bin>pdreg -l Apache
            Process      = Apache
            Path         = C:\PROGRA~2\CSCOpx\MDC\Apache\bin\Apache.exe
            Flags        = -d C:\PROGRA~2\CSCOpx\MDC\Apache -D SSL
            Startup      = y
            Dependencies = Tomcat
    Once above is done try to Restart the Apache and check how it works !!
    Thanks--
    Afroj

  • Firefox.exe suddenly only 2 KB (and IE 1 KB) & flagged up as malware

    On January 13 (2015), I was surprised to find my Kaspersky anti-virus software (Pure 3.0 at the time) flagging up the following as malware (trojan):
    firefox.exe C:\Program Files\Mozilla Firefox\firefox.exe HEUR:Trojan.WinLNK.StartPage.gena
    iexplore.exe C:\Program Files\Internet Explorer\iexplore.exe HEUR:Trojan.WinLNK.StartPage.gena
    eBay Sidebar for Firefox.lnk C:\Users\David\Desktop\eBay Sidebar for Firefox.lnk HEUR:Trojan.WinLNK.StartPage.gena
    I followed the instructions to quarantine and re-boot. No problem. After re-boot, I could not access Firefox and discovered that it had indeed been quarantined - along with IE (which I rarely use) and eBay Sidebar for Firefox (which I haven't used in a long time). On restoring these, they are again identified as malware. Further investigation revealed that firefox.exe was only 2 KB in size - and IE was only 1KB.
    Kaspersky advised to upgrade to Total Security, which I did and this stopped identifying the files as malware. Full virus checks, including from safe mode, revealed nothing. Running a suite of recommended anti-malware programs did pick up a limited number of bits and pieces (and which I deleted) that Kaspersky didn't, although my research on the net points to them all being the kind of things that produce unwanted adverts on browsers .... not anything that would wipe or rename programs (I didn't see any unwanted ads, though, possibly because of my settings in Firefox, Kaspersky and NoScript).
    Kaspersky feels firefox.exe was corrupted (well at 2 KB, it's certainly not right) - although what corrupted it is another question. All other files in \Mozilla Firefox seem to be there, and I have no issues with any other software or files on my PC (just these three). Yet the same thing happened to IE at the same time. That makes a failing hard drive very unlikely indeed - but it does make me suspicious that there was *something* that deliberately did this, which Kaspersky did not pick up. However it would be unusual for decent anti-virus software like Kaspersky to miss something. Further, the same issue should have been occurring widely around the same time, because if everyone around the world were losing their browsers it would have made the news - not to mention advertising malware that corrupts both browsers being rather self-defeating!!
    Incidentally, the desktop shortcuts have been replaced by the default Windows icon for programs that don't have a custom-made shortcut. And clicking on what was the Firefox shortcut opens a DOS box, that closes immediately; IE does the same but a "16 bit MS DOS Subsystem" error box appears (those were the days!) with:
    C:\Users\Public\Desktop\Internet Explorer.lnk
    The NTVDM CPU has encountered an illegal instruction.
    CS: 123f IP:012d OP: 8f af 9f 6e ba Choose 'Close' to terminate this application.
    [Clicking 'close' or 'ignore' both close the DOS box - and that's it. No virus or anything similar is picked up and four anti-malware programs I'm using now show my system to be clean]
    So my questions are:
    (1) Any thoughts as to what happened?
    (2) I need to get Firefox working again. Can I simply copy firefox.exe from another machine and replace the existing 2 KB firefox.exe, and everything should be fine, as it was before .... or is it not as simple as that?? (I understand Firefox keeps preferences, etc., in separate files).
    Thanks in advance for any comments.
    Dave

    Sorry you have had this problem
    It my be possible and work if you overwrite the problem ''firefox.exe''
    However that could cause problems and the usual solution would be to download and install Firefox again from an official site, and using a clean install involving deleting the existing program files. (CARE leave the Firefox profile folders and files alone. In fact it would be worthwhile, as a ''belts braces'' precaution; locating and backing them up first )
    * See [[Firefox keeps crashing at startup#w_try-a-clean-install]]'''_try-a-clean-install'''
    * [[Back up and restore information in Firefox profiles]]
    ** [[Profiles - Where Firefox stores your bookmarks, passwords and other user data#w_finding-your-profile-without-opening-firefox]]'''_finding-your-profile-without-opening-firefox'''
    As for what happened, you have given a well reasoned and intelligent summary but after the event it is going to be almost impossible to pin it down. Sometimes AV does flag false positives especially temporarily &/Or if not fully updated.
    ===Clean Reinstall ===
    Certain Firefox problems can be solved by performing a ''Clean reinstall''. This means you remove Firefox program files and then reinstall Firefox. Please follow these steps:
    '''Note:''' You might want to print these steps or view them in another browser.
    #Download the latest Desktop version of Firefox from [https://www.mozilla.org mozilla.org] (or choose the download for your operating system and language from [https://www.mozilla.org/firefox/all/ this page]) and save the setup file to your computer.
    #After the download finishes, close all Firefox windows (or open the Firefox menu [[Image:New Fx Menu]] and click the close button [[Image:Close 29]]).
    #Delete the Firefox installation folder, which is located in one of these locations, by default:
    #*'''Windows:'''
    #**C:\Program Files\Mozilla Firefox
    #**C:\Program Files (x86)\Mozilla Firefox
    #*'''Mac:''' Delete Firefox from the Applications folder.
    #*'''Linux:''' If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it - see [[Installing Firefox on Linux]]. If you downloaded and installed the binary package from the [http://www.mozilla.org/firefox#desktop Firefox download page], simply remove the folder ''firefox'' in your home directory.
    #Now, go ahead and reinstall Firefox:
    ##Double-click the downloaded installation file and go through the steps of the installation wizard.
    ##Once the wizard is finished, choose to directly open Firefox after clicking the Finish button.
    More information about reinstalling Firefox can be found [[Troubleshoot and diagnose Firefox problems#w_5-reinstall-firefox|here]].
    <b>WARNING:</b> Do not use a third party uninstaller as part of this process. Doing so could permanently delete your [[Profiles|Firefox profile]] data, including but not limited to, extensions, cache, cookies, bookmarks, personal settings and saved passwords. <u>These cannot be easily recovered unless they have been backed up to an external device!</u>

  • Command line render "-reuse" flag with multiple copies of afterFx.exe

    The question is, can i use "-reuse" flag to start rendering with more than one copy of afterFx.exe ?
    //OS Windows 7
    If i start
    aerender.exe -project c:\projects\project_1.aep
    I have to wait about 15 seconds until the After is started and only then start rendering.
    But I can start the After in advance.
    Start
    aerender.exe -project c:\projects\project_1.aep -reuse
    And then render will begin immediately.
    Unfortunately one copy of After effects does not use the power of my computer at 100%. // I need about 5 copies.
    So I tried:
    Execute in command promt:
    AfterFx.exe -m -noui
    AfterFx.exe -m -noui
    AfterFx.exe -m -noui
    Then execute:
    aerender.exe -project c:\projects\project_1.aep -reuse
    aerender.exe -project c:\projects\project_1.aep -reuse
    aerender.exe -project c:\projects\project_1.aep -reuse
    But only the first copy of AfterFx was used. The following two commands of aerender  have launched a new copies of AfterFx.
    Any ideas?
    P.S. I know about the "-mp" flag, it is not a solution.

    I know on the mac side you can send a system command to have "aerender" launch a render in Terminal. Same as Lloyd's BGRenderer script, without all the nice features of course. If you are rendering an image sequence, you can launch a render multiple times and it will begin to use more of the available resources, skipping frames already in process by the other processes. It will take a toll on your computer if you launch too many at once, but I've had at least three or four of these going for one render before.
    The system command is (OS X based):
    /Applications/Adobe\ After\ Effects\ CS6/aerender -project /Volumes/Projects/Lazarus/Project\ Files/AE_Projects/Shots/023_010A1/AE_Projects/023_010A1.aep -sound "on"
    BREAKDOWN
    Path to aerender (spaces are escaped with a backslash):
         /Applications/Adobe\ After\ Effects\ CS6/aerender
    Project flag and then path to aep file:
         -project /Desktop/myShotToRender.aep
    Sound flag to have it "ding" on completion:
         -sound "on"

  • Firefox.exe being flagged as a screen logger by Zemana

    Sometimes, Zemana antilogger flags firefox.exe has trying to capture my screen. I don't have any addons with this function. Have run full antivirus and spyware scan, all clear. I read another poster had his firewall alerting him to this same problem, and was told by the vendor that it was probably being flagged by extensions/addons when checking for updates. Could this be my problem?
    Thanks
    == This happened ==
    A few times a week

    Hello Mal.
    You may want to contact Zemana about this.

Maybe you are looking for

  • ESYU: R11.5.10/R12 - ROI를 이용하여 Receiving Transaction을 Correct 하는 방법1

    Purpose Oracle Inventory Management - Version: 11.5.10 to 12.0 11.5.10/11i.SCM_PF.J/11i.PRC_PF.J (and higher)에서 ROI가 지원하는 새로운 functionality를 알아본다. -. CORRECT to DELIVER to Inventory transactions ROI를 이용하여 Standard Purchase Order에 대한 Receiving Transac

  • ITunes shows error message, QuickTime doesn't respond! PLEASE HELP!

    My iTunes doesn't open anymore, it shows that error message (iTunes needs to close. Send error report... etc). I tried uninstalling it, installing gain from the iPod CD, from the website, and nothing works. On Apple's support site it said I needed to

  • Can website hyperlinks be converted to local links when creating a PDF?

    I'm using the Acrobat X trial version and need some help understanding its capabilities. I have a 600+ page document that resides on a Wiki web site. The Wiki is direct edited by numerous authors and it generates the html code. I have successfully us

  • Using DB_NK_CACHE_SIZE BUFFER

    Please, Below are steps I did in order to move the all_customer_photo table into the photos tablespace.the photos tablespace was created with a 16K block size 1. ALTER SYSTEM SET DB_16K_CACHE_SIZE=100MB SCOPE=SPFILE; 2. CREATE TABLESPACE PHOTOS DATAF

  • SRM Outline PO line not unique with ECC PO line

    Hi Experts, We are using SRM 7.01 Extended Classic scenario. We have requirement in BI reporting for Shopping Cart and Purchase Order Overview Report. There is 1 issue with Outline PO(PO created from external Requirement) in SRM. In SRM, it is create