I recently had a very pleasant experience with Dot Net Nuke and decided to
look into SPS. I don't even know if they are the same thing, but I have been
told they were. Note to marketting: after reading everything I could find on
the Microsoft web site about SPS the only thing I know about it is that it
is the greatest product ever concieved - no idea what business problem it
solves or how it does it.
So I decided to install my MSDN copy and see if it was like duke.
I am installing on an up to date (windows update wise) Windows 2003 server
domain controler, with SQL server 2000 running on it. I looked at the readme
and made sure front page extensions was not installed. I then proceeded to
install.
CLR error during the install, but instalation continued. After instalation
completed I was redirected to a web page that was not found. On
investigation I discovered the portal web site was not started. It turned to
be because an invalid application pool was specified. Changed to 'default'
and started the web site, but all I get is 'access denied' errors on any
pages and I am using the domain admin account.
Now the fun begins, I've tried uninstalling it - error can't uninstall.
Repair - error can't repair (same CLR error as during instalation) and so I
have a hosed up production domain controler server. Is my only choice now
to reformat my production server to get it back to normal? Is there
something in a readme that I missed that would cause the instlation of SPS
to put my server in this condition?
Now I know why others pay for SPS hosting rather than deal with it
themselves. The fact that the product itself is buggy is understandable,
the fact that it leaves iteself in an unrepairable state is unacceptable.