Today I started with the installation of WSS 3.0 on a windows 2003 server using MS SQL 2000. Normally this proces takes up a few hours max.
The only difference is that this time I'm installing it in a company that has very strict regulations. It is not possible to reboot a server without permission, etc. I started with lots of courage because I never had big problems in the past. The only problem I ever had with installing WSS would come to haunt me again!
First I had to install IIS, framework 2.0 and 3.0. Still no problem here. I dindn't had to reboot the server! Then I started the installation of WSS.
GRRRaaaghhh, there it was. The collission of the database was not correct! So I created a database, with the correct collision (Latin1_General_CI_AS_KS_WS). But still it will not install. The default collission of the server needs to be changed because the install proces wants to create a database and therefore it needs the default collission. The last time a had this problemn, I could reinstall the server with the correct collission and all problems were solved. But in this case it is not an option.
So I started looking for other options. There is a tool called rebuildm.exe that rebuilds the master database to the new collision, resetting the default collission of the server. But this tool wasn't present. Because in the installation of the server, this tool was not included. Now I have to wait for the administrator to approve the change, which I'm guessing he won't allow. I'll have to prove that rebuilding the master DB does not affect the collission and data of the user databases. This is the challenge I'm up to now. I will write the solution in this post later.
If people have a better solution then rebuilding the master DB or reinstalling the SQL server, please inform us!