Monthly Archives: November 2013

Dish Network Hopper Rebate Promo Codes – Save $50

Rebate Codes For Dish Network Hopper

It is easy to save $50 on your bill – just give the redemption code below when you are signing up for Dish Network Hopper!  Please let me know if you use these so I can take them offline!

Hop110905187
Hop091632354

If you would like to save $50 when switching to Dish Network – use one of the following Dish Network promo codes.

Dish Network Promo Codes

HOP01122312212/06/1212/31/14
HOP00898373812/06/1212/31/14
DRD75345818512/02/1212/31/14
DRD74951197212/02/1212/31/14
HOP15621875811/14/1302/10/14
HOP15279846611/14/1302/10/14
HOP15203045111/14/1302/10/14
HOP13273957311/06/1302/03/14
AHP00142261711/04/1301/20/14
HOP12643857709/26/1312/23/13
HOP11090518709/17/1312/11/13
HOP09575468309/16/1312/11/13
HOP09163235409/16/1312/11/13
HOP08202678709/10/1312/09/13
HOP05596174508/27/1311/25/13
HOP05267280808/06/1310/31/13
HOP04389127206/28/1309/25/13
ADG17355495806/19/1309/14/13
HOP02839933705/13/1312/31/14
HOP02312630704/12/1312/31/14
HOP01572341304/12/1312/31/14
HOP01548278704/12/1312/31/14
DRD66822481003/16/1312/31/14
DRH87579988502/06/1312/31/14

Mac OS X Server Mavericks Profile Manager: “A Server Error Has Occurred” after uploading dock.plist

The Problem

I am using Mac OS X Server on Mac OS X Mavericks to manage the Apple devices at our school. Specifically – I set up the dock icons exactly how I wanted them arranged. I then uploaded the com.apple.dock.plist to profile manager. It detected all of the settings and everything was find until I clicked “Save.” Immediately after that – I was no longer able to load the device groups page and I got the dreaded “A Server Error Has Occurred” and to “Contact my system administrator if the problem persists”.

No matter what I did – I could not get the page to load. I knew it had to be a corrupt profile as it happened immediately after I pressed save. Resetting profile manager to default was not an option as I had many other profiles loaded already and didn’t want to lost them.

The Solution

There is a postgressql database that stores all the profiles. I went in and manually deleted the profile for the device group that I had created and that fixed the issue. I believe these commands will only work on OS X Server on Mavericks as the database is in a different location then past versions.

1.) Open up Terminal.app

2.) Command to list all of the tables:

sudo psql -h "/Library/Server/ProfileManager/Config/var/PostgreSQL" -U _devicemgr -d devicemgr_v2m0 -c "\dt"

3.) Command to list all profiles so you can find the corrupt one:

sudo psql -h "/Library/Server/ProfileManager/Config/var/PostgreSQL" -U _devicemgr -d devicemgr_v2m0 -c "select * from profiles"

This is going to spit out all the tables – you will need to widen out your Terminal window so you can see everything correctly.

4.) Find the id of the profile that you believe to be the culprit and delete it with the following command:

sudo psql -h "/Library/Server/ProfileManager/Config/var/PostgreSQL" -U _devicemgr -d devicemgr_v2m0 -c "delete from profiles where id=15"

Cisco ASA 5520 Won’t Boot – Booting System, Please wait.

I recently had an extended power outage at work in which our battery backups ran out of power and took our network offline. After the power outage – the network started coming back online.

The Problem

While the entire network came online and I could access everything locally – I was no longer able to pass traffic to the outside world.

A trip to my network closet showed the status light on my Cisco ASA 5520 firewall was blinking a steady green. After hooking up the serial cable to the console port on the firewall and monitoring the boot up with Tera Term – I was greeted with a message, “Booting System, Please wait.” The startup never went any further than that message.

The Fix

I decided to take the top case off the fire wall to see what I could do to recover the config file. There are 16 screws across the top and on the side of the unit that are extremely easy to remove. Once inside – I saw two pieces of ram(same that is in a computer). On a whim – I pulled one of the ram chips out and powered on the firewall. Sure enough – the Cisco ASA 5520 was able to boot again.

Long story short – I had some ram from other computers that I was able to replace the bad memory and was back up and going! Took me the better part of a Saturday to get the school back online and saved the school about $6,000 at the same time!

This ended up being a very easy fix. The ram was as easy to replace as a computer! Plus, I had enough spare ram to actually give the unit an upgrade.