MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Stay away?

  Asked By: Caitlin    Date: Mar 29    Category: MOSS    Views: 1018

I've been following the various threads discussing the SP1 fiascoes and I
am now wondering if I should be keeping my MOSS Farm as far as possible from
this update. Is everyone having the same types of problems?

Here is my MOSS Farm's topology:

1 WFE (sits on MS Virtual Server)
1 Index Server (sits on MS Virtual Server)
1 SQL 2005 (sits on hardware cluster)

I'm not prepared to go through the SP1 just yet but I'm sure there will be a
need at some point to do so. I don't want to break our very relied-upon MOSS
Farm in this process.

Has anyone out there come up with a recipe for installation that doesn't turn
out in disaster?



4 Answers Found

Answer #1    Answered By: Candy Walter     Answered On: Mar 29

I'm getting a copy of my single WFE ready. I'll backup the databases
first of course, when I do the upgrade I'm going to do it on the replica
server. If it breaks, hopefully I can just restore the databases and
bring the original server  back online.

Doesn't that sound like it should work?

Answer #2    Answered By: Leanne Rios     Answered On: Mar 29

I thought I would add some support for MS here or perhaps I was just lucky. I
have the same setup as below. That is 1 WFE, 1 Index and 1 SQL running MOSS I
have this twice over. That is I have it all built in a virtual  environment and
also on real servers. On the real servers the SQL is actually a cluster of 2 but
I don't suppose that makes much difference. Anyway, I installed SP1 in the
virtual environment and it failed straight away but that was my fault as I
hadn't logged in with an account with the correct rights:-( Having logged in
again with the correct account everything worked fine. Feeling brave I then
repeated the exercise on the real servers and it also worked fine. I'm afraid I
don't have a recipe though I tried to follow the instructions but found the
early parts didn't work - for example I never found the patches that were
supposed to be applied before starting. I also never got the windows update  to
work or perhaps I was just too impatient so I did the update manually. The other
thing is that I don't know much about SharePoint so I haven't done anything very
clever or adventurous with MOSS.

Answer #3    Answered By: Zachary Roberts     Answered On: Mar 29

I think clever and adventurous is what gets ya into trouble.

Aside from my mistake, which I believe was running the Configuration
utility right after WSS3, I think adventurous farms  are in danger for

I'm pretty sure remnants of features etc that were maybe "orphaned"
caused the other errors that didn't allow me to recover from my first.
I've always had the trouble that when I install a feature over itself
and then try to remove it I get errors that this component or that
doesn't exist. I usually have a workaround and the features lay dormant
somewhere in the database so they don't adversely affect user experience
at all.

During my second attempt to apply SP1, all of these errors came out of
the woodwork telling me that this application or that feature etc
weren't available. My upgrade failed. I have so many Add-Ons to
sharepoint that even though I have good DB backups I don't really have a
way to rebuild a binary install WFE replica to try the process again.

Lesson learned: I intend to document and deploy a complete rebuild.
Absolutely any change to the Web Front Ends will have to go through some
sort of change management so this is easier to recover from next time.

I've probably been way outspoken about this and don't mind at all being
put in my place if it was my own ignorance that gave me a poor
experience, or if I'm misleading anyone at all.

Answer #4    Answered By: Maura Durham     Answered On: Mar 29

I wasn't trying to "put you in your place" or anything. I've just been
lucky because I don't know much about SharePoint so haven't done very
much. There have been many Microsoft upgrades which I've tried on other
things that have gone horribly wrong. Judging by the many comments here
and in other places anyone with a "real" SharePoint site - that is one
with add-ons and lots of content of a varied kind could face problems
with SP1.

Didn't find what you were looking for? Find more on Stay away? Or get search suggestion and latest updates.