Compound PK problem

Hi guys,
I have compound key from 3 fields. But each of them are FK-s as well.
It works fine exept create.
How to cope with it?
Has JBoss any restrictions?
Or what am I doing wrong?
So, here is ma PK:
public class SasAssignmentPK implements Serializable {
     public Integer sampTableId;
     public Integer productGroupId;
     public Integer sasId;
     public SasAssignmentPK(Integer sampTableId, Integer productGroupId, Integer sasId) {
          this.sampTableId = sampTableId;
          this.productGroupId = productGroupId;
          this.sasId = sasId;
     public boolean equals(Object obj) {
          if (this == obj) {
               return true;
          if (!(obj instanceof SasAssignmentPK)) {
               return false;
          SasAssignmentPK that = (SasAssignmentPK) obj;
          if (!(that.sampTableId == null ? this.sampTableId == null : that.sampTableId.equals(this.sampTableId))) {
               return false;
          if (!(that.productGroupId == null
               ? this.productGroupId == null
               : that.productGroupId.equals(this.productGroupId))) {
               return false;
          if (!(that.sasId == null ? this.sasId == null : that.sasId.equals(this.sasId))) {
               return false;
          return true;
     public int hashCode() {
          int result = 0;
          result = result + this.sampTableId.hashCode();
          result = result + this.productGroupId.hashCode();
          result = result + this.sasId.hashCode();
          return result;
Here is my bean class:
public abstract class SasAssignmentBean implements EntityBean {
     /** Logger */
     static public final Logger LOG = Logger.getLogger(SasAssignmentBean.class);
     /** Entity context */
     protected EntityContext entityContext;
     /** @ejb.persistence column-name = "ST_ID"
     * @ejb.interface-method view-type = "both"
     * @return
     abstract public Integer getSampTableId();
     /** @ejb.interface-method view-type = "both" */
     abstract public void setSampTableId(Integer sampTableId);
     /** @ejb.persistence column-name = "PG_ID"
     * @ejb.interface-method view-type = "both"
     * @return
     abstract public Integer getProductGroupId();
     /** @ejb.interface-method view-type = "both" */
     abstract public void setProductGroupId(Integer productGroupId);
     /** @ejb.persistence column-name = "SAS_ID"
     * @ejb.interface-method view-type = "both"
     * @return
     abstract public Integer getSasId();
     /** @ejb.interface-method view-type = "both" */
     abstract public void setSasId(Integer sasId);
     * @ejb.interface-method view-type = "local"
     * @ejb.relation
     * name = "SampTable-SasAssignments"
     * role-name = "SasAssignment-belongs-to-SampleTable"
     * cascade-delete = "yes"
     * @jboss.relation
     * fk-constraint = "true"
     * fk-column = "ST_ID"
     * related-pk-field = "id"
     abstract public SampTableLocal getSampTable();
     abstract public void setSampTable(SampTableLocal sampTable);
     * @ejb.interface-method view-type = "local"
     * @ejb.relation
     * name = "ProductGroup-SasAssignments"
     * role-name = "SasAssignment-belongs-to-ProductGroup"
     * cascade-delete = "yes"
     * @jboss.relation
     * fk-constraint = "true"
     * fk-column = "PG_ID"
     * related-pk-field = "id"
     abstract public ProductGroupLocal getProductGroup();
     abstract public void setProductGroup(ProductGroupLocal sas);
     * @ejb.interface-method view-type = "local"
     * @ejb.relation
     * name = "SampAttributeSet-SasAssignments"
     * role-name = "SasAssignment-belongs-to-SampAttributeSet"
     * cascade-delete = "yes"
     * @jboss.relation
     * fk-constraint = "true"
     * fk-column = "SAS_ID"
     * related-pk-field = "id"
     abstract public SampAttributeSetLocal getSampAttributeSet();
     abstract public void setSampAttributeSet(SampAttributeSetLocal sas);
     /** Removes Assignments for specified SampAttributeSet
     * @ejb.home-method view-type = "local"
     * @param SampAttributeSet
     public void ejbHomeRemoveAssignments4SAS(SampAttributeSetLocal sampAttributeSet) {
          SasAssignmentLocalHome sasAssignmentLocalHome = (SasAssignmentLocalHome)entityContext.getEJBLocalHome();
     /** Creates a empty SasAssignment with SamplingTable, ProductGroup, SampAttributeSet
     * @ejb.create-method view-type = "both"
     * @param sampTable SamplingTable
     * @param productGroup ProductGroup
     * @param sas SampAttributeSet
     * @throws CreateException if creation failes
     * @return null as specified in EJB
     public SasAssignmentPK ejbCreate(SampTableLocal sampTable, ProductGroupLocal productGroup, SampAttributeSetLocal sas) throws CreateException {
          setProductGroupId(productGroup.getId());
          setSasId(sas.getId());
          setSampTableId(sampTable.getId());
          //return new SasAssignmentPK(sampTable.getId(), productGroup.getId(), sas.getId());
          return null;
     public void ejbPostCreate(SampTableLocal sampTable, ProductGroupLocal productGroup, SampAttributeSetLocal sas) throws CreateException {
          setSampTable(sampTable);
          setProductGroup(productGroup);
          setSampAttributeSet(sas);
And here is an exception:
javax.ejb.TransactionRolledbackLocalException: Internal error setting instance field sampTableId; CausedByException is:
de.keywork.moc.sampling.pk.SasAssignmentPK; CausedByException is:
Internal error setting instance field sampTableId; CausedByException is:
de.keywork.moc.sampling.pk.SasAssignmentPK
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:204)
... bla-bla-bla
Any ides after reading this long story? :-)
Thanks in advance

hi,
have you found a solution yet ?? because I'm facing the same problem .....

Similar Messages

  • Compounding consistency problem not ensured problem in multiprovider

    I have a multiprovider MP1 which has  CUBE1 & CUBE2 as its particiapting cubes. 
    Both of these cubes has infoobject 0FUND which is compounded with 0FM_AREA and I have included both( 0FUND & 0FM_AREA) of these infoobjects in MP1 and mapped it.
    Infoobject 0FUND has attribute called MNGUNIT. I have enabled attribute MNGUNIT as navigational in multiprovider and  mapped it to same attribute from CUBE1, but to different attribute  called RESP_FC of different infoobject COSTOBJ from CUBE2 . Both MNGUNIT & RESP_FC are reffrenced to same infoobject definitiion which is also compunded with 0FM_AREA.
    MP1 syntax check gives a message that, "compounding consistency for infoobject COSTOBJ__RESP_FC not ensured". I have already tried mapping COSTOBJ__0FMA_REA from both the cubes , but it still gives same error message.
    Any solution to this problem.
    Regards
    MB

    Hi Madhukar
    Do you mean COSTOBJ is compounded with 0FM_AREA?
    I think even in that case it will be a problem as your FM area is identified from 0FUND.
    Regards
    Anindya

  • Allow duplicate key in InfoObject/ compounding length problem

    Hi all.
    I try to create InfoObject with compounding key, consisting of IObj itself plus 4 compound attribs and total length of 63 symbols (max allowed is 60). Obviously, the system doesn't allow me to activate the InfoObject.
    I consider to move compounds into attributes area, but don't know is it possible to allow duplicate records in InfoObject?
    or
    Maybe you can help me with some other advise how to manage this compound key limitation?
    additional info:
    The InfoObject is the "copy" of  source system master data table

    Hi,
    ok, now I see. Well there is a restriction that the keyfields as in your example shouldn't be longer than 60 characters (summed up). So you need to think about using another object as compound. Isn't that possible? Another option might be to post the data to a ods/dso first which has your object as well as the compounding attributes as keyfields and which was already recommended, and after that, post the value to a new infoobject which gets it's unique value from a number range object that you need to define specially for this purpose. Add the keyfields of that ods/dso as navigational characteristics to that new object.
    regards
    Siggi

  • Compound Clip Problem in Final Cut Pro X

    I've posted most of the details within the video, explaining the issue. Basically, I'm using a green screen and transitioning pictures behind me on screen. I'm also singing in the video, so I need my lips to match up to the audio in the background. Before I create the compound clip (to fix the black background issue), the timing is perfect. But once I create the compound clip, the timing is off and I can't seem to extend the trasition or figure out a way to get my lips back in sync.
    The exact issue is shown in the video below
    http://youtu.be/raCZ_g2puao

    Look at a video called finalcut pro X tips and tricks on YouTube  it shows how to fix your issue.

  • Compound clip problem resolved

    Having turned the files in a project into a compound clip, FCPX refused to break the clip apart again and crashed every time I tried. While outputting the project in XML to resume it in another editor, I thought I'd try and bring it back into FCPX. It came back in and, voila, the compound clip in the duplicate broke apart nicely without a crash. These Apple software designers think of everything.

    Look at a video called finalcut pro X tips and tricks on YouTube  it shows how to fix your issue.

  • Spring Layout compound spring problem, on container

    I don't understand why these labels are getting resized. This test case is concise and shows the problem clearly, just comment out the line indicated for what the correct behavior I desire is.
    package gaillard;
    import java.awt.Color;
    import java.awt.EventQueue;
    import javax.swing.JFrame;
    import javax.swing.JPanel;
    import javax.swing.JLabel;
    import javax.swing.Spring;
    import javax.swing.SpringLayout;
    import javax.swing.SpringLayout.Constraints;
    import javax.swing.border.LineBorder;
    * @author gaillard
    public class Test
         final SpringLayout layout = new SpringLayout();
         final JFrame frame = new JFrame("Test");
         final JPanel contentPane = new JPanel();
         final JLabel label1 = new JLabel("HI");
         final JLabel label2 = new JLabel("HI AGAIN");
         public Test()
              frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
              frame.setContentPane(contentPane);
              contentPane.setLayout(layout);
              contentPane.add(label1);
              contentPane.add(label2);
              label1.setBorder(new LineBorder(Color.red));
              label2.setBorder(new LineBorder(Color.green));
              final Constraints label1Con = layout.getConstraints(label1);
              final Constraints label2Con = layout.getConstraints(label2);
              final Constraints contentPaneCon = layout.getConstraints(contentPane);
              Spring strut = Spring.constant(5);
              Spring columnOneWidth = Spring.max(label1Con.getWidth(),
                                      label2Con.getWidth());
              label1Con.setX(Spring.sum(columnOneWidth,
                                Spring.minus(label1Con.getWidth())));
              label2Con.setX(Spring.sum(columnOneWidth,
                                Spring.minus(label2Con.getWidth())));
              label2Con.setY(Spring.sum(label1Con.getHeight(), strut));
              //TRY COMMENTING THIS LINE OUT FOR THE DESIRED BEHAVIOR!!!!
              //TRY COMMENTING THIS LINE OUT FOR THE DESIRED BEHAVIOR!!!!
              contentPaneCon.setWidth(columnOneWidth);
              frame.pack();
              frame.setVisible(true);
         public static void main(String[] args)
              EventQueue.invokeLater(new Runnable()
                   @Override
                   public void run()
                        new Test();
    }Edited by: gaillard on Jan 7, 2008 8:49 PM

    is this a bug? Because there are some examples floating around on the web that do similiar such things expecting this code to work, yet when you run their code it doesn't match their screenshot, so perhaps a bug with java 6 or 5?

  • Troubleshoot installation problems in Photoshop Lightroom on Windows Vista

    This document can help you to resolve system errors that occur while you use Adobe Photoshop Lightroom on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:
    A blank or flickering dialog box
    A frozen cursor or screen
    A blue screen
    An unexpected restart
    An error message such as:
    "Setup is unable to load the installation script file."
    "Unable to create a directory under C:\Windows\System. Please check write-access to the directory."
    "Uninstalling: C:\Program Files\Adobe\Adobe Photoshop Lightroom refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."
    Note: If you attempt to install Photoshop Lightroom to a drive that doesn't have the minimum required space available, the installation will fail. You must then completely reinstall to another location that has sufficient free space.
    Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Photoshop Lightroom, Photoshop Lightroom may not necessarily be the cause; it may be the only application that uses enough memory or processor cycles to expose the problem.
    To benefit most from this document, perform the tasks in order. Keep track of the tasks that you perform and the results of each, including errors and other problems. Adobe Technical Support can use this information to better assist you if you need to call.
    You must be logged on as an administrator to perform some of the procedures in this document.
    Important: Some of the procedures in this document may initiate a User Access Control dialog that asks for your permission to continue. Read the details in the dialog to determine if you want to continue. If you choose to cancel the dialog, then you will not be able to continue with that troubleshooting step.
    The steps in this document that refer to the Control Panel are in reference to the Classic view. For information on switching the Control Panel to the Classic view and many other common OS procedures, see Common Microsoft Windows Vista procedures (TechNote kb401275)
    Some of these procedures require you to locate hidden files and hidden folders. Some procedures require you to locate files by their full file names, which include extensions (for example, example_filename.ini). By default, Windows Explorer doesn't show hidden files, hidden folders, and file name extensions that it recognizes.
    To show hidden files, hidden folders, and all file name extensions in Windows Explorer:
    In Windows Explorer, choose Organize > Folder And Search Options.
    Click the View tab in the Folder Options dialog box.
    In Advanced Settings, select Show Hidden Files And Folders.
    Deselect Hide Extensions For Known File Types.
    Click OK.
    Note: The procedures in this document are based on the default interface of Windows Vista. If the interface is customized, some procedures may vary. For example, a commonly encountered difference is the navigation to Control Panel from the Start menu: You may navigate Start > Settings > Control Panel instead of Start > Control Panel. Additionally, the procedures in this document assume you are using the Classic View of the Control Panel: To view the Control Panel in the Classic View, click Switch To Classic View on the Control Panel navigation bar on the left side of the window.
    Beginning troubleshooting
    The tasks in this section can help you resolve the most common system errors. Before performing any of these tasks, back up all personal files (for example, Photoshop Lightroom files you created). Always restart the computer after a system error occurs to refresh system memory. Continuing to work without restarting the computer may compound the problem.
    1.Make sure that the system meets the minimum requirements for PhotoshopLightroom.
    Photoshop Lightroom may not run correctly on a system that doesn't meet the following requirements:
    Intel Pentium 4 or equivalent processor
    Microsoft Windows XP, Windows Vista, Windows 7
    768 MB of RAM (1 GB recommended)
    1 GB of available hard-disk space
    CD-ROM drive
    In addition to these requirements, a video card that supports 24-bit (16 million) or more colors, and a resolution of 1024 x 768 or higher, is recommended.
    * Photoshop Lightroom 1.0 will install and run on Windows Vista but Adobe cannot guarantee the quality of the software experience until Adobe fully certifies Photoshop Lightroom for use on Windows Vista.
    To check basic system information, such as processor speed and how much RAM is installed, choose Start > Control Panel > System.
    2. Delete previously installed application files, especially if you had the public beta version of Photoshop Lightroom installed.
    To delete files from a previous Adobe Photoshop Lightroom installation attempt:
    Choose Start > Control Panels > Add or Remove Programs.
    Select Adobe Photoshop Lightroom and choose to remove it.
    Close the Add Or Remove Programs window and the Control Panel.
    Open Windows Explorer.
    If the Lightroom.exe file is still in the Program Files\Adobe\Adobe Photoshop Lightroom folder, delete it.
    If the Lightroom Preferences.agprefs file is still in the Documents and Settings/[username]/Application Data/Adobe/Lightroom/Preferences folder, delete it.
    Empty the Recycle Bin.
    Try to reinstall. If you cannot, continue with the next two sections in this step:
    Move all the folders under the Users/[username]/AppData/Roaming/Adobe/Lightroom folder into a new folder on the desktop; name the folder Lightroom Presets. These are the presets that were installed with the application and that you created.
    Move all the folders under the Users/[username]/Pictures/Lightroom/Lightroom Previews.lrdata folder into a new folder on the desktop; name the folder Lightroom Previews. If you have a large number of images, you can move this folder back to its original location before you open Photoshop Lightroom, once it's installed. Or you can delete this folders to re-create it when Photoshop Lightroom opens. If there are further problems with Photoshop Lightroom after it's installed, it might be due to corruption in the previews, in which case you need to delete this folder and re-create it.
    Try to reinstall.Important: Do not delete the Lightroom Database.lrdb file!
    If there are further problems with Photoshop Lightroom after it's installed, these issues may be due to corruption in the preset files you created, in which case you need to remove them and re-create them, or test each preset individually.
    Note: If you can reinstall, and if this is not the first time you opened Photoshop Lightroom, then Photoshop Lightroom will look for a library database file. If it does not find a library in the expected location, it will prompt you to create a new library, locate the library, or exit. Exit will close the dialog box, and Photoshop Lightroom will not open. Although you can tell Photoshop Lightroom to locate your library, it's best to put it back in the default location and then open the application.
    If you can reinstall, close Photoshop Lightroom and then copy any presets you created from the Lightroom presets on the desktop back into the Users/[username]/AppData/Roaming/Adobe/Lightroom folder.
    If you cannot reinstall, then move the Lightroom Database.lrdb file from the Users/[username]/Pictures/Lightroom folder into a new folder called Lightroom Database File and save this file on the desktop. This is your database, if you previously had Photoshop Lightroom installed.
    Reinstall Photoshop Lightroom. If you cannot reinstall, continue with the next task in this document.
    3. Log in as Administrator before installingPhotoshopLightroom.
    In Windows Vista, you must be logged in with local (that is, machine) Administrator rights to install Photoshop Lightroom. If you don't have administrator rights, contact your system administrator for assistance.
    4. Check the CD and CD-ROM drive.
    Dust or dirt on a CD can interfere with an installation and prevent the CD-ROM drive from recognizing the CD. Examine the Photoshop Lightroom CD for dirt, dust, or fingerprints. Gently wipe the bottom of the CD from the center outward with a soft, lint-free cloth.
    Verify that the CD-ROM drive can read other CDs. If it can't, examine the CD caddy or loading tray for dirt, and clean it with a lint-free cloth. If it still can't read other CDs, contact the CD-ROM drive manufacturer or the computer manufacturer.
    5. Install current Windows service packs and other updates.
    Updates to the Windows operating system improve its performance and compatibility with applications. You can obtain Windows service packs and other updates from the Microsoft website at www.windowsupdate.com. For assistance installing service packs and other updates, contact Microsoft technical support.
    Important: Before you install a system update, check the system requirements for Photoshop Lightroom (and any third-party software or hardware you may use with Photoshop Lightroom ) to ensure compatibility. If the update isn't listed, then contact Adobe or the manufacturer of your third-party software or hardware.
    6. InstallPhotoshopLightroomfrom the desktop and use the default installation folder.
    Some system components such as device drivers and virus protection utilities can conflict with the Photoshop Lightroom installer and result in an incomplete or failed installation, or they can cause problems when you install to a folder or when you use a path to the default installation folder that contains a special character, such as #. To prevent these conflicts, install Photoshop Lightroom from the desktop, and use the default folder name and path.
    If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
    Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
    Open the Adobe Photoshop Lightroom folder on the desktop.
    Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
    7.Re-create thePhotoshopLightroompreferences file.
    Re-create the Photoshop Lightroom preferences file to eliminate problems that a damaged preferences file might cause:
    Quit Photoshop Lightroom.
    Rename the Lightroom Preferences.agprefs file (for example, to Lightroom Preferences.old) in the Users/[username]/AppData/Roaming/Adobe/Lightroom/Preferences folder.
    Start Photoshop Lightroom. Photoshop Lightroom creates a new preferences file.
    If the problem continues, the preferences file isn't the cause. To restore custom settings, delete the new preferences file and restore the original name of the previous preferences file.
    8.Install and run Photoshop Lightroom while no other applications are running.
    Some applications may interfere with installing or running Photoshop Lightroom. Virus protection programs are meant to stop viruses from installing on your computer. Before installing or starting Photoshop Lightroom, disable other applications, including virus protection programs and startup items (items that start automatically with Windows).
    To disable startup items and non Microsoft services:
    Quit all applications.
    Choose Start, type msconfig in the Search text box, and press Enter.
    Write down all unselected items under the Startup and Services tabs.
    Click the General tab, and choose Selective Startup.
    Click the Startup tab and select Disable All.
    Click the Services tab and select Hide All Microsoft Services.
    Select Disable All then re-select FLEXnet Licensing Service. If you are unsure whether an item is essential, then leave it deselected (disabled).
    Click Apply, and restart Windows for the changes to take effect.
    Note: Upon restart, you'll be notified that the System Configuration utility has made changes to the way that Windows starts up. Click OK. When the System Configuration utility appears, click Cancel.
    Right-click icons in the Notification Area and close or disable any startup items that are still active.
    9. Install Photoshop Lightroom to a different hard disk after disabling startup items and installing from the hard disk.
    Hard disk problems can prevent Photoshop Lightroom from installing correctly. By installing Photoshop Lightroom to a different physical hard disk, you can verify if the original hard disk is preventing installation. First, completely remove Photoshop Lightroom from the hard disk.
    To install Photoshop Lightroom to a different hard disk after disabling startup items:
    Follow the steps in task 8 above to disable startup items.
    If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
    Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
    Open the Adobe Photoshop Lightroom folder on the desktop.
    Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
    Click Change and select a different hard disk in the Change Current Destination Folder window. Click OK, and then follow the on-screen instructions.
    Intermediate troubleshooting
    If the tasks in the previous section don't solve the problem, try the following intermediate troubleshooting tasks.
    10. Install and run Photoshop Lightroom in a new user account.
    Create a new user account that has the same permissions as the account that you use when the problem occurs. If the problem doesn't recur, the original user account may be damaged. For instructions on creating a new user account, see To add a new user to the computer in Windows Help or contact your system administrator.
    11. Optimize handling of temporary files by Windows Vista.
    Windows and applications store working data in temporary (.tmp) files that they create on the hard disk. Excessive or outdated temporary files can interfere with performance of Windows or applications.
    Delete temporary files by using the Disk Cleanup utility included with Windows or by using the following instructions. Make sure that at least 1 GB of free space is available on the hard disk to which temporary files are written. To start Disk Cleanup, choose Start > All Programs > Accessories > System Tools > Disk Cleanup. For information about Disk Cleanup, see Windows Help.
    To manually delete temporary files:
    Note: Windows deletes temporary files when Windows and applications close normally. However, when Windows or an application crashes, temporary files can accumulate on the hard disk. Windows may prevent you from deleting some temporary files as they may be in use. Delete as many temporary files as you possibly can, without deleting the files that are in use.
    Quit all applications.
    Choose Start and type %tmp% in the Search text box and press Enter.
    Delete the contents of this folder.
    Note the drive letter where this directory is located.
    To ensure that at least 1 GB of free space is available on the hard disk to which temporary files are written:
    Choose Start > My Computer.
    Select the drive noted in step 4. Right click and select Properties.
    Confirm the drive has at least 1 GB of free space.
    12. Repair and defragment hard disks.
    System errors can occur if hard disks contain damaged sectors or fragmented files. Repair and defragment hard disks, either by using the Error-checking tool and Disk Defragmenter utility included with Windows or by using a third-party disk utility. You should run such utilities on each hard disk or partition. More information about the Error-checking tool and Disk Defragmenter appears below; for more information about a third-party disk utility, refer to the documentation for the utility.
    The Error-checking tool repairs bad sectors, lost allocation units and file fragments, cross-linked files, and invalid file names. To access the Error-checking tool, choose Start > Computer, right-click the desired hard disk, and choose Properties from the menu. In the Local Disk Properties dialog box, click the Tools tab, and then click Check Now in the Error-checking area.
    Note: To prevent Disk Defragmenter from moving files to bad sectors of a disk, run the Error-checking tool before running Disk Defragmenter.
    Disk Defragmenter rearranges the files and free space on your computer so that files are stored in contiguous units and free space is consolidated in one contiguous block. To access the Disk Defragmenter utility, choose Start > All Programs > Accessories > System Tools > Disk Defragmenter.
    13. Scan the system for viruses.
    Use current anti-virus software to check the system for viruses. Virus infections can damage software and cause system errors. For more information, see the documentation for the anti-virus software.
    14. Try to install Photoshop Lightroomon a different computer.
    Try to install Photoshop Lightroom on a different computer to determine if the problem is unique to your computer. If the problem is unique to your computer, contact the computer manufacturer; if the problem occurs on multiple computers, contact Adobe Technical Support.
    Advanced Troubleshooting
    If the tasks in the previous section don't resolve the problem, you may be able to resolve the problem by reinstalling Windows Vista and Photoshop Lightroom, reformatting your hard disk and reinstalling Windows Vista and Photoshop Lightroom, or by determining if hardware is conflicting with Photoshop Lightroom.
    Disclaimer: Adobe doesn't support hardware and provides these procedures as a courtesy only. For further assistance, contact the hardware manufacturer or an authorized reseller. If you troubleshoot hardware problems yourself, you may void the warranty for your computer.
    Note: Before you remove or rearrange hardware, turn off and disconnect power to the computer and any peripheral devices.
    15. Log in using the built-in Administrator account.
    The built-in Administrator account has a higher access level to the system than a normal local administrator account. By default the built-in Administrator account is disabled. For information about enabling and logging in to the built-in Administrator account, contact your system administrator. You can also refer to this support document on the Microsoft support website: http://support.microsoft.com/kb/926183/en-us?spid=11737&sid=73.
    16. Reformat the hard disk, and reinstall only Windows Vista and Photoshop Lightroom.
    Reformat the hard disk, and then install only Windows Vista and Photoshop Lightroom from the original installation media. Reformatting a disk erases all files it contains, so be sure to back up all personal files first. Also make sure that you have all application and system disks.
    For instructions on performing a clean installation of Windows Vista, see document 918884, "How to install Windows Vista" on the Microsoft website at http://support.microsoft.com.
    Note: Don't install additional software or hardware until you're sure that the problem is resolved. Don't back up the hard disk and restore Windows and Photoshop Lightroom instead of reinstalling them. If the problem is caused by an application or Windows, and either one is restored instead of reinstalled, the problem may recur.
    After you reformat the hard disk and reinstall Windows and Photoshop Lightroom, try to re-create the problem:
    If the problem no longer occurs, then install other applications one at a time and try to re-create the problem after each installation. If the problem occurs after an installation, then the recently installed application may be the cause.
    If the problem occurs when only Windows and Photoshop Lightroom are installed, then the cause may be hardware-related, and you should contact the hardware manufacturer or an authorized reseller for assistance.
    17. Check for problems with RAM modules.
    Ensure that the RAM modules are installed properly and are not the cause of your problem. Do one or both of the following:
    Change the order of the installed modules.
    Remove all but the minimum number of modules needed to run Windows and [product], and test to see if the problem persists. If it does, replace the modules you removed and remove the others, testing again to see if the problem recurs. If it doesn't, then one or more of the removed modules are the cause. For assistance, contact the RAM manufacturer.

    You've tried Help>Updates from within photoshop cs6?
    Or this 8.3 updater
    http://swupdl.adobe.com/updates/oobe/aam20/win/PhotoshopCameraRaw7-7.0/8.3.52/setup.zip
    If that doesn't work, you can install camera raw 8.3 by following the directions on the following page
    Adobe Camera Raw Help | Camera Raw/DNG Converter 8.4 on Mac OS 10.6, Windows XP, and Vista

  • Lightroom & Camera Raw problem

    I really cannot make any sense out of Camera raw and the other adobe products.
    I have Lightroom 2.4, and if I click on the "about" option, I get told I have camera raw 5.4. However I have no DCP files installed, and so no camera calibration options. All I see is "Embedded".
    Also installed are Photoshop Elements 7 (Camera Raw 4.5.0.175), Premiere Elements 7 & Photoshop CS3 (Camera Raw 4.0).
    I am not an expert in this, and I find the instructions on the adobe site completely confusing and hopeless.
    I juts cannot find any reference to how I get a CR update for my Lightroom. I have found 4.6 for CS3 which I understand i sthe latest, but I simply cannot find out how to get the camera profiles installed from any update.  Can someone help.
    Thanks
    Colin

    Thanks everyone. I got more info on this one post than in an hour looking round Adobe’s web site.
    I also checked the FAQ's before I posted. There are 31 messages there, I've checked again, and none of them have RAW or Profiles in the title. Now there may be something in an article, but I didn't spot any relevant titles.
    I also did a search on the forum itself for Raw & Camera profiles. There were a number of articles in there, but no CLEAR statement like you guys have just given me. I did find one that explained where the DCP files were (admittedly on an XP machine although this wasn't mentioned in the post). So I searched in the equivalent position under my User on Vista. Unfortunately I've now discovered Adobe has moved them to
    I then compounded the problem by checking the wrong file in Lightroom. I basically store photos for myself and my wife on my PC, and on my Canon I always shoot RAW. So I then looked at the 1 jpg from my Canon this year!!!!! (well OK maybe there's a few more, but you know what I mean.)
    But this is all part of the problem. It appears that we need to be experts to find the simplest of bits of info. It is still not clear to me how I update CR for Elements and CS3 (but I think at last I've found it.). Those who are professionals or experienced users can find info relatively easily, but a hobby user like me who might only need to look here once a month struggles to get answers. That's why the forums are so good.
    So thanks for your help. Much appreciated. 

  • Fixing duplicate keyword problem in LR 2.2

    I have imported Controlled Vocabulary into my existing keyword library. Unfortunately I already had existing keywords tagged to a couple of hundred photos. As a result I now have duplicate keywords for each photo. I realize I may have compounded my problems by saving the keywords directly to photos(CTRL-S) after the import and before attempting to delete duplicate keywords.
    Is there a way to delete entire library of keywords and re-import CV without deleting keywords from the existing XMP files? Then I could continue keywording photos using a fresh CV library and edit existing duplicates when I had the time. Obviously I am hoping to avoid the worst case scenario of re-keywording all my photos.
    Note: I sent a related question on a previous thread(on 2/7)and never received a response...

    Jim, I'm in a similar workflow attempting to use a single controlled vocabulary across several libraries. The problem I run into is when adding new keywords to the vocabulary, I have to remember to export the whole keyword list and update all of my catalogs before going on to the next task. Also, as in your case, if a keyword is deleted from the vocabulary or moved to a different tree there is no easy way to duplicate the change across all libraries.
    In the same way that all of my catalogs share a common set of develop presets, are you aware of any way to have several lightroom catalogs work from a single set of keywords?

  • ITunes podcast sync problem

    Hi,
    I have my iPod and iPhone 3GS set up to sync only selected podcasts (all unplayed for iPod, 5 oldest unplayed for iPhone). Here's what happens: If there is only one podcast that is unplayed, and I listen to it and then delete it from iTunes (meaning obviously there are no podcasts left to that subscribed podcast feed), I remain subscribed in iTunes, but it gets taken out of the list of "selected podcasts to update" in the settings sections of both the iPod/iPhone. I then have to go back to iPod/iPhone settings, and reselect the podcast feed to be synced with the device. Obviously, it's a waste of time... It also is contradictory with that dumb "iTunes has stopped updating this podcast because you haven't been listening to it" message.
    Any solutions out there?

    No they haven't fixed it. I still, today with the latest updates, am getting that same stupid (non existent) error message "iTunes has stopped updating this podcast because you haven't been listening to it" How do I turn the #$@% thing off?
    Some of my podcasts only are on line for 24 hours before the source removes them (an asinine policy) and if I don't happen to notice Itunes has kicked into that error mode, I can never get those episodes.
    I guess my habits compound this problem. I never listen to a podcast on the computer, nor do I ever sync the IPod. I do it all manually to carefully control what is on both. It doesn't mean I'm not listening, just that the computer doesn't know it.

  • Macbook pro (not charging) problem

    Hi i am new to this community
    I know a similar post has been made before but I feel my case is a little weird and would like to know if there's anyone else out there facing the same thing.  So basically the problem is whenever i do anything even remotely graphic intensive, the laptop would say (not charging) and the orange light on the charger turnds green. Like say i watch a youtube video or a high def trailer from www.gametrailers.com, it immediately says not charging for the duration of the video. It 100% happens while gaming without fail even before the laptop starts to rev up.
    Does anyone else have this problem?
    I have given it to the apple care 3 times and had my battery changed, software updated and the third time in a different place they said this was 'normal'. NORMAL? how can it be normal for a latop to not be able to get charged while doing anything its supposed to be used for. I have never in my life faced this problem while running highly intensive graphic games in much cheaper laptops. Never really expected this problem to come from such a premium brand and at a such a steep price. Especially since they arent even admitting its a problem...

    You have exactly the same problem that has been discussed in an endless thread here previously. It has been true of all MBPs since the first ones in 2006 that if pressed to the wall, they could require more power than their AC adapters can supply. Under those circumstances, the first thing to happen is that battery charging ceases (if it was going on in the first place) and the second thing that happens, if the machine's power demand is high enough, is that the battery is drawn upon to make up the deficit. So with any MBP, there is the possibility that under extremely heavy load, the battery won't be charged or will actually be depleted while the AC adapter remains connected.
    Very few users ever ran into this with early MBPs, because it was hard to push them to the point of needing more power than their 85W adapters provided. It has become all too common in the 2011 models, with their enormously powerful (and enormously power-hungry) discrete GPUs and the expectation of many users that they will be able to use a notebook for everything they used to do on large desktop computers. I suspect (and this is purely my own hypothesis) that Apple has unintentionally compounded the problem with the automatic GPU switching in recent 15" and 17" MBPs, causing the discrete GPU to be invoked automatically when it isn't really needed and the integrated graphics would suffice, such as when browsing the web. Anecdotal evidence suggests that the problem only arises in the 2011 models when the discrete GPU is in use, so if you turn off automatic switching and limit yourself to the integrated graphics, you may be able to put an end to it, or at least limit its occurrence to times when you're willing and able to cope with it. But it probably does mean that you won't be able to place graphically-intensive 3D action games around the clock without running your battery down, and will need to take breaks of several hours to recharge from time to time.
    In other words, it IS normal, though it's also unfortunate.
    You might well wonder why Apple doesn't just provide a larger, higher-capacity AC adapter, and the only answer I can suggest (speaking for myself of course, and not for Apple) is that it might not be possible for the MBP in its existing case design to dissipate the additional heat that would be generated by continuing to charge the battery at times of extreme CPU and GPU activity.

  • Won't play video

    Since using iCloud I have problems which I presume are related to data being downloaded on the fly.
    When I try to play any music videos on my iPhone 4 I receive this message:
    'This item can't be downloaded over a cellular network.
    You must connect to a Wi-Fi network to use iTunes on your computer.'
    When I play music there is a very long delay between songs, and in many cases the song stops in mid-play.
    To compound my problems, I have two different iTunes accounts due to a mixup and lost password a few years ago.
    I can access both my accounts now, but when I switch iCloud off for my iPhone - on iTunes it shows all the songs
    in both libraries on my phone but I can only play songs and videos from one of the accounts.
    If anyone can offer solutions to one or both of these problems I'd greatly appreciate it.
    Cheers

    try downloading Flip4Mac. It's free (or used to be, anyway), very highly rated, and plays all kinds of online video files, including wmv files. One place you can find it is at versiontracker.com (just put Flip4Mac in the Search box).
    Check your DSL line speed too. One place to do this is at dslreports.com/tools. And if you only have 256K connection, that will cause video to stutter or hang... you'd need to upgrade to higher speed connection.

  • Null object not centred, why?

    Create a null object and it's not centred to its location. Why?
    Seems like that would be the most obvious position to put the visual representation of a null object. So the least likely place for Adobe to put it?
    Or is there some logical reason?

    dissidently wrote:
    Rick, all other apps that have Null objects use them far more wisely than Adobe does. Mylenium has confirmed my suspicion, that these things weren't thought through, simply created (probably in a panic or out of laziness) as a half way house to what Null objects actually can be.
    I get your point about the anchor point, but that's not what I'm talking about. In ALL other apps with a Null object, the visual representation of that Null object is centred. There's a tonne of reasons to do that, and I'm not contending the placement of the Null objects "anchor", it's in the right spot. It's the visual representation of the Null object that's utterly wrong.
    That it's a deformable visual representation only compounds this problem.
    Your usual presumptuous assumptions.
    The null object was a remarkable improvement over how, in the olden days, we created invisibly small or transparent objects to do roughly the same thing.AE's were the first nulls I ever encountered. I learned how to use them when introduced and never really thought about how they might have been better. AE's nulls made perfectly good sense to me. And I don't use the other applications you are alluding to so I don't really need AE's null to be any different. I have, more than once, moved the null's anchor to its geometric center to help my project contributors grasp the concept. But they had no prior experience with nulls, either, so once they got it, I moved things back to their default because that works for me. Why are you still using After Effects?

  • Since software update, can't see contents of iPod when connected to iTunes

    About 2 days ago, when I connected my iPod to my pc (iTunes), it said there were some software updates for my iPod so I downloaded them and the iPod rebooted itself. Once it came back up, my iPod showed up in iTunes under "devices" on the left hand sidebar. I got the registration page - I usually click register later, but nothing happened this time. It didn't bring me into my iPod. So I tried to Register. I could get so far, then it asked if I wanted some free movie or something, I said NO THANKS, CONTINUE, but nothing happened. I wasn't registered AND I couldn't access my iPod. I can see my iPod under My Computer. I can see "sandra's iPod" uder devices in iTunes. BUT, I can't get to the content when connected to iTunes. All of my stuff is there on the iPod. I can play my iPod when it's not connected to iTunes - but I can't see the content, manipulate playlists, delete songs, etc. when connected to iTunes. I am almost positive this is a result of the latest software updates to the iPod. I have not updated iTunes - I didn't want to and compound the problem. I'm not a techy person - so please be gentle! Thank you. Sandra

    Resolved at home.

  • I have just taken delivery of a brand new 15" macbook pro, tried migration assistant from a time machine backup, music, photos, programs etc. They now take up 350gb of my hard drive but the files are nowhere to be found? can anyone help?

    Set migration assistant to run whilst on a lunch break, given that it needed 2 hours or so, when i returned all programs and applications had moved across from my time machine backup of a now dead 15"macbook pro 2009 edition running snow leopard...When i look at my new system information it shows my new 500gb drive is full of music, movies and photos and has only 168gb free, not enough to run a new migration and i don't have any boot disks for Lion so really don't want to erase the hard drive. To compound the problem i'm in Vietnam where there isn't a genius bar just around the corner, or even an aasp within 700km - what should I do?

    Is the HDD in the 2009 15" MBP dead?  (The original source of your data)  If not, you might want ot take it out and put it in an enclosure.
    You might try spotlight on know files to see if that gives you any clues where your data is located.
    You might down load from the Internet OmniDiskSweeper (free) and open it.  It should show you all of the files you have on your MBP and enable to locate them.
    Ciao.

Maybe you are looking for