9/9/2004 4:21:09 PM: Meta-Applications

Microsoft is so big that it develops software applications for its other software applications. It’s a self-join of monumental proportions. It’s quite a jump from some kid hacking together a small VB6 app’ or a tiny toy Access form.

Windows SharePoint Services, SharePoint Portal Server, Office Project Server and SQL Server

All of these mugs are now installed on one Windows 2003 server. After installing SP1 for WSS and SPS, I was able to run WSSWIZ.EXE that dumped some templates on SPS (including some Project Server web parts). This executable was a step defined in MS KB Article 840701 (“How to install SharePoint Portal Server 2003, Windows SharePoint Services, and Project Server 2003 on the same server”).

Now I thought I was being conservative when I installed SPS on top of MSDE but Office Project seems to require SQL Server (preferably with analysis services). Also, Project Server still uses ASP files so SPS has to be configured to allow this file type. And Window Server 2003 has to be configured as well. Both configurations reduce the level of security.

Those Phong-shaded cartoon drawings of happy perfect applications holding hands with other happy applications are quite annoying when the gritty complicated reality is faced. To make life easier I should have set up at least two virtual machines because Microsoft does not recommend running Office Project and SharePoint Portal servers on the same machine. But I can’t imagine having less problems running multiple, virtual, Windows 2003 servers on one machine.

Interoperability and backwards compatibility is starting to become a seriously heavy burden.