ACR modifications not reflected in bridge

Hello,
  Off and on my ACR changes are not being reflected in the bridge content thumbnails nor the preview.  It is currently happening all the time (year change?) but it was happening sporadically previous to this (sorry, not very helpful information).  I open the RAW file in ACR by double-clicking on the thumbnail in bridge, change the various settings,click on done or edit further in PS.  When I go back to bridge none of the ACR modifications are there.  If I re-open the file in ACR the changes are still there.  I have cleaned-out the cache and the dates on the xmp file are later than the ones on the CR2 file.
Windows Vista (:still)
CS5
Canon 5D Mark II
Thanks in advance for you help.

Reference for anyone else having the same problem ...  I updated to the latest version of PS, Bridge and ACR and the problem seems to be resolved.  It may be because of the updated files or it may be because some settings were changed back to the way they used to be.

Similar Messages

  • ACR Plugins not working and Bridge won't view cr2 files

    Hey there.. I've been using Photoshop/Bridge/ ACR for 7 years now but from memory I have had this issue before when installing.
    My laptop just got a new hard drive and fan and I've had to reinstall everything.
    I downloaded 3 different ACR plugins and none of them have enabled Camera Raw reading for bridge.
    I'm using CS6 with Canon 5dmk2 cr2 files.
    I have tried 7.1
    Adobe - Adobe Camera Raw and DNG Converter : For Windows : Camera Raw 7.1 Update
    I have tried 6.7
    Adobe - Adobe Camera Raw and DNG Converter : For Windows : Camera Raw 6.7.1 Update
    I've tried this link
    Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.8
    and I've tried a Microsoft codec pack somebody else suggested
    Download Microsoft Camera Codec Pack (6.3.9721.0) from Official Microsoft Download Center
    Please help....

    The 5D2 only needs ACR 5.2 or newer so your current version of ACR 7.1 should open the files.
    If ACR isn’t enabled in Bridge then the usual thing is to launch Photoshop and open a raw file at least once without using Bridge, with File / Open or PS / Open.
    Doing Help / Updates from PS should install the latest ACR version for you in case that helps.
    You can also try installing ACR manually.
    If you have a newer OS like Windows 7+ or OSX 10.8+ then try ACR 8.8 is what you want to install:
    https://helpx.adobe.com/x-productkb/multi/camera-raw-plug-in-installer.html
    If you have an older OS like Windows Vista or OSX 10.6.8 then ACR 8.3 is what you want an installer further down on this page:
    https://helpx.adobe.com/x-productkb/multi/camera-raw-84-support-policy.html

  • Essbase member modifications not reflecting in OBIEE after a refresh

    Hi ,
    I am getting the following message in my developed reports , after changing certain member names (adding / removing members also) of ENTITY dimension in essbase .
    [nQSError: 96002] Essbase Error: Unknown Member Total India Entity 1 used in query (HY000)
    After selecting the renamed members only the report is working , i.e from specified ENTITY report filters I had to select , Total India (old name : Total India Entity 1) .
    Reload server metadata or refresh is not helping ... Is there any setup , which will directly reflect these changes in dashboard without repeatedly selecting new members in analysis .
    OBIEE version : 11.1.1.6
    Essbase version : 11.1.2.1
    Thanks
    Sayak

    Hi ,
    thanks for responding .
    Just to clarify my question :
    I have a dimension named ENTITY , it has several generation under it (gen1,gen2,gen3 etc .) .
    for example , gen1 has member total region and no region .
    gen2 has UK and US region .
    gen 3 has manchester , london , new york , manhatton .
    In the report i'm using ENTITY .gen3 = manchester , london , new york , manhatton ..... this filter.
    Now , I am renaming (changing) gen 3 members like liverpool , birmigham , california , washington .
    So , after refreshing dashboard , will these member names automatically gets refreshed or i have to again manullay select them ?

  • Changes made in LR 1.3 to psd files are not reflected in ACR 4.3, Bridge 2.1.1.9, or Photoshop CS3

    I have repeatedly imported several psd images into LR 1.3, made changes in the develop mode, and saved metadata to file manually in addition to having the auto write metadata option on in LR and ACR. Any changes I have made in LR are not reflecting in Bridge previews or in ACR or Photoshop. I don't believe I should have to utilize the write to xmp options (even though I have been) since the files in question are psd and the metadata gets written directly into the file. If I delete the photo from LR, and even delete the LR catalog (new user trying to make it work with 1 photo at least before importing all images) and re-import the psd to LR it appears with the changes and can backlog in the history panel to it's original state upon import into LR. I would have to be in LR though to know that anything was altered as the other Adobe programs will not display the changes.
    If anyone has any help - I would greatly appreciate it!
    Thanks,
    Ann
    System=
    160 GB hard drive
    Intel core duo T7500
    2 GB Ram
    Windows Vista 32 bit
    ACR 4.3
    LR 1.3
    Bridge 2.1.1.9
    PS CS3 (updated last week)

    I don't think the problem lies in the name. LR is after all meant to function as a data base of images and be a companion program to PS - with PS doing the heavy editing lifting. I do understand that PS is a pixel editing file and LR is not. I like the idea of the non-destructive editing that LR has to offer and for a lot of image "developing" I prefer LR's interface to ACR.
    In my humble opinion, I just think that the Photoshop family of products should all be able to read the same metadata. If I am starting in LR with a psd file (with layers) and I continue to process the image further in LR and save the metadata - therefore saving the changes - I want to be able to open that same file (not another copy) in ACR, PS, or Bridge and have those changes reflected. The only way to do that currently is to export the file and when you do that you lose the PS layers and the LR history panel or another way around it is you can have edit copies of the same file. If at a later date you wanted to go back and change something, you can't just pull out a layer in PS or undo a history state in LR and with the multiple copies of essentially the same image you end us with any editing history scattered amongst multiple files. I already keep 2-4 (original, psd, jpeg print, jpeg web) files for one image which I think is more than adequate. Which is why I find the current set up so frustrating. For now I have just settled for exporting jpegs so I can see the changes.

  • Metadata edited in Bridge is not reflected in the Info Dialogue Box, but shows up in Photoshop.

    Metadata edited in Bridge is not reflected in the Info Dialogue Box, but shows up in Photoshop.

    Dear Ramón,
    You are right that not all metadata is shown in the Finder info but in my case the once added in IPTC core do show as expected for most file types (but not CR2 raw). As you now I convert my CR2 to DNG for a long time now I had to look up the original Raw file and create the data for description, location, keywords again. The data you can add and alter yourself in the IPTC Core field. I added a series of screenshots showing different info and to my surprise (another reason to keep to DNG…) the Raw file had very less info and the xmp shows it all in a rather long and obscure way. Yet PSD, DNG and File info in PS show the same.
    Could not recreate the Bridge metadata workspace from the OP because mine (Bridge CC) does not have the description field as an option anymore for some obscure reason. Also checked this in my CS6 version with same result, making the metadata workspace unusable but that was it already for a long time.
    Still leaves us with the problem the OP showed, having all info in most files, as in Finder info, but not in Bridge. So could the OP respond to the purge cache for selection option in post 4?
    Here are (a bit to many, sorry) my screenshots showing different file info (in Dutch but you will manage with that) and metadata in Bridge:
    Finder info for PSD and DNG:
    Finder info for CR2 and XMP:
    File info Bridge / PSD:
    And a Bridge Metadata view:

  • NEF Thumbnails not displaying in Bridge CS3

    I decided to dip my toe into RAW images. However unlike jpegs and tiffs the NEF thumbnails are not rendering in Bridge CS3. However when I double-click on an unrendered thumbnail it does open normally. As seeing thumbnails would be very helpful I decided to do a software update to see if this would cure the problem. During the install process I got the following message - Installation Incomplete - The Updater is unable to locate the product to be updated - Adobe Camera Raw 4.6 Update failed to install.
    Outcome - NEF thumbnails still not rendering.  By the way my NEF images were produced on a Nikon D60.
    Help would be appreciated. Thanks in anticipation. Victor Patterson, Ireland

    This is the Photoshop Elements forum.
    Sounds like you need the ACR or Photoshop or Bridge fora. select from this link:-
    http://forums.adobe.com/community/photoshop?view=overview
    It may be worth starting with this link:-
    http://kb2.adobe.com/cps/407/kb407110.html

  • New Nikon Df camera RAW files not recognized in Bridge and Photoshop.

    New Nikon Df camera RAW files not recognized in Bridge and Photoshop.  Is there a fix?  Surely Adobe make a mistake and not keep up with Nikon.

    I looked at the current list http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html and did not see the Nikon DF listed.
    Would post in ACR forum and see if they know anything more.  http://forums.adobe.com/community/cameraraw

  • Adobe Camera Raw changes not reflecting in Premiere Pro

    I was super excited to try out the new CNDG support in Premiere Pro CC 2014, but I have to be honest - I am a bit disappointed...
    I am using 16bit Cinema DNG files and the source settings sliders really aren't doing it for me (notice the pink highlights)
    That's alright though, I would much rather use Adobe Camera Raw!
    Right click > Edit Original
    There we go, that looks nice - no pink highlights, nicely recovered details in the shadows and highlights. 
    PERFECT, click DONE!
    Nothing...For whatever reason, changes are not reflecting.
    Adobe - please allow us to use Adobe Camera Raw, there are so many folks out there that want to incorporate it into their workflow.  I have tried SpeedGrade and various other color correcting tools and I have found Adobe Camera Raw to work the best IMHO
    Thank you for your time.
    -Loyal Paying Customer

    Hi Ekombokom,
    ekombokom wrote:
    Hello! I too am having this same problem. I used Camera Raw (both in Bridge and Photoshop to make sure) to adjust and correct the Cinema DNG files I shot with my BMPCC; however, the video sequence in Premiere does not reflect any of the changes made. Why would Adobe not support Camera Raw settings in Premiere?
    Sorry, but Premiere Pro does not have a camera raw importer. You adjust the settings in the Source Settings dialog box instead (for RED, ARRI Raw, BMCC and BM Pocket Camera DNG files). You do have access to some controls for these formats, but in some cases, Camera Raw has more controls.
    ekombokom wrote:
    Camera Raw is an amazing tool for refining an image and gives me the best results compared to SG and Davinci. I was so excited to be able to use it once Premiere supported CinemaDNGs but now I'm confused as to why it's not supported.
    Cinema DNG from the Blackmagic Cameras are supported, you just adjust settings in Source Settings, as I mentioned. Have you tried that? The reasoning behind this is that Cinema DNG video coming from camera raw is too difficult to playback and edit with.
    That said, some users bring Cinema DNG footage to After Effects, adjust the video there, then render out files that are suitable to edit with.
    ekombokom wrote:
    I thought the point of using Adobe was that all their products worked together seamlessly? I really hope they fix this.
    You can always make a request here: http://adobe.ly/feature_request, however, I don't see a camera raw importer going into Premiere Pro any time soon (if ever) because of the reasons I previously mentioned (editing with camera raw would be too cumbersome). I think the more realistic feature request would be to add more controls in Source Settings.
    Thanks,
    Kevin

  • .xmp not recognized by Bridge CS 5.5.  All previous solutions here not working for me.  Please help.

    First of all, this issue has existed for me since CS4.
    When I load an .nef file into photoshop from bridge, it opens in camera raw.  Once I edit that photo and send it to photoshop, an .xmp file is created and those changes should show up in bridge, but they don't.  Looking in my folder of raw files, I can see the .xmp file.
    To make matters more confusing, this only occurs with one of my two cameras.  I have two seemingly identical Nikon D300s DSLRs.  One with a 14mm and one with a 70-200 zoom.  Bridge's issue with failing to recognize .xmp files only occurs with folders that contain photos shot with the camera with the zoom lens.
    I have exhausted all of the solutions I have been able to find on this forum: telling my mac to open .xmp files with Bridge, telling Bridge to always use high quality thumbnails with 100% preview.
    Can someone please help?

    I have exhausted all of the solutions I have been able to find on this forum: telling my mac to open .xmp files with Bridge, telling Bridge to always use high quality thumbnails with 100% preview.
    For several years ago I decided to convert all my CR2 Raw files (I use Canon) to DNG upon ingestion of the files. Not only is DNG an open standard and therefor will it be long supported but mainly because I was growing mad of all the side car XMP files. DNG stores the XMP info into the file itself. No more hidden files no more mistakes in copy files leaving XMP lost in a folder, etc. etc.
    Although it is strange one dSLR has this problem and the other not I don't think it is lens related as Curt kindly suggested. To my knowledge lenses affect the EXIF data and Bridge creates the XMP Data as a sidecar file (by default selected in the Camera Raw preferences) with rating, labeling and ACR settings.
    By default Bridge also does not show hidden items (that XMP files are). Could you double check with Raw files from both cameras next to each other and after having altered them both in ACR (i.e. plus 2 in exposure to make a real difference) and in the Bridge menu view show hidden files (sort Bridge on filename for easy viewing).
    And if one is not showing the altered result could you click on it and with right mouse click menu check 'purge cache for selection and see if this changes things.  (If the changes are there in PS as Curt already asked this might also help)
    Could you also convert both files to DNG (Adobe has a free DNG converter for download (see also this link or Google it):
    http://www.adobe.com/products/photoshop/extend.displayTab2.html
    And could you provide a short summary of the solutions you already tried (all previous solutions is a little vague :-) )
    Having set XMP to open in Bridge is not important, XMP is not meant to be opened by the user, Bridge uses it to read and write but other apps also. For instance I just tested on an old CR2 file with XMP and by default it opens in Adobe Photoshop Elements (also on my system like CS5 Suite, Aperture and Lightroom) as I discovered using the get info command. Bridge wasn't even on the list for possible opening options :-)
    Also 100 % preview will not help, it just slows things down very much because the cache needs much more time to build and the cache file will grow to huge proportions...
    Only if you want to use to compare all files at 100 % you might benefit from that setting.

  • Files from Windows Vista do not open in Bridge CS5

    I am having trouble opening my images from Window Explorer level with Bridge.
    I tried to open my jpgs with "open with" option  and my PC does nothing. Same happens when I double click the raw images.
    I have my jpgs assigned to open in windows but I assigned my raw files to open in Bridge CS5 unfortunately raws will not open after double click.
    Can someone help?
    Thanks

    Perhaps it is just semantics, but you want the double click to open in Photoshop CS5 and not Bridge.  Same thing with the raw it should open in ACR and not Bridge, as Bridge is just a browser.
    With your raw problem.  If you open photoshop and click help/about plug-in/camera raw you should get one version listed.  Most camera raw problems result from ACR in wrong folder, or more than one version in the folder.

  • Changes in Crystal reports are not reflecting after publishing

    Dear SDN Mates,
    We are facing problem with Crystal reports. After making the changes in the crystal reports, it is not reflecting in the portal after publishing. Still it is showing the older version of the report.
    Can anyone please help me on this.
    Thanks and Regards
    Arun S

    Hello Prathamesh,
    After publishing the report, we require some changes in the report and doing some modifications in crystal report and again we are publishing this report. After publishing the report for second time, those changes are not reflecting in the BOE portal.
    This is happening for all reports. Can you please suggest me on this.
    Thanks and regards
    Arun S

  • Changes made to files are not reflecting

    File updates not reflected. I modified content, added data validation and saved the file back - next day file is still the way it was before modification.
    Other file, another site but similar situation.
    Content changed - form added but next day the change is not reflected.
    SharePoint 2013
    Please help.
    Thanks
    Pj

    HI Alex,
    Answers to your questions inline below:
    So you are editing a file, modifying the content in there and saving it but the changes are being lost?
    Ans: Yes.
    1. Have you checked the file immediately after closing it to see if the changes lasted?
    Ans: I am not sure, if I checked the files immediately after. I think the changes were saved properly because I didn't get any error.
    I managed to print out a file with a new element on one day but on the next day in the same file, I saw that element was not there.
    I sometimes open the files through the Newsfeed tab, does that matter? My understanding is that the system is going to the original location to open the file
    2. Do the changes then disappear later that day at some point?
    Ans: That is my understanding.
    3. Does this happen just for those files?
    Ans: So far I have observed it for two of the files only.
    4. Do you have versioning or publishing enabled on those lists? Versioning will let you see who changed it when and approval or publishing might be hiding things?
    Ans: Versioning is enabled, publishing - not.
    When I go to check versions to see, if maybe someone overwritten my change and retrieve the previous version, there is no previous version with the changes i made
    the previous day.
    Thanks.

  • ACR 6.3RC still makes Bridge display some TIFFs & JPGs overexposed

    I had the same problem with TIFFs & JPGs after upgrading from ACR 6.1 to 6.2. My system is Win 7x64 and, of course, PsCS5 and Bridge 4.0.39. This time the upgrade was from ACR 6.1 to 6.3RC. Not all images are affected. The problem seems to be entirely random. The amount of overexposure seems to be in the order of 1 to 2 stops. The problem is limited in this way for me:
    1. All the affected images display correctly exposed when opened in Ps and ACR 6.3RC (and ACR 6.2) hosted by Bridge.
    2. Only TIFFs & JPGs (both B&W and Colour) "derived" ultimately from original TIFF scans (both B&W and Colour) made on a Nikon SuperCoolscan 5000 ED are affected. The original TIFF scans (99.99% are 16-bit) are all unaffected.
    3. The problem does not occur with any TIFF or JPG file derived from native CRW or NEF raw files or from native JPG files produced in-camera (Canon EOS 300D and Nikon D700), all of which are themselves unaffected.
    4. It does not matter were you might be in an image editing process. Some intermediate edits to TIFFs (I never make intermediate JPG edits) are affected, others are not. Editing might start with the TIFF and continue with edits to the TIFF, and only some of the subsequent TIFFs (or final JPGs derived from them) are affected. For example, there might be 6 distinct edits to a TIFF and only edits 3 through 6 are affected. Editing might procede immediately from the original TIFF scan to PSD, finalise with PSD, and then, AND sometimes only, any TIFF or JPG made from the final, flattened PSD produces a file which Bridge will display overexposed. Only some files in a batch of scans, all made at the same time and under exactly the same conditions (almost always with no adjustments made with the Nikon scanning software), are ever affected - never all of them.
    5. Some of the edits to the original TIFF scans (where the edits were kept as TIFFs) were made with Picture Window Pro, some with Lightroom 1.3 (I think), some with ACR 4.x, ACR 5.x, but most were made with PS CS3, CS4 and CS5: it does not matter, there are some affected files from each. The problem certainly does occur with files which have never been opened, let alone edited, in any version of ACR.
    6. I have several instances where simply making a copy of a TIFF scan in another folder (whether the copy was made by Bridge or with Windows Explorer has no influence) results in the copy only and not the original being displayed overexposed.
    7. If a file is affected, all TIFFs AND all JPGs derived from it will be overexposed, never just one or the other.
    The overexposure problem detailed above does not occur with ACR 6.1. All the files affected by ACR 6.2 and 6.3RC are displayed with correct exposure by Bridge when ACR 6.1 is installed.
    I'm at a complete loss to understand what is going on. Any suggestions would be most welcome.
    Has anyone else who was experiencing the Bridge/overexposure problem with either ACR 6.2 or 6.3RC found a solution?

    This will be posted in both the ACR and Bridge User Forums
    I've done some experimentation and found a workaround for, not the solution to, my problem with ACR 6.2 and 6.3RC causing Bridge to display random TIFFs and JPGs overexposed.
    This is a temporary, and, if you have lots of affected files, a very laborious, individual file workaround. Unless Adobe investigates, finds and corrects the cause of the problem, it seems likely to re-occur. Only fixing the cause of the problem (which must lie in the new (different from ACR 6.1) code of ACR 6.2 and 6.3RC) could be be truly regarded as a solution.
    Here is how I enabled Bridge to display my affected TIFFs and TPGs correctly, that is, with no amount of overexposure. These steps apply equally to B&W and Colour images.
    For a 16-bit TIFF, duplicate it in Bridge (Edit/Duplicate) and then open the duplicate in ACR 6.2 or 6.3RC (ACR) hosted by Bridge. Make sure that all the sliders are zeroed in the Main panel and that the Amount slider in the Sharpening section of the Details panel is also set to zero (to avoid unwanted additional sharpening). Then open the image in Photoshop (Ps) and immediately save the image (Save As) over itself (yes, you're replacing the file) back in the folder from which you opened it into ACR, making sure to choose no compression. The resaved duplicate will now be displayed with its proper exposure in Bridge, and any further TIFFs or JPGs (whether 16-bit or 8-bit) derived from this file will also be displayed correctly. Following this procedure, my invariable experience is that I end up with a TIFF either the same size as or smaller than the affected TIFF.
    Why no compression? Strangely, if you choose LZW compression (really the only logical alternative to "None") you end up with a larger file than you get with no compression. I have no idea why. Why not simply fix the affected file instead of a duplicate? No reason really, other than safety. If things go belly-up you still have your original, albeit, affected file. I also intend to keep my affected files for awhile just in case of some possible desire or need to re-examine them in the future.
    For an 8-bit TIFF, although I don't have any which are affected, the procedure would be the same as for a 16-bit TIFF. You will need to conduct your own tests regarding compression/no compression and the resulting file size.
    For a JPG, the procedure is pretty much the same (duplicating, opening in ACR, zeroing all sliders, opening in Ps and then saving over itself) but when saving try choosing Maximum Quality (12) which mostly, for me at least, produces a replacement JPG the same size as the original affected file. Of course, you can choose a greater level of compression if you wish, and my tests show that this will not adversely affect the outcome. You can use the replacement JPG to produce further, derivative 8-bit TIFFs or JPGs and all will display properly exposed in Bridge.

  • DNG image not appearing in Bridge CS6

    When I open Bridge on my laptop I find that instead of images from the DNG files appearing, what I get are small icons having DNG and a camera iris.  This happened after I reinstalled the CS6 program. (I managed to lose the icuuc40.dll file and received a message advising to reinstall the program). 
    I use my laptop when travelling.  I download all files from the camera onto it and view them in Bridge.  After returning home I transfer the files to the PC desktop for processing etc..  Bridge is working normally on the desktop.
    Assistance in sorting matters will be greatly appreciated.
    Andre Barallon

    Thanks for your e-mail telling that Adobe Camera Raw (ACR)may not be
    installed at the default location, and asking for contents of system
    info.  These are set out below.
    Regards,
    Andre Barallon
    Adobe Photoshop Version: 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:7, Stepping:10 with MMX,
    SSE Integer, SSE FP, SSE2, SSE3
    Physical processor count: 2
    Processor speed: 2294 MHz
    Built-in memory: 3964 MB
    Free memory: 2105 MB
    Memory available to Photoshop: 3374 MB
    Memory used by Photoshop: 60 %
    Image tile size: 128K
    Image cache levels: 4
    OpenGL Drawing: Enabled.
    OpenGL Drawing Mode: Basic
    OpenGL Allow Normal Mode: False.
    OpenGL Allow Advanced Mode: False.
    OpenGL Allow Old GPUs: Not Detected.
    Video Card Vendor: Intel
    Video Card Renderer: Mobile Intel(R) 4 Series Express Chipset Family
    Display: 1
    Display Bounds:=  top: 0, left: 0, bottom: 768, right: 1366
    Video Card Number: 2
    Video Card: Mobile Intel(R) 4 Series Express Chipset Family
    OpenCL Unavailable
    Driver Version: 8.15.10.2086
    Driver Date: 20100220000000.000000-000
    Video Card Driver: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32
    Video Mode:
    Video Card Caption: Mobile Intel(R) 4 Series Express Chipset Family
    Video Card Memory: 1854 MB
    Video Rect Texture Size: 4096
    Video Card Number: 1
    Video Card: Mobile Intel(R) 4 Series Express Chipset Family
    OpenCL Unavailable
    Driver Version: 8.15.10.2086
    Driver Date: 20100220000000.000000-000
    Video Card Driver: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32
    Video Mode: 1366 x 768 x 4294967296 colors
    Video Card Caption: Mobile Intel(R) 4 Series Express Chipset Family
    Video Card Memory: 1854 MB
    Video Rect Texture Size: 4096
    Serial number: 91198445225883318064
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64
    Bit)\
    Temporary file path: C:\Users\Andre\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
       Startup, 78.0G, 23.2G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6
    (64 Bit)\Required\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64
    Bit)\Plug-ins\
    Additional Plug-ins folder: not set
    Installed components:
        A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
        ACE.dll   ACE 2012/06/05-15:16:32   66.507768   66.507768
        adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012  
    66.1025012
        AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
        AdobeOwl.dll   Adobe Owl 2012/06/26-12:17:19   4.0.95   66.510504
        AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
        AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
        AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661  
    66.145661
        AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661 
    66.145661
        AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27  
    66.145661   66.145661
        adobe_caps.dll   Adobe CAPS   6,0,29,0
        AGM.dll   AGM 2012/06/05-15:16:32   66.507768   66.507768
        ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
        aif_core.dll   AIF   3.0   62.490293
        aif_ocl.dll   AIF   3.0   62.490293
        aif_ogl.dll   AIF   3.0   62.490293
        amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0;
    BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
        ARE.dll   ARE 2012/06/05-15:16:32   66.507768   66.507768
        AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830
      66.26830
        AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830  
    66.26830
        Bib.dll   BIB 2012/06/05-15:16:32   66.507768   66.507768
        BIBUtils.dll   BIBUtils 2012/06/05-15:16:32   66.507768   66.507768
        boost_date_time.dll   DVA Product   6.0.0
        boost_signals.dll   DVA Product   6.0.0
        boost_system.dll   DVA Product   6.0.0
        boost_threads.dll   DVA Product   6.0.0
        cg.dll   NVIDIA Cg Runtime   3.0.00007
        cgGL.dll   NVIDIA Cg Runtime   3.0.00007
        CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
        CoolType.dll   CoolType 2012/06/05-15:16:32   66.507768   66.507768
        data_flow.dll   AIF   3.0   62.490293
        dvaaudiodevice.dll   DVA Product   6.0.0
        dvacore.dll   DVA Product   6.0.0
        dvamarshal.dll   DVA Product   6.0.0
        dvamediatypes.dll   DVA Product   6.0.0
        dvaplayer.dll   DVA Product   6.0.0
        dvatransport.dll   DVA Product   6.0.0
        dvaunittesting.dll   DVA Product   6.0.0
        dynamiclink.dll   DVA Product   6.0.0
        ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082  
    66.490082
        FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433  
    66.145433
        filter_graph.dll   AIF   3.0   62.490293
        hydra_filters.dll   AIF   3.0   62.490293
        icucnv40.dll   International Components for Unicode
    2011/11/15-16:30:22    Build gtlib_3.0.16615
        icudt40.dll   International Components for Unicode
    2011/11/15-16:30:22    Build gtlib_3.0.16615
        image_compiler.dll   AIF   3.0   62.490293
        image_flow.dll   AIF   3.0   62.490293
        image_runtime.dll   AIF   3.0   62.490293
        JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
        libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
        libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r)
    Fortran Compiler   10.0
        LogSession.dll   LogSession   2.1.2.1640
        mediacoreif.dll   DVA Product   6.0.0
        MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
        msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
        msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
        msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
        msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
        msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
        msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
        msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
        msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
        pdfsettings.dll   Adobe PDFSettings   1.04
        Photoshop.dll   Adobe Photoshop CS6   CS6
        Plugin.dll   Adobe Photoshop CS6   CS6
        PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)  
    3.0.0.383
        PSArt.dll   Adobe Photoshop CS6   CS6
        PSViews.dll   Adobe Photoshop CS6   CS6
        SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
        ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082  
    66.490082
        tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0,
    2010, 0406
        tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3,
    0, 2010, 0406
        TfFontMgr.dll   FontMgr   9.3.0.113
        TfKernel.dll   Kernel   9.3.0.113
        TFKGEOM.dll   Kernel Geom   9.3.0.113
        TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
        updaternotifications.dll   Adobe Updater Notifications Library  
    6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
        WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build
    0.17112   0.17112
        wu3d.dll   U3D Writer   9.3.0.113
    Required plug-ins:
        Accented Edges 13.0
        Adaptive Wide Angle 13.0
        ADM 3.11x01
        Angled Strokes 13.0
        Average 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Bas Relief 13.0
        BMP 13.0
        Camera Raw 7.4
        Chalk & Charcoal 13.0
        Charcoal 13.0
        Chrome 13.0
        Cineon 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Clouds 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Collada 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Color Halftone 13.0
        Colored Pencil 13.0
        CompuServe GIF 13.0
        Conté Crayon 13.0
        Craquelure 13.0
        Crop and Straighten Photos 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00)
        Crop and Straighten Photos Filter 13.0
        Crosshatch 13.0
        Crystallize 13.0
        Cutout 13.0
        Dark Strokes 13.0
        De-Interlace 13.0
        Difference Clouds 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00)
        Diffuse Glow 13.0
        Displace 13.0
        Dry Brush 13.0
        Eazel Acquire 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Embed Watermark 4.0
        Extrude 13.0
        FastCore Routines 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00)
        Fibers 13.0
        Film Grain 13.0
        Filter Gallery 13.0
        Fresco 13.0
        Glass 13.0
        Glowing Edges 13.0
        Grain 13.0
        Graphic Pen 13.0
        Halftone Pattern 13.0
        HDRMergeUI 13.0
        IFF Format 13.0
        Ink Outlines 13.0
        JPEG 2000 13.0
        Lens Blur 13.0
        Lens Correction 13.0
        Lens Flare 13.0
        Liquify 13.0
        Matlab Operation 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Measurement Core 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Mezzotint 13.0
        MMXCore Routines 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Mosaic Tiles 13.0
        Multiprocessor Support 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00)
        Neon Glow 13.0
        Note Paper 13.0
        NTSC Colors 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Ocean Ripple 13.0
        Oil Paint 13.0
        OpenEXR 13.0
        Paint Daubs 13.0
        Palette Knife 13.0
        Patchwork 13.0
        Paths to Illustrator 13.0
        PCX 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Photocopy 13.0
        Photoshop 3D Engine 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00)
        Picture Package Filter 13.0.1 (13.0.1.2 20130522.r.24
    2013/05/22:21:00:00)
        Pinch 13.0
        Pixar 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Plaster 13.0
        Plastic Wrap 13.0
        PNG 13.0
        Pointillize 13.0
        Polar Coordinates 13.0
        Portable Bit Map 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Poster Edges 13.0
        Radial Blur 13.0
        Radiance 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Read Watermark 4.0
        Reticulation 13.0
        Ripple 13.0
        Rough Pastels 13.0
        Save for Web 13.0
        ScriptingSupport 13.0.1
        Shear 13.0
        Smart Blur 13.0
        Smudge Stick 13.0
        Solarize 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Spatter 13.0
        Spherize 13.0
        Sponge 13.0
        Sprayed Strokes 13.0
        Stained Glass 13.0
        Stamp 13.0
        Sumi-e 13.0
        Targa 13.0
        Texturizer 13.0
        Tiles 13.0
        Torn Edges 13.0
        Twirl 13.0
        Underpainting 13.0
        Vanishing Point 13.0
        Variations 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Water Paper 13.0
        Watercolor 13.0
        Wave 13.0
        WIA Support 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        Wind 13.0
        Wireless Bitmap 13.0.1 (13.0.1.2 20130522.r.24 2013/05/22:21:00:00)
        ZigZag 13.0
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
        Mini Bridge
        Kuler
    Installed TWAIN devices: NONE

  • Master data updation not reflected in Bex report

    Hi,
    There is a field "Approver" in a report. It will only show the name of the Approver. And recently the same approver name has been changed in MDM system and now the problem is newly changed name is not reflecting the reporting. It shows the only old name in reporting.
    My doubt is, what about already loaded record in BW system. Whether changes will be made for the older data. I mean it is possible to overwrite the approver name stored earlier in BW.
    D Raj

    Hi
    Yes, master is always overwritten.
    load the new value to the  approver Info object.
    in RSA1 -> right click --> activate master data.
    Initially when data loaded, records will be Modified version. when you perform activate master data then M versions records will turn to A version.
    records with A version are only visible in Report.
    If your report is on Aggregates, then you have to perform ACR (attribute change run) to update the same new value in aggregate.
    you can use the program RSDDS_AGGREGATES_MAINTAIN.
    Regards,
    Venkatesh

Maybe you are looking for