Update vault errors yet to be solved.

As suggested in the forums, I have dragged the aperture.app to the trash and installed the new v2.1 once again. I can create a vault in an external HDD (FAT32), but I still get the 'cannot create ... *.apfile' errors when I update it.
Did I missed any steps, say delete any preference files, in order to make it works?
I hope Apple could fix the error in the next update soon.

Ohhh...
You cannot have a vault on a FAT32 volume. It has to be an HFS+ volume.
FAT32 cannot handle the file naming that Aperture uses... Aperture uses characters that are illegal on FAT32.
So you have 2 options:
1) Reformat the drive as Mac OS X extended (Journaled) -- a.k.a. HFS+ Journaled
2) Create a sparse image on the drive using Disk Utility, open that image, and create the vault on that. This is more work, more complicated, and really not recommended (but will work in a pinch).

Similar Messages

  • Update Vault Error

    I can no longer update my Apertue 2.1.4 vault. Since installing Snow Leopard, I first noticed my iPhone would no longer sync pictures via Aperture 2, but would via iPhoto. Now I find I also cannot update vault to an external drive. Have redone permissions, rebuilt Aperture library, tried to create new vaults on the original external drive and the internal drive. Always get same "Update Vault Error" response and images don't appear to go into the vault. I see similar posts with no solution. My Aperture Library has 14000 photos.
    I wonder if these problems will carry over to an Aperture 3 library.
    Hoping for some advice

    No, I thought of that, I tried to make it simple:-
    Lacie/backup/Vault
    Or on the internal:-
    Users/me/pictures/vault
    It may be that one of the images or possibly a sidecar file in my project is corrupt, thus making the library itself corrupt.
    Therefore, when Aperture tries to compare its internal library structure to the Vault, it finds an error and blames the Vault for being corrupt; even so it still finds errors trying to backup to a blank brand new vault. I have a problem with the fact that it is suggestng that the vault be deleted(!) and replaced, even though the problem is likely to be with the internal Library itself and not the vault. And replacing the vault with a new one is impossible (still has same error).
    Unfortunately I have no way of finding out which one of the 2500 or so images in the library has the problem. I thought that the commandoptionrestart Aperture to rebuild the library would have worked, but unfortunately it doesn't.
    L

  • Update Vault error message

    Aperture is not letting me update my vaults. I am receiving update vault error messages when trying to back up to Vaults. I have three backup Vaults on external firewire drives, formatted Mac HFS+ (not MS-DOS) and not partitioned. My Aperture library is also on a dedicated external drive. I get the same message for all three vaults, so this seems to be an Aperture problem, not a disk problem. The error messages refer to NEF (raw) image files that do not exist in my Library (or anywhere else, for that matter). Message reads:
    update vault error:
    The following error occured:
    Couldn't create/Volumes/LaCie/ApertureV2.apvault/Library/....
    Any insights would be appreciated.

    James Bouret's problem is fixed -- or maybe not.
    From my blog: +We traced the problem to "something bad" about the folder or its contents that was being reported. By opening the library and the vault with control-click Show Package Contents and navigating down, it was possible to trash the folder. Not only did the vault update complete once that was done, but it worked many, many times faster than before. The bad news is that I think this is due to a bad spot on the disk, indicating a drive that is on its way out. If you have vault problems: back up carefully and consider that you may have a bad disk.+
    A bad spot on the disk may also be the reason that Johnny Cappuccino could fix his problem by modifying the image. That will have rewritten the sidecar files, a process that usually involves creating a new temporary file and then atomically deleting the old file and renaming the new one. So the new file is shiny and good and the bad spot is ready for use by another hapless program.

  • Update Vault Error:  Errors creating a directory in vault "date".

    I updated my Aperture vault in December.
    When I tried to update it again this morning I get the message *Update Vault Error: Errors creating a directory in vault "date".* In one instance it says 15 errors occurred. In another it says 219 errors occurred.
    Other than delete the current vault and re-create it, are there any suggestions as to a fix for this problem?
    Jerry

    I have noticed the following:
    + While I cannot update an existing vault, I can create a new vault on the same folder/disk. For my purposes, I will probably use this vault and delete my old vault that I can no longer update.
    + The last time that I successfully updated one of my existing vaults was 4 days ago. Since then, I accidentally blew-away my preferences and subsequently restored them from backup... but the restored preferences predated the current Aperture library.
    Perhaps there is something in the Preferences ( <user>/Library/Preferences/com.apple.* ) that retains some state about the state of recent vaults. I haven't looked. Perhaps the status of my Aperture Library was out of sync with my restored preference files.
    Anybody with this problem have a similar situation?

  • Update vault errors connected to Spotlight rescan?

    I haven't had a vault update error for a long time. Then I had spotlight rescan my external drives. Now I get ONLY errors, on external and internal vaults.
    Anyone have any ideas?
    Thanks,
    Brent

    Ohhh...
    You cannot have a vault on a FAT32 volume. It has to be an HFS+ volume.
    FAT32 cannot handle the file naming that Aperture uses... Aperture uses characters that are illegal on FAT32.
    So you have 2 options:
    1) Reformat the drive as Mac OS X extended (Journaled) -- a.k.a. HFS+ Journaled
    2) Create a sparse image on the drive using Disk Utility, open that image, and create the vault on that. This is more work, more complicated, and really not recommended (but will work in a pinch).

  • Can't software update, networking error, yet internet connection fine

    I am trying to use software update, but can't. I get this:
    "A networking error has occured: timed out (-1001). Make sure you can connect to the internet, then try again. Software Update can't check for updates because of a network problem."
    Yet network diagnostics show everything fine; mail works fine; network utility shows everything ok; wireless connection fine; TCP/IP looks normal; and browsers are fine -- here i am posting.
    WTH?!
    I know there are other threads about this, but the questions there are unanswered, even though the threads are marked answered.
    I tried the following:
    1. i backed up using Carbon Copy Cloner, then wiped my HD and copied back. That was ok, but still couldn't use software update.
    2. i archived/installed 10.4, restarted.Some prefs gone but basically ok, couldn't use software update.
    3. downloaded last combo update 10.4.7, and last security update. Quit everything, repaired perms, installed combo update, restarted. Installed security update, restarted.
    4. i reset PRAM.
    5. i checked the disk using Disk Utility. It's fine.
    6. I made a new user account to test. Logged in there, tried software update, same result.
    And i still can't use software update.
    Someone in another thread wrote that this seems to be in UK and Netherlands. Possible?
    Any suggestions anybody?
    thanks, P
    powerbook g4, 1ghz, 512 mb ram   Mac OS X (10.4.7)  

    sorry, i forgot that: Yes, i deleted:
    /Library/Preferences/com.apple.SoftwareUpdate.plist
    [home]/Library/Preferences/com.apple.SoftwareUpdate.plist
    [home]/Library/Preferences/ByHost/com.apple.SoftwareUpdate.plist
    This last i am not sure of the exact name, i saw it before, deleted it, but it hasn't been regenerated.
    there is also:
    [home]/Library/Caches/Software Update/
    which has nothing in it;
    and
    [home]/Library/Preferences/com.apple.SoftwareUpdate/
    which has a lot of numbered folders and cache files with names like
    '1321878279-2428557571.cache'
    Should i try deleting those?
    How do i find out the server name for Software Update btw?
    Perhaps i should try plugging that into the SoftwareUpdate.plist?
    thanks, P
    powerbook g4, 1ghz, 512 mb ram Mac OS X (10.4.7)

  • Recurring vault errors

    I'm having a recurring problem when updating vaults from Aperture 2. I fixed it first time around but its started to occur again. Any help?
    *_First time_*
    Back in November, our copy of Aperture 2 installed on a PowerMacG5 kept on quitting unexpectedly, and vault updates on a Lacie hdd brought back errors. I tried to rebuild the library on another Mac (a PowerBook) running Aperture 2 but this brought up errors too, saying certain items would not copy. Items causing these errors were deleted out of the G5 library but the vault would still not update.
    Our next step was to copy the library off the G5 onto a smaller external hdd (successful), move library onto an iMac (successful) and try to import this into a copy of Aperture 2 running on the iMac. This last part failed, until we re-installed Aperture 2. However we could not create an vault from this new library (errors coming up again). Several different external hdd drives were tried, all bringing up problems.
    We hit success when, on the iMac still using the 'good' library, we deleted all links to previous vaults, and reformatted external hdds so they were all in Mac OS X Extended (Journaled) format. We were then able to make two vaults successfully.
    *_Second time_*
    Update Vault Error has started up again (approx 700+ errors....). Has anyone got an idea why this could be happening, or give me any hints of new things to try?
    I'm sorry I can't give exact details right now but I am not at the same location as the affected Apple Macs

    hi, i'm not positive but i think i may have the same problem. furthermore, i've noticed a common theme to the problem.
    first off, some background. i'm by no means a power user of the package, nor am i a mac expert and i've been 'satisfied' with aperture 2, that is until last november 2009, when for some reason, i lost all my aperture image files on my macbook, they had all been imported using the aperture wizard and saved to the vault. i was very diligent. so, no problem i thought, i'll just restore from my vault.
    plugged in my portable hdd, commenced the restore routine, aperture restarts and on clicking confirm, i get a message stating that aperture has failed (or something similar) with 'close', 'try again' and 'report' buttons.
    now i've been trying to get to the bottom of the problem for some time and Apple seem to have ignored this issue i thought i was defeated and all my images lost for ever. However, i've got round this issue and found most of my images.
    there are two elements to the issues i've been experiencing:
    _first accessing aperture:_
    - i tried re-installing the application and much more. i just couldn't open aperture. however i finally tried opening aperture and at the welcome screen selecting - *import from a media card* (or something like that), rather than my standard option - *continue to aperture*. This worked for me and got me into aperture.
    _the second issue - restoring the image files - well this is a more of a problem:_
    - i noticed that most of the project folders worked perfectly well and that the images had been restored, however, those project folders with a light-table or a similar sub-set folder; well only the images in the light-table had been restored, the project folder images have been lost. i can't get these back. So before giving up completely, try reviewing the light-table or filter file within the project folder.
    to summarise - i don;t know why aperture failed on me last november. additionally, i would recommend to any aperture user that you do not create a backup vault of your files if you have a subset of images selected within the project folder, such as a light-table or a filter, the vault doesn;t seem to be able to handle them.
    i do hope this helps people if they have experienced a similar problem. for me, i've now given up on the mac platform, its just been to painful. Mac works great if there are no problems, but when a problem occurs, its generally a big one.
    I've lost a considerable number of images, ones which i am extremely proud of and enjoyed looking at and sharing, and this experience and a few other gripes (i.e. a distinct lack of appreciation for an issue which has affected many people) has now driven me back to the pc platform. so long Apple, if you fancy buying my second hand, but well looked after macbook, you will find it on ebay soon.

  • Vault error

    I've created a vault to backup my photo libraries and that went fine.
    However, when I try to update it with new images I get an error message "Update Vault Error" along with the directory path.
    I've tried creating a new vault, and then backing up, and get the same message.
    DOes anyone have advice on what is wrong with the Vault routine?
    Thanks.

    Yesterday I had the same problem in all three of my vaults. It happened after I'd made major changes in the organization of my Aperture library. I moved hundreds of masters from one project to another. When I tried to update the vaults, I got the same error messages or similar as the rest of you are reporting...something like "Can't create a directory on the Vault" and there'd be some 700 errors and the message was relaying the first five.
    I rebuilt the library (press Command and Option while booting Aperture). Still the Vaults could not be updated. So I trashed all three vaults and re-created them all. Very frustrating!
    The happy thing is that it seems that the Library itself was never compromised, and the Rebuild went very smoothly and quickly.
    I also have two full bootable back-ups of my hard drive on external drives. And these bootable back-ups include full copies of the Aperture Library. I re-did the bootable back-ups after the major re-organization of the Library, and there was no problem.
    In my view, there are major problems with the Vault software itself. It seems to stumble unnecessarily. Many users report that one corrupt file will cause the whole Vault procedure to crash. It would be much better if the Vault system carried on with the update and then simply reported the problem file, which could be corrected or deleted. But to have one corrupt file compromise the whole Vault update is ridiculous.
    And the Vault message which was repeated some 700 times was not helpful at all. It gave me no idea how to correct the situation, other than trashing the whole Vault and starting all over again.
    I use Synchronize Pro X (by Qdea) and Data Backup (by Prosoft Engineering) for my bootable back-ups and other backing up to external drives. Neither of these will handle a smart back-up of the Aperture Library package alone, covering only the incremental changes in the Library. But they do the incremental changes as part of the overall bootable back-up process.
    I'd like Apple to make the Vault process as solid as the back-up process provided by Qdea and Prosoft.

  • Error when I "Update Vault Path..."

    I have had some lingering problems with my Aperture library that I am just getting around to addressing. One is that I need to back up to my vault, but it is not letting me do so. When I hit the little (red) refresh button on the bottom of my window, I get the message:
    "Update Connected Vaults?
    Some vaults are not connected. Do you wish to replace the contents of all connected vaults with the current contents of your library?
    This cannot be undone."
    Because I'm an adventerous guy, I did this, but when I try to refresh my vault the next time I get the same error.
    So I started poking around and found the "Update Vault Path" menu item. This sounds like it should solve my problem, but when I go through and select my vault and try to update the path I get the error message:
    "Incorrect Vault Selected
    The path could not be updated because the selected vault does not match the original vault."
    This is definitely the right vault. It is on a partition of my Time Capsule. However I may have moved the file or changed the name of something a few months ago, which I suspect is why I'm having this problem now?
    What do I do to get that vault path back in order?

    Is this Aperture 3? Are you talking about one library or multiple libraries? How many vaults do you have connected to the library?
    If you click the *show/hide Vaults* button what does Aperture show you? This is the name of your vault(s) and their locations. Does that match what you think it should be?
    Sounds like you may be better off just creating a new vault and using that going forward.

  • Error when updating vault 3.3

    Hi,
    Just updated to 3.3
    tried updating vault
    it says  "To open this Library in Aperture, you must quit (null)"
    I click cancel and Aperture quits
    if  hold down option and open and the go to the vault it's greyed out
    Any one know how to update from Aperture 3.2.3
    Mark

    "Using Aperture Library First Aid Utilities
    Aperture 3 includes a new tool called Aperture Library First Aid that can correct the most common library and database issues Aperture 3 users are likely to encounter. To access the tool, do the following:
    Quit Aperture 3 if it is currently open.
    Press and hold the option and command keys while you launch Aperture 3.
    The Aperture Library First Aid utility will launch, and provide three different repair processes you can perform.
    Repair Permissions: Examines your library for permissions problems and repairs them. This requires Administrator access.
    Repair Database: Checks for inconsistencies in your library and repairs them.
    Rebuild Database: Examines and rebuilds your database. This option should be used only when repairs to the database or permissions do not address library problems."
    >>> repairing permissions will most likely resolve your problem.

  • Update failed, error code: 1, how to solve

    Update failed, error code: 1, how to solve

    Link for Download & Install & Setup & Activation problems may help
    -Chat http://www.adobe.com/support/download-install/supportinfo/

  • Cannot Update Vault in Aperture 2

    Today I started getting an error (actually 6 of them, all the same) when I try to update my vault. I am told "Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one." When I try to update the vault I get the "Comparing Library to Vault" barberpole for a while and then the error. Prior to today this vault file has been on the same drive for over a year and has worked flawlessly. I have done the following: 1) Deleted the old vault ad created a new one, 2) Deleted the Aperture plist file, 3) Repaired permissions on my boot drive and run Disk First Aid on the Western Digital MyBook (the drive is only 1/2 full) 4) Rebuilt the Library and run a Consistency Check 5) Trued putting the vault on any of my other drives.
    None of this has worked, I still get the same error message. Any suggestions as to what to try next?

    I had the same problem and tried about everything I found on this forum. None of it worked. Then I found the following two blog posts:
    http://rickcogley.blogspot.com/2010/01/fixing-aperture-vault-errors-from.html
    As I am not familiar with Terminal I did dare changing the settings. Trying via CMD-I didn't change anything.
    Then I found the following solution
    http://www.onlinenerd24.de/2009/04/17/aperture-you-need-to-remove-this-vault-and -create-a-new-one-error-message/
    Hooray! Removed the Flickr and Facebook plugins and everything is solved!
    Guess, I'll need to upgrade to Aperture 3 since this functionality is now standard available. Was that done intentionally, dear Apple?

  • HT1338 When trying to update getting (error surle error domain error-1100). It started yesterday, any help would be great. I have Mountain Lion 10.8.1 on a new macbook pro with retina display.

    When trying to update getting (error surle error domain error-1100). It started yesterday, any help would be great. I have Mountain Lion 10.8.1 on a new macbook pro with retina display.

    There are many people suffering from this problem right now (including me). It appears to be a server issue. Just wait and try checking for updates again tomorrow.
    Some things I have heard indicate that this may be a regional problem, though what parts of the world are affected I don't know yet. A few people have been helped by deleting the following preference file (paste the path into the Go -> Go to Folder window in the Finder to locate it), though most have not:
    ~/Library/Preferences/com.apple.SoftwareUpdate.plist
    Note that if you are trying to download iTunes 10.7, that can be found here:
    http://support.apple.com/kb/DL1576
    Also, note that there is no reason to be anxious to get it, as the only thing added in iTunes 10.7 is compatibility with iOS 6, which will not be available until the 19th, and the new iPhone, which will not be available until later as well. The new iTunes that was announced is iTunes 11, which is also not yet available.

  • Potential Windows Update database error detected 0x80070490

    This is the response I get when I run the Windows update troubleshooter from the Windows 8.1 Action Center.  If I click next it reports the errors have been fixed.  However if I run it again it reports exactly the same errors.
    After searching the Internet I have found that several users have reported having this issue.  As result of the aforementioned search I have tried the following:
    1) Run the Fixit tool for Windows 8.1 located at:
    http://support.microsoft.com/kb/971058/en-us.
    2) Run the System Update Readiness commands: DISM.exe /Online /Cleanup-image /Scanhealth and DISM.exe /Online /Cleanup-image /Restorehealth located at:
    http://support.microsoft.com/kb/947821/en-us.
    3) Saved contents of C:\Windows\System32\catroot2 to a temp folder and then deleted contents of C:\Windows\System32\catroot2.
    4)Renamed C:\Windows\SoftwareDistribution to C:\Windows\SoftwareDistribution.old
    5) Restarted Windows 8.1.
    6) Verified that C:\Windows\System32\catroot2 and that C:Windows\SoftwareDistribution folders had been rebuilt.
    7) I then ran the Windows update troubleshooter from the Window 8.1 Action Center again and got the same response as listed above. The errors still exist and are not fixed.
    8) Finally, I downloaded Windows 8.1 Enterprise Evaluation and I did a completely new clean install of Windows 8.1 and without installing anything else (no updates, no software, no antivirus) the above errors appeared within minutes after connecting
    to the internet.  I checked using the Windows update troubleshooter several times before connecting to the Internet and each time no problems were found, but shortly after I connected the above errors are shown to exists.
    Any suggestions that will help fix this issue will be of great help.

    Did anyone ever find an actual fix for this problem?  I have a very similar problem.  I have gone through the same steps for fixing my issues with getting a message of problems found every time I run the Windows Update troubleshooter.  It
    continually finds what it says are Potential Windows Update Database error detected 0x800700D and says they are fixed, along with another message saying Windows Update components must be repaired and it says they are fixed as well.  However, each time
    I run the troubleshooter it finds the same issues.  I have no problems running Windows Update under Windows 8.1 and them all installing without issue, yet I can't download or update ANY apps within the MS store and like the problem above, when it looks
    for my apps it says it's having problems finding them and to try later.  If I try to download even a free app, I get an error message that something happened and your purchase can't be completed. Error code: 0x80096004.
    I have dug through everything I can find on this error message and tried changing my sign in on my laptop to a local account, created a new MS account to access the store and continue to get the same error message.  I have tried it with my Kaspersky
    Internet Security 2015 turned completely off.  I've also ran SFC scannow and there are no errors and have ran DISM which found a problem but says it was fixed.  After running it again, there were no errors.  I have no other problems with anything
    else (that I know of on my machine).  It is an Asus Q400A and came with Windows 8.0.  I ran all the updates and then upgraded to 8.1 through the MS store without issue.  I have installed all updates since upgrading to 8.1 and have absolutely
    no problem running ANY updates, but can't seem to access the store no matter what I try.
    If anyone has found a solution to this I'd appreciate your input.  Hard to believe MS would put out a product that has such a basic problem that has affected so many users and can't seem to come up with some resolution that doesn't require registry
    editing, running commands from elevated command prompts, and a CS degree to resolve--there are soooo many issues online regarding this kind of error and others related to running SFC and DISM...most ending up in their ultimate default answer....renew or reinstall
    Windows and all the updates....which still doesn't resolve the problem for many!  I've always been a PC guy, but I'm starting to like the MacBook Pro I picked for work related reasons with great hesitation.  I've wasted more time chasing this issue
    down than I all the time I've spent actually using the Mac without even a hitch!
    Thx in advance for any feedback....please no MAC blasting....at this point, it would be not well received!!

  • Installation Failure: Windows failed to install the following update with error 0x800F0922

    Hi folks,
    I have a HP Elitebook Folio 9470p.  It came with Windows 8, and I installed it on my corporate domain.  I was trying to do some Windows updates so  I could upgrade it to Windows 8.1, but it fails installing the updates, whether or not I try
    to install them one at a time or all of them.  It has about 18 updates it needs from security updates to a .net framework update.  I run Symantec EP, and disabled it, checked for driver updates for things like display and networking and they are
    all up to date.
    I'm at a loss as to what to do.  It gives this error in the event log for each file, Event ID 20.
    Installation Failure: Windows failed to install the following update with error 0x800F0922: Security Update for Windows 8 for x64-based Systems (KB2862152).
    This is the example for KB2862152, but it gives the same error for every one.  I've tried to auto fix for Windows update issues and it fixed a couple of the issues, but not all of them, and provides no other help.
    I also deleted folders and files from the SoftwareDistribution folder as well, to no avail.  Any ideas what I can do to get whatever updates it needs, so I can fully patch it, and upgrade it to Win 8.1?
    Thanks for any help!

    Hi MM. Mr Kywildcat and Vegan Fan,
    GOOD NEW ! At this time, my issue is solved. The only black side is "how ?" : I hope that we will get a response some day ; however, and for in information  pnly - hoping this could help someone - I resume some actions which allowed this the happy end
    1) about installing 8.1 : I wanted to be sure that gain/pain ratio was positive, and that upgrading from a (potentially) damaged system would'nt produce something looking like a new Win 8.1, but difficult to maintain and keeping some negative potentialities.
    2) I was influenced by the fact that this
    0x800F0922  error acted as "a serial killerror", whose root cause could be a unique update error at reboot time concerning several (>20) packages, so I decided to test some manual upgrades.
    3)   Manual update (i.e. manual download and maunching of .msu packages) of the 2 following packages
    (whose update previously failed on a Windows Update) was successful : .NET Framework version 3.5 for  x64 (KB2898866) and Camera Codec Pack Windows 8 for x64 (KB2899190)
    4) So I decided to try Windows Update on a selection of packages, first : those concerning .Net Framework 3.5 and 4.5 (that is: KB2898866, 2901120, 2898865) --> Successful !
    5) finally, I selected almost all other packages, with some exceptions wich I (think to) have no need for : KB2871690, 2904659, 2843630. To be complete, here is the list of pakages updated one time at all :
    KB 2892074, 2893294, 2893984, 2909210, 2912390, 2916036, 2889784,2903938, 2911101, 2913152, 2917499
    --> always succesful.
    I am not a specialist, but I uess that this 0x800F0922 error hides another problem which is globally "H-RESULTED"
    to all updates pending in one update operation with reboot. This could be assumed from this CBS.log exterped from my last wrong attempts, where root cause seems not to be
    0x800f0922, but 0x80004003 :
    2014-02-15 21:29:13, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2014-02-15 21:29:13, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-02-15 21:29:18, Error  CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
    Anyway, thanks to you who spent some of your time to describe issues and search/ suggest solutions ; I will upgrade my system to 8.1 anyway, some of this day, when I am sure that my configuration does not hides some other problem. I thing that potential
    issue remains until maybe a new KB corrects it, wrong :-) ?
    And I hope that you - Mr Kywildcat - can upgrade your system on "current levels" trying similar attempts. 
    Phil   

Maybe you are looking for