SharePOINT!!!!!!

Oh, how I hate you, Sharepoint. So, so much.

I’ve had nothing but problems with Sharepoint since the 2003 version. And I can’t say that it’s all Sharepoint’s fault. I probably just don’t know what I’m doing wrong, and it seems like we’ve had the three stooges of the Sharepoint contracting community in here to do things.

Our Sharepoint 2003 implementation was actually pretty stable, but for some dumb reason it used our domain account for the SQL Server Agent in some critical areas. It managed to plug along without any real problems, but we never really used it for more than a document repository.

Then along comes MOSS. We decided to upgrade in conjunction with our switch to Microsoft CRM 3 last summer. BIG MISTAKE. Not because of MOSS per-se, but because we couldn’t find anyone competent here locally to help us. One guy essentially disappeared in the middle of the project, and the next one decided to do a reinstall using his own domain account instead of any of the service accounts created for him. In addition, they both managed to completely under-spec the installation, leaving us with a solution that was hobbled due to a bad service account reference AND could hardly crawl its own content.

I found another Sharepoint resource and recommended it to our company as someone who could help reimplement our MOSS farm “for realz,” but the cost ended up being too high for our budget. It was too bad, because I’m certain those folks would have kicked butts and taken names. Luckily we did get some very good training in the process of trying to “smarten ourselves up” about Sharepoint, and we found a local person (a former employee) who was able to do what we needed.

So we have rebuilt our MOSS farm into a 3-server structure – one for front end, one front end for crawling and indexing and a back-end for the database. We have around 120gb of content in MOSS so far and it’ll just keep growing. Hopefully this reimplementation will work out, but as of right now I’m trying to determine if our interfacing systems – including the aforementioned CRM – can cope with the new MOSS structure. Right now CRM seems to be barfing in our custom callout that seemed to work in Staging, so I’m not certain what the problem is. Hopefully the developer will be able to get that fixed so that QA can finish and we can all go to bed…but that may be wishful thinking.

The problem is that I think MOSS is a really cool technology, and if leveraged properly it could really improve our ability to collaborate and interact. I just hope that our most recent iteration will work out – maybe the third time will be the charm.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: