Always Remember: With Gusto Comes Data Loss.

How To Improve Your iPhone Battery Life (iOS7)

I was recently sent an article about how to improve your iPhone battery life and asked my opinion of it. I tried reading through it, but the author lost me in the first two sentences of his first recommendation. It was pretty clear that he didn’t quite understand how the technology worked – a sort of knowing just enough to be dangerous situation. I figured I would throw together my own little guide for those interested.
Continue reading

To Fix App Store Updates For Apps You Don’t Have Installed

A friend recently reported a problem where he was getting update notifications from the Mac App Store (MAS) for programs he did not have installed, under an AppleID that was not his. Since these programs were not installed, he had no way to remove them, and since it was not his AppleID, he had no way to update them. As such, it seemed he was going to be stuck getting these update notifications forever. Luckily, with a little know-how and a lot of persistence, we were able to track down the cause of this and resolve it.
Continue reading

Manually Rebuilding Microsoft Outlook for Mac (2011)

From my experience, it is not uncommon for Microsoft Outlook 2011 to develop problems that are essentially unrecoverable using the standard tools (such as the Microsoft Database Utility). When rebuilding, restoring and upgrading fails, you can still recover your data and return to a working state with relative ease. If you restore your Identity from Time Machine or another backup and it fails to rebuild, or you upgraded to Service Pack 2 (SP2) 14.2.1 and you have missing data you can restore your data from your old Identity. Outlook stores your data in the Data Records folder in your Identity folder:

~/Documents/Microsoft User Data/Office 2011 Identities/Main Identity/Data Records
  1. Upgrade to Service Pack 2 (SP2) 14.2.1 or later.
  2. Create a new blank SP2 Identity using the Microsoft Database Utility.
  3. Quit Outlook.
    1. Some users have found that deleting the database file in the new Identity helped.
  4. COPY these Data Records folders from the old Identity to the new blank Identity replacing the new folders. Do NOT replace the root Data Records folder. Only the sub-folders listed here:
    • Contacts
    • Events
    • Folders (one user reported replace Categories (not folders) worked better)
    • Mail Accounts
    • Message Attachments
    • Message Sources
    • Messages
    • Note
    • Signatures
    • Signature Attachments
  5. Rebuild the new Identity in Database Utility.
  6. Open Outlook and your data should be back.

Note: ALWAYS WORK OFF A COPY.

Bonjour Devices Not Seen on Ruckus Wi-Fi

This is a known issue that affects ZoneFlex 7363’s. This does not present under all conditions, and Ruckus is still working on figuring out exactly what the cause is. In the meantime there is a work around that fixes this issue. To implement this workaround follow these instructions:

1. Connect to the Ruckus unit via SSH

2. Run the command:

set qos <ifname> directed multicast disable

Where you see <ifname> replace this with the interface name. You can figure this out by running:

get ssid wlan0

then

get ssid wlan1

…and so on until you locate the SSID of the network you are trying to get bonjour working on. By default, the first 2.4GHz SSID has the ifname wlan0 and the first 5GHz SSID has the ifname wlan8.

3. Exit SSH

4. Reboot the Ruckus

Resolving Common Problems in CrashPlan PROe

This post is going to cover resolutions for some common CrashPlan problems you may encounter. I am assuming you have at least a basic level of familiarity with the Command Line interface. If this is not the case, I’d suggest asking for help from someone who does. Unless otherwise stated, these fixes should work for any version of CrashPlan (CP+, CPP, CPPe). I have written these in the order in which you should attempt them, unless you have evidence directing you past a certain step.

CrashPlan Client Constantly Crashing

Common Cause: CrashPlan backup engine is running out of memory.
Resolution: Edit the CrashPlan engine’s com.crashplan.engine.plist (“the plist file”) file to allow it to use more java memory. You will need to use Terminal for this, and edit the file using the ‘sudo’ command.
1.  Stop the backup engine by typing this into the Terminal application:
sudo launchctl unload /Library/LaunchDaemons/com.crashplan.engine.plist

2.  Run this command to edit the backup engine:

sudo nano /Library/LaunchDaemons/com.crashplan.engine.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

-Xmx512m

4.  Edit that line to something larger such as 640, 768, 896, or 1024. E.g.:

-Xmx1024m

This sets the maximum amount of memory that CrashPlan can use. CrashPlan will not use that much until it needs it. I would recommend starting out setting it to 768, and go higher only if you continue experiencing problems. You can increase it above 1024 if you have a really large file-selection.

5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

7.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.engine.plist

 

CrashPlan PROe Server Not Running

Common Cause: This can happen for any number of reasons.

Resolution: Manually stop and restart the LaunchDaemon.

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.proserver.engine.plist

2.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist

The server should start running and be accessible within 30 seconds. If this does not resolve the issue, continue down this page for further steps to try.

 

CrashPlan PROe Server Not Starting

Common Cause: CrashPlan PROe Server engine is running out of memory.

Resolution: Edit the CrashPlan engine’s com.crashplan.proserver.plist (“the plist file”) file to allow it to use more java memory. You will need to use Terminal for this, and edit the file using the ‘sudo’ command.

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.proserver.engine.plist

2.  Run this command to edit the backup engine:

sudo nano /Library/LaunchDaemons/com.crashplan.proserver.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

-Xss128k

4.  Edit that line to:

-Xss256k

This sets the maximum amount of memory that CrashPlan PROe Server can use. CrashPlan will not use that much until it needs it. Do not excede 256 1024 as, at the time of this writing, CrashPlan has not verified that the program is stable beyond that.

5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

7.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist

 

CrashPlan PROe Server Not Starting

Common Cause: CrashPlan PROe Server engine is having trouble reading Java. This is most common directly after an update to the server.

Resolution: Edit the CrashPlan engine’s com.crashplan.proserver.plist (“the plist file”) file to allow it to use a specific Java engine. You will need to use Terminal for this, and edit the file using the ‘sudo’ command.

1.  Stop the backup engine by typing this into the Terminal application:

sudo launchctl unload /Library/LaunchDaemons/com.proserver.engine.plist

2.  Run this command to edit the backup engine:

sudo nano /Library/LaunchDaemons/com.crashplan.proserver.plist

3.  In /Library/LaunchDaemons/com.crashplan.engine.plist, find this line:

<string>/usr/bin/java</string>

4.  Edit that line to:

<string>/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Commands/java</string>
This specifies the exact Java Virtual Machine that CrashPlan should use, rather than using the more common default setting.

5.  Hold the Control key and tap the x key to exit. Choose “y” to confirm it.

6.  You’ll see the prompt “File Name to Write.” Hit enter to save to the existing location.

7.  Start the backup engine by typing:

sudo launchctl load /Library/LaunchDaemons/com.crashplan.proserver.plist
If this does not resolve the issue, be sure to change the line back to its original settings from Step 3.