IMessages still not working since upgrading months ago

I keep googling the error message:
"The Messages database is being upgraded, please wait while it finishes or Quit Messages and relaunch it later."
i've check my applegothic, I've zapped pram, I've tried turning on text message forwarding, i've checked containers of settings (and sadly erased my old time machine backups before i realized i had a problem) and have even tried re-installing my OS... nothing.
Anyone else (like from apple???) have any bright ideas? I've been back to using Skype with the rest of the heathens and i hate it...
S.O.S!!!!
Thanks and best wishes for the holidays!

Back up all data.
Quit Messages if it’s running. Force quit if necessary. Relaunch it and test after each of the following steps. If the problem isn't resolved, quit again and go on to the next step.
Step 1
Make sure you know the ID and password you use with iMessage. Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Select the login keychain from the list on the left side of the Keychain Access window. If your default keychain has a different name, select that.
If the lock icon in the top left corner of the window shows that the keychain is locked, click to unlock it. You'll be prompted for the keychain password, which is the same as your login password, unless you've changed it.
Right-click or control-click the login entry in the list. From the menu that pops up, select
          Change Settings for Keychain "login"
In the sheet that opens, uncheck both boxes, if not already unchecked.
From the menu bar, select
          Keychain Access ▹ Preferences ▹ First Aid
If the box marked
          Keep login keychain unlocked
is not checked, check it.
Select
          Keychain Access ▹ Keychain First Aid
from the menu bar and repair the keychain.
From the Category list in the lower left corner of the window, select My Certificates. Look carefully at the list of certificates in the right side of the window. If any of them is marked with a red "X" as expired or invalid, delete it. Also delete all items with "iMessage" or "com.apple.idms" in the name, whether valid or not.
From the menu bar, select
          Keychain Access ▹ Preferences... ▹ Certificates
There are three menus in the window. Change the selection in the top two to Best attempt, and in the bottom one to  CRL.
Log out and log back in.
Step 2
Hold down the option key and select
          Go ▹ Library
from the Finder menu bar. Move the following items from the Library folder to the Trash (some may not exist):
          Containers/com.apple.corerecents.recentsd
          Caches/com.apple.Messages
          Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent
          Containers/com.apple.iChat
          Containers/com.apple.soagent
          IdentityServices
Leave the Library folder open. Log out and log back in.
Step 3
Go back to the Finder and move the following item from the open Library folder to the Desktop:
          Messages
Note: you are not moving the Messages application. You’re moving a folder named “Messages.”
If Messages now works, delete the Messages folder on the Desktop. Otherwise, quit Messages again. Put back the folder you moved, overwriting the newer one that may have been created in its place.
Step 4
In the Preferences subfolder, there may be several files having names that begin with any of the following strings:
          com.apple.iChat
          com.apple.ids
          com.apple.imdsmsrecordstore
          com.apple.imessage
          com.apple.imservice
Move them all to the Desktop. There may also be a file with the name "com.apple.imagent.plist". Move that to the Trash.
Also in the Preferences folder, there's a subfolder named "ByHost". Open it and do the same thing.
Log out and log back in. Test again. This time Messages should perform normally, but your settings will be lost. You may be able to put back some of the files you moved to the Desktop in this step. Relaunch and test after each one. Eventually you should find one or more that causes Messages to malfunction. Delete those files and recreate whatever settings they contained.
If the issue is still not resolved, quit Messages again and put all the items you moved to the Desktop back where they were. You don’t need to replace the items you moved to the Trash. Stop here and post your results.
If you later decide that you don’t like the results of Steps 3 and 4, you can undo them completely by quitting Messages and restoring the items you deleted in those steps from your backup.

Similar Messages

  • IMessage is not working since upgrade to 6.0

    Hello, this is my first time posting.
    Since upgrading my i4 to 6.0 OS my imessage is not working.  My daughters with an i4 and i4S are having the same problem.  We always iMessage each other and all the bule bubbles are gone
    Any suggestions?
    thank you
    Barbara

    Didn't make a difference. Still no activity in the downloads window. The window pops up the download is saved in the target file but nothing shows up in the window. No progress, no file name or location and no options to open it or navigate to the folder.

  • IMessage does not work after upgrade to iOS 8.1.3 to my iPad 4

    iMessage does not work after upgrade to iOS 8.1.3 on my iPad 4

    I Fixed it by trying to sign in with a different ID and canceling when it asked For a password and then signed in with my ID and it works! No more error message. I got this idea from another discussion. Thank you for replying though.

  • 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

  • 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.

  • IMessages still not work properly

    My iMessage still not work properly after updated iOS 7.0.3, still can not directly sent to any user using iPhone, there messages will become SMS.

    http://support.apple.com/kb/ts2755

  • 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

  • IMessage not working since upgrading to ios 5.1 iPhone or iPad??!!

    Both myself and my partner have iPhones. I'm on a 4S she has my old 3GS. Since we both updated to 5.1 iMessage doesn't work, anyone I know who hasn't upgraded past 5.0, iMessage still works. Any ideas. Auto time update is on, on both handsets, it's strange as it was working for a few days after the update then it suddenly stopped one afternoon and hasn't worked since.

    Try turning iMessage off, wait a few minutes, then turn it back on.

  • Pcie_aspm control not working since upgrade to 2.6.39.1

    Hi
    Since upgrading to 2.6.39.1 it seems no longer possible to control power saving of pcie devices by echoing (default|performance|powersave) to /sys/module/pcie_aspm/parameters/policy.
    I am doing this as root, obviously.  The file is still there and can be read, root also has read and write permission, yet it seems I can no longer switch power levels by echoing like I used to.
    Has this been somehow disabled, or have the acceptable values been changed to something other than (default|performance|powersave)?
    Thanks

    OK. This same problem occurs on three different machines. 
    Before upgrading to 2.6.39.1 I can change the value of /sys/module/pcie_aspm/parameters/policy, after upgrading I cannot - I just get "bash: echo: write error: Operation not permitted"
    A look in /var/log/kernel.log finds these entries for pcie_aspm
    Jun 6 14:22:18 localhost kernel: [ 0.441788] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 6 21:00:12 localhost kernel: [ 0.441160] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 7 22:17:28 localhost kernel: [ 0.441171] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 8 07:23:00 localhost kernel: [ 0.441195] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 8 17:58:05 localhost kernel: [ 0.448257] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 8 18:08:47 localhost kernel: [ 0.448229] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 9 09:02:31 localhost kernel: [ 0.444868] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 10 13:35:44 localhost kernel: [ 0.448193] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 11 09:48:17 localhost kernel: [ 0.448820] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Jun 11 09:51:21 localhost kernel: [ 0.490917] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    But there is no change here between today, when I upgraded and the problem began, and a few days ago when everything was working well.
    I also found this in the changelog for 2.6.39 with regard to pcie aspm.  But it's not clear, at least to me, if this might have any bearing on my issue.  I would appreciate more knowledgeable eyes taking a quick look.
    commit bbfa306a1e5d9618231aa0de3d52a8eb1219d0c3
    Author: Naga Chumbalkar <[email protected]>
    Date: Mon Mar 21 03:29:14 2011 +0000
    PCI: Changing ASPM policy, via /sys, to POWERSAVE could cause NMIs
    v3 -> v2: Modified the text that describes the problem
    v2 -> v1: Returned -EPERM
    v1 : http://marc.info/?l=linux-pci&m=130013194803727&w=2
    For servers whose hardware cannot handle ASPM the BIOS ought to set the
    FADT bit shown below:
    In Sec 5.2.9.3 (IA-PC Boot Arch. Flags) of ACPI4.0a Specification, please
    see Table 5-11:
    PCIe ASPM Controls: If set, indicates to OSPM that it must not enable
    OPSM ASPM control on this platform.
    However there are shipping servers whose BIOS did not set this bit. (An
    example is the HP ProLiant DL385 G6. A Maintenance BIOS will fix that).
    For such servers even if a call is made via pci_no_aspm(), based on _OSC
    support in the BIOS, it may be too late because the ASPM code may have
    already allocated and filled its "link_list".
    So if a user sets the ASPM "policy" to "powersave" via /sys then
    pcie_aspm_set_policy() will run through the "link_list" and re-configure
    ASPM policy on devices that advertise ASPM L0s/L1 capability:
    # echo powersave > /sys/module/pcie_aspm/parameters/policy
    # cat /sys/module/pcie_aspm/parameters/policy
    default performance [powersave]
    That can cause NMIs since the hardware doesn't play well with ASPM:
    [ 1651.906015] NMI: PCI system error (SERR) for reason b1 on CPU 0.
    [ 1651.906015] Dazed and confused, but trying to continue
    Ideally, the BIOS should have set that FADT bit in the first place but we
    could be more robust - especially given the fact that Windows doesn't
    cause NMIs in the above scenario.
    There should be a sanity check to not allow a user to modify ASPM policy
    when aspm_disabled is set.
    Signed-off-by: Naga Chumbalkar <[email protected]>
    Acked-by: Rafael J. Wysocki <[email protected]>
    Cc: Matthew Garrett <[email protected]>
    Signed-off-by: Jesse Barnes <[email protected]>
    commit 1a680b7c325882188865f05b9a88d32f75f26495
    Author: Naga Chumbalkar <[email protected]>
    Date: Mon Mar 21 03:29:08 2011 +0000
    PCI: PCIe links may not get configured for ASPM under POWERSAVE mode
    v3 -> v2: Moved ASPM enabling logic to pci_set_power_state()
    v2 -> v1: Preserved the logic in pci_raw_set_power_state()
    : Added ASPM enabling logic after scanning Root Bridge
    : http://marc.info/?l=linux-pci&m=130046996216391&w=2
    v1 : http://marc.info/?l=linux-pci&m=130013164703283&w=2
    The assumption made in commit 41cd766b065970ff6f6c89dd1cf55fa706c84a3d
    (PCI: Don't enable aspm before drivers have had a chance to veto it) that
    pci_enable_device() will result in re-configuring ASPM when aspm_policy is
    POWERSAVE is no longer valid. This is due to commit
    97c145f7c87453cec90e91238fba5fe2c1561b32 (PCI: read current power state
    at enable time) which resets dev->current_state to D0. Due to this the
    call to pcie_aspm_pm_state_change() is never made. Note the equality check
    (below) that returns early:
    ./drivers/pci/pci.c: pci_raw_set_pci_power_state()
    546 /* Check if we're already there */
    547 if (dev->current_state == state)
    548 return 0;
    Therefore OSPM never configures the PCIe links for ASPM to turn them "on".
    Fix it by configuring ASPM from the pci_enable_device() code path. This
    also allows a driver such as the e1000e networking driver a chance to
    disable ASPM (L0s, L1), if need be, prior to enabling the device. A
    driver may perform this action if the device is known to mis-behave
    wrt ASPM.
    Signed-off-by: Naga Chumbalkar <[email protected]>
    Acked-by: Rafael J. Wysocki <[email protected]>
    Cc: Matthew Garrett <[email protected]>
    Signed-off-by: Jesse Barnes <[email protected]>
    commit 8b8bae901ce23addbdcdb54fa1696fb2d049feb5
    Author: Rafael J. Wysocki <[email protected]>
    Date: Sat Mar 5 13:21:51 2011 +0100
    PCI/ACPI: Report ASPM support to BIOS if not disabled from command line
    We need to distinguish the situation in which ASPM support is
    disabled from the command line or through .config from the situation
    in which it is disabled, because the hardware or BIOS can't handle
    it. In the former case we should not report ASPM support to the BIOS
    through ACPI _OSC, but in the latter case we should do that.
    Introduce pcie_aspm_support_enabled() that can be used by
    acpi_pci_root_add() to determine whether or not it should report ASPM
    support to the BIOS through _OSC.
    Cc: [email protected]
    References: https://bugzilla.kernel.org/show_bug.cgi?id=29722
    References: https://bugzilla.kernel.org/show_bug.cgi?id=20232
    Reported-and-tested-by: Ortwin Glück <[email protected]>
    Reviewed-by: Kenji Kaneshige <[email protected]>
    Tested-by: Kenji Kaneshige <[email protected]>
    Signed-off-by: Rafael J. Wysocki <[email protected]>
    Signed-off-by: Jesse Barnes <[email protected]>
    Thanks

  • Gmail push not working since upgrading to 4.0

    I have not been able to get my email to push since upgrading to 4.0. I have a 3GS and it worked great until the upgrade. Still have it set to push. Tried deleting itunes completely and then restore of iphone. Still no go. Please help.

    I have this problem also. It's really persistent and quite annoying. My Mail is silent like a rock on my iPhone 3gs; it's not pushing email notifications at all. To get new emails, I have to open Mail repeatedly, which defies the very definition of "notification" and "push" I really dislike the 4.0 update. I wish I never upgraded to it because everything was perfectly fine prior to the upgrade...

  • Develop module not working since upgrade to 4.2

    I've installed the 4.2 upgrade and now the develop module doesn't work anymore. It was working fine on 4.1, 64bit version.
    I'm on Windows 7 Pro, with second generation i7 CPU, 16 gig Ram
    Please have look at this thread at Photoshop.com were I reported this problem with a lot of details already. So far no help provided.....and that's 4 days ago.
    I really need help with this as I cannot work my Photos until this is fixed...or at least a solution to remove system files that are not removed when un-installing, as they bring the problem to a previous version that was working just fine before upgrade to 4.2 ( un-installed 4.2 then re-install 4.1, then 4.1 now has the same problem I have with 4.2) What a mess.......

    Thank you both, as this was the lead I needed to follow.....
    The profile is the problem...yes,.... and no....
    I use X-rite Color Munki as my profiler, latest upgrade, 1.0.2.0
    Using the above info, I've switched from my profile to sRGB, to manufacturer profile and others in the list...result : mine has the problem and not any of the others.
    I've just spent 7 hours straight, un-installing, re-installing, LR 4.2, 4.1, Color Munki, deleting the content of the LR Preference file, re-profiling using "easy" and "advanced", trying all kinds of combinations and sequences of the above....
    My findings:
    1- In LR 4.1   Using my profile, and deleting the content of the " Preference" file before starting LR, everything works just fine. Then when you shut it down and re-open it, the problem is back. Using " Task manager", I force the shut down of the " Not responding" LR, go back to deleting the "preference file" content, and LR works again. This does not work with LR 4.2
    2- In LR 4.1   On the last re-calibration I've done, I tried again and it did not work. Went to change profile to my default manufacturer's one and as expected LR worked....but I noticed that the calibration profile change did not affect the monitor screen, and LR 4.1 works perfectly on multiple starts and closes.
    Here is the interesting part....: My Color Munki profile is still displayed on the monitor, ( I did not "Restart" or "Re-boot" ) and the selected profile is the manufacturer's in Control Panel's Color Management, and LR 4.1 works perfectly.Can it be that the profile itself, displayed on the monitor, is not really the problem?
    Is it possible the "Conflict" would be in "Windows Color Management"? or LR's color management protocols?.....
    I have not tried # 2 with LR 4.2 as I'm kind of chicken of going another round of hours at it.... Like the saying goes..." If it ain't brokin', don't fix it ".....
    So, for now, I'll cary on with 4.1 as I can at least continue working......hopefully, using the "Sleep mode", and not "Shut down", the set-up will maybe stay "as is", and if not, I now know how to fool it.....

  • Smart actions not working since upgrade

    since installing the upgrade this weekend, why is my smartactions not working correctly?

        rlum1,
    We want you to be able to still enjoy the smart actions on your device! What type of device do you have? What exactly is happening with your smart actions? Please provide details.
    LindseyT_VZW
    Follow us on Twitter @VZWSupport

  • Volume keyboard shortcut not working (since upgrade to Snow Leopard)

    The following keyboard shortcut commands, when I have upgraded to OS 10.6 a couple of months ago, have stopped working:
    Command-Up Arrow
    Command-Down Arrow
    (They control the volume of the iTunes application itself)
    Apparently they still exist according to: http://www.apple.com/itunes/how-to/shortcuts.html
    I have the newest version of OS X and itunes, respectively: 10.6.2 and 9.0.2

    Try adding every drive to Spotlight's Privacy Pane in System Preferences>Spotlight, wait a few minutes & remove them, then wait a few hours/days to see if it's better.
    Though slower, in the intterim, you might try...
    EasyFind...
    http://www.macupdate.com/info.php/id/11076
    Find Any File...
    http://www.macupdate.com/info.php/id/30079/find-any-file
    I've actually disabled the worst Searh utility/Function I've ever seen on most of my Macs, just keep Spotlight active on a couple to try to assist with all it's problems.

Maybe you are looking for

  • Edit MSS 60.1 iView

    Hi, EP: 6.0 SP14 SAP: 4.70 X200 MSS : 60.1 I need to make a couple of changes to the standard worksets. NWDI is not configured. So can I simply install NWDS and make the required changes to these iViews by importing the PAR files and adjusting them,

  • Word of the Day Screensaver -- using non-English dictionaries

    As I'm studying German, I'd like to use an alternate dictionary with the "Word of the Day" screensaver. I've already installed the German dictionary, but it doesn't show up as an option. Is there a way to do this? As a side note, I'm disappointed wit

  • Oracle XE occasionally doesn't start correctly

    Hi, I have the services OracleServiceXE and OracleXETNSListener set to start automatically and most of the time when I try to connect to the database in the morning after booting up it works fine. However, occasionally I get TNS-12514 or TNS-12505 er

  • Headphone sound only when changing level or balance

    Hi, I have a weird problem with my Logitech B530 USB headset. I have configured it as the main input and output device in system settings, but I only hear sounds when changing sound level or balance. So if I e.g. start some music in iTunes I hear not

  • Passing Parameters To A Form

    I have a custom item which has a procedure to open a Portal application form, I would like to pass a value from a custom attribute into a field on the application form at the same time as opening it. Any HTTP experts done this or know how to do this?