Validation d'une transformation de calque ou de sélection

Bonjour,
Un changement inexpliqué est intervenu dans un élément d'interface de CS6.
Jusqu'à présent, lorsque je modifiais un calque ou une sélection (taille, forme, orientation), il suffisait de cliquer sur les petite icônes dans la barre d'application, soit le "cercle barré" pour la refuser, soit le "coche" pour l'accepter. Ces icônes ont disparues et maintenant, je dois pointer à l'extérieur du calque pour faire surgir une fenêtre de dialogue qui me demande expressément de faire ce choix. Inutile de dire que cette manoeuvre fait perdre du temps et devient insupportable surtout lorsqu'on opère beaucoup de modifications sur un même calque.
J'ai étudié avec soin tous les détails d'interface mais rien ne m'a permis de retrouver ces 2 petites icônes.
La solution est peut-être simple mais je ne l'ai pas trouvée.
Merci pour votre aide.
Michel
(iMac 27" Yosemite)

C'est Photoshop bien sûr, j'ai indiqué CS6.
Je prends note de votre conseil mais il est plus naturel de cliquer sur l'une de ces 2 fameuses icônes disparues puisque j'ai la souris en main en faisant ces transformations. Je souhaiterais avant tout voir réapparaitre ces icônes très pratiques. Cela est-il dû à un changement de paramètres, je ne vois pas lequel ?
A suivre ...

Similar Messages

  • No validation of xsl transforms within process

    Hi there,
    I've posted this before with no avail.
    I have process which creates an XML schema from a file adpator.
    The input/output XML validation is turned on, on my BPEL server and is working well.
    I then transform this XML to another 'global schema' which is heavily validated with lots of <restricts>.
    More processing is done on this global schema, then finally it is converted over to a DB schema for output to a DB.
    As meationed above the schemas are validated on input and output (from file, to DB) fine. If i place a <restrict> on any values on these schemas the process fails.
    BUT, is the transformation the takes place within the process (from the file schema to the global schema) suppose to be validated?
    Using the XSLT mapping tool i am able to test the transformation and when i click validate quite rightly it fails. But when in the BPEL server this section does not fail, it just does the tranformation without validation.
    Is this just functionality?
    thanks,

    You want to tell whether the output of an XSL transformation will validate against a schema? I don't see what good looking at the XPath expressions in the XSLT would do -- it might not even have any, or they might be simple ones relative to the context node. And even if you did have any, I can't see how they are relevant to the output of the transformation. Which could be anything.
    And I don't see how you could find out anything about paths in the output document. I doubt you could even tell whether the output was well-formed XML let alone whether it conformed to a schema.
    So: I don't think there's an existing solution for that because (a) it isn't very simple and (b) it isn't a common requirement. Of course I could be wrong in my opinion that it isn't possible to do such a thing. But I don't think I'm wrong about it being extremely difficult.

  • Disable validation inside Transformer?

    is there a way to turn off validation within the Transformer class? Our XSL uses document() to reference external XML files:
      <xsl:value-of
       select="document($teamsched-resource-file)/schedule/event-metadat\a[@event-key = $event-id]/@start-date-time"/>where the external file DOCTYPE uses a relative (but invalid) SystemID DTD file path:
    <!DOCTYPE schedule PUBLIC "-//XMLTEAM//DTD sportsml-core 1.0/EN" "dtds/sportsml\-core.dtd">and the transform gives the following on each call to document():
        file:///home/ticker/xsl/scoresxml.xsl; Line #394; Column #41;
        Can not load requested doc:  /home/ticker/resources/l.nba.com/dtds/sportsml-core.dtd
        (No such file or directory)Is it possible to dig out the XMLReader (or whatever it is) from the Transformer and toggle it's validation?
    We're using Java 1.4.2 and the apache Xalan classes.

    That's an interesting hack (which one would think would be simpler to do!) but it's not the problem I have -- I do not want to disable the entity resolver in the DOM builder, I need to disable it in the Transformer ... and so far as I can tell, I can't get my hands on the SAXBuilder used inside the Transformer class to provide the XML parsing supporting the XSL document() method for importing external XML documents during a transform.
    Or do I misunderstand the answer in that other thread? Is it actually possible to extract and modify, or replace, the SAXBuilder (or whatever it is) used with the Transformer?
    Also, for the example given in that other thread, why do they not simply use SAXBuilder's setValidation(false)? When I do this for the builder used to create the Document class from an XML file, the DTD is completely ignored.

  • Error report from validation

    Hi,
    I used validation in the transformation and pointed to PASS and FAIL. The fail should generate an error report, but where will i find the error report?
    Is it in the management console?
    Appreciate your help.
    Thanks,
    Arun

    Hi Arun,
    If I understood your design, youu2019re using a Validation transform and redirecting the u2018FAILSu2019 to another target. Is that right?
    Well, the statistics for that can be found in the MC, under Data Validation area. But the statistics will be collected only if you set the u2018Collect data validation statisticsu2019 under the u2018Validation Transform optionu2019 found inside the Validation transform (Validation, validation, validation!). This data is collected only for failures.
    Try that and let us know if you manage to find what you need.
    Regards,
    Pedro

  • Transformée de fourier

    Bonjour,
    J'ai un signal que j'ai normalisé sous forme de tableau de sorte à avoir 10 000 valeurs, ce qui me donne un pas de 1 seconde. (en fait je n'acquière que 2048 points, et je complète mon tableau de zéro).
    Je voudrais appliquer une transformée de fourier à mon signal, mais je ne trouve pas d'exemple simple de code qui utilise la transformée de fourier, et si je mets ma transformée juste à la sortie de mon tableau, ça ne me donne pas un beau pic, c'est que je dois manquer une étape.
    Je suis donc à la recherche d'un exemple simple de transformée de fourier afin de pouvoir m'en inspirer.
    Merci d'avance.

    Bonjour,
    Etes vous sur que vous devez obtenir un pic ?
    Quelle est la forme du signal ? Avez vous calculé la transformée théoeique ?
    Avez vous pensé a effectuer un fenêtrage ? (Hamming, Blackmann, etc)
    Cordialement,
    Da Helmut

  • Extraire des données d'une FFT

    Bonjour,
    J'ai un VI qui me sert à échantillonner une tension alternative à 25000 Hz (à l'aide d'un accéleromètre, en fait un relevé de vibration), et je souhaite effectuer une transformée de fourier de ce signal afin d'obtenir un spectre et récuperer des valeurs spécifiques à certaines fréquences afin d'alimenter un tableau excel... (Valeur efficace de différents pics)
    une idée ?

    Bonjour,
    Pour effectuer une transformée de Fourier d'un signal, vous avez plusieurs possibilités, en fonction que votre signal soit représenté par un tableau de doubles, ou par une waveform.
    Vous pouvez utiliser la fonction FFT.vi, que vous trouverez dans la palette de fonctions Traitement du signal>>Transformées.
    Vous pouvez également utiliser la fonction Analyseur de Distorsion Harmonic.vi , que vous trouverez  dans la palette Traitement du signal>>Mesures sur Waveform.
    Cependant, ces deux fonctions ne sont disponibles qu'à partir de la version Full de LabVIEW. Si vous disposez d'une version de base, ces fonctions ne seront pas disponibles.
    Cordialement,
    Olivier L. | Certified LabVIEW Developer

  • Comment faire pour ne pas perdre tous les effets de calques lorsque j'applatis l'image?

    Lorsque j'applatis l'image ou que je fusionne tous les calques pour pouvoir enregistrer un tif à partir de mon psb, je perds systématiquement tous les effets de calques présent sur chacun de mes calques!!! Donc l'image que j'obtient n'est plus conforme à l'originale car je n'ai plus les ombres, les lumières internes, etc????
    Merci à quiconque pourrait m'aidet je dois porter au labo demain matin mes tif pour mon expo perso et je désespère de trouver une solution!!!

    Bonjour, certains de ces effets de calques utilisent des modes de mélange particuliers qui ne peuvent être rendus s'il y a de la tranparence dessous.. Aussi, assurez-vous de regarder l'image à 100%.
    Une alternative est aussi de faire une copie des calques aplatie: CMD+MAJ+OPT+E sur Mac /CTRL+MAJ+ALT+E sur Pc, et la copier sur une nouvelle image.

  • Any hints on how to go from Requirement to Transformation Code?

    Hi Experts,
    I am trying to upgrade my skills in Transformation and reading some books on Transformations logic and I am getting lost. But when you bring in your practical guide it helps make it clear and I will appreciate some hints based your experience.
    1. Do you have any specific transformation requirement (from source to target) to share with me? And I will appreciate an explanation of the transformation requirement and transformation logic
    2. Is there a specific approach to converting the requirement to code? can you use a real-life case to explain it?
    3. Are there any best practices in converting requirements into codes?
    4. Is there a best practice for testing and validation of the transformation code?
    5. Any Dos and Don'ts in converting requirements into transformation logic?
    Thanks
    Edited by: AmandaBaah on Nov 9, 2011 8:55 PM

    Hi Amanda,
    I think you should start with the type of routines you can write
    start routine
    Field level Routine
    End Routine .
    Expert Routine
    There are lots of SDN articles available for the same .In forum you will find various scenarios and requirements comes in projects.
    1.Start and End Routine works on package so you need knowledge of  tables ,loops ,structures etc to write the code .
    They are good when you want to update multiple fields and want to implement complex logic.
    2.Field level routine works as one record at a time so its good when you want to do lookup etc for one field only .
    3.There are specific scenario when you can use a specific routine and it also depend greatly on your business requirement ,efficiency and performance of code  ,your comfort level .
    ex: Write start routine if
    you want processing of multiple fields at source data without filtering .
    You want to implement some logic based on which you need to update some more records at field level or at end routine .    *  You want to delete unwanted records.
    You  are doing master data lookup at field level routine so selecting master data in an internal table should be done at start routine.
    Write field routine if
    Only one field need to be update  and logic is simple .
    You want to change record by record.
    You have lookup .
    You want to further implement some logic at  end routine based on changes done at field level routine   
    Write End routine if
    It is final logic that you want to implement .
    You have multiple fields to update
    start routine and end routine can be used vice verse .Use them based on your requirement and efficiency of code.
    4.These threads will be helpful for you :
    Scenario examples for Lookup
    Re: What is the use of Look Ups?
    Sample Routine Code
    Re: Start routine - how to....?
    Re: Routine
    ABAP in BW
    Re: Abap for BW
    Hope this will be helpful .
    Regards,
    Jaya Tiwari

  • Problème avec une composition dans after effect

    Bonjour,
    j'ai un problème avec une composition dans after effect (12.2.1.5). Lors d'une transformation à l'échelle d'une image, elle se double et se déforme

    ci joint,deux capture d'écran, sur la première le logo déformé sur la composition et la deuxième le logo à l'initiale.
    Comment faire pour éviter la déformation?

  • Code de validation non lisible sur la carte itunes comment aller le chercher car la carte vaut 25 dollars

    Comment faire pour avoir le code de validation sur une carte itunes car le code n'est plus apparent et la carte vaut 25 dollards et je ne veut pas perdre cet argent

    iTunes Store:  Invalid, Inactive, or Illegible codes http://support.apple.com/kb/TS1292 - gift cards
    Maybe you're in Francophone Canada and it makes sense for you to be talking about dollar value card, but just so you're aware, a card from one country won't work in another.

  • FILTRE GRAIN PHOTOSHOP CS6

    Bonjour,
    dans Photoshop CS6, il est possible d'appliquer à un fichier video le filtre "ajout de bruit".
    Ce filtre s'applique uniquement à l'image sélectionnée. Hors je souhaite pouvoir automatiser cet effet sur l'ensemble des images de ma video.
    Une solution, bien-sûr, serait de transformer mon calque video en calque dynamique et d'appliquer le filtre sur ce calque.
    Le problème c'est que l'effet est toujours le même sur chaque image, hors je souhaite avoir un grain différent sur chaque image.
    Comment puis-je "automatiser" cet effet ?
    Merci d'avance

    Tu veux quelque chose de complètement aléatoire ?
    Si non, tu peux peut-être appliquer des valeurs différentes de filtre à différentes instances d'un calque gris 50% (ici 3, identifiés par des couleurs pour l'exemple) et facilement les dupliquer dans un Groupe vidéo…
    Ce n'est pas parfait, mais c'est une piste.

  • XSLT for adding Namespace is not being executed at runtime

    Hi Gurus,
    I am trying to add a Namespace to inbound xml and I wrote a simple XSLT mapping as below, when I execute this using XML spy or in Operation mapping manually it is working fine and giving me output as expected but at runtime it is not executing, I am getting same input xml as output xml and receiver agreement is failing...
    Appreciate your thoughts..
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
         <xsl:output method="xml" encoding="UTF-8"/>
            <xsl:template match="*">
              <ns0:SalesXmlExtended xmlns:ns0="urn:/company.com/H/sndr">
              <xsl:copy-of select="//SalesReportInfo"/>
         </ns0:SalesXmlExtended>
         </xsl:template>
    </xsl:stylesheet>
    input xml is as below....
    <?xml version="1.0" encoding="UTF-8"?>
    <SalesXmlExtended>
         <SalesReportInfo>
              <SalesReport>
                   <Detail>
                        <deptNum>0270</deptNum> etc...
    output I am getting in XMLSpy and OM is as below, this is exactly what I need...
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:SalesXmlExtended xmlns:ns0="urn:/company.com/H/sndr">
         <SalesReportInfo>
              <SalesReport>
                   <Detail>
                        <deptNum>0270</deptNum>
    Thanks...
    Sukarna...

    Hi Baskar,
    Yeah, that is what my issue is , it shouldn't be failing but it is...
    I tried by manipulating the required namespace in the input file and it is working fine with out any errors....so I am guessing the XSLT is not being executed...
    I am getting below error which is valid because the transformation is not happening
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Technical Routing --> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
    <SAP:P1>-BS_HOUSE_OF_FRASER_DEV</SAP:P1><SAP:P2>-BD1_100,urn:.com/HoF/POS/EOD/sndr.SI_Out_HoFSales_XML</SAP:P2>
    <SAP:P3/>
    <SAP:P4/>
    <SAP:AdditionalText>No standard agreement found for , BS_HOUSE_OF_FRASER_DEV, , BD1_100, urn:/HoF/POS/EOD/sndr, SI_Out_HoFSales_XML</SAP:AdditionalText
    ><SAP:Stack>Problem occurred in receiver agreement for sender -BS_HOUSE_OF_FRASER_DEV to receiver -

  • Silent Uninstall lync 2013 client

    Hi,
    i try to uninstall Lync 2013 Client silently but no matter what i try Lync won't uninstall.
    maybe someone can explain me what i'm doing wrong
    I tried the recommended command
    copy "%~DP0uninstall_lync.xml" "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup
    Controller\uninstall_lync.xml"
    "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config "%COMMONPROGRAMFILES(x86)%\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml"
    Config File
    <Configuration Product="LYNCENTRY">
    <Display Level="None" AcceptEULA="TRUE" />
    <Setting Id="SETUP_REBOOT" Value="NEVER" />
    <Logging Type="standard" Path="c:\windows\log\" Template="Microsoft Office Lync Uninstall(*).log" />
    </Configuration>
    Log:
    2014/11/24 14:49:11:039::[4844] PERF: TickCount=11665520 Name=OBootStrapper::Run Description=Begin function
    2014/11/24 14:49:11:040::[4844] Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2
    2014/11/24 14:49:11:040::[4844] Running 32-bit setup on a 64-bit operating system.
    2014/11/24 14:49:11:040::[4844] Command line: "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\setup.exe" /uninstall LYNCENTRY /dll OSETUP.DLL /config "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml"
    2014/11/24 14:49:11:040::[4844] Parsing command line.
    2014/11/24 14:49:11:040::[4844] Config XML file specified: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
    2014/11/24 14:49:11:040::[4844] Uninstall requested for product: LYNCENTRY
    2014/11/24 14:49:11:040::[4844] Parsing config.xml at: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
    2014/11/24 14:49:11:060::[4844] Preferred product specified in config.xml to be: LYNCENTRY
    2014/11/24 14:49:11:060::[4844] Parsed setting: SETUP_REBOOT with value: NEVER in config.xml.
    2014/11/24 14:49:11:060::[4844] Logging type standard specified in config.xml.
    2014/11/24 14:49:11:060::[4844] Log directory: c:\windows\log\ specified in config.xml
    2014/11/24 14:49:11:060::[4844] Log file template: Microsoft Office Lync Uninstall(*).log specified in config.xml
    2014/11/24 14:49:11:060::[4844] Display level none specified in config.xml.
    2014/11/24 14:49:11:075::[4844] Using setup controller dll at location [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL].
    2014/11/24 14:49:11:075::[4844] Verify file signature in "C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe"
    2014/11/24 14:49:11:129::[4844] C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\Setup.exe is trusted.
    2014/11/24 14:49:11:129::[4844] Verify file signature in "C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL"
    2014/11/24 14:49:11:198::[4844] C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL is trusted.
    2014/11/24 14:49:11:296::[4844] Using setup controller dll at [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL].
    2014/11/24 14:49:11:296::[4844] PERF: TickCount=11665785 Name=OBootStrapper::Run Description=Calling RunSetup
    2014/11/24 14:49:11:302::[4844] PERF: TickCount=11665785 Name=RunSetup Description=Begin function
    2014/11/24 14:49:11:303::[4844] WER element [P2] is set to value [OSETUP.DLL]
    2014/11/24 14:49:11:303::[4844] WER element [P3] is set to value [15.0.4569.1503]
    2014/11/24 14:49:11:304::[4844] Catalyst execution began: 11/24/2014 14:49:11.
    2014/11/24 14:49:11:305::[4844] Parsing config.xml at: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller\uninstall_lync.xml
    2014/11/24 14:49:11:307::[4844] Preferred product specified in config.xml to be: LYNCENTRY
    2014/11/24 14:49:11:307::[4844] Parsed setting: SETUP_REBOOT with value: NEVER in config.xml.
    2014/11/24 14:49:11:307::[4844] Logging type standard specified in config.xml.
    2014/11/24 14:49:11:307::[4844] Log directory: c:\windows\log\ specified in config.xml
    2014/11/24 14:49:11:307::[4844] Log file template: Microsoft Office Lync Uninstall(*).log specified in config.xml
    2014/11/24 14:49:11:307::[4844] Display level none specified in config.xml.
    2014/11/24 14:49:11:308::[4844] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [enabled] for the [UninstallExecutionMode]
    2014/11/24 14:49:11:308::[4844] Ensuring the install-state of setup controller files for product [LYNCENTRY].
    2014/11/24 14:49:11:308::[4844] Warning: Product registation information for 'LYNCENTRY' not detected. ErrorCode: 1011(0x3f3). Failed attempt to force-repair setupexe boot files.
    2014/11/24 14:49:11:308::[4844] Searching for default versions of resource files under the folder [C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\Office Setup Controller].
    2014/11/24 14:49:11:328::[4844] Found [1] resource files under the default folder.
    2014/11/24 14:49:11:328::[4844] Running in [UninstallExecutionMode]. Run from TEMP folder at [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214].
    2014/11/24 14:49:11:345::[4844] Loaded resource file [C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUPUI.DLL] (CultureTag=de-DE).
    2014/11/24 14:49:11:345::[4844] WER element [SuppressModal] is set to value [false]
    2014/11/24 14:49:11:346::[4844] WER element [P1] is set to value [15.0.4569.1503]
    2014/11/24 14:49:11:346::[4844] Loaded Dll : C:\Users\ADMIN_~1\AppData\Local\Temp\Setup00000214\OSETUP.DLL.
    2014/11/24 14:49:11:346::[4844] Catalyst version is : 15.0.4569.1503
    2014/11/24 14:49:11:346::[4844] JobExecutionMode is UninstallExecutionMode.
    2014/11/24 14:49:11:547::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:11:547::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:11:548::[4844] IsProductTransitionToMModeSafe: An exception was caught, therefore transition to MMode is unsafe for product:
    2014/11/24 14:49:11:548::[4844] Error: Product is not installed, therefore transition to MMode is unsafe for product: LYNCENTRY Type: 27::InstalledProductStateCorrupt.
    2014/11/24 14:49:11:548::[4844] Ensuring the install-state of setup controller files for all Products.
    2014/11/24 14:49:11:548::[4844] Opening registry key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
    2014/11/24 14:49:11:549::[4844] Ensuring the install-state of setup controller files for product [LYNC].
    2014/11/24 14:49:11:549::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNC.
    2014/11/24 14:49:11:549::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNC.
    2014/11/24 14:49:11:549::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002A-0407-1000-0000000FF1CE}].
    2014/11/24 14:49:11:549::[4844] Product INSTALLSTATE for ProductCode '{90150000-002A-0407-1000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:11:549::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:13:038::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002A-0000-1000-0000000FF1CE}].
    2014/11/24 14:49:13:038::[4844] Product INSTALLSTATE for ProductCode '{90150000-002A-0000-1000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:13:038::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:15:639::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-006E-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:15:639::[4844] Product INSTALLSTATE for ProductCode '{90150000-006E-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:15:639::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:18:424::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0410-0000-0000000FF1CE}].
    2014/11/24 14:49:18:424::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0410-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:18:424::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:20:222::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:20:222::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:20:222::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:21:766::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-040C-0000-0000000FF1CE}].
    2014/11/24 14:49:21:767::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-040C-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:21:767::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:23:339::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-001F-0409-0000-0000000FF1CE}].
    2014/11/24 14:49:23:339::[4844] Product INSTALLSTATE for ProductCode '{90150000-001F-0409-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:23:340::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:25:046::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-002C-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:25:047::[4844] Product INSTALLSTATE for ProductCode '{90150000-002C-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:25:048::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:26:619::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-012B-0407-0000-0000000FF1CE}].
    2014/11/24 14:49:26:620::[4844] Product INSTALLSTATE for ProductCode '{90150000-012B-0407-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:26:620::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:28:951::[4844] Ensuring the install-state of setup controller feature[SetupControllerFiles] for product[{90150000-012C-0000-0000-0000000FF1CE}].
    2014/11/24 14:49:28:951::[4844] Product INSTALLSTATE for ProductCode '{90150000-012C-0000-0000-0000000FF1CE}' is '5'.
    2014/11/24 14:49:28:952::[4844] Feature INSTALLSTATE for Feature 'SetupXmlFiles' is '3'.
    2014/11/24 14:49:36:136::[4844] Opening registry key: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:36:136::[4844] Opening registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Office15.LYNCENTRY.
    2014/11/24 14:49:36:136::[4844] IsProductTransitionToMModeSafe: An exception was caught, therefore transition to MMode is unsafe for product:
    2014/11/24 14:49:36:136::[4844] Error: Product is not installed, therefore transition to MMode is unsafe for product: LYNCENTRY Type: 27::InstalledProductStateCorrupt.
    2014/11/24 14:49:36:136::[4844] Not showing message because suppress modal has been set. Title: 'Setupfehler', Message: 'Diese Produktinstallation wurde besch..digt. F..hren Sie Setup erneut von der CD, DVD oder einer anderen urspr..nglichen Installationsquelle aus.'
    2014/11/24 14:49:36:136::[4844] Message returned: 1
    2014/11/24 14:49:36:141::[4844] Error: Catalyst boot time check failed Type: 66::PreReqCheckFailure.
    2014/11/24 14:49:36:141::[4844] Catalyst execution finished: 11/24/2014 14:49:36. Return code: 30066. Exception caught: PreReqCheckFailure.
    2014/11/24 14:49:36:141::[4844] PERF: TickCount=11690621 Name=RunSetup Description=End function
    My next attempt was to look for MSI Files in Windows\Installer and the Uninstall RegKey
    MsiExec.exe /X{90150000-012C-0000-0000-0000000FF1CE} /qn /norestart /L*v
    "c:\windows\log\Microsoft_Lync_2013_Update_KB2817626_x86_0185_Install.LOG"
    MSI (s) (10:4C) [15:10:52:612]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (10:4C) [15:10:52:628]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (10:4C) [15:10:52:631]: End dialog not enabled
    MSI (s) (10:4C) [15:10:52:631]: Original package ==> C:\Windows\Installer\bfb379.msi
    MSI (s) (10:4C) [15:10:52:631]: Package we're running from ==> C:\Windows\Installer\bfb379.msi
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall Flags override found.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90150000-012C-0000-0000-0000000FF1CE}'.
    MSI (s) (10:4C) [15:10:52:645]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (10:4C) [15:10:52:649]: Opening existing patch 'C:\Windows\Installer\bfb3d2.msp'.
    MSI (s) (10:4C) [15:10:52:650]: Opening existing patch 'C:\Windows\Installer\bfb37a.msp'.
    MSI (s) (10:4C) [15:10:52:650]: Opening existing patch 'C:\Windows\Installer\bfb386.msp'.
    MSI (s) (10:4C) [15:10:52:651]: SequencePatches starts. Product code: {90150000-012C-0000-0000-0000000FF1CE}, Product version: 15.0.4569.1506, Upgrade code: {00150000-012C-0000-0000-0000000FF1CE}, Product language 0
    MSI (s) (10:4C) [15:10:52:652]: Note: 1: 2205 2: 3: MsiPatchMetadata
    MSI (s) (10:4C) [15:10:52:652]: SequencePatches returns success.
    MSI (s) (10:4C) [15:10:52:652]: Final Patch Application Order:
    MSI (s) (10:4C) [15:10:52:652]: {27D7A8D0-8E28-4A2A-A1D4-473E31DF6438} -
    MSI (s) (10:4C) [15:10:52:652]: {73E81413-5A7E-40A3-9BD5-821ADDF30B10} -
    MSI (s) (10:4C) [15:10:52:652]: {D448DFE1-B83E-4394-9484-25563EFBF58D} -
    MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'DisablePatch' is 0
    MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (10:4C) [15:10:52:652]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (10:4C) [15:10:52:653]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (10:4C) [15:10:52:653]: Looking for patch transform: 90006E0401000015.0.4569.1506
    DEBUG: Error 2746: Transform 90006E0401000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0401-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:653]: Skipping validation for patch transform #90006E0401000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:653]: Looking for patch transform: 90006E0401000015.0.4420.1017
    1: 2746 2: 90006E0401000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0401-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0401000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0401-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:654]: Skipping validation for patch transform #90006E0401000015.0.4420.1017. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:654]: Looking for patch transform: 90006E0402000015.0.4481.1005
    1: 2746 2: 90006E0401000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0401-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:654]: Skipping validation for patch transform #90006E0402000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:654]: Looking for patch transform: 90006E0402000015.0.4569.1506
    1: 2746 2: 90006E0402000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0402000015.0.4505.1008
    1: 2746 2: 90006E0402000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0402000015.0.4454.1509
    1: 2746 2: 90006E0402000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0402000015.0.4454.1509 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0402-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:655]: Skipping validation for patch transform #90006E0402000015.0.4454.1509. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:655]: Looking for patch transform: 90006E0405000015.0.4481.1005
    1: 2746 2: 90006E0402000015.0.4454.1509 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0402-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4569.1506
    1: 2746 2: 90006E0405000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4505.1008
    1: 2746 2: 90006E0405000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:656]: Skipping validation for patch transform #90006E0405000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:656]: Looking for patch transform: 90006E0405000015.0.4454.1004
    1: 2746 2: 90006E0405000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0405000015.0.4454.1004 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0405-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0405000015.0.4454.1004. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4481.1005
    1: 2746 2: 90006E0405000015.0.4454.1004 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0405-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0406000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4569.1506
    1: 2746 2: 90006E0406000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:657]: Skipping validation for patch transform #90006E0406000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:657]: Looking for patch transform: 90006E0406000015.0.4433.1507
    1: 2746 2: 90006E0406000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4433.1507 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0406000015.0.4433.1507. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0406000015.0.4505.1008
    1: 2746 2: 90006E0406000015.0.4433.1507 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0406000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0406-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0406000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0407000015.0.4569.1506
    1: 2746 2: 90006E0406000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0406-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0407000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0407-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:658]: Skipping validation for patch transform #90006E0407000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:658]: Looking for patch transform: 90006E0407000015.0.4420.1017
    1: 2746 2: 90006E0407000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0407-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0407000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0407-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:659]: Skipping validation for patch transform #90006E0407000015.0.4420.1017. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:659]: Looking for patch transform: 90006E0408000015.0.4481.1005
    1: 2746 2: 90006E0407000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0407-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4481.1005 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:659]: Skipping validation for patch transform #90006E0408000015.0.4481.1005. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:659]: Looking for patch transform: 90006E0408000015.0.4569.1506
    1: 2746 2: 90006E0408000015.0.4481.1005 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0408000015.0.4505.1008
    1: 2746 2: 90006E0408000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4505.1008 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4505.1008. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0408000015.0.4454.1004
    1: 2746 2: 90006E0408000015.0.4505.1008 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0408000015.0.4454.1004 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0408-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:660]: Skipping validation for patch transform #90006E0408000015.0.4454.1004. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:660]: Looking for patch transform: 90006E0409000015.0.4569.1506
    1: 2746 2: 90006E0408000015.0.4454.1004 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0408-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0409000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0409-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:661]: Skipping validation for patch transform #90006E0409000015.0.4569.1506. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:661]: Looking for patch transform: 90006E0409000015.0.4420.1017
    1: 2746 2: 90006E0409000015.0.4569.1506 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0409-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0409000015.0.4420.1017 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0409-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000FF1CE}.
    MSI (s) (10:4C) [15:10:52:661]: Skipping validation for patch transform #90006E0409000015.0.4420.1017. Will not apply because previous transform was invalid
    MSI (s) (10:4C) [15:10:52:661]: Looking for patch transform: 90006E0C0A000015.0.4569.1506
    1: 2746 2: 90006E0409000015.0.4420.1017 3: C:\Windows\Installer\bfb379.msi 4: {90150000-006E-0409-0000-0000000FF1CE} 5: {90150000-012C-0000-0000-0000000FF1CE}
    DEBUG: Error 2746: Transform 90006E0C0A000015.0.4569.1506 invalid for package C:\Windows\Installer\bfb379.msi. Expected product {90150000-006E-0C0A-0000-0000000FF1CE}, found product {90150000-012C-0000-0000-0000000
    MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:072]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:072]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:073]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:073]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:074]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:074]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:074]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:074]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:075]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:075]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:076]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:076]: Transforming table Error.
    MSI (s) (10:20) [15:16:59:076]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (10:20) [15:16:59:076]: Produkt: Microsoft Lync 2013 -- Das Entfernen ist fehlgeschlagen.
    MSI (s) (10:20) [15:16:59:077]: Das Produkt wurde durch Windows Installer entfernt. Produktname: Microsoft Lync 2013. Produktversion: 15.0.4569.1506. Produktsprache: 0. Hersteller: Microsoft Corporation. Erfolg- bzw. Fehlerstatus der Deinstallation: 1603.
    MSI (s) (10:20) [15:16:59:079]: Attempting to delete file C:\Windows\Installer\bfb5a2.mst
    MSI (s) (10:20) [15:16:59:085]: Deferring clean up of packages/files, if any exist
    MSI (s) (10:20) [15:16:59:085]: Attempting to delete file C:\Windows\Installer\bfb5a2.mst
    MSI (s) (10:20) [15:16:59:085]: Unable to delete the file outside of the engine. LastError = 2
    MSI (s) (10:20) [15:16:59:085]: MainEngineThread is returning 1603
    MSI (s) (10:4C) [15:16:59:089]: RESTART MANAGER: Session closed.
    MSI (s) (10:4C) [15:16:59:089]: No System Restore sequence number for this installation.
    === Protokollierung beendet: 24.11.2014 15:16:59 ===
    MSI (s) (10:4C) [15:16:59:090]: User policy value 'DisableRollback' is 0
    MSI (s) (10:4C) [15:16:59:090]: Machine policy value 'DisableRollback' is 0
    MSI (s) (10:4C) [15:16:59:090]: Incrementing counter to disable shutdown. Counter after increment: 0

    2014/11/24
    14:49:36:136::[4844]
    Error: Product
    is not installed, therefore transition to
    MMode is unsafe
    for product: LYNCENTRY
    Type: 27::InstalledProductStateCorrupt.
    2014/11/24
    14:49:36:136::[4844]
    Not showing message because suppress modal has been
    set.  Title:
    'Setupfehler', Message:
    'Diese Produktinstallation wurde besch..digt. F..hren Sie Setup erneut von der CD, DVD oder einer anderen urspr..nglichen Installationsquelle aus.'
    From the snippet of the log, it appears that the product installation has been corrupted. Probably, try to repair it from Control Panel first and then test the command again?
    Also, is it Microsoft Lync Basic 2013?
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • The installation of this package failed" error while installing Nov 2013 CU (KB 2889944) for SharePoint 2013

    Hi,
    I'm currently installing Nov CU on my Sharepoint 2013 farm, I have 2 APPS and 2 WFE. I successfully installed the patch in 3 servers however, I got this error "The installation of this package failed” in one of my server.
    Now i cant run the configuration wizard because it of this error.
    Any advise how on to solve this issue? it's giving me headache the whole day already.
    thanks!
    JD

    Hi Trevor,
    Thank you for your reply, I just want to share with you what i found in the msi logs.
    DEBUG: Error 2746:  Transform 9010F70000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10F7-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010F70000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010F70000100015.0.4420.1017
    1: 2746 2: 9010F70000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-10F7-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010F70000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10F7-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010F70000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010FB0000100015.0.4454.1510
    1: 2746 2: 9010F70000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-10F7-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010FB0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10FB-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010FB0000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 9010FB0000100015.0.4420.1017
    1: 2746 2: 9010FB0000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-10FB-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 9010FB0000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-10FB-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:466]: Skipping validation for patch transform #9010FB0000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:466]: Looking for patch transform: 90107F0000100015.0.4454.1510
    1: 2746 2: 9010FB0000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-10FB-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 90107F0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-107F-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:482]: Skipping validation for patch transform #90107F0000100015.0.4454.1510.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:482]: Looking for patch transform: 90107F0000100015.0.4420.1017
    1: 2746 2: 90107F0000100015.0.4454.1510 3: C:\Windows\Installer\27476d.msi 4: {90150000-107F-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2746:  Transform 90107F0000100015.0.4420.1017 invalid for package C:\Windows\Installer\27476d.msi. Expected product {90150000-107F-0000-1000-0000000FF1CE}, found product {90150000-104B-0000-1000-0000000FF1CE}.
    MSI (s) (A8:10) [14:34:35:482]: Skipping validation for patch transform #90107F0000100015.0.4420.1017.  Will not apply because previous transform was invalid
    MSI (s) (A8:10) [14:34:35:482]: Looking for patch transform: 90104B0000100015.0.4454.1510
    1: 2746 2: 90107F0000100015.0.4420.1017 3: C:\Windows\Installer\27476d.msi 4: {90150000-107F-0000-1000-0000000FF1CE} 5: {90150000-104B-0000-1000-0000000FF1CE} 
    DEBUG: Error 2749:  Transform 90104B0000100015.0.4454.1510 invalid for package C:\Windows\Installer\27476d.msi. Expected product version == 15.0.4454.1510, found product version 15.0.4420.1017.
    I hope you can help me shed light on this.
    Regards,
    JD

  • Error in IMPORT PACKAGE!

    Hello there!
    Just to ask if somebody knows about the error "No match defined for the lookup dimension CATEGORY", I get this error when I execute the import package.
    I have to tell you that I created a copy from the CATEGORY dimension to a new called CATEGORIA, this new dimension is of category type, I have changed into the System_Constans file the line:
    *FUNCTION CATEGORYDIM         =%CATEGORIA_DIM%
    If somebody could help me into this error, I would be appreciate.
    Regards

    I did the data manager validation using the Transformation File and the data file used at the time to do the import, there are no errors everything is fine, all records are acepted abd there are no reject.
    Running the Import package, there are no rejected records, all of them are acepted, but and error is happening into the detail log (at the end)  the error "No match defined for lookup dimension CATEGORY".
    Regards

Maybe you are looking for

  • Purchase Price for the Material

    Hello World of SAP, Hallo Welt von SAP, Is there any report in standard SAP for Material Purchasing Price? Basically I'm using table EINA and EINE to check that purchase price, if the MAP price i check in MBEW.

  • MBA or MBP? can't decide

    I've been using a MBP 2.2 for 2 years now and want to get another mac but I can't decide. I've heard the MBA overheats a lot and no multitouch. The only thing attractive is the size. New MBP has better battery life, don't know about the overheating i

  • PO History qty invisible

    DEar All, For the past  4 months it is been observed that for all service POs after creating service entry sheet and after GRN PO history gets updated without qty. When i check last decemeber month POs in ME23N PO History sytem is showing document nu

  • MAX Simulated Device SCXI-1001

    I open "Measurement and Automation Explorer". Right click on "Device and Interfaces". Select "Create New". Select "NI-DAQmx Simulated Device". Press "Finish". Expand "SCXI Chassis". Select "NI SCXI-1001". Press "OK". Window "Create New SCXI Chassis"

  • Photoshop CC lagging - moving layers, video

    Here is my problem: https://www.youtube.com/watch?v=bCMbASsil7Y Any solutions? I need help with lagging. Moving layers with move tool (time: 1:26). Any solutions? PSD only 40MB. Not helped: - Task manager process to High - Switch off integrated video