As of today, I have officially added SharePoint as only the second of two Microsoft technologies I want nothing to do with (the other being System Center Configuration Manager), both chiefly on the ground of being far too complicated for their own good.
I have long held the belief that only a sadist would run an on-premises SharePoint server, due to my previous experience with it usually resulting in far more work troubleshooting problems than the actual server was worth to me. I’ve never even run anything more complicated than a single standalone server, and I’ve had to look up more SharePoint error messages than possibly every other Microsoft product I’ve worked with combined.
Yesterday, my last remaining SharePoint Foundation server self-destructed to the point where all I could coax from it was “Service unavailable”. Inspection of the error logs revealed that right after the SP1 upgrade last week, it had started spewing error messages to the Event log that, when searched for on Google, revealed only 5 pages on the entire web, none of which cast any light on the issue whatsoever. The actual site itself had been working normally for 5 days after; why it chose last night to finally expire remains as much a mystery as the error itself.
Luckily this wasn’t a production server; it was a server I kept around to test little things out on like InfoPath submissions. I’d barely touched it from the default config, and it had managed to destroy itself so utterly that I couldn’t even uninstall it without restoring from a backup 6 days ago. None of this fills me with the confidence I would want when running a system to store anything even remotely important.
I eventually migrated what little data I had in there to different systems, and removed it from the server.
Goodbye SharePoint; I won’t miss you.
P.S. Thanks for that 3GB of server RAM back that I can now use for something stable.