I thought I’d post a quick entry this morning to share a few things that I learned about MOSS 2007 in the last few days.
1) Don’t use spaces in your user names. While I can not say with absolute definitiveness that my issues with MOSS have been because of user names with spaces … I have a strong suspicion.
2) Log files for various operations can be found in the user’s temp folder (for the installation operations), under C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS (for most of the web stuff), and in the computers application and system logs. There are a few things to note, check the computer’s event logs first. The good stuff tends to show up there. You may need to follow up with the logs in the 12 hive but at least you get a starting point. You can use central administration to turn up the logs. They get big quickly, but can definitely help you home in on problems.
3) If you’re trying to create an SSP and you don’t see a web application that you expect to see in the list, delete it — including the IIS site. It’s possible that the IIS site wasn’t created correctly. (This was the case for me recently.)
4) If you need to delete an SSP because it didn’t provision correctly you need to create another SSP first. Delete on the context menu will only be enabled after there is another SSP for the web application to attach to. Even doing a delete from the command line will fail until your web application has another SSP.
5) If you miss entering the load balanced address for a web application the first time through, you have to go to operations and alternate URLs, from application management you can’t change the URLs for the web application.
6) There’s still an unexplainable affinity to using host headers rather than IP addresses for provisioning sites. Don’t even both trying to use IP addresses with B2TR. When it provisions sites it will add the host headers in on the IIS site — even if you’ve already created it yourself.
No comment yet, add your voice below!