Please Help! Keychain has not worked since upgrading to lion

Please help...I need Keychain access to work asap. Here is the error message that I'm getting:
Process:         launchd [8657]
Path:            /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access
Identifier:      com.apple.keychainaccess
Version:         ??? (???)
Build Info:      KeychainAccess-55121004000000000~155
Code Type:       X86-64 (Native)
Parent Process: launchd [137]
Date/Time:       2013-01-30 10:02:19.284 -0500
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report:          3707422 sec
Crashes Since Last Report:           65
Per-App Crashes Since Last Report:   63
Anonymous UUID:                      561D3F14-17F5-4940-B90F-F7C0AB826F8B
Crashed Thread: Unknown
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fc01028
Backtrace not available
Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
   r8: 0x0000000000000000   r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 0
Binary images description not available
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 1
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 3863
    thread_create: 0
    thread_set_state: 0
Model: MacBook4,1, BootROM MB41.00C1.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 2 GB, SMC 1.31f1
Graphics: Intel GMA X3100, GMA X3100, Built-In, 144 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz, 0xAD00000000000000, 0x48594D503131325336344350362D59352020
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz, 0xAD00000000000000, 0x48594D503131325336344350362D59352020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.15)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 2 incoming serial ports
Network Service: Ethernet Adaptor (en2) 6, Ethernet, en2
Network Service: Wi-Fi 2, AirPort, en1
Serial ATA Device: Hitachi HTS545025B9SA02, 250.06 GB
Parallel ATA Device: HL-DT-ST DVDRW GSA-S10N
USB Device: iPhone, apple_vendor_id, 0x12a0, 0xfa200000 / 2
USB Device: FreeAgent GoFlex, 0x0bc2 (Seagate LLC), 0x5031, 0xfd100000 / 3
USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0229, 0x5d200000 / 3

I installed, and ran, the Time Machine Buddy Widgit and it displayed this message:
Starting standard backup
Backing up to: /Volumes/Backup/Backups.backupdb
Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Backup/Backups.backupdb/Abraham size:37
Backup failed with error: 2

Similar Messages

Time Machine has not worked since upgrade to Lion

Hello,
I've noticed that my Mac Mini's Time Machine will no longer perform a backup - I keep receiving a "could not create the backup folder" error message. This problem only started after I upgraded my Mac Mini (2010 Model) to Lion, Time Machine had worked perfectly when I use to use Snow Leopard. I have both formatted and partitioned my Time Machine drives (the first drive was a Seagate Barracuda 7,200 RPM 1TB drive, the 2nd drive is a 2TB Porsche Drive I bought at my local Apple Store). Both drives, when I was partitioning them, were set to use the GUID Partition Scheme. The Seagate Drive is an Internal Hard Drive that is sitting in a ThermalTake 2-Bay Drive Dock which is connected by a USB Cord, the Porsche drive is an External Drive that is connected via a USB cord. I have also tried unmounting/remounting each drive, deleting the Time Machine "plist" file from my Library folder and restarting, and finally re-installing Lion from the recovery drive I made using the instructions on support.apple.com. Unfortunately, nothing I've done so far has solved the issue.
I checked my Console log for Time Machine and this is what I found:
Initial Time Machine Backup
9/16/11 1:24:03.918 AM com.apple.backupd: Backing up to: /Volumes/Backup/Backups.backupdb
9/16/11 1:24:07.255 AM postfix/master: master exit time has arrived
9/16/11 1:24:07.277 AM postfix/master: daemon started -- version 2.8.3, configuration /etc/postfix
9/16/11 1:24:07.000 AM kernel: nstat_lookup_entry failed: 2
9/16/11 1:24:13.344 AM com.apple.backupd: 571.1 MB required (including padding), 1.70 TB available
9/16/11 1:24:19.677 AM com.apple.backupd: Copied 1601 files (10.3 MB) from volume Macintosh HD.
9/16/11 1:24:19.765 AM com.apple.backupd: 558.7 MB required (including padding), 1.70 TB available
9/16/11 1:24:20.346 AM com.apple.backupd: Copied 100 files (93 bytes) from volume Macintosh HD.
9/16/11 1:24:20.413 AM mds: (Error) Volume: Could not find requested backup type:2 for volume
9/16/11 1:24:20.427 AM com.apple.backupd: Starting post-backup thinning
9/16/11 1:24:20.427 AM com.apple.backupd: No post-back up thinning needed: no expired backups exist
9/16/11 1:24:20.442 AM com.apple.backupd: Backup completed successfully.
Second Backup (1 Hour Later)
9/16/11 2:24:05.102 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Backup/Backups.backupdb/Abraham size:37
9/16/11 2:24:08.685 AM postfix/master: master exit time has arrived
9/16/11 2:24:08.726 AM postfix/master: daemon started -- version 2.8.3, configuration /etc/postfix
9/16/11 2:24:09.000 AM kernel: nstat_lookup_entry failed: 2
9/16/11 2:24:15.143 AM com.apple.backupd: Backup failed with error: 2
Being a relatively new Mac User (I only knew about the above "fixes" after doing several Google Searches) I have no idea what the Console Log is trying to tell me or how to fix whatever is being referred to. I will be very grateful for any assistance that can be offerred.

I installed, and ran, the Time Machine Buddy Widgit and it displayed this message:
Starting standard backup
Backing up to: /Volumes/Backup/Backups.backupdb
Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Backup/Backups.backupdb/Abraham size:37
Backup failed with error: 2

Threaded Email NOT working since upgrading to Lion

Threaded emails were working fine until I upgraded to Lion. I have even done a fresh reinstall, enabled classic view, organize by conversation, and adjusted the view setting in the preferneces to include related messages.
While my replies are grouped together, the other persons are group on their own and NOT bundled with mine. I am using IMAP, NO Rules in place on the server OR on Mail.app.
Any suggestions?
Thanks,
Shelby

iOS: Unable to send or receive email
http://support.apple.com/kb/TS3899
Can’t Send Emails on iPad – Troubleshooting Steps
http://ipadhelp.com/ipad-help/ipad-cant-send-emails-troubleshooting-steps/
Setting up and troubleshooting Mail
http://www.apple.com/support/ipad/assistant/mail/
Server does not allow relaying email error, fix
http://appletoolbox.com/2012/01/server-does-not-allow-relaying-email-error-fix/
Why Does My iPad Say "Cannot Connect to Server"?
http://www.ehow.co.uk/info_8693415_ipad-say-cannot-connect-server.html
iOS: 'Mailbox Locked', account is in use on another device, or prompt to re-enter POP3 password
http://support.apple.com/kb/ts2621
iPad Mail
http://www.apple.com/support/ipad/mail/
Configuration problems with IMAP e-mail on iOS with a non-standard SSL port.
http://colinrobbins.me/2013/02/09/configuration-problems-with-imap-e-mail-on-ios -with-a-non-standard-ssl-port/
Try this first - Reset the iPad by holding down on the Sleep and Home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons. (This is equivalent to rebooting your computer.)
Or this - Delete the account in Mail and then set it up again. Settings->Mail, Contacts, Calendars -> Accounts Tap on the Account, then on the red button that says Remove Account.
 Cheers, Tom

Time Machine backups have not worked since upgrade to Lion OS X

I get the following error message when trying to use Time Machine - "The backup was not performed because an error occurred whilecopying files to the backup disk. The problem may be temporary. Try again later to back up. Ifthe problem persists, use Disk Utility to repair your backup disk."

Not one of Apple's better messages.
It's having a problem with a particular file, but there's no hint of that.
See #C3 in Time Machine - Troubleshooting.

I cannot conect to APP Store. I upgraded to IOS 8.3 and APP Store has not worked since. I am being asked to tipe my user name /password and nothing happens afterwards. No error messages either.

I cannot connect to APP Store. I upgraded to IOS 8.3 and APP Store has not worked since. I am being asked to type my user name /password and nothing happens afterwards. No error messages either.

hey the sever is down for the moment try again latter tonight... we have been attepting and i eveen went to the apple store third Street Primonade and alejadnro could not help me he said to try soon
John

HT3258 My Parallels program is now not working since upgrading my MacBook Pro to OS X Mountain Lion. I was wondering if there is a solution to getting this working again?

My Parallels program is now not working since upgrading my MacBook Pro to OS X Mountain Lion. I was wondering if there is a solution to getting this working again?

You just need to update it to the latest version. See:
http://kb.parallels.com/114449

I have an Iphone 4 and the camera shutter wont open, I have tried most things and it has still not opened, it has not worked since I have got it. What should I do?

I have an Iphone 4 and the camera shutter wont open, I have tried most things and it has still not opened, it has not worked since I have got it. What should I do?

Here's basic troubleshooting for iOS:
https://sites.google.com/site/appleclubfhs/support/advice-and-articles/troublesh ooting-ios
(Note that my links to other pages may promote my organization, and this should not be taken as an endorsement by Apple)

Home sharing on apple tv not working since upgrade to yosimite

home sharing with my Apple TV (gen 3) and iMac not working since upgrading iTunes (12.0.01.26) and installing Yosemite (10.10) on my iMac (2008).
everything worked fine before this!

Hey stephenfromdominion,
Thanks for the question. I understand that you are experiencing issues with Home Sharing after upgrading to OS X Yosemite. For troubleshooting information, check out the following resource:
Troubleshooting Home Sharing
http://support.apple.com/kb/ts2972
Thanks,
Matt M.

Everytime i plug my iphone into my computer it says device not recognized i was syncing my phone and it got interupted and has not worked since i have iphone 4 with 4.1 software lol what can i do to not lose everything

Everytime i plug my iphone into my computer it says device not recognized i was syncing my phone and it got interupted and has not worked since i have iphone 4 with 4.1 software lol what can i do to not lose everything

I'd start with the following document with that one:
iPhone, iPad, iPod touch: How to restart the Apple Mobile Device Service (AMDS) on Windows

My morphie pack does not work since upgrading

My juice pack (Morphie) Does not work since i have upgraded the ios to 7.1.1
I have two iphones a 4s that has not been updated yet and also the 5s which has been updated. The 4s is working perfectly well with the juice pack but the 5s is absoultely crap to say the least. I complained to Morphie and to their credit the sent me a new pack and it has the same problem. This MEANS since the update there has been a change with apple and they have made our 100€ chargers redundant as I only get 20 - 25% extra battery when I should be getting a full charge
This is not acceptable for phones that are expensive and the accessories that we buy to go with them are also an additional expense and very expensieve to. That doesnt matter too much when they work, but then they dont it is NOT good.
Someone come back to us and give us a solution please.
Elena - a very loyal apple client with apple imacs in the office, mac book pros and air mac for sale staff along with ipad minis and iphones......... NOT A HAPPY CLIENT

3l3na t wrote:
Thanks guys for the responses but I am not convinced this is a MOPHIE problem. Their customer service department have been great and look after their clients. I have two iphone 4s´s which have not been upgraded for fear of being left with the rubbish battery I have with my relatively new iphone 5s. Mophie have replaced the amost new juice pack that I had with a completely new one that has the same problem...... funny how this has happened since the ios 7.1.1. update
I have been using MOPHIE juice packs for a number of years and have never experienced anything like this before. It seems rather strange that after upgrading I have this problem that APPLE negates to rectify.
Of course I wouldn´t have to use a 3rd party accessory if the battery was made to last and if APPLE had an alternative, I would of course buy apple but they don´t. I am a huge fan of Apple but cannot run a business with phones that cannot be upgraded for the fear of loosing battery life which would mean loosing clients which would mean loosing my lively hood.
Full phone restore was done too.
Still not HAPPY
Sorry, as already stated your using a 3rd party accessory take it up with mophie.
I have no issue with my mophie after updating to 7.1.1 - so your theory is flawed.
My battery life can last up to a day and a 1/2 - I only bought the mophie as a backup battery and because it is bulky and can protect my phone in case I drop it.

Canon Printer mx860 not working since upgrade to Yosemite, it is connected to my Mac via usb. Any suggestions? Thanks. LL

My 2009 Canon MX860 Pixma printer not working since an upgrade to Yosemite on my MAC version 10.10. It is connected by USB. Have had no previous issues with printing, scanning or faxing. When trying to print my Calendar I only get light vertical dotted lines, none horizontal, no words and vague header colors. Checked printer image on the on my MAC which shows the same problem. All of the color and black cartridges are new.
The recent upgrade to the Canon application says it is completed but it is not, image on application upgrade is a circle with an X.
Any suggestions? Could this simply be a compatibility problem? I'd sure like to keep my Canon printer.
Thanks, LL

Can you open System Information (Applications > Utilities) and select Printers in the left sidebar. If the MX is the only printer connected to the Mac then its information will be shown in the right pane. If you have more than one printer, then a list will be shown in the top right pane. Select the MX to see its information in the bottom right pane. Can you copy this information and paste back here for me to check.
Also an FYI - this is the Mavericks forum. The Yosemite forum is here

Signature field NOT working since upgrade to Adobe Pro X

Hi Forum,
Form stop working since upgraded to Pro X (ver 10) in Adobe. Getting this message:
IntegriSign
This plug-in is intended for validating signatuers signed using earlier versions of Acrobat. To sign using this version of Acrobat use "IntegriSign to Acrobat 9.0 and later" handler
I have changed settings in Adobe Pro X to the above but still get the same message.
Do anyone know how to fix this?
Thanks,
Patricia

Download directly from Apple and install over what you have now;
iTunes 12.0.1

Full-Text Search has not worked since we upgraded to 2012

I have a filestream database and table. Our full-text searches have always worked until we upgraded to SQL 2012 in December. Now, no file that has been uploaded since December is searchable. What has gone wrong here. It should have been
a clean upgrade. We are not getting any error messages. We are just not getting any records returned when we search on a word that we know are in the documents we've uploaded since December (for instance, the word 'aluminum').
Filestream is enabled for the instance.
A full-text catalog exists and contains a full-text index (the same one we've always had). Full-text indexing is ENABLED.
I've tried rebuilding the catalog and the index. I've tried to do a FULL POPULATION on the table.
We haven't changed our queries nor the way the files are uploaded.
Nothing works. I have been a database administrator since the SQL 2005 days and I have never seen anything like this.
Please help.

Hi GINGER PIERCE,
Since the issue regards SQL Server Search. I will help you post the question in the related forums. It is appropriate and more experts will assist you.
According to your description, in theory , if you can do a full-text search for SQL Server 2008, when upgrading the SQL Server version from 2008 to 2012, the Full text indexing feature should be run well in SQL Server 2012 databases. If not , you can try
to restore your database from SQL Server 2008 to SQL Server 2012, create an new Full-Text Catalog and Index on the table or view in the database, and then use Full Text Index to search words, phrases and multiple forms of word or phrase via FREETEXT() and
CANTAINS() with “and” or “or” operators. check if it is normal that the full-text search feature is enabled in the SQL Server 2012 instance. For more information , see:
Full Text Search step by step in SQL Server 2012.
Note: In SQL Server 2012 SP1 ， the server will report that Full Text Search is not supported in this edition of SQL Server when it clearly is. The workaround is to create the initial catalog by using a T-SQL query:
CREATE FULLTEXT CATALOG
In addition, since it is a fileStream database, we need to verify if you do Full Text Searches on documents in FileTables, if yes, you should enable FileStream database for your SQL Server, and enable FileTable options for the database. For more information,
see:
Full Text Searches on Documents in FileTables.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

Node.js: running "npm help term " not working since upgrade to 0.8.3

Running
npm help <command>
usually displays npm's man page on <command>. And if the the command doesn't exist, npm will show a "top hits" list of related commands.
But since upgrading to 0.8.3, running it will always show the "top hits" list, even for existing commands.
After digging around I found that the problem is the man files that npm uses in /usr/lib/node_modules/npm/man are gzipped (with filenames like install.1.gz) which breaks npm since npm is expecting ungizipped filenames.
After further digging, it seems that the gzipping of npm's man pages was only added in node 0.8.2-2
So, basically just checking if anyone has this same problem (and confirming it's not a problem with upstream) before submitting it to bugs.archlinux.org

The man command should handle gzipped or non-zipped man pages just fine. I'm not sure if there is an official standard, but packages are free to use gz'ed or non-zipped man pages - they both work just fine. If it's not an official standard recommendation, though, gzipped man pages have become so common that they are almost a 'de facto' standard. But package managers (at least pacman) do not gzip the man pages. This is generally handled upstream or in the packages Makefile.
But, more to the point for the present issue, while man can open either format of page, if you give a full path, you must include the extension. Example:
$pacman -Ql bash | grep man
bash /usr/share/man/
bash /usr/share/man/man1/
bash /usr/share/man/man1/bash.1.gz
bash /usr/share/man/man1/bashbug.1.gz
$ man bash #works
$ man /usr/share/man/man1/bash.1.gz #works
$ man /usr/share/man/man1/bash.1
man: /usr/share/man/man1/bash.1: No such file or directory
No manual entry for /usr/share/man/man1/bash.1
.... er ... I just installed this again and did some tinkering. Most of what I've said is true (and perhaps someday useful) but currently irrelevant. Npm does not use `man` at all. It just echo's it's help information directly to the terminal.
Perhaps the syntax has changed since the last version you used, but it seems to be doing just what it is supposed to:
$ npm help
Usage: npm <command>
where <command> is one of:
... <snip> ...
npm <cmd> -h quick help on <cmd>
npm -l display full usage info
npm faq commonly asked questions
npm help <term> search for help on <term>
npm help npm involved overview
Specify configs in the ini-formatted file:
/home/jmcclure/.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config
[email protected] /usr/lib/node_modules/npm
$ npm help cache
Top hits for "cache"
npm help cache cache:23
npm help config cache:20
npm help folders cache:7
npm help pack cache:2
npm help index cache:2
npm help changelog cache:1
(run with -l or --long to see more context)
$ npm cache -h
npm cache add <tarball file>
npm cache add <folder>
npm cache add <tarball url>
npm cache add <git url>
npm cache add <name>@<version>
npm cache ls [<path>]
npm cache clean [<pkg>[@<version>]]
Note in the first output it specifies that "npm help <term>" is only supposed to search for the term and return the top-listing list while "npm <command> -h" is the syntax to view the help information for a given command.
Last edited by Trilby (2012-07-25 14:16:31)

Bluetooth and Isight not working since upgrade to Mountain Lion

Hello,
I have a mid-2010 MBP running OSX 10.8.2.
Ever since upgrading to Mountain Lion, My bluetooth and iSight both have stopped working. I have tried the clear the SMC numerous times. Mostly it does not have any effect. However, a couple of times, it has restored service to the iSight and the bluetooth, but as soon as I reboot the machine they are back to being disabled. Sometimes they become available without my resetting the SMC and for seemingly no reason. I have also replaced a couple of different kext files: Apple_iSight.kext and AppleUsbVideoSupport.kext with known good ones. I also Verified and Repaired on the disk. In this case, permissions issues were detected and repaired, but without fixing my original problems.
I would like desperately to resolve this without buying a new disk and doing a fresh install of OSX Lion. I would definitely NOT go back to Moutain Lion in this scenario. But I don't know what do next. I don't see many posts on this subject and those I have seen do not offer much hope. I know I am not the only one suffering with this, but I don't think Apple is addressing the problems, because they may not be pervasive enough right now.
If anyone has found a way to resolve this permanently, please share with me. I would like to roll back to Lion, but can't do that either.
Can anyone help me out?
Thanks,
Brad.
<Edited by Host>

This is likely a conflict with some 3-rd party s/w you have on the MBP but not the other two computers. Have a look in here
 > System Preferences.. Users & Groups | Login Items
Is there something in here that's not in the same list on the other Macs? If so, try removing it and restarting your computer. If that solves the problem, try contacting the developer to see if there's an update.
If that doesn't solve the problem, go through your other 3rd party apps and look for updates on all of them. One of them is stopping your mouse from working properly.

Please Help! Keychain has not worked since upgrading to lion

Similar Messages

Maybe you are looking for