Food at the Ballgame

I recently attended an event at Progressive Field as a guest of Sirius Computer Solutions to watch a Cleveland Indians game. I’m thankful to Sirius for inviting me along, even if some of the speakers that they brought in left something to be desired, however there was something else at the game that was beyond their control that I didn’t care for: the food.

The food looks great, but after one bite I was reminded of a game I attended late last year at Progressive Field where I ate a good deal, but after the fact realized that in my speed of eating I had missed the fact that I didn’t really care for what I had eaten. Part of where this stems from is my part time hobby of cooking. That’s not much of a hobby in my mind, but I’ve met enough people who don’t cook much or at all to know that my limited cooking knowledge can bring to light things that I would probably gloss over if I lacked the little bit of knowledge that I have. I’ll start with the rubens that they served at the game since it’s a great example of what they do wrong there:

Progressive Field Rubens

It might not look it, but the presentation on this was actually very nice. The corned beef was ‘real’ meat and not ‘flaked and formed’, the bread was a nice marbled rye and the portions were quite (and some would say ‘too’) generous. However, the whole experiment suffered from flaws that makes one think that food served at Progressive Field begins with good ingredients and ends with looking good and not much in between. The grilled bread tastes like it was fried in mildly used fryer oil, the beef had been seared, concentrating the taste and saltiness of what is already a strong, salted meat, and a layer of soulless sauerkraut made the sandwich too salty to consume and ill tasting at that.

It’s as if no one bothered to taste the stuff .  Needless to say other items pulled the same stunt:

  • Brownies that someone obviously put a lot of time into crafting, but lacking in sufficient cocoa to taste chocolatey enough to cover up the oil (not butter) base.
  • Pretty sandwiches with too much thick, bland bread that washes out that taste of the pleasant and mild meats and cheeses that they contain.
  • I recall a cheese platter from last year that had a big spread of European ‘style’ cheeses, with exactly one cheese that was worth anything.

And those were the star performers, other less desirable entrees were the ridiculously oversized hotdogs made from nothing but salt and grease and pizza from Pizza Pan (seriously, is the worst pizza joint in town the best you can do?).  In fairness though what makes me truly sore is that by and large it appears that they use great ingrediants, but the execution of assembling them is so awful.

I seem to remember someone telling me that the kitchen used for the luxury boxes is the same one used for the elegant Terrace Club, but I’d more likely guess that ‘box’ food comes from the depths of the lower levels, or maybe the Terrace Club staff is too busy making the great, elegant dishes for their main restaurant to bother with the stuff for the luxury boxes.

Either way, vendors don’t have to bother to invite me back there as the food is….disgusting; and I’m not a picky eater.

(If anyone is doing a Browns game though….oh my goodness that’s good stuff!)

Exchange 2003 to 2010

While uninstalling Exchange 2003 I was getting the error “you cannot remove a server that is a target bridgehead for a routing group connector. This server is a target bridgehead for the following connections”.I deleted the connector on the Exchange 2003 server, but I still received the uninstall error. This post clued me in that I should be looking for something on the new Exchange 2010 server, and after performing a Remove-RoutingGroupConnectorin the Exchange console I was able to uninstall (though just be sure to have that Exchange 2003 ISO laying about).

Update:After only having the stat tracker running for two days on my site, this post has turned up as being disproportionately popular so I figured I’d post another note on my uninstall experience with this Exchange 2003 server: I ended up having to manually uninstall it in this case and then had to remove entries from active directory using ADSI edit that were subsequently causing errors on the new Exchange server.  I know the post I relied on over on Microsoft’s forum had follow-ups that said to absolutely not do that, but it was the only thing that worked.  Use at your own risk, of course.

I believe, if I remember correclty, that  the issue that led to this result was the fact that I just couldn’t remove the stores from the 2003 server.

When Upgrading Equals Lost Features

I remember an old version of Exchange had the ILS service and upon ‘upgrading’ I noticed that the feature had been eliminated, and nothing much added to the package, apart from management headaches (“You want to flush the queues? Sorry!”). For SMBs, the highpoint of Microsoft Exchange was version 5.5, though the RPC over HTTP feature which was added in 2003 is a notable exception.  I never got a chance to really use ILS so I didn’t really miss it, but I thought the functionality was promising and it provided a nice feature beyond a generic IMAP/SMTP setup.

A little bit ago I upgraded our Exchange 2007 to 2010.  Although we got the upgrade ‘for free’ via SA, the main driver for the migration was so that I could allow an Apple Mac user to access file shares via OWA (Outlook Web Access/Application).  With such a nice feature it didn’t even occur to me that Microsoft would dump it, so when I read up and learned that A) OWA on Exchange 2007 only supports Premium OWA on Internet Explorer and B) Network file share access is only available under Premium OWA and C) Exchange 2010 supports all platforms/browsers under Premium OWA, ergo D) Upgrade Exchange to 2010 to allow my (important) Mac user to access file shares via Premium OWA.

But alas no; even though the Exchange 2010 console appears to support file share access, it has in fact been removed:

OWA removed features

I browsed the ‘”What’s new” for Exchange 2010, but unfortunately I don’t see anything in there that I can hang my hat on that makes it worthwhile to have spent a weekend upgrading it.  There’s the advantage that I’m now very early in the upgrade cycle so it will be some time before I have to upgrade again, but that’s just upgrading for the sake of upgrading (which is not without it’s appeal, but still…).

Exchange 2010 Upgrade Notes

I’ve upgraded our Exchange 2007 setup to Exchange 2010 and two irksome issues cropped up that sponged up a great deal of my time:

  • First, when I was moving users (aka ‘local move’) in a remote domain from the Exchange 2007 server to the Exchange 2010 server I was receiving the ‘insuff_access_rights’ error and I was unable to move the mailbox*.  Eventually I did have to do the ’include inheritable permissions’ checkbox on most of the users, but since that didn’t work right away I investigated quite a bit more before finding that the permissions for various ‘Exchange’ entries at the root of the remote domain within active directory users and computers were “goofed”.  Things went more smoothly after setting the matching entries to (about) the same permissions as the ones at the host domain.
  • I couldn’t uninstall Exchange 2007 since it was hosting unremovable folders on the public folder database (‘Internet Newsgroups’, etc.).  I tried to do things the right way, but wound up resorting to the ADSI edit tip here.

*By the way, I liked the ‘cached move’ method in Exchange 2010, but why can I clear out the flags for successful moves in the GUI, but I have to resort to a painful command line method if it fails? (Which, it failed for me a lot while working on it).

Does Anyone Else Use Microsoft RMS?

I think not, which leads to a dearth of searchable content when I encounter an issue.

My latest round of technical snafus that I’ve encountered with Microsoft’s digital rights management software for Windows 2003 revolve around the fact that I’d like to upgrade the server to Windows Server 2008.  I’d love even more to port it to the 64 bit Windows Server 2008 R2, but I gave up on ever getting that to work.

However I did get a virtual lab install of the server to upgrade to regular old 32 bit Server 2008, except that RMS on 2008 runs off of SQL (express) 2005.  Unfortunately my existing install of RMS was running on the old MSDE 2000.  After making sure that the SQL upgrade worked, I upgraded MSDE on the server to Express and everything seemed to run okay, except that occasionally the DRMS_Logging service wouldn’t start.  I’d start it back, and at some point in time it would stop (sometimes stopping right away after I tried to start it).  Finally, I couldn’t get it to start at all (to be fair to myself I figuring it was a timing issue with IIS since cycling IIS seemed to get the RMS service to start, though obviously this turned out to be a coincidence).

When I first looked at the server I noticed that I was getting ‘file full’ SQL errors, which I figured came about because SQL Express was hitting it’s space limit.  When I looked at the MOM/Onepoint database I noticed that it had grown quite large.  I looked up how to purge data and the posts all seemed to go back to the ‘sqlagent’ running a process that ran a stored procedure that handled the ‘grooming’.  After messing around with the SQL Express installer a bit looking for the agent install I’d found that although the SQL agent at least appeared to be included with MSDE 2000, it’s not with 2005.  I then went through the database and determined that the procedure ‘dbo.MOMXGrooming’ was the winner.  After executing that and shrinking the DB and files it cleared up the SQL space issue.  Yet still, the DRMS_Logging service wouldn’t start.

I looked at the logging database for RMS and it was rather large as well, but with no built in grooming procedure I just dropped the table and recreated it (backing up first of course).  The service still wouldn’t start, no errors, no nothing.  I figured that even though it wasn’t working it was worth looking at the web management piece to see if it would let me configure it.  When I tried to pull it up, the site kicked out an error saying that it could not run because the event viewer was full – the application event log had filled up with SQL space errors.  After purging the log, the service started and people could get into their documents yet again.