Tanya Weinmann


What follows is a eulogy I delivered for my friend Tanya at her funeral services which were on 8/13/2016.  She died after a brave, year and a half long fight with an aggressive form of cancer.

Tanya was not an outgoing person by nature, but she practiced very hard at it.  This along with her friendly and caring nature drew people to her and my eulogy was one of several delivered along with beautiful, moving songs sung by her talented friends.  She will be missed dearly.


First I have to confess that I’m jealous of those of you who have known Tanya for so much longer than myself. [For those who don’t know me my name is Steve and] I only first met Tanya back in 2007 when she came to work as one of my few coworkers in a small office. As I would later learn, Tanya had a very sensitive sense of smell and one of my first interactions with her was when she was going around her new workplace looking for what she thought was a backed up toilet. She stopped by my office and she said something like “can you smell that? It’s like a sewer pipe or toilet…” and I said “oh it’s not a toilet, that’s just my lunch”.

I thought at the time, and still think that the whole situation was funny. But Tanya herself was mortified, and even years later, when we knew each other much better, I had repeated the story and as amusing as I still found it, she still felt bad that she had insulted the stinky lunch that I was eating.

Polite and considerate to a fault, but very honest also. Part of the outfit that I had on when I last saw her I had obtained because she once thought so little of my work wardrobe, that I liked, that she had me go shopping with her at lunch so that she could help me pick out some new clothes.

This honesty usually caused her much consternation though. She hated conflict, and she would often rather spend time alone than risk a situation where her honesty might cause issues, or even where she felt that her very presence would be an inconvenience to others. But for those of us who knew her, she was never “inconvenient”, and we needed her just as she was: because her honesty didn’t come from any maliciousness or self-righteousness; no, it came from the same deeply polite, caring and considerate person.

I would have conversations with her where she would bring up issues that she might be having with her loved ones but in the same breath talk about how much she cared about them. She, certainly wasn’t in any way arrogant or even thought that her way was the best and in fact her modesty could be one of her most challenging character traits because even though like anyone else she might berate others at times, she very often took extra care in berating herself. This lead me at one point to exclaim to her that her self-flagellation was hurting me even more than she hurt herself, because the person she saw herself as bore so little relation to who she actually was, to the person that I loved. And who was she? A loving daughter, sister, aunt, and friend; yes. But what else?

Just like many others here, when I would go to see her in the hospital I was always genuinely happy to see her, to see that she was ready to be amused with me lightly aggravating her yet again. This was good because not only did I go there to check in on my friend but I also wanted to be able to have normal conversations, cheer her up and generally try to at least temporarily distract her from the very unfortunate situation that she found herself in. This got harder and harder over the later months and once, only once, I completely broke down in front of her. I felt awful, I had let her down. This one thing was the only thing that I could do to help her, and I couldn’t do it.
Seeing me, as she lay there in pain from the disease that eventually take her from us, all she said in the most calming and lovely voice was “Steve, don’t be sad”.

That is who she was to me and to others, her caring when in times of distress, a calming influence in times chaos, and…
There’s a line that I caught in a book that reads: “...we all lie to ourselves; we tell our own selves more lies than we ever do other people. “
Tanya was my much needed honesty that I relied upon to break the cycle of lies that I constantly tell myself because she cared enough that she would risk even our friendship rather than see me come to harm.

Just like everyone else she had her flaws; she could be obstinate, disconnected, and difficult to get along with at times, often seemingly to the point of pushing people away. But she was such a beautiful person because her flaws never originated from ill will.

I have to mention that even before she had gotten sick she would occasionally tell me that no one would remember her when she was gone, that some people might cry for a day and but they would then soon forget all about her. I of course would tell her that she was very wrong, that there are just too many people who care about her.

I never really knew if she actually believed what she said or if she just wanted reassurance from her fears. However, it warms my heart seeing all the wonderful people here today, friends and family; those who know what a wonderful person she was. People who know that a piece of their heart is gone, a piece that will never completely heal. As part of the honesty between us, Tanya and I would celebrate when the personal flaws that we thought that we had turned out not to exist. Thank you everyone for coming to celebrate with her one more time, in love.


Tanya Weinmann
February 15th, 1972 –
August 9th, 2016


I upgraded the Image Widget plugin for WordPress on one of my sites and, as I’d gotten into the habit of, I didn’t back everything up before updating, oops!  For some reason the upgrade bombed and I was greeted with the dreaded 500 error when trying to load the site.  From past experience I knew that the plugins needed to be disabled so that I could administer the site so I followed the directions on this site (under “Updated Method”).  The site would then load and I then reactivated all the plugins except that the Image Widget died with a fatal error of :

Warning: require_once(/var/www/website/wp-content/plugins/image-widget/freemius/includes/sdk/Freemius.php): failed to open stream: No such file or directory in /var/www/website/wp-content/plugins/image-widget/freemius/includes/class-fs-api.php on line 85

I tried in vane to try and track down the offending code but had no luck; and it doesn’t help that no one seems to own up to using this Freemius program.  What was quite aggravating is that there is no “freemius” directory anywhere, but this turned into part of the solution: why don’t I just recreate it and make everything null?  So I made the folder structure and required files:


And then filled the files thusly:

class Freemius_Api {
public $empty=’empty’;

class Freemius_Api{
function SetClockDiff(){}
function Api(){}
function Test(){}

After entering in the dummy files I was able to fire the plugin back up.  Hopefully the next time the plugin is upgraded it will flush this business out of the system.

DacEasy is Dead

It took longer than it should have to confirm this since Sage has cleverly replaced the now discontinued DacEasy links with Sage 50 links (aka Peachtree).  More here:


There seems to be lots of hate for Sage over this, but I guess there wasn’t much of a market for an inferior point-of-sale product that tied into an inferior accounting package (not that I’ve ever heard good things said about Sage 50 which seems to survive based on inertia).

AD RMS Upgrade along with the CA

I had a server running with the 32 version of Server 2008 that I needed to migrate over to the 64 bit version of Windows Server.  The server hosted both our Active Directory Rights Management Server (AD RMS) along with our Microsoft Certificate Server (CA).  I had tried porting it years ago but was unable to get the certificate services to start.  As part of the process I had already ported the RMS DB to SQL.  I decided to give it another try and have some tips in no particular order:

  • First I needed to get certificate services running.  I started by turning off the old server, installing a new Windows Server 2008 64 bit version with the same name.  I then installed certificate services role using the instructions here.  However when I tried to follow the instructions for migrating the database I was getting errors like ‘jet_errmissinglogfile’ or sector size mismatch.  The fix was to copy over a ‘clean’ version of the database from the old server (a copy taken while Certificate Services is stopped), deleting all the files but the database (edb) and starting the service.  (I had also previously imported the original ‘config’ registry entries per the earlier referenced instructions).
  • AD RMS proved a bit more tricky.  First I installed 64 bit version of SQL Express which matched the instance name of the old server.  HOWEVER, the better move would have been to uninstall AD RMS from the old server first.  In this case I had to use ASDI edit to remove the ‘SCP’ section from AD (under Configruation->Services->RightsManagementServices).  I was then able to install and restore my settings (DB and registry).  Be sure to check the functionality of documents secured with RMS and the admin console though.  Of special note is that after upgrading to Server 2012 I needed to run the ‘Update-ADRMS’ utility; it will NOT work right without doing this!

Migrating from SharePoint 2010 Foundation to SharePoint 2013 Foundation/Services/etc.

I followed the well illustrated instructions here, but several key points were missing.  Perhaps a lot of the grief was caused by the fact that I didn’t want the SharePoint application pool to be run by Local System/Network Service/Administrator.

  • First the security in 2013 uses ‘Claims Based’ security (the exact details of which I am not completely clear on, but anyway) while 2010 security is referred to as ‘Classic’.  On this page (step 6) they detail how to setup a site with classic security within 2013, though my impression is that there is no benefit to ‘upgrading’ when doing this (you would just make the new site that you want and attach your content database that was brought over using the steps from the first article and it could be left there I suppose).
  • In order to upgrade your restored content to the new security model I followed the proper steps in the same article that has the tip on how to make a ‘classic security’ site.  After that the plot thickens.  It will be necessary to modify the web.config files for the site, the admin site, and the security tokens “site”.  I used this article as a reference (step #3), but it is missing pieces as well.  Be sure to make backups of the originals as a mistake can render the entire installation inaccessible!  An important note is that although I basically copied the tags from the source website over to the admin and security tokens site, it’s important not to put any switches in the ‘<roleManager>’ in either of those.  Within that article are also steps on adding ‘SPN’s so that the application pool account can run authentications (otherwise watch out for KDC_ERR_S_PRINCIPAL_UNKNOWN/0xc0000035 errors); as well, this article points out the delegation steps required in setting up the SPNs.
  • I believe at this point the site was working enough that I was getting the “Sorry, this site hasn’t been shared with you.” error when accessing the site (though from somewhere it noted that you should be able to pull up the local settings under “domain.com/_layouts/15/settings.aspx”.  Just a few final things needed to be done.  First forms authentication had to be disabled within the central administrator and IIS.  As well I needed to follow the steps here in order to make sure that the application uses the …SPN, or something.  Lastly I was getting an error where my application pool account did not have ‘local activation’ rights over an app (the CLSID is for the IIS WAMREG admin Service).  In order to remedy this I had to follow the instructions here so that I could change the permissions for IIS WAMREG admin Service.
  • Extra credit: I used this page to mock up a forms authentication, but further study is needed.

Corrupt Exchange AutoComplete

So this has happened to me twice and I had forgotten how to fix (‘fix’) it from before so I’m writing it down here for when I inevitably forget again.

The symptom is that the user’s address autofill/AutoComplete within Outlook stops working. Since we run on a later version of Exchange this means that the autofill information that is stored on the server is corrupt (this post applies specifically to Outlook 2010/Exchange 2013). As far as I can tell the settings on the server are gone so the information has to be reconstructed, which for the user, is better than nothing. To do so I follow these easy steps:

  1. Download NK2Edit
  2. If you want a backup of the corrupt information, you can follow the steps here or backup the ‘DAT’ files (outlined in this post, though there seems to be a consensus that this won’t do the trick on Exchange where these files are always ‘pushed’ and never ‘pulled’)*.
  3. Clear out the existing AutoComplete (Step 4 here under “let me do this myself”)
  4. Open NK2Edit and make a new NK2 file with the same name as the Outlook profile (typically ‘Outlook’).
  5. Click the add button within NK2Edit and add every address that you can get your sticky fingers on, especially the addresses under ‘suggested contacts’.
  6. Exit Outlook and put the NK2 file in the proper path and go to Start->Run->outlook.exe /importnk2

Other suggestions:

  1. This article suggests the command ‘/CleanAutoCompleteCache’, but this would only seem to apply if there was a problem with the single Outlook install.
  2. One could always (*ugh*) restore the mailbox from an earlier time, etc., etc. I would reserve that course of action only for drastically desperate situations.

*I came by this tip (http://www.msoutlook.info/question/backup-and-restore-autocomplete) which says that you may be able to restore autocomplete entries with the cache file by using the MFCMAPI tool.  The caveat is added since the procedure basically involves hacking the mailbox so some risk is involved.