"Not applicable (list geometry)" in a Bex Condition

Hi All:
I have defined a condition in a query in Bex.
Basically I have formula that calculates the difference between two key figures.
The condition is very simple: When this difference is positive (> 0), then the record should be listed.
I execute the query. When I try to navigate through the result set, the condition is no active anymore and I receive the message "Not applicable (list geometry)".
What can I check?
Thanks.

Hi Raj,
Please check the characteristic assignment in the condition. I think individual characteristics are assigned. If you select all characteristics in the drilldown independently then it will work.
Regards
Yasemin...

Similar Messages

  • Pricing: New condition type not getting listed in options in product master

    Hi,
    I have created a new pricing procedure and also created a new condition type for it. I am trying to create a condition record in the product master for this  condition type but the condition is not there in the list of conditions. How can I inlcude it in the condition list?
    Even the new condition type I have created by copying 0PR0 is not getting listed in the options, whereas 0PR0 is getting listed.
    Regards,
    Meenakshi
    Edited by: Meenakshi Sawhney on Sep 9, 2010 8:27 AM
    Edited by: Meenakshi Sawhney on Sep 9, 2010 8:29 AM

    Hi Meenakshi,
    you need to enhance the condition maintenance group in the customizing, which is assigned to the product master. Please check: IMG: Customer Relationship Management -> Master Data -> Products -> Special Settings for Sales Operations -> Assign Condition Group to Application CRM and IMG: Customer Relationship Management -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Maintenance Group.
    Best Regards,
    Michael

  • Download for Lightroom 5 listed as "not applicable"

    When trying to download Lightroom 5 upgrade - after receiving confirmation email from Adobe - there is a message that reads "not applicable" where the Download button should be.

    Hi ezrocker,
    Please try to download Lightroom from the mentioned link: http://prodesigntools.com/lightroom-5-ddl-comparison-vs-lr4.html .
    Regards,
    Romit Sinha

  • HELP! InDesign CC got an error: The property is not applicable in the current state." number 30615

    HELP! Was working perfectly now it is giving me this error and doesn't seem to be going past the printing option. Code is below.
    main.scpt
    set posixIdPath to "/Applications/Adobe InDesign CC/Adobe InDesign CC.app"
    do shell script "/Users/cdapice/Desktop/cryptoquip/getquip.sh"
    delay 8
    tell application posixIdPath
    activate
    end tell
    delay 8
    set scripttoRun to ":Users:cdapice:Desktop:cryptoquip:Script.jsx" as alias
    tell application "Adobe InDesign CC"
    do script scripttoRun language javascript
    end tell
    delay 5
    Adobe InDesign CC got an error: The property is not applicable in the current state." number 30615
    Script.jsx
    var myDocument = app.open(File("/Users/cdapice/Desktop/cryptoquip/NewCryptoquip.indt"), true);
    //var myDocument = app.activeDocument;
    var myPage = myDocument.pages.item(0);
    var myTextFrame = myPage.textFrames.add();
    //Place a text file in the text frame.
    //Parameters for TextFrame.place():
    //File as File object,
    //[ShowingOptions as Boolean = False]
    //You'll have to fill in your own file path.
    myTextFrame.place(File("/Users/cdapice/Desktop/cryptoquip/quips.txt"));
    //var myTextFrame = app.selection[0];
    myTextFrame.parentStory.pointSize = 10;
    var brkStory = myTextFrame.parentStory.contents;
    var myPIs = myDocument.pageItems;
    var  destTextFrame = myPIs[6];
    destTextFrame.parentStory.contents = brkStory;
    firstChange();
    myTextFrame.remove();
    app.select(destTextFrame);
    splitStory();
    for (i = 0; i < myPIs.length; i++) {
              if (myPIs[i].appliedObjectStyle.name == "puzzleBox") {
                        var newBoxStyle = myPIs[i].appliedObjectStyle;
                        secondChange(myPIs[i]);
            myPIs[i].applyObjectStyle(newBoxStyle,true);
        if(myPIs[i].appliedObjectStyle.name == "otherBox"){
            var newBoxStyle = myPIs[i].appliedObjectStyle;
            myPIs[i].applyObjectStyle(newBoxStyle,true);
    Date.prototype.getMonthFormatted = function() {
        var month = this.getMonth() + 1;
        var formMonth = month < 10 ? '0' + month : month; // ('' + month) for string result
              return formMonth.toString();
    Date.prototype.getDayFormatted = function() {
        var day = this.getDate();
        var formDay = day < 10 ? '0' + day : day; // ('' + day) for string result
              return formDay.toString();
    var newdate = new Date();
    var laterdate = new Date();
    var dayofweek = newdate.getDay();
    var offsetdays = 0;
    switch(dayofweek) {
        case 2:
            offsetdays = 6;
            break;
        case 3:
            offsetdays = 5;
            break;
        case 4:
            offsetdays = 4;
            break;
        case 5:
            offsetdays = 3;
            break;
    app.epsExportPreferences.appliedFlattenerPreset.convertAllStrokesToOutlines = true;
    app.epsExportPreferences.appliedFlattenerPreset.convertAllTextToOutlines = true;
    app.epsExportPreferences.appliedFlattenerPreset.rasterVectorBalance = 100;
    //app.activeDocument.exportFile(ExportFormat.epsType, newFile, false);
    for (i = 1; i < 7; i++) {
        var curPage = i + "";
        var x = i + (offsetdays - 1);
        laterdate.setMonth(newdate.getMonth());
        laterdate.setDate(newdate.getDate());
        //alert(newdate);
        //alert(x);
        //alert(laterdate);
        laterdate.setDate(newdate.getDate() + x);
        //alert(laterdate);
        var nameDate = laterdate.getMonthFormatted() + laterdate.getDayFormatted() + ".eps"
        //alert(nameDate);
        app.epsExportPreferences.pageRange = curPage;
        var curFile = new File("/Users/cdapice/Desktop/cryptoquip/" + nameDate);
        app.activeDocument.exportFile(ExportFormat.epsType, curFile, false);
    var endDate = laterdate.getMonthFormatted() + laterdate.getDayFormatted();
    var firstDate = new Date();
    firstDate.setDate(newdate.getDate() + offsetdays);
    var startDate = firstDate.getMonthFormatted() + firstDate.getDayFormatted();
    var idFile = "cryptoquip_" + startDate + "_" + endDate + ".indd";
    app.activeDocument.save(new File("/Users/cdapice/Desktop/cryptoquip/" + idFile));
    with (app.activeDocument.printPreferences){
            printer = "Advertising - Creative - Color Xerox";
            copies = 1;
            pageRange = "1-6";
            paperSize = "US Letter";
            paperHeight = "11 in";
            paperWidth = "8.5 in";
            printPageOrientation = PrintPageOrientation.landscape;
            pagePosition = PagePositions.centered;
           scaleHeight = 100;
           scaleWidth = 100;
            scaleMode = ScaleModes.scaleWidthHeight;
            scaleProportional = true;
            pageInformationMarks = true;
            colorOutput = ColorOutputModes.COMPOSITE_CMYK;
    app.activeDocument.print(false);
    for(myCounter = app.documents.length; myCounter > 0; myCounter--){
    app.documents.item(myCounter-1).close(SaveOptions.no);
    function firstChange() {
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
              app.findChangeTextOptions.caseSensitive = false;
        app.findTextPreferences.findWhat = "^t";
              app.changeTextPreferences.changeTo = "";
              myDocument.changeText();
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
         app.findTextPreferences.findWhat = "^p^p";
              app.changeTextPreferences.changeTo = "^p";
              myDocument.changeText();
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
              app.findTextPreferences.findWhat = "^p";
              app.changeTextPreferences.changeTo = "^R";
              myDocument.changeText();
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
    function secondChange(curFrame) {
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
              app.findChangeTextOptions.caseSensitive = false;
        app.findTextPreferences.findWhat = "    ";
              app.changeTextPreferences.changeTo = "|";
              curFrame.changeText();
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
         app.findTextPreferences.findWhat = " ";
              app.changeTextPreferences.changeTo = "";
              curFrame.changeText();
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
              app.findTextPreferences.findWhat = "|";
              app.changeTextPreferences.changeTo = " ";
              curFrame.changeText();
              app.findTextPreferences = NothingEnum.NOTHING;
              app.changeTextPreferences = NothingEnum.NOTHING;
    function splitStory(){
              //Make certain that user interaction (display of dialogs, etc.) is turned on.
              app.scriptPreferences.userInteractionLevel = UserInteractionLevels.interactWithAll;
              if(app.documents.length != 0){
                        if(app.selection.length != 0){
                                  //Get the first item in the selection.
                                  var mySelection = app.selection[0];
                                  //Process the selection. If text or a text frame is
                                  //selected, do something; otherwise, do nothing.
                                  switch(mySelection.constructor.name){
                                            case "Text":
                                            case "InsertionPoint":
                                            case "Character":
                                            case "Word":
                                            case "Line":
                                            case "TextStyleRange":
                                            case "Paragraph":
                                            case "TextColumn":
                                            case "TextFrame":
                                                      //If the text frame is the only text frame in the story, do nothing.
                                                      if(mySelection.parentStory.textContainers.length > 1){
                                                                //Splitting the story is a two-step process: first, duplicate
                                                                //the text frames, second, delete the original text frames.
                                                                mySplitStory(mySelection.parentStory);
                                                                myRemoveFrames(mySelection.parentStory);
                                                      else{
                                                                alert("Please select a story containing more than one text frame and try again.");
                                                      break;
                                            default:
                                                      alert("Please select some text or a text frame and try again.");
                        else{
                                  alert("Please select some text or a text frame and try again.");
              else{
                        alert("Please open a document and try again.");
    function mySplitStory(myStory){
              var myTextFrame;
              //Duplicate each text frame in the story.
              for(var myCounter = myStory.textContainers.length-1; myCounter >= 0; myCounter --){
                        myTextFrame = myStory.textContainers[myCounter];
                        myTextFrame.duplicate();
    function myRemoveFrames(myStory){
              //Remove each text frame in the story. Iterate backwards to avoid invalid references.
              for(var myCounter = myStory.textContainers.length-1; myCounter >= 0; myCounter --){
                        myStory.textContainers[myCounter].remove();

    Hotfixes are special, out-of-band patches created to fix specific problems, so they are never published to Windows Update.  Often the hotfix gets incorporated into a released patch that is published on Windows Update.  If this hotfix was incorporated
    into a released patch, and you applied that patch to your system, the hotfix would see that its files are older than the latest files on the system and would give you this message.  Because the hotfix is not for general distribution, there is rarely documentation
    saying that it has been superceded.
    Generally there is a file list with a hotfix/patch that gives you the version number of the affected files.  You can go through those files to see that you have the latest files.  The problem is finding the actual patch that updated those files. 
    Without going through lots of patches, it is hard to find which patch made the hotfix obsolete.
    .:|:.:|:. tim

  • Windows 2008 R2 SP1 Windows update not applicable

    HELP!!! We have 3 Windows 2008 R2 servers that were updated with SP1 back in March. Last month we noticed on our Retina audit that the three servers were missing several Windows critical patches that were released after SP1 was applied. WSUS did not report
    any missing patches for those three servers. When we tried to manually apply those missing patches we get the error message "This update is not applicable to your computer". After some troubleshooting we found that KB976932 (Service Pact 1) is not listed in
    installed updates. However, system property shows Windows 2008 R2 SP1 Enterprise Edition. We are certain that SP1 did NOT come pre-installed. Microsoft Baseline Security Analyzer detected no missing patches. Microsoft System Readiness Tool CBA logs show no
    errors. Ran SFC /SCANNOW and found no error also. Force install of the patches with command switch /wuforce, did not work we still get the same message patch not applicable. We compared our servers that are fully patched running Windows 2008 R2 SP1 against
    the three unpatched servers and found several dll and sys file's version to be different. Those dll and sys files are also the files that would have been updated by the critical patches. The only thing different between the fully patched Windows 2008 R2 SP1
    servers and the unpatch are the unpatch have no public internet access. We confirmed patches that were required prior to SP1 push are installed: KB2454826 KB2534366 KB2533552 KB976902 Confirmed: Partition with Windows 2008 R2 SP1 installed is set to "ACTIVE"
    Windows Event Collector service is started Windows Modules Installer is started Uninstalling SP1 is not possible because the KB976932 is not listed and verified "not hidden" in installed updates list. Rebuilding the three servers are the very last option,
    since they are critical. Other than the missing patches.... the servers are running great, we have no reported issues with the three servers. Attempt to reinstall SP1 failed after reboot, error 0X800F0826. If anyone has experience this problem and know of
    a solution please help.

    Hi,
    I would like to confirm that what updates are not applicable for your three Windows Server 2008 R2 SP1 servers?
    Based on the current situation, please run the System Update Readiness Tool as Meinolf Weber mentioned and check the CheckSUR.persist.log for the corrupted
    files. After that, please refer to the following Microsoft TechNet article for how to repair them.
    Advanced guidelines for diagnosing and fixing servicing corruption
    http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx
    Regards,
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • The Update is Not Applicable To Your Computer when installing patch on Windows Server 2008 R2 machine

    When I try to install security patch KB2525694 and KB978542 on my Windows Server 2008 R2 machine, I get the message "The Update is Not Applicable To Your Computer".  I am using the following files:
    Windows6.1-KB978542-x64 (KB978542)
    Windows6.1-KB2525694-x64 (KB2525694)
    I believe these are the correct files but no luck installing it.  Any help would be greatly appreciated!

    When I try to install security patch KB2525694 on my Windows Server 2008 R2 machine, I get the message "The Update is Not Applicable To Your Computer".  I am using the following files:
    Windows6.1-KB2525694-x64 (KB2525694)
    This update has been superseded many times.
    If you already have installed one of the superseding updates below, KB2525694 will not be applicable.
    For the list of superseding updates, check this list:
    http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2525694%20r2%20x64
    (click on the result, then click on the "Package Details" tab to get the list below..
    This update has been replaced by the following updates:
    Security Update for Windows Server 2008 R2 x64 Edition (KB2555917)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2567053)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2639417)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2641653)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2660465)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2676562)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2709162)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2718523)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2731847)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2761226)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2778344)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2778930)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2779030)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2808735)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2829361)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2850851)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2876315)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2883150)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2893984)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2913602)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2930275)
    Security Update for Windows Server 2008 R2 x64 Edition (KB2973201)
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Can't download photoshop elements 13 purchased on line with download page showing not applicable. what must I do next?

    Can't download Photoshop elements 13 purchased on line with download page showing not applicable.
    What must I do next?
    Years ago started with Photoshop 2.0 advanced to Photoshop Deluxe 4.0 so far so good.
    Purchased Photoshop Elements 8 some time ago, but never got help because Elements never downloaded
    and can only use it just to open pictures that's all.
    Now I Purchased adobe Photoshop Elements 13 and if I can't download this one with no help
    with a Trouble Ticket # 186456123 still pending after a week of promises from support calling
    1-800-833-6687 after 4 phone calls, to call me back.
    Who can I call to get my money back?
    My name is Gunter Krummet (nicknamed Bill)
    My phone number is 815-385-1761
    My Email is [email protected]
    Thank You to anyone that contacts me.

    Downloadable installation files available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4, CS4 Web Standard | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
    Photoshop Elements:  13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
    Lightroom:  5.7.1| 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5.5, 5
    Contribute:  CS5 | CS4, CS3
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

  • An update installed using DISM in install.wim seen as "Not Applicable" by WSUS report instead of "Installed"

    Hi all,
    To make server's installation faster, I intend to make an updated "install.wim" every 6 months using DISM.
    Then, after installation, the Win2012R2 server connect to a WSUS server to get the latests update not included in the install.wim.
    As a test, I used DISM to install an update in the install.wim file of Windows 2012R2 sources.
    In a new installed Windows server 2012R2, I can see that the KB is installed.
    But on the WSUS report of this server, the status of the KB included in the install.wim by DISM displayed as "Not applicable".
    Is it because WSUS did not installed it itself ?
    Is there a way to display it as "installed" in the report, even if the patch had not been installed by the WSUS server ?
    Thanks
    ML

    But on the WSUS report of this server, the status of the KB included in the install.wim by DISM displayed as "Not applicable".
    Very possible, and likely.
    It depends on how the detection logic of the update has been written. In some cases, detection logic is based on what an installer does during installation, e.g. create and/or set a registry key or value. This may not happen when injecting an update into
    an image using DISM. As a result, the detection logic will not see the necessary flags it's looking for to determine that an update is "Installed" vs "Not Applicable".
    You also have to think of this in terms of the baseline image installed on the system. To be true, a baseline image that already has the necessary content is, in fact, "Not Applicable", and has, in fact, not actually been installed to that machine.
    Most often you see this in the realm of installing images with slipstreamed service packs.
    Consider a scenario with a slipstreamed Win7SP1 baseline. Functionally speaking, all previous updates are contained within that SP1 baseline, but if you inspect the state of the actual updates in WSUS, they will all be listed as Not Applicable. They're not
    actually "installed", and they cannot be installed, thus the only viable remaining state is "Not Applicable", which is true -- because they cannot be installed on an SP1-based machine. (Functionally they are superseded, which is also a
    contributing factor to the state of "Not Applicable".)
    There is no way to display it as "Installed". It's not. This is something that should be documented in the declaration of the baseline image you're using (by patching up the image with DISM once every six months).
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Patch Management config - Enable not applicable patches

    Hi,
    I am trying to clean our list of enabled patches in order to reduce the time taken by the analyze.exe. I plan to uncheck the "Enable not applicable patches" in the ZPM Configuation and asked myself when a patch is "not applicable", because there are not applicable patches in our list, some devices are patched with so I think disabling not applicable patches will result in missing patches that could be useful.
    Thanks for every enlightenment
    Yves

    Hi
    Well this part has been left out of the docs (Help), so yes not easy to see what this really covers. But my guess is that you should be fine deselecting this, if it's not applicable it should mean that you have no devices in need of the patch.

  • Field avaialble in field catalog but not when I try to create the condition

    Hi,
      I wanted to add a new table to a delivery output. I need the fields delivery type/ship point and destination country. I could see that destination country (LAND1) is not available in the field catalog. I added it from the list of available fields (in KOMKBV2) and can see it in the field catalog but not when I try to create the condition table. What else do I need to get this field ?
    Regards,
    Hari.

    Also add your new field to structure KOMBZ
    If you want to use a new field in the field catalog, you must add the field to KOMP or KOMK in the following INCLUDES:
    - header data in INCLUDE KOMKAZ in KOMK
    - item data in INCLUDE KOMPAZ in KOMP
    When you use INCLUDES, the field is automatically added to KOMG and the field catalog.
    The routines for assigning values to the new fields in order processing are found in member MV45AFZZ. Use the following user exits:
    - USEREXIT_PRICING_PREPARE_TKOMK (header fields)
    - USEREXIT_PRICING_PREPARE_TKOMP (item fields)

  • KB2524478 Detected As Not Applicable

    Microsoft recently released KB2524478 (The network location profile changes from "Domain" to "Public" in Windows 7 or in Windows Server 2008 R2) to WSUS.  Neither of my two WSUS instances detects any of my Windows Server 2008 R2 SP1 systems as needing
    the update, though (status = Not Applicable).  Everything looks good in WSUS (the update is not declined); I've verified that the files in the KB are newer versions than the ones my servers; and I successfully downloaded the update from the Microsoft
    Download Center and manually installed it (no errors or other statements that it wasn't applicable).  There are no special requirements listed in the KB article, so I can't figure out why WSUS thinks my servers don't need the update.  Is there something
    I'm missing?
    Below is 30 minutes worth of output from WindowsUpdate.log after stopping and restarting the Windows Update agent service on one of my servers and then doing a wuauclt /resetauthorization /detectnow.  Looks normal to me.
    2012-04-19 12:37:01:617  820 f38 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2012-04-19 12:37:02:320  820 f38 Report CWERReporter finishing event handling. (00000000)
    2012-04-19 12:37:02:352  820 f38 Service *********
    2012-04-19 12:37:02:352  820 f38 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2012-04-19 12:37:02:352  820 f38 Service *************
    2012-04-19 12:37:14:883  820 a5c Misc ===========  Logging initialized (build: 7.5.7601.17514, tz: -0500)  ===========
    2012-04-19 12:37:14:883  820 a5c Misc   = Process: C:\Windows\system32\svchost.exe
    2012-04-19 12:37:14:883  820 a5c Misc   = Module: c:\windows\system32\wuaueng.dll
    2012-04-19 12:37:14:883  820 a5c Service *************
    2012-04-19 12:37:14:883  820 a5c Service ** START **  Service: Service startup
    2012-04-19 12:37:14:883  820 a5c Service *********
    2012-04-19 12:37:14:883  820 a5c Agent   * WU client version 7.5.7601.17514
    2012-04-19 12:37:14:898  820 a5c Agent   * Base directory: C:\Windows\SoftwareDistribution
    2012-04-19 12:37:14:898  820 a5c Agent   * Access type: No proxy
    2012-04-19 12:37:14:898  820 a5c Agent   * Network state: Connected
    2012-04-19 12:37:28:788  820 e74 Report CWERReporter::Init succeeded
    2012-04-19 12:37:28:788  820 e74 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2012-04-19 12:37:28:788  820 e74 Agent ***********  Agent: Initializing global settings cache  ***********
    2012-04-19 12:37:28:788  820 e74 Agent   * WSUS server:
    http://<SUS Server>
    2012-04-19 12:37:28:788  820 e74 Agent   * WSUS status server:
    http://<SUS Server>
    2012-04-19 12:37:28:788  820 e74 Agent   * Target group: (Unassigned Computers)
    2012-04-19 12:37:28:788  820 e74 Agent   * Windows Update access disabled: No
    2012-04-19 12:37:28:788  820 e74 DnldMgr Download manager restoring 0 downloads
    2012-04-19 12:37:28:804  820 e74 AU ###########  AU: Initializing Automatic Updates  ###########
    2012-04-19 12:37:28:804  820 e74 AU   # WSUS server:
    http://<SUS Server>
    2012-04-19 12:37:28:804  820 e74 AU   # Detection frequency: 22
    2012-04-19 12:37:28:804  820 e74 AU   # Approval type: Pre-install notify (Policy)
    2012-04-19 12:37:28:804  820 e74 AU   # Auto-install minor updates: No (Policy)
    2012-04-19 12:37:29:148  820 a5c Report ***********  Report: Initializing static reporting data  ***********
    2012-04-19 12:37:29:148  820 a5c Report   * OS Version = 6.1.7601.1.0.196882
    2012-04-19 12:37:29:148  820 a5c Report   * OS Product Type = 0x0000000E
    2012-04-19 12:37:29:148  820 a5c Report   * Computer Brand = VMware, Inc.
    2012-04-19 12:37:29:148  820 a5c Report   * Computer Model = VMware Virtual Platform
    2012-04-19 12:37:29:148  820 a5c Report   * Bios Revision = 6.00
    2012-04-19 12:37:29:148  820 a5c Report   * Bios Name = PhoenixBIOS 4.0 Release 6.0    
    2012-04-19 12:37:29:148  820 a5c Report   * Bios Release Date = 2011-04-15T00:00:00
    2012-04-19 12:37:29:163  820 a5c Report   * Locale ID = 1033
    2012-04-19 12:37:29:195  820 e74 AU Successfully wrote event for AU health state:0
    2012-04-19 12:37:29:195  820 e74 AU Initializing featured updates
    2012-04-19 12:37:29:195  820 e74 AU Found 0 cached featured updates
    2012-04-19 12:37:29:195  820 e74 AU Successfully wrote event for AU health state:0
    2012-04-19 12:37:29:195  820 e74 AU Successfully wrote event for AU health state:0
    2012-04-19 12:37:29:195  820 e74 AU AU finished delayed initialization
    2012-04-19 12:37:29:195  820 e74 AU Triggering AU detection through DetectNow API
    2012-04-19 12:37:29:195  820 e74 AU Triggering Online detection (non-interactive)
    2012-04-19 12:37:29:195  820 a5c AU #############
    2012-04-19 12:37:29:195  820 a5c AU ## START ##  AU: Search for updates
    2012-04-19 12:37:29:195  820 a5c AU #########
    2012-04-19 12:37:29:195  820 a5c AU <<## SUBMITTED ## AU: Search for updates [CallId = {0635BB08-288E-4D31-9F51-2D480FBC42E3}]
    2012-04-19 12:37:29:195  820 ba0 Agent *************
    2012-04-19 12:37:29:195  820 ba0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-04-19 12:37:29:195  820 ba0 Agent *********
    2012-04-19 12:37:29:195  820 ba0 Agent   * Online = Yes; Ignore download priority = No
    2012-04-19 12:37:29:195  820 ba0 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
    or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2012-04-19 12:37:29:195  820 ba0 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-04-19 12:37:29:195  820 ba0 Agent   * Search Scope = {Machine}
    2012-04-19 12:37:29:195  820 ba0 Setup Checking for agent SelfUpdate
    2012-04-19 12:37:29:195  820 ba0 Setup Client version: Core: 7.5.7601.17514  Aux: 7.5.7601.17514
    2012-04-19 12:37:29:195  820 ba0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-04-19 12:37:29:210  820 ba0 Misc  Microsoft signed: Yes
    2012-04-19 12:37:31:788  820 ba0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-04-19 12:37:31:788  820 ba0 Misc  Microsoft signed: Yes
    2012-04-19 12:37:31:804  820 ba0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-04-19 12:37:31:804  820 ba0 Misc  Microsoft signed: Yes
    2012-04-19 12:37:31:804  820 ba0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-04-19 12:37:31:804  820 ba0 Misc  Microsoft signed: Yes
    2012-04-19 12:37:31:867  820 ba0 Setup Determining whether a new setup handler needs to be downloaded
    2012-04-19 12:37:31:867  820 ba0 Setup SelfUpdate handler is not found.  It will be downloaded
    2012-04-19 12:37:31:867  820 ba0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-04-19 12:37:31:867  820 ba0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
    2012-04-19 12:37:31:867  820 ba0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-04-19 12:37:31:898  820 ba0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
    2012-04-19 12:37:31:898  820 ba0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
    2012-04-19 12:37:31:945  820 ba0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
    2012-04-19 12:37:31:945  820 ba0 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-04-19 12:37:32:288  820 ba0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-04-19 12:37:32:288  820 ba0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://<SUS Server>/ClientWebService/client.asmx
    2012-04-19 12:37:32:288  820 ba0 PT WARNING: Cached cookie has expired or new PID is available
    2012-04-19 12:37:32:288  820 ba0 PT Initializing simple targeting cookie, clientId = 12237968-1016-4f2d-89ce-fd6730363556, target group = , DNS name = <Client DNS Name>
    2012-04-19 12:37:32:288  820 ba0 PT   Server URL =
    http://<SUS Server>/SimpleAuthWebService/SimpleAuth.asmx
    2012-04-19 12:37:33:163  820 ba0 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-04-19 12:37:33:163  820 ba0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://<SUS Server>/ClientWebService/client.asmx
    2012-04-19 12:37:33:288  820 ba0 Agent   * Found 0 updates and 60 categories in search; evaluated appl. rules of 375 out of 625 deployed entities
    2012-04-19 12:37:33:304  820 ba0 Agent *********
    2012-04-19 12:37:33:304  820 ba0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-04-19 12:37:33:304  820 ba0 Agent *************
    2012-04-19 12:37:33:304  820 ba0 Report REPORT EVENT: {EC975DBE-82E5-4402-9733-C0648B489D94} 2012-04-19 12:37:33:304-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2012-04-19 12:37:33:304  820 af8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {0635BB08-288E-4D31-9F51-2D480FBC42E3}]
    2012-04-19 12:37:33:304  820 af8 AU   # 0 updates detected
    2012-04-19 12:37:33:304  820 af8 AU #########
    2012-04-19 12:37:33:304  820 af8 AU ##  END  ##  AU: Search for updates [CallId = {0635BB08-288E-4D31-9F51-2D480FBC42E3}]
    2012-04-19 12:37:33:304  820 af8 AU #############
    2012-04-19 12:37:33:304  820 af8 AU Successfully wrote event for AU health state:0
    2012-04-19 12:37:33:304  820 af8 AU Featured notifications is disabled.
    2012-04-19 12:37:33:304  820 af8 AU AU setting next detection timeout to 2012-04-20 14:34:00
    2012-04-19 12:37:33:304  820 af8 AU Successfully wrote event for AU health state:0
    2012-04-19 12:37:33:304  820 af8 AU Successfully wrote event for AU health state:0
    2012-04-19 12:37:33:320  820 ba0 Report CWERReporter finishing event handling. (00000000)
    2012-04-19 12:37:38:304  820 ba0 Report REPORT EVENT: {21339474-376B-45FB-BD4D-DA41E28A4197} 2012-04-19 12:37:33:304-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
    Check Reporting client status.
    2012-04-19 12:37:38:304  820 ba0 Report CWERReporter finishing event handling. (00000000)
    2012-04-19 12:44:26:356  820 ba0 Report Uploading 2 events using cached cookie, reporting URL =
    http://<SUS Server>/ReportingWebService/ReportingWebService.asmx
    2012-04-19 12:44:26:372  820 ba0 Report Reporter successfully uploaded 2 events.
    Thanks,
    Mark

    Hi,
    Thank you for posting here.
    This update you mentioned above is a hotfix.Hotfixes cannot be deployed via WSUS unless the update is published in the Microsoft Catalog.
    In this case, the update do publish in the Microsoft Catalog.if the server 08 r2 doesn't have the Symptom describled in
    http://support.microsoft.com/kb/2524478 ,and also read as not "Not Applicable",it probably indicate it is not applicable, this kb also indicate this hotfix might receive additional testing. Therefore,
    if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. In short, pls simply decline this hotfix in the wsus console.
    Regards,
    Clarence
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
    [email protected]
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Hotfix not applicable

    Hi all
    I put a request through for hotfix kb2661001 but when I try to apply it to my test server (Windows Server 2008 R2 SP1) I receive the "Update is not applicable to your computer" error. I have double-checked we do not already have it installed. Any
    possible cause for this?
    Thanks
    Chris Thackwray
    Systems Administrator
    Amana Living Inc.

    Yes, Remote Desktop Services role is installed.
    Yeah.. sorry about that. I caught that fact on my third re-read of the thread. ;)
    To catch up on one point of interest I've been trying to track back down for the past few days.. there are three REQUIRED post-KB2775511 hotfixes that you'll want to install ASAP, which may or may not have any relevance on the issue in this thread:
    KB2732673 fixes a regression issue in RDBSS.SYS
    KB2728738 fixes a regression issue in PROFSVC.DLL
    KB2878378 fixes a regression issue in ADVAPI32.DLL (be sure you use the 11/11/13 revision of this hotfix)
    While KB2661001 is included in the rollup (and is listed in that KB article), KB2661332 is not listed, thus I must assume that it's not contained in the rollup. It's possible that KB2661332 is superseded by KB2661001 (which would be consistent with
    it's inclusion in the rollup).
    To get a clue on that requires that we dig into the update itself and observe what's actually being patched.
    KB2661001 replaces two files: RPCSS.DLL and WIN32K.SYS with versions dated Jan 16, 2012.
    KB2661332 replaces only one file: WIN32K.SYS with a version dated Feb 10, 2012
    So, there's no supercession relationship... but wait, there's more, we're not yet done with this analysis! :-)
    Consider, also, that there may have been other update(s), released after February, 2012, that also updated WIN32K.SYS. The relevant question is what version of WIN32K.SYS is actually installed on that WS2008R2 server?
    On my Windows 7 x64 system I have a version of WIN32K.SYS dated February, 2014, which suggests that a very recent update may have actually superseded the hotfix identified as KB2661332. With a newer WIN32K.SYS on the system, then it would be absolutely correct
    that a hotfix containing a Feb 2012 version of that file would actualy be NOT APPLICABLE to that system.
    FWIW, I have a WS2008R2 system, not recently patched, that has an April 2013 version of that file. If one wanted to engage in a thoroughly pedantic investigation, one could research the February and March updates and find the actual update that provided
    the most recent WIN32K.SYS.
    And.. if one were to dig into that list of updates looking for this file, one would find that WIN32K.SYS (Feb 2014) is replaced in KB2930275 (MS14-015) Security Update for Windows Server 2008 R2 x64 Edition -- which I'd be pretty confident in guessing
    has already been installed to your systems. :-)
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Unable to install the security patches KB2677070 in Windows Server 2008 R2 SP1 (The update is not applicable to your computer)

    Dear everyone, 
    We are trying to install the below KB in our windows server 2008 R2 SP1, however, it will show "The update is not applicable to your computer". There is no problems to install the other patches except this one. Do anyone have idea about it?
    http://support.microsoft.com/kb/2677070
    Thanks,
    Users

    Hi,
    According to this KB article, there are many exceptions where this KB is not applicable.
    Please perform the following steps:
    Expand the “For all supported…” title in the File Information section in the KB article.
    Find Crypt32.dll.mui files on your machine.
    Then compare the file version, file size, data and time with the ones listed in the KB article.
    If there is a match, then this KB doesn’t apply to your machine, which is by design.
    Hope this helps.
    Best Regards,
    Amy Wang

  • Windows Update fails: KB2957189 is not applicable to your computer

    Hello,
    I am having trouble with some Windows Updates on a Win2012R2 Server.
    We have two servers which will become nodes in a 2-node-cluster. The Cluster Configuration Wizard complains about four updates not present on Server A but ok on Server B.
    Both servers are identical - same model, same time of installation etc. 
    These are the updates the Cluster Configuration Wizard complains about:
    KB2957189 - not in list of installed updates on both machines
    KB2918614 - present in list of installed updates on both machines
    KB2926765 - present in list of installed updates on both machines
    KB2939087 - present in list of installed updates on both machines
    When I try to manually install the update KB2097189 on Server A I get this error "Windows Update Standalone Installer - This update is not applicable to your computer". However if I try the same update file on Server B I get
    "this update is already installed on this computer".
    I already read that 2918614 can sometimes break Windows Update on a machine but am not sure how to proceed.
    What I need to achieve is an identical update state on both machines to make the Cluster Configuration Wizard accept the config. It is the only issue we have.  
    Any ideas?
    Regards, rj
    Regards, Ralph

    Thanks for the reply!
    The issue is a bit more tricky:
    The Cluster Configuration Wizard complains about those four updates not being installed on Server A.
    Server B is fine.
    The displayed list of installed updates on both servers is IDENTICAL.
    When I try to run manual setup for KB2097189:
    Server A: "This update is not applicable for your Computer"
    Server B: "This update is already installed on your Computer"
    KB2957189 is not visible in the list of installed updates on either machine.
    KB2918614, KB2926765 and KB2939087 however, are.
    Kind of clueless here. Seems to me Server A has a glitch in Windows Update itself...
    Regards, Ralph

  • Hotfix KB2277439 Says "The update is not applicable to your computer" when trying to install.

    We have two Dell Poweredge 710 servers both running Windows Server 2008 R2 Enterprise x64 using Failover Clustering. These servers host a Microsoft SQL Server 2008 database. They are being back up by a EMC Networker.
    Recently, we had the active node hang overnight around the same time that the backups run. After further digging into what could have caused the problem, I found some usefull information on our issue in KB2277439 The symptoms described match our situation
    exactly: 
    [VSS] OnFreeze : preparedToBackup 1, freeGumSent 0, snapshotSet fc0641af-a15b-4b44-a147-69a52e8373b5
    0000089c.000086e0::2013/10/08-02:14:15.844 INFO  [VSS]
    OnBackupShutdown - preparedBackup 1, gumsent 0, snapshotSet 4b907950-8316-42f3-9aa2-18040520b383
    0000089c.00006f28::2013/10/08-02:14:15.969 INFO  [VSS] HandleBackupGum - Initiating the backup
    0000089c.00006f28::2013/10/08-02:14:15.969 INFO  [VSS] HandleOnFreezeGum - Stopping the Death Timer
    0000089c.00006f28::2013/10/08-02:14:15.969 INFO  [VSS] HandleBackupGum - Acquiring lock and flushing DB
    0000089c.00006f28::2013/10/08-02:14:15.969 INFO  [VSS] HandleBackupGum - Completed the backup Request
    0000089c.00006f28::2013/10/08-02:14:15.969 INFO  [VSS]
    OnFreeze returning true
    0000089c.000012c0::2013/10/08-02:14:17.638 INFO  [VSS]
    OnThaw : preparedToBackup 0, freeGumSent 1, snapshotSet fc0641af-a15b-4b44-a147-69a52e8373b5
    0000089c.000012c0::2013/10/08-02:14:17.638 INFO  [VSS]
    OnThaw returning false
    0000089c.000012c0::2013/10/08-02:14:17.716 INFO  [VSS] OnAbort - preparedBackup 0, gumsent 0
    0000089c.000012c0::2013/10/08-02:14:17.716 INFO   Current request is Aborted - Context4194304[VSS] OnThaw : preparedToBackup 0, freeGumSent 0, snapshotSet fc0641af-a15b-
    The package I downloaded extracted a file named Windows6.1-KB2277439-x64.msu  However when I tried installing the hotfix I get an error saying: "The update is not applicable to your computer"
    Can someone please explain why this update is not applicable? As far as the KB article says, it's specifically meant for Windows Server 2008 R2 Enterprise x64 with Failover Clustering installed, which is exactly the setup that these servers are running.
    Also I have verified that this hotfix had not been previously applied and I'm pretty sure we couldn't have gotten this as an automatic update. Any help with this would be greatly appreciated.

    Hotfixes are special, out-of-band patches created to fix specific problems, so they are never published to Windows Update.  Often the hotfix gets incorporated into a released patch that is published on Windows Update.  If this hotfix was incorporated
    into a released patch, and you applied that patch to your system, the hotfix would see that its files are older than the latest files on the system and would give you this message.  Because the hotfix is not for general distribution, there is rarely documentation
    saying that it has been superceded.
    Generally there is a file list with a hotfix/patch that gives you the version number of the affected files.  You can go through those files to see that you have the latest files.  The problem is finding the actual patch that updated those files. 
    Without going through lots of patches, it is hard to find which patch made the hotfix obsolete.
    .:|:.:|:. tim

Maybe you are looking for