Idle time lockup troubleshooting tips

My Macbook Pro is locking up during idle times.  It seems pretty random.  Sometimes it will get through a night, sometimes not.  Sometimes it will get through a workday, sometimes not.
What tips do you all have to help me nail down the problem?
Here is what I have tried and more info:
- Removed all recently installed software
- No new hardware was added since the problem started
- Turned off screensaver thinking that might help, it didn't
- At one point it seemed to get better, so I updated to 10.9.4 and now its back
- Turned off Apple Persistence off so I would start with a fresh slate after a crash (Why isn't this standard?)
- Checked the Console, there doesn't seem to be any reasonable standard set of messages that happen before the lock up.
- Bunch of external drives connected, doesn't seem to matter, locks up with or without them connected.
- Connected to 23" ASUS monitor via DisplayPort/Thunderbolt, locks up with or without it connected.
The lock up:
I come back to my computer, and hit a key.  Screen lights, but stays black. If monitor connected, it wakes, and I see a mouse cursor.  The mouse is responsive, but otherwise it is dead.  Network is not responsive either.  Tried SSH into the box to shutdown more elegantly, but no dice.  The last time I saw the beach ball of death.  The only way out is to hold down the power button until the thing reboots.
Thanks for any ideas and any help!
Chris

Removed them and it still happened.
New EtreCheck log
EtreCheck version: 1.9.15 (52)
Report generated August 31, 2014 at 10:57:50 PM EDT
Hardware Information: ?
  MacBook Pro (13-inch, Mid 2012) (Verified)
  MacBook Pro - model: MacBookPro9,2
  1 2.5 GHz Intel Core i5 CPU: 2 cores
  16 GB RAM
Video Information: ?
  Intel HD Graphics 4000 - VRAM: (null)
  Color LCD 1280 x 800
  ASUS VK278 spdisplays_1080p
System Software: ?
  OS X 10.9.4 (13E28) - Uptime: 0 days 0:8:27
Disk Information: ?
  HGST HTS541515A9E630 disk0 : (1.5 TB)
  S.M.A.R.T. Status: Verified
  EFI (disk0s1) <not mounted>: 209.7 MB
  Mac HD (disk0s2) / [Startup]: 1.3 TB (635.72 GB free)
  Recovery HD (disk0s3) <not mounted>: 650 MB
  BOOTCAMP (disk0s4) /Volumes/BOOTCAMP: 202 GB (130.38 GB free)
  MATSHITADVD-R   UJ-8A8 
USB Information: ?
  Seagate FreeAgentDesktop 320.07 GB
  S.M.A.R.T. Status: Verified
  disk1s1 (disk1s1) <not mounted>: 32 KB
  Cockpit (disk1s3) /Volumes/Cockpit: 319.94 GB (247.46 GB free)
  Western Digital Ext HDD 1021 1.5 TB
  S.M.A.R.T. Status: Verified
  EFI (disk4s1) <not mounted>: 209.7 MB
  Spare (disk4s2) /Volumes/Spare: 1.5 TB (992.31 GB free)
  Western Digital My Passport 0730 750.12 GB
  S.M.A.R.T. Status: Verified
  EFI (disk3s1) <not mounted>: 209.7 MB
  My Passport (disk3s2) /Volumes/My Passport: 749.78 GB (286.4 GB free)
  Seagate FreeAgent Pro 750.16 GB
  S.M.A.R.T. Status: Verified
  EFI (disk2s1) <not mounted>: 209.7 MB
  FreeAgent (disk2s2) /Volumes/FreeAgent: 749.81 GB (289.31 GB free)
  Apple Inc. FaceTime HD Camera (Built-in)
  Apple Inc. Apple Internal Keyboard / Trackpad
  Apple Computer, Inc. IR Receiver
  Apple Inc. BRCM20702 Hub
  Apple Inc. Bluetooth USB Host Controller
Thunderbolt Information: ?
  Apple Inc. thunderbolt_bus
Gatekeeper: ?
  Mac App Store and identified developers
Kernel Extensions: ?
  [loaded] com.Logitech.Control Center.HID Driver (3.9.1 - SDK 10.8) Support
  [not loaded] com.Logitech.Unifying.HID Driver (1.3.0 - SDK 10.6) Support
Launch Daemons: ?
  [loaded] com.adobe.fpsaud.plist Support
  [running] com.crashplan.engine.plist Support
  [loaded] com.dustinrue.CPHelperTool.plist Support
  [loaded] com.google.keystone.daemon.plist Support
  [loaded] com.microsoft.office.licensing.helper.plist Support
  [running] com.teamviewer.teamviewer_service.plist Support
  [loaded] net.sourceforge.MonolingualHelper.plist Support
  [not loaded] synmacph.plist Support
Launch Agents: ?
  [running] com.amazon.sendtokindle.launcher.plist Support
  [loaded] com.google.keystone.agent.plist Support
  [running] com.Logitech.Control Center.Daemon.plist Support
  [running] com.teamviewer.teamviewer.plist Support
  [running] com.teamviewer.teamviewer_desktop.plist Support
User Launch Agents: ?
  [running] com.amazon.cloud-player.plist Support
  [loaded] com.valvesoftware.steamclean.plist Support
User Login Items: ?
  iTunesHelper
  ControlPlane
  Alfred 2
  Dropbox
  CrossOver CD Helper
  Google Chrome
  Google Drive
  Eye-Fi Helper
  Air Video Server HD
  CrashPlan menu bar
Internet Plug-ins: ?
  FlashPlayer-10.6: Version: 14.0.0.176 - SDK 10.6 Support
  QuickTime Plugin: Version: 7.7.3
  Flash Player: Version: 14.0.0.176 - SDK 10.6 Support
  Default Browser: Version: 537 - SDK 10.9
  nplastpass: Version: 2.5.5 Support
  Silverlight: Version: 5.1.30514.0 - SDK 10.6 Support
  JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Safari Extensions: ?
  LastPass
Audio Plug-ins: ?
  BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
  AirPlay: Version: 2.0 - SDK 10.9
  AppleAVBAudio: Version: 203.2 - SDK 10.9
  iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins: ?
  Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes: ?
  remoting_host_prefpane  Support
  Flash Player  Support
  Logitech Control Center  Support
  Webmailer  Support
Time Machine: ?
  Time Machine not configured!
Top Processes by CPU: ?
      6% WindowServer
      3% CrashPlanService
      2% Safari
      2% com.apple.WebKit.WebContent
      2% LCCDaemon
Top Processes by Memory: ?
  410 MB com.apple.IconServicesAgent
  393 MB mds_stores
  213 MB com.apple.WebKit.WebContent
  213 MB Safari
  147 MB Google Chrome
Virtual Memory Information: ?
  8.06 GB Free RAM
  5.66 GB Active RAM
  1003 MB Inactive RAM
  1.30 GB Wired RAM
  793 MB Page-ins
  0 B Page-outs

Similar Messages

  • Time Machine - TROUBLESHOOTING

    This article provides some troubleshooting tips for common Time Machine errors and problems.
    It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
    Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
    _*C o n t e n t s*_
    *Section A. _TOOLS YOU MAY NEED*_
    *A1. Time Machine Buddy widget*
    *A2. Time Tracker*
    *A3. Tinker Tool*
    *Section B. _SET - UP PROBLEMS*_
    |
    *B1. I can't select my drive for use with Time Machine*
    *B2. The Change Disk option doesn't work*
    *B3. No last or oldest backup date shown*
    *B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
    *Section C. _BACKUP FAILURES*_
    |
    *C1. Initial Backup Failed*
    *C2. Other Backup Fails*
    *C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
    *C4. "This backup is too large"*
    *C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*
    *C6. The backup volume is read only*
    *C7. "Error (12): Link of previous volume failed."*
    *C8. Backup fails after Logic Board replacement*
    *C9. "The back-up disk image could not be created."*
    *C10. Error: (-50) Creating directory*
    *C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    |
    *D1. Stuck in Preparing*
    *D2. Backup is Slow or "hung"*
    *D3. TM is doing a full backup for no good reason*
    *D4. My backups seem too large*
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    |
    *E1. Backups were deleted unexpectedly*
    *E2. I can't see some backups*
    *E3. I can't see backups for a disk/partition that's no longer connected*
    *E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
    *Section A. _TOOLS YOU MAY NEED*_
    There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
    _*A1. Time Machine Buddy widget*_
    |
    Click here to download the +*Time Machine Buddy*+ widget.
    It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
    You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing CMD-C. This copies them to your "clipboard," so you can post them in a thread here (via CMD-V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
    If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /var/log for the other user.
    Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
    |
    _*A2. Time Tracker*_
    |
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
    |
    _*A3. Tinker Tool*_
    |
    Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
    Do not use any of the other options unless you know the possible consequences.
    |
    *Setcion B. _SET - UP PROBLEMS*_
    _*B1. I can't select my drive for use with Time Machine*_
    If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
    |
    _*B2. The Change Disk option doesn't work*_
    If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
    |
    _*B3. No last or oldest backup date shown*_
    |
    If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
    1. Do a +*Back Up Now.*+ That will often recover the info.
    2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
    3. A Log Out or Restart may fix it.
    4. If they're still not shown, try a *"Full Reset:"*
    |
    a. Turn TM Off, de-select the drive (select "none"), note any exclusions in Options, quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Re-select your drive (and re-enter any exclusions).
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    |
    _*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
    |
    Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
    Try a "Full Reset" as in item #B3.
    |
    *Section C. _BACKUP FAILURES*_
    _*C1. Initial Backup Failed*_
    The most common cause is the TM drive not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
    First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
    Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
    Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
    Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
    |
    _*C2. Other Backup Fails*_
    If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
    If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
    Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
    If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
    *Messages that might indicate trouble:*
    Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
    Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
    . . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
    Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
    Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    These may indicate a problem with the first file referenced. See the next item.
    If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
    |
    _*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
    Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock. If that backup completes normally, there's no real problem.
    If the next one fails also, then there most likely is something wrong -- the question is, what?
    Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
    |
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    |
    If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
    /Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
    The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
    If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
    Go to TM's Preferences and click Options.
    In the next panel, click the plus sign at the bottom.
    In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
    Select it, click Exclude, then Done.
    Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
    If the backup runs ok, then you need to figure out what's wrong with that file.
    If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #B3).
    If you get the same message for a different file, you may need stronger stuff:
    a. Exclude your TM disk from any anti-virus scanning.
    b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
    c. Do a +*Repair Disk*+ (not permissions) on your TM drive/partition, via Disk Utility (in your Applications/Utilities folder).
    d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
    e. If the original file is on your internal HD, do a +*Verify Disk*+ (not permissions) on it. If that reports errors, you'll have to boot from your Leopard Install disc and use it's copy of Disk Utility to repair it:
    1. Insert your Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
    2. Select your language when prompted.
    3. On the next screen select Utilities in the Menubar, then +*Disk Utility.*+
    4. Do a +*Repair Disk*+ on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
    5. Reboot normally.
    If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
    |
    _*C4. "This backup is too large"*_
    |
    For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
    There are some backups that Time Machine *will not delete,* however. It won't delete the most recent backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it won't delete any from the prior sequence, either.
    Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
    When this happens, you have a few options:
    1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
    2. Erase the TM disk/partition and let TM start over, with a new, full backup of your entire system.
    3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    4. Get a different disk/partition for your Time Machine backups. Then either:
    Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
    Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder. Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    |
    _*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*_
    |
    Open the Terminal app (in your Applications/Utilities folder).
    Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
    In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
    (where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
    At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
    <pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
    example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
    Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
    Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
    |
    _*C6. The backup volume is read only*_
    First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
    If that doesn't correct it,
    If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
    If you don't want to erase it, here's a workaround:
    First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
    If not, use the TinkerTool app (see #A3) to show hidden files.
    In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet address). Copy or make a note of it.
    Then follow the rest of the instructions in item #C5.
    |
    _*C7. "Error (12): Link of previous volume failed."*_
    |
    This usually happens when you replaced a drive with a different one, but with the same name as the original.
    Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
    Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
    And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
    |
    _*C8. Backup fails after Logic Board replacement*_
    The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
    This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or control-click (right-click) the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
    |
    _*C9. "The back-up disk image could not be created."*_
    |
    If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
    It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
    |
    _*C10. Error: (-50) Creating directory*_
    |
    This may indicate a problem with your TM drive. Use Disk Utility (in your Applications/Utilities folder) to do a +*Repair Disk*+ (not permissions) on it. If any errors are found that Disk Utility can't fix, run it again (and again) until they're all fixed or it can't fix any more.
    If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #B3.
    If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
    |
    _*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
    |
    If this happens after getting a new Logic Board, see item #C8.
    This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
    You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
    If that doesn't help, try a complete reset. See item #B3.
    |
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    _*D1. Stuck in Preparing*_
    |
    See this Apple Support document: Time Machine may display "Preparing" for a longer time
    Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
    Also see the next topic:
    |
    _*D2. Backup is slow or "hung"*_
    |
    Get the Time Machine Buddy messages (see #A1).
    If it shows Event store UUIDs don't match
    and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
    If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
    1. Exclude your TM disk/partition from any anti-virus scanning.
    2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
    _*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
    3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them.
    4. Try moving the TC or AEBS and Mac closer together.
    5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
    6. Try repairing the Sparse Bundle with Disk Utility (in your Applications/Utilities folder). Mount the Sparse Bundle, then drag it into the Disk Utility sidebar, then use +*Repair Disk*+ (not permissions).
    _*If backing up to an External hard drive:*_
    7. Do a +*Repair Disk*+ (not permissions) on it via Disk Utility (in your Applications/Utilities folder).
    8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
    9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard).
    10. Try different port(s), cable(s).
    11. See if your drive has an automatic sleep or "spin down" feature you can disable.
    12. Check the maker's web site (support or forum) for any updates.
    If nothing helps, your drive may be failing.
    |
    _*D3. TM is doing a full backup for no good reason*_
    Time Machine may do a full backup after any of the following:
    Using a new disk or partition for backups (always).
    A full restore (probably).
    Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
    Changing your computer's name via System Preferences > Sharing (probably).
    Renaming a disk/partition that's being backed-up (probably).
    Going several days without a backup (probably; also seems to depend on the volume of changes).
    Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
    |
    _*D4. My backups seem too large*_
    |
    Time Machine may be doing a full backup of your entire system. See item #D3.
    Doing an OSX update can cause a large backup, as it may add or update several thousand files.
    Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
    Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
    There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
    You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
    |
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    _*E1. Backups were deleted unexpectedly*_
    |
    Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
    Usually when this happens unexpectedly, it's because TM has done a new full backup, which of course requires a lot of space. See item #D3 for the common reasons.
    If in doubt, get the widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
    |
    _*E2. I can't see some backups*_
    |
    TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
    Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
    To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your Dock.
    You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
    Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    |
    _*E3. I can't see backups for a disk/partition that's no longer connected*_
    |
    Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
    Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
    On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
    Select the Finder window for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
    |
    _*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
    |
    Do a +*Repair Disk*+ (not permissions) on your TM drive, via Disk Utility (in your Applications/Utilities folder).
    Re-select your TM drive via TM Preferences > Change Disk.
    If you're using Spaces, try disabling it, at least temporarily.
    If you have any sort of video out cable, especially HDMI, try disconnecting it, at least temporarily.
    Do a "complete reset" of TM, as in item #B3.

    This article provides some troubleshooting tips for common Time Machine errors and problems.
    It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
    Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
    _*C o n t e n t s*_
    |
    *Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
    |
    *A1. Time Machine Buddy widget*
    *A2. Time Tracker*
    *A3. Tinker Tool*
    *A4. Full Reset of Time Machine*
    *A5. How to do a Repair or +Verify Disk+*
    *Section B. _SET - UP PROBLEMS*_
    |
    *B1. I can't select my drive for use with Time Machine*
    *B2. The +Change Disk+ button doesn't work*
    *B3. No last or oldest backup date shown*
    *B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
    *Section C. _BACKUP FAILURES*_
    |
    *C1. Initial Backup Failed*
    *C2. Other Backup Fails*
    *C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
    *C4. "This backup is too large"*
    *C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM drive>"*
    *C6. The backup volume is read only*
    *C7. "Error (12): Link of previous volume failed."*
    *C8. Backup fails after Logic Board replacement*
    *C9. "The back-up disk image could not be created."*
    *C10. Error: (-50) Creating directory*
    *C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    |
    *D1. Stuck in "Preparing" or "Calculating changes"*
    *D2. Backup is Slow or "hung"*
    *D3. TM is doing a full backup for no good reason*
    *D4. My backups seem too large*
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    |
    *E1. Backups were deleted unexpectedly*
    *E2. I can't see some backups*
    *E3. I can't see or restore from backups for a disk/partition that's no longer connected*
    *E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
    *Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
    There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
    _*A1. Time Machine Buddy widget*_
    |
    Click here to download the +*Time Machine Buddy*+ widget.
    It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
    You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing Cmd+C. This copies them to your "clipboard," so you can post them in a thread here (via Cmd+V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
    If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /private/var/log and it's contents for the other user.
    Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
    |
    _*A2. Time Tracker*_
    |
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
    |
    _*A3. Tinker Tool*_
    |
    Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
    Do not use any of the other options unless you know the possible consequences.
    |
    _*A4. Full Reset of Time Machine*_
    |
    a. Go to TM Preferences, turn TM Off, de-select the drive (select "none"), and click the Options button. Note any exclusions in the +Do Not Back Up+ box, and other option(s) on that panel. Then quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Go back to TM Preferences, re-select your drive, re-enter any exclusions and other options.
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    |
    _*A5. How to do a Repair or +Verify Disk+*_
    |
    This will Repair or Verify the +File System+ on a disk, partition, or sparse bundle (not the actual hardware). Use the +*Disk Utility+* app, in your Applications/Utilities folder. Do this when TM backups are turned-off, or at least not running.
    To Repair an *external disk attached to an Airport Extreme,* disconnect it from the Airport, connect it directly to your Mac and select it in the Disk Utility Sidebar.
    To Repair an external or *internal Time Machine* disk/partition, select it in the Disk Utility Sidebar.
    To Repair the *sparse bundle* on a Time Capsule, connect via an Ethernet cable if you can; it will be much faster. Then mount the sparse bundle by opening the TC in the Finder and double-clicking on the sparse bundle. Drag the sparse bundle into Disk Utility's sidebar and select it.
    With the desired partition or sparse bundle selected, click the +*Repair Disk+* (not permissions) button. This may take a while, especially on a Time Capsule. If errors are found, but not all of them were repaired, run the +*Repair Disk+* again, and again, until it either fixes all the errors or can't fix any more.
    To Verify your internal (boot) drive/partition (since you can't Repair the one you're running from), select it in Disk Utility's sidebar and click the +*Verify Disk+* (not permissions) button. If it shows errors, you'll need to fix them via this procedure:
    1. Insert your Leopard/Snow Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
    2. Select your language when prompted.
    3. On the next screen, select Utilities in the Menubar, then +*Disk Utility.*+
    4. Do a +*Repair Disk*+ (not permissions) on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
    5. Reboot normally.
    |
    *Section B. _SET - UP PROBLEMS*_
    _*B1. I can't select my drive for use with Time Machine*_
    If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
    |
    _*B2. The +Change Disk+ button doesn't work*_
    If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
    |
    _*B3. No last or oldest backup date shown*_
    |
    If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
    1. Do a +*Back Up Now.*+ That will often recover the info.
    2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
    3. A Log Out or Restart may fix it.
    4. If they're still not shown, try a Full Reset (see #A4).
    |
    _*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
    |
    Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
    Try a "Full Reset" as in item #A4.
    |
    *Section C. _BACKUP FAILURES*_
    _*C1. Initial Backup Failed*_
    The most common cause is the TM drive (but not a Time Capsule) not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
    First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
    Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
    Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
    Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* must be either GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be either +Apple Partition Map+ (preferred) or GUID for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
    |
    _*C2. Other Backup Fails*_
    If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
    If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
    Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
    If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
    *Messages that might indicate trouble:*
    Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
    Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
    . . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" (Leopard) or "Calculating changes" (Snow Leopard) phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
    Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
    Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    These may indicate a problem with the first file referenced. See the next item.
    If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
    |
    _*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
    Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock. If that backup completes normally, there's no real problem.
    If the next one fails also, then there most likely is something wrong -- the question is, what?
    Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
    |
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    |
    If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
    /Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
    The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
    If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
    Go to TM's Preferences and click Options.
    In the next panel, click the plus sign at the bottom.
    In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
    Select it, click Exclude, then Done.
    Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
    If the backup runs ok, then you need to figure out what's wrong with that file.
    If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #A4).
    If you get the same message for a different file, you may need stronger stuff:
    a. Exclude your TM disk from any anti-virus scanning.
    b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
    c. Do a +*Repair Disk*+ on your TM drive/partition. See #A5 above.
    d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
    e. If the original file is on your internal HD (your boot drive), do a +*Verify Disk*+ on it. See #A5 above.
    If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
    |
    _*C4. "This backup is too large"*_
    |
    For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
    There are some backups that Time Machine *will not delete,* however. It won't delete the last remaining backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it may not delete any from the prior sequence, either.
    Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
    When this happens, you have a few options:
    1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
    2. Erase the TM disk/partition with Disk Utility (in Applications/Utilities) and let TM start over with a new full backup.
    3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    4. Get a different disk/partition for your Time Machine backups. Then either:
    Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
    Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder (in Snow Leopard only, you can copy the Backups.backupdb folder via the Finder). Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    |
    _*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM Drive>"*_
    |
    Open the Terminal app (in your Applications/Utilities folder).
    Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
    In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
    (where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
    At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
    <pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
    example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
    Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
    Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
    |
    _*C6. The backup volume is read only*_
    First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
    If that doesn't correct it,
    If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
    If you don't want to erase it, here's a workaround:
    First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
    If not, use the TinkerTool app (see #A3) to show hidden files.
    In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet Address). Copy or make a note of it.
    Then follow the rest of the instructions in item #C5.
    |
    _*C7. "Error (12): Link of previous volume failed."*_
    |
    This usually happens when you replaced a drive with a different one, but with the same name as the original.
    Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
    Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
    And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
    |
    _*C8. Backup fails after Logic Board replacement*_
    The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
    This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or right-click the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
    |
    _*C9. "The back-up disk image could not be created."*_
    |
    If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
    It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
    If that doesn't help, apply the same rules to the name of your Time Capsule.
    |
    _*C10. Error: (-50) Creating directory*_
    |
    This may indicate a problem with your TM drive. Do a +*Repair Disk*+ on it. See #A5 above.
    If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #A4.
    If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
    |
    _*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
    |
    If this happens after getting a new Logic Board, see item #C8.
    This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
    You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
    If that doesn't help, try a full reset. See item #A4.
    |
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    _*D1. Stuck in "Preparing" or "Calculating changes"*_
    |
    See this Apple Support document: Time Machine may display "Preparing" for a longer time
    Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
    Also see the next topic:
    |
    _*D2. Backup is slow or "hung"*_
    |
    If this is your first backup under Snow Leopard after updating from Leopard, try cancelling the backup, doing a Restart, and trying again.
    Otherwise, get the Time Machine Buddy messages (see #A1).
    If it shows Event store UUIDs don't match
    and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
    If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
    1. Exclude your TM disk/partition from any anti-virus scanning.
    2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
    _*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
    3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them. Remove any punctuation and spaces. Do the same with the Time Capsule or Airport Extreme name.
    4. Try moving the TC or AEBS and Mac closer together.
    5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
    6. Try repairing the TC's Sparse Bundle or AEBS drive's TM disk/partition. See #A5 above.
    _*If backing up to an External hard drive:*_
    7. Do a +*Repair Disk*+ on it. See #A5 above.
    8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
    9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard, as some are USB 1.0).
    10. Try different port(s), cable(s).
    11. See if your drive has an automatic sleep or "spin down" feature you can disable.
    12. Check the maker's web site (support or forum) for any driver or firmware updates.
    If nothing helps, your drive may be failing (they all do, sooner or later).
    |
    _*D3. TM is doing a full backup for no good reason*_
    If this is your first backup on Snow Leopard after upgrading from Leopard, try cancelling the backup, doing a Restart, and trying again.
    Time Machine may do a full backup after any of the following:
    Using a new disk or partition for backups (always).
    A full restore (probably).
    Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
    Changing your computer's name via System Preferences > Sharing (maybe).
    Renaming a disk/partition that's being backed-up (probably).
    Going several days without a backup (probably; also seems to depend on the volume of changes).
    Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
    |
    _*D4. My backups seem too large*_
    |
    Time Machine may be doing a full backup of your entire system. See #D3.
    Doing an OSX update can cause a large backup, as it may add or update several thousand files.
    Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
    Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
    There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
    You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
    |
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    _*E1. Backups were deleted unexpectedly*_
    |
    Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
    In addition, regardless of space, TM also routinely "thins" your backups. It keeps one per week for as long as there's room; one per day (the first) for a month; all others for 24 hours.
    Usually when old weekly backups are deleted unexpectedly, it's because TM has done a new full or large backup, which of course requires a lot of space. See #D3 or D4 for common reasons.
    If in doubt, get the +Time Machine Buddy+ widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
    |
    _*E2. I can't see some backups*_
    |
    If you can't see the backups for a disk/partition that's no longer connected, see #E3 below.
    TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
    Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
    To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by right-clicking the TM icon in your Dock.
    You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
    Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    |
    _*E3. I can't see backups for a disk/partition that's no longer connected*_
    |
    Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
    Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
    On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
    Select the Finder window or TimeLine entry for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore selected items, since they're from a different disk/partition. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    You can restore an entire disk/partition to a different one (erasing any previous contents) via the procedure in item #14 of the Frequently Asked Questions *User Tip* at the top of this forum.
    |
    _*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
    |
    This can be caused by any of a number of things. Try these fixes:
    If you're using a Finder replacement (such as Pathfinder), be sure the Finder is running.
    If you're using Spaces, turn it off temporarily.
    If you have a second monitor, or anything plugged-in to a video-out port, disconnect it temporarily.
    De-select your TM drive via TM Preferences > Change Disk (select "none"), then re-select the correct one.
    Do a "complete reset" of TM, as in item #A4.
    Do a +*Repair Disk+* on your TM drive. See #A5 above.
    Try or create another user (System Preferences > Accounts). If it works ok from that user, delete the file:
    +*<home folder of the user where it doesn't work>/Library/Preferences/com.Apple.Finder.plist+*

  • TROUBLESHOOTING TIPS RE: iCLOUD MAIL SERVER DROPOUT

    Here's what I learned throughout this and I will post a discussion in a separate thread for the rest of the folk out there.
    MYTHS AND FACTS RE: iCLOUD MAIL SERVER DROPOUT- WHAT I'VE LEARNED
    Hopefully this troubleshooting helps everyone that has had or having issues, for now and for the future...
    Firstly, the Apple system status is a bit of a myth. Because it is a global community of people using iCloud, it does not always update in real time. The Apple techs check this when there is issues, as do the public, so odds are unless every single person is having issues around the globe, then it won't reflect an issue. http://www.apple.com/au/support/systemstatus/
    Apple technicians work in territories. For example, I live in Australia so I had to deal with a tech supervisor who looks after Australasia and who is based in Singapore. They don't get a notification if a group of people in Canada are having problems, even if they are identical to mine, unless as above, the whole world is having issues.
    CHECK THESE FORUMS as a first step measure to work out if the problem seems to be just you and your account, or a wider community. Particularly before you make any major change to your email accounts, passwords, computers or phones.
    If you get an issue in the next week or so (and keep in mind for the future) Error Message: "MY NAME" returned the error "[AUTHENTICATIONFAILED] Authentication failed." Your username/password or security settings may be incorrect. Would you like to try re-entering your password?" and this happens multiple times when you know the password is correct, then odds are that the server is down and you are best to wait it out. Try checking your mail via iCloud to test. If you can send it through there, odds are that the glitch has nothing to do with your password or issues with your account and rather than make changes, try and wait it out.
    If all of your folders in your email disappear, if they are IMAP folders, then log into iCloud mail in your web browser to check that they are still there. It just means that your mail client (Mac Mail, Outlook for Mac etc) can't access the IMAP folders via the server. Don't panic until they are gone from every device you use your email on.
    Be wary of deleting ANYTHING from your computer unless you are backing it up first. For example, I had a tech guy on the first day of the server drop out, who gave me the wrong advice of deleting EVERYTHING from my keychain. This resulted in me having massive security issues for web browsers and thus, I couldn't log into my iCloud mail in my browser. Not only did I have to re-install my OS Maverick to fix it (which took 10 hours) but I could have muddled through this mess by continuing to work using web mail.
    If everyone seems to be having a mail server problem based on online community discussions, then you are not alone and TELL your Apple tech this. Send copies of the links to the various conversations. Push them (nicely) to investigate internally what is going on and don't let them rely on the System support status. It also helps to put in a report to Apple down the track.
    Make sure that you can get a copy of Apple tech guys email address. Thankfully, even though I was on the phone to them for in excess of 7 hours over the past two days, I could update my guy via email and also send him screen shots of things that did or didn't work using my iPhone. We would keep in contact and all I would have to do is send him an email and he would call me back straight away. No holding or dealing with any call centre issues, which is probably the only reason why I didn't lose my cool too much.
    If you can get into your iCloud through your web browser, you have the options under the inbox and then the little wheel thing down the bottom (preferences) to put a vacation message, like an out of office. Put that on and explain you are having email issues and give another email address or your contact number. At least the people that you need to contact will know that things could get lost in cyberspace. I wish I had of known this earlier.
    You can also forward emails emails to another email address under preferences. Also very handy.
    Become friends with your tech guy rather than enemies. If you don't feel like your tech guy knows what he's talking about, politely request to speak to a supervisor. I would be having a nervous breakdown right now (small business owner, lost two days of billable hours so I am financially behind) if I didn't have a good relationship with the guy that has been helping me. We are a good team, with me updating him with the information, via these forums, to find a proper solution to the issue and to rectify the wrong information I was given by the previous Apple tech guy I spoke to.
    Ask them to replicate your issue on their side of the fence to troubleshoot. For example, my tech guy Levi replicated my issue with websites by intentially removing the system certificate from his computer and he realised that was what the problem was, and thus he could quickly find out how to fix it.
    Back up your stuff regularly. It might be annoying but it is peace of mind if know you are only going to lose a minimum of a week's worth of stuff.
    Apple has an engineering team and tech guys raise 'tickets' to them with information on what has happened to their clients. I don't know much about this but I would assume it is having the engineering team investigate to stop this happening in future. They can only work with the feedback they get I suppose. I would also suggest doing the Apple Care survey so they also get feedback. We need to explain to them that we are asking for communication first and foremost - whilst it is inconvenient, if we all knew when and where they would be doing server upgrades (which the rumours indicate that this is what happened) then I don't feel everyone would be so frustrated.
    Using your computer is like raising a child - you know when something is not right, even if you are not experienced at it yet. Sure, you may not know the lingo but trust your instincts and tell your tech guy. I have learned more in the past two days about computers and Mac's than ever before and I know when I can confidentially say that strange things were happening to my Mac and where Apple went wrong in guiding me. Don't always take a blanket or easy explanation if you don't think it is right; odds are it will result in making changes to your product that do more harm than good.
    Keep a record of notes of how much time you have spent on the issue (including phone calls to Apple), what they have told you to do and at what time, changes to passwords, troubleshooting tips and the contact details (and reference numbers) of who you speak to. I'm not sure if Apple provides compensation for these issues or anything along these lines, but I certainly will be informing them so they can try and better their service to me in the future.
    Anyway, I hope that helps everyone a bit - these are just things that I have learned and if anyone else has any tips please feel free to add them.

    Tried port 465 but it wouldn't work.
    Went to our help desk and here's the reply I got (paraphrased slightly cuz the person at the help desk was trying hard to be helpful and I don't want to get him/her in trouble):
    I presented this question to the university team and then waited for a long time to get the following reply:
    we do not allow relay from non-university IP addresses.
    port 25 for smtp is a standard worldwide.
    For the most part, that went right over my head and didn’t answer anything, but I hope it means something to you.
    I called him to get more clarification, but all I really got out of it was that, if you don’t use exchange which is secure via port 443, then your other option is to use smtp.  And then he said something about how relay, iron ports, and authenticated accounts work together to make it secure.  I know it makes me sound a lot more inept than I am, but all that made little sense to me.  What I gather, is… that by selecting SSL when configuring your client, it makes it so that your login info and mail content is safe.  Sorry, I can’t provide a more cohesive and comprehensive explanation, but I think the bottom line is that they have combined a non-secure protocol with other stuff to make it secure.
    So, I'm hoping that checking SSL and using port 25 somehow solves the problem to the satisfaction of our IT professionals at the University ...
    Again, thanks for taking the time to educate the rest of us!

  • After upgrading, I am getting the dreaded "iTunes has stopped working" message.  I've followed all of the troubleshooting tips on the forum without success.  Fortunately, it works on my other computers.  Running Win7 pro.

    After upgrading iTunes, I'm getting the dreaded "iTunes has stopped working" message after launch.  I've tried the troubleshooting tips on the Forum without success (though most are pretty old...).  Fortunately, iTunes works on my other computers, but I have iPad backups on this one that I'd like to keep.  Anybody else with this issue??

    My inclination is that it is something in the projects or in the manuals being linked that is the culprit because that is where the consistency lies - projects were created identically and manuals all follow identical formats. The problem typically only occurs after the project has been successfully created and the manual is subsequently updated and I am syncing the manual in RH so I can generate a new AIR file. This is the first time the project has consistently corrupted every time I try to generate the Word document after linking it in RH. This makes little sense to me since it generated fine a couple weeks ago and I did nothing special when I updated it in Word yet when I tried to update it in RH, that is when it originally corrupted. The bottom line is that I cannot 100% trust that any project I run will work the next time. I end up just crossing my fingers and hoping for the best.
    My problems seemed to start once I went to RH9 (from RH8) because we had upgraded from MS Office 2003 to the 2010 version and I needed 9 for the docx extension. Like I said, it is not all the time - I can be beating my head against the wall getting one of the projects to work, then create 3 more projects that have no problems and then the next one leaves me wanting to throw my PC through a window....
    Deleting the CPD does not corrupt the project, it just removes my default linked document that allows me to circumvent linking the styles individually for that project. Once I have a manual linked and I remove the CPD, it just creates a new one. What I am saying is that if I delete the CPD file, it does not prevent the project from corrupting nor does it make the corrupted project viable again.
    thanks!
    Kathi

  • IP device tracking and idle timer problem

    Hi,
    We are deploying 802.1X in our network and have encountered problem with a type of payment terminal.
    The problem is that the terminal do not 'speak' to the network after the first initial DHCP request, the terminal waits for incoming packets from a counter to start the payment process. After the idle-time the MAC is flushed from the switch and the port is not authorized any more.
    To solve this we set 'authentication control-direction in' on the port and use 'ip device tracking' to keep the client on the network, ip device tracking sends an arp request every 30 seconds to clients.
    Our ISE is sending Radius:Idle-Timeout = 300 and the timer start to count down when the client is authenticated.
    In Wireshark, I can see that the ARP request is going out and the ARP reply coming back in but this does not update the inactivity timer for the client. So after 5 minutes the port is gone, and there is no way to get the port up again from the network. Traffic from the client brings up the network.
    This looks like a bug to me, anyone seen this, or a similar behaviour?
    Running:
    ISE 1.2p6
    IOS 12.2(55)SE6
    From Trustsec 1.99 Wired 802.1X Deployment Guide:
    Tip Enable IP Device Tracking with inactivity timers to keep quiet endpoints connected. When IP Device Tracking is enabled, the switch periodically sends ARP probes to endpoints in the IP Device Tracking table (which is initially populated by DHCP requests or ARP from the end point). As long as the endpoint is connected and responds to these probes, the inactivity timer is not triggered and the endpoint is not inadvertently removed from the network.
    From CLI output
    SW03#sh auth sessions int fa0/4
                Interface:  FastEthernet0/4
              MAC Address:  xxxx.xxxx.5289
               IP Address:  10.10.10.64
                User-Name:  XX-XX-XX-XX-52-89
                   Status:  Authz Success
                   Domain:  DATA
           Oper host mode:  multi-auth
         Oper control dir:  both
            Authorized By:  Authentication Server
               Vlan Group:  N/A
          Session timeout:  N/A
             Idle timeout:  300s (server), Remaining: 2s
        Common Session ID:  0A17BD07000000A925152A7B
          Acct Session ID:  0x00000458
                   Handle:  0x090000A9
    Runnable methods list:
           Method   State
           dot1x    Failed over
           mab      Authc Success
    SW03#
    SW03#
    SW03#
    SW03#sh auth sessions int fa0/4
                Interface:  FastEthernet0/4
              MAC Address:  Unknown
               IP Address:  Unknown
                   Status:  Running
                   Domain:  UNKNOWN
           Oper host mode:  multi-auth
         Oper control dir:  both
          Session timeout:  N/A
             Idle timeout:  N/A
        Common Session ID:  0A17BD07000000AA251A0019
          Acct Session ID:  0x00000462
                   Handle:  0x800000AA
    Runnable methods list:
           Method   State
           dot1x    Running
           mab      Not run

    Here is the port config.
    Just to clarify, everything is working except that the terminal is losing the authentication. The terminal works again if traffic is initiated from the terminals menu, like with ping.
    interface FastEthernet0/4
     description Standard
     switchport access vlan xxx
     switchport mode access
     switchport block unicast
     switchport voice vlan xxx
     switchport port-security maximum 2
     switchport port-security
     switchport port-security aging time 5
     switchport port-security violation restrict
     priority-queue out
     authentication control-direction in
     authentication event fail action next-method
     authentication event server dead action reinitialize vlan xxx
     authentication event server dead action authorize voice
     authentication event server alive action reinitialize
     authentication host-mode multi-auth
     authentication order dot1x mab
     authentication priority dot1x mab
     authentication port-control auto
     authentication periodic
     authentication timer reauthenticate server
     authentication timer inactivity server
     authentication violation restrict
     mab
     no snmp trap link-status
     dot1x pae authenticator
     dot1x timeout tx-period 5
     storm-control broadcast level pps 100
     storm-control multicast level pps 100
     storm-control action trap
     spanning-tree portfast
     service-policy input users

  • IMessage - Idle timer setting?

    Is it possible to change the default "idle time" in iMessage before it changes status to "Away"?
    Running OS X 10.8.2 on a MBP.
    I checked all the preference settings in the iMessage UI, but nothing seems to exist for controlling when the system automatically changes my status from "Online" to "Away".  Many times I'm working at my desk, but not actively typing and the system will change state.  In other IM utilities such as Adium, I am able to adjust the timer to reflect my work habits.

    Did your son inherit your old iPhone when you got the 5C? Somewhere in his phone's settings it either still has your phone number or email address as part of his FT/Messages configuration.
    Read through this and make sure that both of your phone's are configured correctly for just your numbers and addresses.
    http://www.ilounge.com/index.php/articles/comments/the-complete-guide-to-facetim e-imessage-set-up-use-and-troubleshooting/

  • Increase the showing time of tool tip

    Hi Experts,
    We have a requirement in OAF. We want to increase the time of tool tip which is showing on the field. Right now whenever we move to the field, its showing after some time its disappering. We know that is the functionality of tool tip. but user want to see that until he move from that field.
    where we can set the timings? or any other way to achieve the requirement.
    Thanks in Advance.
    Regards,
    Ganesan G

    Rajesha,
    It did not help in increasing the Idle time, I was going through google and other blogs they was mentioning tcode RZ11
    I looked into the above tcode but was not sure where the increase the idle time, but anyway thank you
    due points have been assigned

  • Can't Find Answer In Troubleshooting tips

    I repeatedly get this message:
    "This backup is too large for the backup disk. The backup requires 446.53 GB but only 379.40 GB are available."
    Yet, the original disk is only half full and 160GB in capacity, while the disk volume that I'm trying to transfer to is roughly a clear and empty external 370GB volume. Found nothing on troubleshooting that addressed this exact problem.
    Any ideas?
    Message was edited by: phranky

    If you have it excluded, but Time Machine still tries to back it up, the preferences file is probably corrupted. (But note that it will only appear in the exclusions box while it's connected.)
    Try a "full reset" of Time Machine per #A4 of [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

  • Is my mx1000 dead? troubleshooting tips?

    my logitech mx1000, which was working fine for about a year until now, still lights up when moved, but it's not actually moving the cursor on screen.
    in the System Profiler, I can see that it is plugged in - it shows up in the list.
    i've tried unplugging + plugging, tried it on a different 'puter - but no luck.
    anyone have any troubleshooting tips?
    Powerbook G4 15 inch   Mac OS X (10.4.8)  

    I'm on my 4th MX1000, 3 were replacements for failed units from connection problems with the base station/charger that would cause skipping and moments of inoperability. I have noticed that Logitech gear lasts about a year. I called Logitech and told them the problems that I was having, which seems less than what you are having, and they sent me replacements with relatively little trouble. Same thing with the Apple cordless keyboard. After X amount of time both would loose the ability to connect and/or operate properly, thus, needing replacement and both at about a year into their use.
    I trust you have tried to reconnect the mouse to the Charger/Receiver and/or reinstalled the LCC software for your OS?
    I have also noticed that certain versions of the LCC software will cause problems with OSX and/or will not operate properly. But in these cases the mouse would still operate under the OS mouse pref parameters to the point that the health of the mouse would let it.
    I was told once that there was a problem with the charger stations for the MX1000. That is the first place for connectivity.
    Call Logitech and talk to them. This their problem and I doubt that you will find any solutions here. But a good trouble shooting activity, if you can, is to try it on a PC. If it works there then the mouse and parts are in working order. I have noticed that Logitech is PC first and foremost, even though they say their gear is Mac compatible.
    G4 FW800, 2GB RAM, 2-DVR110s, 4-500GB HDs, 3-Monitors, 2-Turtle Doves, 1-iTTUSB   Mac OS X (10.4.8)   Totally Stuffed/Max'd Out with lots of great toys.

  • Unable to capture the Idle time for BSP page

    Hi Experts,
    I want to capture the Idle time of my BSP page. If that is 5 mins then i have to display the pop up displaying the remaining time.
    Please let me know how to capture the IDLE TIME. not the time after the page is loaded.
    Any suggestion will be helpful.
    Aready checked in SDN but unable to get the solution so posting it.
    Thanks in advance.
    Sravanthi.V

    hi,
    After capturing the idle time iam giving the warning popup to user before 5mins of expiry.Now my requirement is if the user clicks on OK button of popup the page should get refresh. i.e.Idle time should of system should break and we have to get one more hour for expiry.
    Thanks in advance,
    Sravanthi.V

  • RCA Connection Pool idle Time-Out takes no effect !

    My question description goes here.
    According to JCA specification, I developed my 'ManagedConnectionImpl' class from the interface 'ManagedConnection'. I realize the 'destroy()' function to send out logout request to the EIS.
    Then I deployed the connector in Sun Java System Application Server, I noticed there are two parameters in Connection Pool part, they are:
    1. Idle Timeout. It said it's the maximum time that a connection can remain idle in the pool. I assume the connection will be removed after the specific time expired and before it's removed it will call the recallable function, 'destroy()', in my concrete class, 'ManagedConnectionImpl'.
    2. Pool Resize Quantity. it said it's number of connections to be removed when pool idle time expired.
    I am weird about it. I think EIS had itself session control strategy, if the specific session time-out expired, it will invalidate this session. So I think we will set 'Idle Timeout' in application server to be shorter than the EIS session time-out. If the 'Idle Timeout' in application server expired, it should remove all connections inside otherwise maybe the connection with invalid session will exist! (the background knowledge is our system will return back soap fault when it meets invalid session, so the invalid connections will not be removed by switching on your configuration item, 'On Any Failure')
    So I set "inital and minimum pool size" to 8, "maximum pool size" to 32 and "Pool Resize Quantity" to 32. (I expect AS to remove all when pool idle time expired)
    After deploying, I send out requests at the first round and wait for the time expired but I can't see the desired logout requests from pool automatically even one. Firstly I guess if my recallable function definition is wrong but when I shut down the Application Server, the desired logout requests are sent out from pool automatically. So I think my recallable function definition is workable.
    What's your comments on it?
    P.S.
    I am using Sun Java System Application Server 8.1.
    Thanks in advance!
    BRs
    /Leo

    I have had following test to ensure I sent out notification to listener.
    [#|2005-08-23T16:14:25.061+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    It's in managed env!|#]
    [#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    enter matchManagedConnections() !|#]
    [#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    try to find a matching and existing one, reuse it!|#]
    [#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    Found a matching and existing one, reuse it!|#]
    [#|2005-08-23T16:14:25.495+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    tearDown() is called, the application-level connection is released!|#]
    [#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    enter calling close() of managed connection.|#]
    [#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    Start calling close() of managed connection.|#]
    [#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    start to notify the listener the completeness of connection.|#]
    [#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
    notify the listener the completeness of connection successfully.|#]
    Whether it's related with the initial and minimum number parameter? Although I found it will not be created during AS start-up and will be created at the first request.
    Whether it shall be kept to meet the minimum requirement? I have failed to set it to 0.

  • Crystal report not shown after application idle time

    i have a web page which uses around 10 session variables to store values on a button click.and after assign session values Response.Redirect("~/url",false); to a a page which contains crystal report viewer.and report should show those session values.after keeping the application idle for 45 mins i click on the button which assign session values.then it's redirecting to the report page but the report is not shown.it shows a empty page and no errors shown(only happens application is idle for nearly 45 mins other wise works fine)
    i'm using iis 7
    in the web.config i have set sessionState timeout="60" and application pool idle time out to 60 mins.
    any idea why this happens

    Make sure you are on SP 8
    Make sure you are using .Close and .Dispose on your report objects as you get done with them.
    What OS? (2003, 2008, 2012)
    Provide more info on the following:
    The problem is that the Crystal Report Viewer does not load after a few hours.
    What does that mean? Errors? Warnings? Behavior? Symptoms?
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
    Follow us on Twitter

  • SSRS 2012 report integrated with SharePoint 2013 issue :Report refreshing after some idle time

    we have SSRS 2012 report integrated with SharePoint 2013  , when we click on any toggle item after some idle time of 60 secs and try again to expand
    another toggle item then  complete report is getting refreshed and  if we are in child report it is redirecting to parent report. . we didn’t set any refreshing property at report level. I hope there will be some idle time setting at sharepoint site
    level.
    what we observed.
    1. there is no problem when we expand toggle items without any idle time.
    2. when we open the report and expand few toggles and keep idle for 60 seconds and try
    again to expand another toggle item then  complete report is getting refreshed (all toggle items are collapsing).
    3. If you keep idle for 60 minutes and if you didn’t do any action like expanding toggle
    items it is not refreshing.
    why it is happening and how to stop that complete refresh.
    Surendra Thota

    Hi Surendra,
    I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
    I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
    Please reference to the setting below to don't limit the timeout values if you got the report reloading:
    Point to a report in the library.
    Click the down arrow, and select Manage processing options.
    In Processing Time-out, select Do not time out report processing or
    Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
    If you got the session timeout that refresh the page, please reference to the setting in below article:
    http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
    Details information in the article below about the timeout setting for your reference:
    Set Processing Options (Reporting Services in SharePoint Integrated Mode)
    If you still have any problem, please feel free to ask.
    Regards
    Vicky Liu
    If you have any feedback on our support, please click
    here.
    Vicky Liu
    TechNet Community Support

  • My ipod classic has decided to become corrupt, will not sync etc. Tried all of Apple's troubleshooting tips but nothing works. It is an 80GB classic which has been well looked after. what could of caused this and how can i rectify?

    help!

    These are also in the Troubleshooting tips, but it works for me.
    What system are you using Mac or Windows?
    a. If Windows. run Chkdsk drive: /F
    b. if Mac run Diskutilty -> CRC
         Click on the iPod device
         select FirstAid tab on the right window.
         click on the first Aid Button.
    Then connect to iTunes and Restore.
    Good luck.

  • (final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink?

    (final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink eventhough the files are there.

    (final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink eventhough the files are there.

Maybe you are looking for

  • Cellular reconnectivity issues with 3rd Gen iPad 3G/4G/LTE

      I've read a few other threads regarding a reconnection issue with the new (3rd Gen) iPad. I'm creating a discussion so people can put there thoughts here regarding the issues they are having with reconnection of cellular data connections.   I have

  • Report Admin - Print Preview Error

    In reports admin, I get the following error when I select print preview:error marshalling arguments; nested exception is; java.net.SocketException; Socket write failed.Any ideas?

  • DVD Drive not recognized by Computer

    Hi, I rebooted my computer the other day and realized my DVD drive is not listed in the devices shown under "my computer".  Under the device manager it has a yellow triangle with an exclamation point in it.  The driver is current and loaded.  I tried

  • Labview 8.0.1 installer error

    hello all, I am having an issue with building an installer package in labview 8.0.1.  I can build an executable every time, but when i try to build an installer I get the error message in the attatched txt file (its to lengthy to paste here) .  this

  • Best practices for accessing remote management

    So, I've been looking into consolidating and moving our servers and such to a colocation datacenter. A problem for me that arises from moving is, what do we do about our remote access?In a private office enviornment, I haven't ever opened up VMWare v