SharePoint search - Reduce network traffic

Scenario:
http://hostname1.com is an intranet site is hosted on an internal Server 1. The host file on server has an entry to make sure all requests made to hostname1 points to the same server, 
127.0.0.1 hostname1
However each time the SharePoint search crawler runs all requests made to http://hostname1 is first made to the proxy which then redirects it back to Server 1 which unnecessarily increases load on the network and the proxy introducing performance issues.


Solution:
- Review the corporate proxy script (if you have one) used for IE on the server and make sure it does not send intranet request to the proxy.


- If the above does not solve the problem, follow below steps
        => Grant search content access local server rdp access on Server 1
        => Login to the server with the search content access account 
        => Open IE and uncheck "Automatically detect proxy"
        => Remove the search content access account rdp access to Server 1
I am very sure the above steps can be handled differently by editing the registry for the local machine which is something I was not able to uncover so far.

STSADM import error

Scenario: You get this error although you have a valid export of a subsite from a site collection which you had taken using a farm account. You are trying to import using the farm account.


FatalError: The file cannot be imported because its parent web does not exist


Solution:


Make sure that before you do the export the site is not set to readonly.

Could not find webtemplate

Scenario: stsadm export worked fine for a subsite. stsadm import of the same subsite under a different sitecollection on the same farm under the same webapplication as a subsite failed with below error. And yes, the template is present on the environment. 


FatalError: Could not find WebTemplate #75820 with LCID 1033.


Solution:
Since the template was installed and the source site works on the same environment to only way I found to proceed with the import was to manually modify the requirements.xml file located in the uncompressed export folder and remove the faulty webtemplate xml line.

Upload SP2007 list templates to SP2010

Solution:

1. Rename the original .STP to .CAB
2. Extract its manifest.xml and other contents (if any) to a local folder (lets call it [folder])
3. Search for the ProductVersion element. This should have a value of 3
4. Change its value to 4
5. Repackage the manifest.xml into a .CAB. I've done this by using makecab.exe in the C:\Windows\System32 folder
   Syntax: makecab.exe [folder]\manifest.xml [folder]\{template-name}.cab
6. Change the generated cabinet's extension from .CAB back to .STP and upload it into the _catalogs/lt

References:

http://www.heyweb.net/2010/09/converting-sharepoint-2007-list-templates-for-sharepoint-2010/

http://tom-dw.blogspot.com/2010/06/importing-sharepoint-2007-list.html