Ken's Blog | Sharepoint 2010 Install Hell (aka, Don't use Windows Compressed Filesystem with Sharepoint 2010 or SQL Server Express)

Sunday, 1. August 2010

Sharepoint 2010 Install Hell (aka, Don't use Windows Compressed Filesystem with Sharepoint 2010 or SQL Server Express)08/01/2010 06:17 PM

Ran into this trying to minimize the size of a VM running on my laptop (set up a 25GB drive for Win2008 and Sharepoint 2010). Sharepoint will give you a cryptic error message in the log files and you have to look at the SQL Server Express install logs to see this (MS SQL Server refuses to install on a compressed file system, so you have to make the data directory uncompressed). Also, install all the prerequisites manually (Win2008 SP2, then run the Sharepoint prerequisites installer). If you're that close on disk space, you'll just get random failures and each install attempt involves sucking down 400MB off the network :-P

Then after all this, Sharepoint's configuration wizard ran the SQL DB install and ran out of memory (SQL Server cryptic error about "insufficient 'internal' memory" because I only allocated 768MB to the VM; it seems happy w/ 1.5GB). And finally after that, the Sharepoint configuration wizard bombed out w/ a cryptic "SPUpdatedConcurrencyException: update conflict in OWS timer" error which luckily is covered in someone's blog entry which apparently happens a lot for different reasons (not just during configuration or user updates in that blog entry); and the workaround is to go clean out some xml files by hand in a hidden directory ("\ProgramData") on the windows drive.

Next I run another app that causes Sharepoint to repair itself, which fails because with a suggestion to a link that there are multiple versions of SQL Native Client installed which I fix by uninstalling (apparently, you can't have the SQL2005 and SQL2008 native clients installed), but it fails again with the same suggestion later but the log file claims the Sync Framework test failed. So I uninstall all 4 Sync features, then do the repair again until it finally passes.

And then Sharepoint takes over port 80, so you can't run your own web sites on the machine (it kills off your Default Site without warning you). All your previous URLs are greeted with a "404 NOT FOUND" error which you have to waste time debugging.

So I'd suggest a minimum: 40GB of disk for Sharepoint 2010 and 1.5GB of memory in a VM...though you're probably safer w/ 50GB and 2GB as mentioned in Nik Patel's blog. With 1.5GB of memory allocated to the VM, I still saw the paging file go up to 2.9GB which I can't do much about because I only have 4GB on my laptop :-O

Sharepoint definitely feels like Microsoft's version of IBM's Large Wallowing Pig (aka Lotus Workplace)-: that was held together by bubble gum and wire and sucked craploads of memory and was a PITA to fix problems with :-P

Comments :

No comments.

Su	Mo	Tu	We	Th	Fr	Sa

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31