SharePoint, .Net, SQL, MS BI, Collaboration and Gadgets

Here are some resources regarding Moss which I get from my colleague, LJ. There are good resources for every sharepoint developer. Here you go:

MOSS Form Based Authentications
Part 1 - http://msdn2.microsoft.com/en-us/library/bb975136.aspx
Part 2 - http://msdn2.microsoft.com/en-us/library/bb975135.aspx
Part 3 - http://msdn2.microsoft.com/en-us/library/bb977430.aspx

MOSS Alternate Access Mappings
Part 1 - http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx
Part 2 - http://blogs.msdn.com/sharepoint/archive/2007/03/19/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-2-of-3.aspx
Part 3 - http://blogs.msdn.com/sharepoint/archive/2007/04/18/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-3-of-3.aspx

**Thanks ot LJ who willing to share out the resources!

Simple error when trying to setup single sign on in Sharepoint 2007. Error: 

Please make sure you login as MS Single sign-on service account to configure it. Do check out here for more. http://cs.grossmann.com/blogs/fg/archive/2007/09/02/setting-up-single-sign-on-in-sharepoint-2007-errors.aspx

One of my colleague found out one funny bug in moss 2007. Here are the steps to reproduce it:

1. Add the content query web part, set to query items from page libraries from the whole site collection. (this should be default).
2. Add filter on “Scheduling End Date” and set to a specific date
3. Apply the setting and close the web part properties pane
4. Open back the properties pane, settings for the date are gone, and went back to [Today]. 

This seems like a bug in MOSS 2007.  The bug still exist after install SP1. Do let me know if anybody out there having the same problem and solutions.

p/s: My colleague already contacted a MS guy in my region. I will update this blog once got any feedback from them.

This is a common mistake when try to start a MOSS search services:

An unhandled exception occurred in the user interface.Exception Information: OSearch (Administrator)

This error occur when you do not specific the machinename in your username. you must put in fulll name. e.g. mossadministrator.

If you ever get this error during moss or wss 3.0 installation, you can follow the step below to fix it.

Setup is unable to proceed due to the following error(s):
This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of Internet Information Services (IIS) Web Server Extensions. If it is not available in the list, reinstall ASP.Net v2.0.
Correct the issue(s) listed above and re-run setup.

Steps

1.  Run aspnet_regiis -i at .NET 2.0 folder.

2. If the error still exist, you need to manual “Allow” the asp.net 2.0 in IIS Web Server Extensions.