Troubleshooting some of the issues associated with Shared Service Provider (SSP) in SharePoint

Problem:
Shared Services Provider could be a very complex subject. Troubleshooting some of the errors associated with SSP can take 1 or hours to resolve. One of this is when you click on Search settings, Usage reports, Search Usage Reports links in SSP you get this error: Unknown Error to Troubleshoot issues with windows SharePoint Services. See below





Cause:
SSP can be broken by number of things including failure to load some dlls, incremental crawl etc. This problem will normally affect your /ssp/admin/_layouts/searchsspsettings.aspx, /ssp/admin/_layouts/SpUsageConfig.aspx (Usage reports), /ssp/admin/_layouts/SpUsageSspSearchQueries.aspx (Search Usage Reports), etc
Resolution:
Still frustrated. The message above do not mean anything. To view detailed error message go to the SSP web application web Config like so.
1. Open on your IIS (start run inetmgr)
2. Look for your web application, right click -> click properties - >click home directory
3. Copy your directory, paste on run command to open it.
Find Web.config (Alternatively, you can find your web applications on c:\Inetpub\wwwroot\wss\VirtualDirectories, look for the port hosting your SSP. find you web cofig.)
4. Search for callStack
5. Change the line callStack=”false” to CallStack=”True”
6. Now search for customErrors (), change the customErrors tag to (customErrors mode="Off")
7. At this point when you browse to the SSP search settings, you will find detailed errors, see the figure below.




Well now that makes sense to me. What this says is that you have dlls missing. The question is which one? The next steps show you how to find these dlls. You will use a tool called Fusion Log Viewer "FUSLOGVW.EXE." You may find this tool in one of the following locations:
C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\FUSLOGVW.EXE dated 9/23/2005 and C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\FUSLOGVW.EXE dated 11/7/2007
Please note for some obvious reasons you might not have this tool in the production environment. Copy the tool from your dev environment and paste in production. Follow the following post to complete the exercise : http://colinborrowman.spaces.live.com/Blog/cns!5BE1E6D14CDF840F!264.entry?sa=198329881