“The WebResource.axd handler must be registered in the configuration to process this request”

The app’s used to work fine when I change the application pool to classic mode. But i wanted to make them work in integrated mode so I googled the error message a lot but i did not find any appropriate solution. I finally gave up and started using classic mode for the problematic application’s.

Few months before, i was browsing for some issue and found that coldfusion application and asp.net application cannot use same application pool on IIS7. But i did not investigate more on it. Few days back, i was browsing to see the issues with coldfusion and asp.net on IIS7  and found this Link which helped me to fix the “The WebResource.axd handler must be registered in the configuration to process this request” issue.

Cause: ASP.net handler mapping’s are conflicting with coldfusion handler mapping’s.

Solution: Once I removed the coldfusion mappings from ASP.net problematic website, the issue is gone and the website is working fine with integrated mode.

This is what I did to solve the issue

I ran the following command to get the deployment ID’s which are stuck

stsadm –o enumdeployments

Then i cancelled the deployment using the deployment GUID and the following command

stsadm –o canceldeployment  -id “GUID”

Then ran stsadm –o enumdeployments to make sure the deployment has been cancelled

When I checked the solution management, all the solutions status shows “deployed”.

Here is the work around

For the site collection which you intend to use all sites, create a subsite using search template(Enterprise tab). Goto site settings->search settings->create a custom scope

In the custom scope give the path of search site

For Example: http://servername:portnumber/sites/test1 is the site collection

http://servername:portnumber/sites/test1/searchcenter is the path of search center website

“/sites/test1/searchcenter” has to be given in custom scope text box

click ok

Once you go back to test1 site collection you can see “all sites”, “people’, and advanced search option.

For Example, if you have 20 site collections and all need these options then you will need to create 20 subsites(one subsite for each site collection with search template and create custom scope with search website path)

If all these site collections are grouped under one SSP and when you search with all sites scope you will get the results from all site collections.

msiexec /i “D:\xyz.msi”

If the installation fails even after running with administrator privileges then there might be a problem with the package

If you are looking for a WSP for ten themes check out Daniel Browns blog. Here is the link to download the WSP http://www.danielbrown.id.au/Lists/Posts/Post.aspx?ID=256

Once you install the package, goto Central Admin–>Operations–>Manage Farm Features and activate all the themes. Even after doing this some themes won’t show up. The workaround is to deactivate the ones which are not showing up and activate them again. You should get all themes.

MOSS Query: If serving queries, it will handle the search requests to look up indexed content.

Note : We should never use a network service \ local account to run the search service, it should always be a dedicated service account

2) If you want to have more than one index server in a farm, you must use a different Shared Services Provider (SSP) for each index server

3) You must install Office SharePoint Server 2007 on the same drive on all load-balanced front-end Web servers.

4) In farms with more than one index server, you should stop the Central Administration service on all index servers. This service is used for the Central Administration site and is not required on index servers. Stopping this service on index servers can help avoid URL resolution problems with indexing. On the other hand, you must be sure that this service is started on the server that hosts the Central Administration Web site, even if that server is also an index server. You do not need to stop this service for installations where the farm has only one index server.

Before stopping the service on the index server, make sure that the service is running another server.

5)The account we use to propagate the index must be must a member of the Administrators group and a member of the WSS_ADM_WPG group on the query server before you proceed to the next step or propagation of the index will fail. Refer this Link