Geeks With Blogs

About Me:
I am a Female SharePoint Developer (a platinum unicorn). I have been working with SharePoint since I attended the Portal University in 2005. I hold a BA in Computer Science from the University of Missouri - Kansas City. I love playing Rockband, organizing user group meetings, working with code, attending events as a speaker or organizer, and having bizarre conversations about geek things with cool people. If you have any comments or questions fill out the contact form and I will try my best to help.

The Guide of a MOSSLover Becky Isserman's Blog

I did something stupid against all my beliefs and should have never done it.  I tried to deploy something on Friday.  It was the dumbest mistake.  First off I had no idea what type of master pages were in the environment.  I assumed there was only one master page in the entire environment and I used the most disgustingly wrong program for a developer, SharePoint Designer.  I pasted in this fix for AJAX Update Panels with FireFox (<script type='text/javascript'>_spOriginalFormAction = document.forms[0].action; _spSuppressFormOnSubmitWrapper=true;</script>).  The environment immediately crashed.  For some weird reason the Safe Control no longer existed in the web .config files for the System.Web.Extensions assembly as some guys found out today.  Overall a lot of weird things happened and the master page was never approved.  I tried hard last week to roll it back.  Needless to say that part was fixed and then they found a couple other weird issues that ended up getting fixed by the end of the day.  I spoke with a few people they finally told me why everything failed.  There were two WFE’s and 4 master pages.  I had no idea that was the case.  I never thought to ask.  I had just looked in the site settings at the master page for the main site.  It never really dawned on me there were multiple master pages.  I felt like a complete imbecile when I found out this was the case.  Honestly looking back on it there were just a ton of different follies between me and my co-workers.  It just dawned on me how important it was that a change control system were in place…

I mean think about it you have a form that someone else checks over and approves.  Someone who knows better and comments on what you might need to know before submitting these changes.  At my old job I knew exactly what was going on at all times (well most of the time, aside for patches and the infrastructure guys).  I was in control, but as a consultant I am not the SharePoint Guru (or whatever they called me).  I am going into someone else’s environment and changing something.  I need to know the what and the where before I start digging into the how part.  I don’t know maybe when there are situations without a Change Control System in place I need to write down and outline what I need to know before poking into someone else’s environment.  I know better or at least I knew better.  You never go into a prod environment first off when it’s not off hours, without testing your fix, and without knowing what you are doing.  Finally I went in today and fixed up both WFE’s and all the master pages with the proper fix.  If I had asked the proper questions I could have avoided some issues (not all the issues, there was obviously something else cracked).  Anyway, don’t be like me and just jump right in when you know it would be a mistake.  I knew it felt wrong and yet I still did it.  I hope that someone reads this post and thinks before they act on a production environment.  Catch you all later.

Technorati Tags: ,,
Posted on Tuesday, March 10, 2009 2:02 AM MOSS , .Net | Back to top

Comments on this post: Why Change Control Systems are Good...

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © MOSSLover | Powered by: