Topic
15 replies Latest Post - ‏2011-09-21T15:42:46Z by SystemAdmin
ns_gds
ns_gds
6 Posts
ACCEPTED ANSWER

Pinned topic Purify: The application was unable to start correctly

‏2011-04-01T15:29:44Z |
Hi,

after successfully instrumenting on of our applications for error and leak data I get the following error as Purify is trying to start the application:

The application was unable to start correctly (0xc0000142). Click OK to close the application.


Is there anything I can do to get it working?

Here comes some additional information..

The full output that Purify gives in the Data Browser.

[I] Starting Purify
'd c:\<Path>\Application.exe at 01.04.2011 17:03:18 Version 7.0.1.0 build 11103 Windows 6.1 7600  Multiprocessor Free Instrumented executable: C:\Program Files\IBM\RationalPurifyPlus\PurifyPlus\cache\Application$<PathEncoded>.exe Working directory:       c:\<Path> Command line arguments:  <none> Process ID:              0x11e4 Thread ID: 0x1318 [I] Program terminated at 01.04.2011 17:07:39


The output of the instrumenting:

Purify 

for Windows, (C) Copyright IBM Corporation. 1992, 2009. All Rights Reserved. Version 7.0.1.0; Build: 11103; WinNT 6.1 7600  Multiprocessor Free Instrumenting: Application.exe  1672704 bytes NTDLL.DLL    1289536 bytes ADVAPI32.DLL 640000 bytes ADVAPI32.DLL 640000 bytes APPDLL1.DLL 1646080 bytes APPDLL3.DLL 869376 bytes   Purify: While processing file c:\<Path>\APPDLL3.DLL: Note: Instrumentation repeating with 1 additional entry point. 3GTTMONITORS.DLL 953344 bytes MFC90.DLL    3765064 bytes MSVCR90.DLL  653136 bytes   Purify: While processing file C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\MSVCR90.DLL: Note: Instrumentation repeating with 24 additional entry points. KERNEL32.DLL 857088 bytes USER32.DLL   811520 bytes USER32.DLL   811520 bytes GDI32.DLL    304640 bytes GDI32.DLL    304640 bytes COMDLG32.DLL 486912 bytes COMDLG32.DLL 486912 bytes SHELL32.DLL  12867584 bytes COMCTL32.DLL 1680896 bytes COMCTL32.DLL 1680896 bytes OLE32.DLL    1413632 bytes WSOCK32.DLL  15360 bytes MSVCRT.DLL   690688 bytes   Purify: While processing file C:\Windows\system32\MSVCRT.DLL: Note: Instrumentation repeating with 7 additional entry points. KERNELBASE.DLL 288256 bytes KERNELBASE.DLL 288256 bytes API-MS-WIN-SERVICE-CORE-L1-1-0.DLL 2560 bytes API-MS-WIN-SERVICE-CORE-L1-1-0.DLL 2560 bytes API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL 3584 bytes API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL 3584 bytes API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL 2560 bytes API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL 2560 bytes API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL 2560 bytes API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL 2560 bytes API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-NAMEDPIPE-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-NAMEDPIPE-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-PROCESSTHREADS-L1-1-0.DLL 4608 bytes API-MS-WIN-CORE-PROCESSTHREADS-L1-1-0.DLL 4608 bytes API-MS-WIN-SECURITY-BASE-L1-1-0.DLL 6144 bytes API-MS-WIN-SECURITY-BASE-L1-1-0.DLL 6144 bytes RPCRT4.DLL   652288 bytes RPCRT4.DLL   652288 bytes PCWUM.DLL    33280 bytes PCWUM.DLL    33280 bytes CRYPTSP.DLL  78848 bytes CRYPTSP.DLL  78848 bytes VERSION.DLL  21504 bytes SETUPAPI.DLL 1668608 bytes SETUPAPI.DLL 1668608 bytes OLEAUT32.DLL 571904 bytes MSVCP90.DLL  569680 bytes WS2_32.DLL   206336 bytes WS2_32.DLL   206336 bytes SHLWAPI.DLL  350208 bytes SHLWAPI.DLL  350208 bytes MSIMG32.DLL  4608 bytes API-MS-WIN-CORE-RTLSUPPORT-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-RTLSUPPORT-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-HEAP-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-HEAP-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-MEMORY-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-MEMORY-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-HANDLE-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-HANDLE-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-SYNCH-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-SYNCH-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-FILE-L1-1-0.DLL 5120 bytes API-MS-WIN-CORE-FILE-L1-1-0.DLL 5120 bytes API-MS-WIN-CORE-IO-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-IO-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-THREADPOOL-L1-1-0.DLL 4608 bytes API-MS-WIN-CORE-THREADPOOL-L1-1-0.DLL 4608 bytes API-MS-WIN-CORE-LIBRARYLOADER-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-LIBRARYLOADER-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-MISC-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-MISC-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL 4096 bytes API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-STRING-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-STRING-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-DEBUG-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-DEBUG-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-ERRORHANDLING-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-ERRORHANDLING-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-FIBERS-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-FIBERS-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-UTIL-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-UTIL-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-PROFILE-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-PROFILE-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-XSTATE-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-XSTATE-L1-1-0.DLL 3584 bytes LPK.DLL      26624 bytes LPK.DLL      26624 bytes API-MS-WIN-CORE-INTERLOCKED-L1-1-0.DLL 3584 bytes API-MS-WIN-CORE-INTERLOCKED-L1-1-0.DLL 3584 bytes SHUNIMPL.DLL 10240 bytes MSWSOCK.DLL  232448 bytes API-MS-WIN-CORE-CONSOLE-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-CONSOLE-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-DATETIME-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-DATETIME-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL 3072 bytes API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL 3072 bytes CFGMGR32.DLL 145920 bytes CFGMGR32.DLL 145920 bytes DEVOBJ.DLL   64512 bytes DEVOBJ.DLL   64512 bytes DEVRTL.DLL   44544 bytes DEVRTL.DLL   44544 bytes NSI.DLL      8704 bytes NSI.DLL      8704 bytes WINMM.DLL    194048 bytes WINMM.DLL    194048 bytes MPR.DLL      64000 bytes MPR.DLL      64000 bytes USP10.DLL    627200 bytes USP10.DLL    627200 bytes


Here are the contents of EngineCmdLine.log:

File: c:\<Path>\Application.exe Time: Freitag, 1. April 2011 16:57:48 Command: 
"C:\Program Files\IBM\RationalPurifyPlus\PurifyPlus\purifye.exe" -purify -purify_home=
"C:\Program Files\IBM\RationalPurifyPlus\PurifyPlus" /pwq-instance=0 /CacheDir=
"c:\<Path>\cache" /Replace=no /SaveData=Purify.pfy /SaveMergeData=Purify.cfy /SourcePath=
"<PathsDelimitedBySemiColons>" -user32_base=2007040000 -first-search-dir= C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd; C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb; C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4974_none_4bf89ae8bf9a48c0; C:\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_581cd2bf5825dde9; c:\<Path> -out=c:\<Path>\cache\Application$<PathEncoded>.exe -exe_ini_filename=c:\<Path>\Application_pure.ini c:\<Path>\Application.exe


The application ini file Application_pure.ini contents:

[Purify] option -working-directory=
"c:\<Path>" option -command-line-args=
"-config=\"Settings.xml\" -user=advanced" option -service-thread-leakscan-interval=1 option -inuse-at-exit option -handles-in-use-at-exit option -trap-umc option -purify-app-precise-files=
"c:\<Path>\APPDLL1.dll;c:\<Path>\Application.exe" option -purify-app-exclude-files=
"c:\windows\system32\shell32.dll;c:\windows\system32\mswsock.dll" option -use-quick-when-over-size-limit option -purify-user-precise-list=
"c:\<Path>\APPDLL1.dll;c:\<Path>\Application.exe" option -purify-user-exclude-list=
"c:\windows\system32\shell32.dll;c:\windows\system32\mswsock.dll" option -dynamic-module-list=
" c:\windows\system32\api-ms-win-core-console-l1-1-0.dll; c:\windows\system32\api-ms-win-core-fibers-l1-1-0.dll; c:\windows\system32\api-ms-win-core-localization-l1-1-0.dll; c:\windows\system32\api-ms-win-core-threadpool-l1-1-0.dll; c:\windows\system32\api-ms-win-security-base-l1-1-0.dll; c:\windows\system32\api-ms-win-service-core-l1-1-0.dll; c:\windows\system32\api-ms-win-service-winsvc-l1-1-0.dll; c:\windows\system32\api-ms-win-service-management-l1-1-0.dll; c:\windows\system32\nsi.dll; c:\windows\system32\advapi32.dll; c:\windows\system32\api-ms-win-service-management-l2-1-0.dll; c:\windows\system32\user32.dll; c:\windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\msvcp90.dll; c:\<Path>\APPDLL3.dll; c:\<Path>\APPDLL2.dll; c:\windows\system32\api-ms-win-core-sysinfo-l1-1-0.dll; c:\windows\system32\shell32.dll; c:\windows\system32\devobj.dll; c:\windows\system32\api-ms-win-core-synch-l1-1-0.dll; c:\windows\system32\api-ms-win-core-string-l1-1-0.dll; c:\windows\system32\api-ms-win-core-profile-l1-1-0.dll; c:\windows\system32\api-ms-win-core-processthreads-l1-1-0.dll; c:\windows\system32\api-ms-win-core-processenvironment-l1-1-0.dll; c:\windows\system32\api-ms-win-core-misc-l1-1-0.dll; c:\windows\system32\api-ms-win-core-namedpipe-l1-1-0.dll; c:\windows\system32\api-ms-win-core-localregistry-l1-1-0.dll; c:\windows\system32\api-ms-win-core-memory-l1-1-0.dll; c:\windows\system32\api-ms-win-core-libraryloader-l1-1-0.dll; c:\windows\system32\api-ms-win-core-heap-l1-1-0.dll; c:\windows\system32\api-ms-win-core-io-l1-1-0.dll; c:\windows\system32\api-ms-win-core-interlocked-l1-1-0.dll; c:\windows\system32\api-ms-win-core-handle-l1-1-0.dll; c:\windows\system32\kernelbase.dll; c:\windows\system32\api-ms-win-core-file-l1-1-0.dll; c:\windows\system32\api-ms-win-core-util-l1-1-0.dll; c:\<Path>\APPDLL1.dll; c:\windows\system32\api-ms-win-core-errorhandling-l1-1-0.dll; c:\windows\system32\api-ms-win-core-delayload-l1-1-0.dll; c:\windows\system32\api-ms-win-core-debug-l1-1-0.dll; c:\windows\system32\api-ms-win-core-datetime-l1-1-0.dll; c:\windows\system32\lpk.dll; c:\windows\system32\ws2_32.dll; c:\windows\system32\version.dll; c:\windows\system32\msimg32.dll; c:\windows\system32\wsock32.dll; c:\windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\msvcr90.dll; c:\windows\system32\cfgmgr32.dll; c:\windows\system32\shlwapi.dll; c:\windows\system32\comdlg32.dll; c:\windows\system32\usp10.dll; c:\windows\system32\msvcrt.dll; c:\windows\system32\setupapi.dll; c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd\comctl32.dll; c:\windows\system32\gdi32.dll; c:\windows\system32\rpcrt4.dll; c:\windows\system32\kernel32.dll; c:\windows\system32\ntdll.dll; c:\windows\system32\oleaut32.dll; c:\windows\system32\ole32.dll; c:\windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4974_none_4bf89ae8bf9a48c0\mfc90.dll
" option -pause-console-at-exit


If there is anything else I can provide please let me know. I tried setting the instrumentation level of the application executable and dlls to 'minimal' but that did also have no effect.

The application is built using visual studio 2008, it is a c++ (unmanaged) MFC application that consists of an executable and 3 dlls. I did apply the build and linker options that are recommended by Purify (at least as far as I know them).

Any help is appreciated!

ns_gds
Updated on 2011-09-21T15:42:46Z at 2011-09-21T15:42:46Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    2948 Posts
    ACCEPTED ANSWER

    Re: Purify: The application was unable to start correctly

    ‏2011-04-04T18:14:57Z  in response to ns_gds
    When I've seen this problem in the past, it usually stemmed from some sort of incompatibility or apparent corruption in the Purified binaries. Flushing the Purify cache folder usually solved it. Sometimes a reboot was also necessary.
  • ns_gds
    ns_gds
    6 Posts
    ACCEPTED ANSWER

    Re: Purify: The application was unable to start correctly

    ‏2011-04-05T11:51:43Z  in response to ns_gds
    Hi,

    thanks for your reply but emptying the cache didn't help.
    I tried running it under the debugger directly but there is not much output other than that the dlls are loaded and some message caused by side-by-side configuration (which is mentioned here http://www-01.ibm.com/support/docview.wss?uid=swg21129338 as being no problem).

    Is there anything else I can try? Can I, for example, try to only instrument one of my DLLs and leave the others untouched (if so, how would that work?).

    Thanks.

    Regards,
    ns_gds
    • SystemAdmin
      SystemAdmin
      2948 Posts
      ACCEPTED ANSWER

      Re: Purify: The application was unable to start correctly

      ‏2011-04-05T13:44:50Z  in response to ns_gds
      I see those "invalid sub-instance " messages as well, and they don't seem to indicate any problem.

      The only other thought is to perform a complete rebuild on all of your binaries. That's also something that's cleared up that issue for me.
      • ns_gds
        ns_gds
        6 Posts
        ACCEPTED ANSWER

        Re: Purify: The application was unable to start correctly

        ‏2011-04-06T14:39:42Z  in response to SystemAdmin
        Ok, of course I tried rebuilding the application already, did not help.

        Do you know of a way to completely exclude some binaries from instrumentation maybe this will allow me to pinpoint the error?
        • SystemAdmin
          SystemAdmin
          2948 Posts
          ACCEPTED ANSWER

          Re: Purify: The application was unable to start correctly

          ‏2011-04-06T18:15:02Z  in response to ns_gds
          Make sure you perform(ed) a FULL rebuild - "nmake clean", followed by nmake (or whatever your build environment requires.) This will delete all current binaries and rebuild them.

          The last file instrumented might give you some indication as to where the issue originates, but I don't know how definitive that is.

          My *-pure.ini file for my app has several exclude options that contain an extra file that is specific to our app, as below. I'm not sure exactly what these do, or how they got added. Purify support may have had me add those manually.

          option -purify-app-exclude-files="c:\windows\system32\mswsock.dll;c:\windows\system32\shell32.dll;<path>\logmsg.dll"
          ....

          option -purify-user-exclude-list="c:\windows\system32\mswsock.dll;c:\windows\system32\shell32.dll;<path>\logmsg.dll"
          I don't know what impact Selective Instrumentation might have, but if you are using that , you might try disabling it.

          Other than that, you may have to open a support incident.
          • ns_gds
            ns_gds
            6 Posts
            ACCEPTED ANSWER

            Re: Purify: The application was unable to start correctly

            ‏2011-04-11T14:56:14Z  in response to SystemAdmin
            I build the application in Visual Studio so a 'Clean'-Solution and 'Build'-Solution did do a full rebuild. But it did not help.

            What do you mean with last instrumented file? In the log file that is some windows library file or something..

            I tried running purify from commandline and excluded all files that are directly created by me, which did not have any effect, but I think if you tell purify to instrumend some executable and also state on the same line that this executable is not to be instrumented than this is ignored. Because the file size of my executable changes everytime. I also tried to execlude, literally all files instrumented (incl. windows files) but this results in Purify crashing with a C++ runtime environment error (the provided file list with paths was pretty long though).

            Another thing I wanted to test was just instrumenting one of my DLLs, but this fails with:
            
            Purify: While processing file C:\Windows\WinSxS \x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4974_none_4bf89ae8bf9a48c0\MFC90.DLL: Error: Couldn
            't open MSVCR90.dll. Possible cause is missing embedded or external manifest in  C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.4974_none_4bf89ae8bf9a48c0 \MFC90.DLL System error code: The system cannot find the file specified.
            


            Any other hints? ;-)
            • SystemAdmin
              SystemAdmin
              2948 Posts
              ACCEPTED ANSWER

              Re: Purify: The application was unable to start correctly

              ‏2011-04-11T17:19:30Z  in response to ns_gds
              I just realized you were running the 7.01 GA release. You might try a newer build - I found 11103 unusable in our environment, including one app that reported 142 error.

              If the manifest problems continue after the upgrade, you could try copying that manifest file into the cache folder. I had to do that with the 7.0 release, but I don't think I've had to with 7.01.

              Or you could try support.
  • valgrindwasheaven
    valgrindwasheaven
    6 Posts
    ACCEPTED ANSWER

    Re: Purify: The application was unable to start correctly

    ‏2011-09-17T11:20:21Z  in response to ns_gds
    I'm also facing the same problem. I have tried after deleting the cache files but no use. I'm trying to purify java.exe and it fails with a dialog box
    java$Purify_C_Windows_system32.EXE - Application Error
    X The application was unable to start correctlly (0xc000142). Click OK to close the application.

    Below is the console output during instrumentation.

    C:\Users\kjayapra>Purify java
    Purify for Windows,
    (C) Copyright IBM Corporation. 1992, 2006. All Rights Reserved.
    Version 7.0.0.0; Build: 6274;
    WinNT 6.1 7600 Multiprocessor Free
    Instrumenting:
    java.EXE 145184 bytes
    NTDLL.DLL 1293120 bytes
    ADVAPI32.DLL 640000 bytes
    ADVAPI32.DLL 640000 bytes
    KERNEL32.DLL 1048576 bytes
    MSVCRT.DLL 690688 bytes

    Purify: While processing file C:\Windows\system32\MSVCRT.DLL:
    Note: Instrumentation repeating with 7 additional entry points.
    KERNELBASE.DLL 272384 bytes
    KERNELBASE.DLL 272384 bytes
    API-MS-WIN-SERVICE-CORE-L1-1-0.DLL 2560 bytes
    API-MS-WIN-SERVICE-CORE-L1-1-0.DLL 2560 bytes
    API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL 3584 bytes
    API-MS-WIN-SERVICE-WINSVC-L1-1-0.DLL 3584 bytes
    API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL 2560 bytes
    API-MS-WIN-SERVICE-MANAGEMENT-L1-1-0.DLL 2560 bytes
    API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL 2560 bytes
    API-MS-WIN-SERVICE-MANAGEMENT-L2-1-0.DLL 2560 bytes
    API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-NAMEDPIPE-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-NAMEDPIPE-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-PROCESSTHREADS-L1-1-0.DLL 4608 bytes
    API-MS-WIN-CORE-PROCESSTHREADS-L1-1-0.DLL 4608 bytes
    API-MS-WIN-SECURITY-BASE-L1-1-0.DLL 6144 bytes
    API-MS-WIN-SECURITY-BASE-L1-1-0.DLL 6144 bytes
    RPCRT4.DLL 662528 bytes
    RPCRT4.DLL 662528 bytes
    PCWUM.DLL 33280 bytes
    PCWUM.DLL 33280 bytes
    CRYPTSP.DLL 78848 bytes
    CRYPTSP.DLL 78848 bytes
    API-MS-WIN-CORE-RTLSUPPORT-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-RTLSUPPORT-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-HEAP-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-HEAP-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-MEMORY-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-MEMORY-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-HANDLE-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-HANDLE-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-SYNCH-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-SYNCH-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-FILE-L1-1-0.DLL 5120 bytes
    API-MS-WIN-CORE-FILE-L1-1-0.DLL 5120 bytes
    API-MS-WIN-CORE-IO-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-IO-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-THREADPOOL-L1-1-0.DLL 4608 bytes
    API-MS-WIN-CORE-THREADPOOL-L1-1-0.DLL 4608 bytes
    API-MS-WIN-CORE-LIBRARYLOADER-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-LIBRARYLOADER-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-MISC-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-MISC-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-SYSINFO-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-LOCALIZATION-L1-1-0.DLL 4096 bytes
    API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-STRING-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-STRING-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-DEBUG-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-DEBUG-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-ERRORHANDLING-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-ERRORHANDLING-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-FIBERS-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-FIBERS-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-UTIL-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-UTIL-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-PROFILE-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-PROFILE-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-XSTATE-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-XSTATE-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-CONSOLE-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-CONSOLE-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-DATETIME-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-DATETIME-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-INTERLOCKED-L1-1-0.DLL 3584 bytes
    API-MS-WIN-CORE-INTERLOCKED-L1-1-0.DLL 3584 bytes
    SSPICLI.DLL 96768 bytes
    SSPICLI.DLL 96768 bytes
    API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL 3072 bytes
    API-MS-WIN-CORE-DELAYLOAD-L1-1-0.DLL 3072 bytes
    CRYPTBASE.DLL 36864 bytes
    CRYPTBASE.DLL 36864 bytes
    API-MS-WIN-SECURITY-LSALOOKUP-L1-1-0.DLL 3584 bytes
    API-MS-WIN-SECURITY-LSALOOKUP-L1-1-0.DLL 3584 bytes

    Please help before I shoot myself.
    • valgrindwasheaven
      valgrindwasheaven
      6 Posts
      ACCEPTED ANSWER

      Re: Purify: The application was unable to start correctly

      ‏2011-09-17T11:23:23Z  in response to valgrindwasheaven
      I downloaded “IBM Rational PurifyPlus Windows 7.0 eAssembly” from https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?lang=en_US&source=RATL-RATIONAL

      on my Windows 7 64 bit system. (I'm purifying 32 bit applications).
      Version of Purify is 7.0.0.0 Build: 6274
      • SystemAdmin
        SystemAdmin
        2948 Posts
        ACCEPTED ANSWER

        Re: Purify: The application was unable to start correctly

        ‏2011-09-17T16:07:20Z  in response to valgrindwasheaven
        The first version of PurifyPlus to support 32-bit Windows 7 is version 7.0.1 iFix 001
        (Build 11785). The version of PurifyPlus that you are using dates back to 2006 and
        has never been verified on Windows 7. Entitled users can download PurifyPlus 7.0.1
        iFix 001 here:

        https://www-304.ibm.com/support/entdocview.wss?uid=swg24027911

        Regards,
        Don
        • valgrindwasheaven
          valgrindwasheaven
          6 Posts
          ACCEPTED ANSWER

          Re: Purify: The application was unable to start correctly

          ‏2011-09-17T16:27:15Z  in response to SystemAdmin
          I have a license. What is an entitlement?
          • SystemAdmin
            SystemAdmin
            2948 Posts
            ACCEPTED ANSWER

            Re: Purify: The application was unable to start correctly

            ‏2011-09-17T18:36:16Z  in response to valgrindwasheaven
            >
            > I have a license. What is an entitlement?
            >

            When you first bought PurifyPlus, you bought a license which allows you to
            use that copy of PurifyPlus for as long as you can. (For example, let's
            suppose you purchased PurifyPlus 7.0.0.0 back in 2006. You can continue to
            use that version of PurifyPlus on the OS's and compilers that were supported
            back in 2006.)

            Entitlement means that you're paying an annual support/maintenance contract
            which entitles you to Tech Support via phone and email, and access to all
            upgrades and patches. (In order to use PurifyPlus on Windows 7, for example,
            you would have to upgrade from PurifyPlus 7.0.0.0 to the latest release.)

            Regards,
            Don
  • JerryCallen
    JerryCallen
    9 Posts
    ACCEPTED ANSWER

    Re: Purify: The application was unable to start correctly

    ‏2011-09-20T16:47:54Z  in response to ns_gds
    Have you tried disabling incremental linking? This one one of the obstacles I had when trying to use Quantify on a C++ executable...
  • valgrindwasheaven
    valgrindwasheaven
    6 Posts
    ACCEPTED ANSWER

    Re: Purify: The application was unable to start correctly

    ‏2011-09-21T08:01:29Z  in response to ns_gds
    My employer does have an entitlement, they downloaded the fixpack and gave it to me. I followed the install steps mentioned in
    http://public.dhe.ibm.com/software/rationalsdp/v7/purifyplus/70101/docs/pplus-ifix-release-notes.html
    • Select the Repositories entry and the "Add Repository..." button.
    I unzipped the patch and configured added the repository.config file as a IBM installation manager’s repository.

    • Select Update to update Purify or PurifyPlus 7.0.1.0, and it will update your installation.

    But when I click on “Update”, there are no packages listed there to update. I'm attaching the screenshot of this window.
    Please assist.
    • SystemAdmin
      SystemAdmin
      2948 Posts
      ACCEPTED ANSWER

      Re: Purify: The application was unable to start correctly

      ‏2011-09-21T15:42:46Z  in response to valgrindwasheaven
      The UPDATE option should only be used if you've got Purify 7.0.1 installed
      previously. The update option does not work if you currently have an older
      version of PurifyPlus like 7.0.0.0. Those older versions didn't use the
      Installation Manager for updates and so forth. So, the key is to install
      the 7.0.1 version before attempting to install iFix 001. As an entitled
      user, you can download PurifyPlus 7.0.1 from your Passport Advantage account:

      https://www-304.ibm.com/support/docview.wss?rs=993&uid=swg24024963
      http://www-01.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

      Regards,
      Don