| Issue Type |
Question or Issue |
Answer |
| Search |
After upgrading from SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007 Beta 2 TR, the account used for profile import is account not upgraded.
Symptom: Profile import fails after upgrade.
|
Workaround: After upgrade, re-enter the user account and password for profie import.
To enter the profile import account,
- Go to the SSP Admin page.
- Click on User Profiles and Properties.
- Click on Configure profile import.
- Enter an account and password for the Default Access Account setting.
|
| Search |
After upgrading from SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007 Beta 2 TR:
Symptom: Search results contain links to content which is not reachable by users. This happens because the crawler gets farm admin credentials for crawling which may crawl more than is desired.
|
Search results may contain items whose publication date is expired, or which has not yet been published.
Workaround: Change crawl account from farm admin to an account that has only read permissions on the portal content.
- Go to central admin page.
- Navigate to the Application Management tab.
- In the Application Security Section, click Policy for Web Application.
- In the right most corner, make sure that the correct application is selected. If not, select the correct one by clicking on the drop-down arrow and then selecting the application in the pop-up window and press ok.
- Click on Add users -> Next, and then enter a domain account and give it Full Read permissions -> Finish.
- Go to SSP admin page.
- In Search section, click Search settings.
- Click Crawl rules.
- Add a new rule and provide a path which covers your portal site.
- Select Include all items in this path.
- Specify crawling account and enter account and password , and for the account which you have given full read permissions.
|
| Search |
The temporary folder used for search indexing is created on the operating system drive rather than under the configured data directory. The size of this folder may grow and fill the partition. If the disk runs out of space, crawls will fail. |
The workaround is:
Open regedit
Look for the regkey based on the product as stated below:
MOSS: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Global\Gathering Manager
WSS: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Global\Gathering Manager
Set the following:
- TempPath = Custom path
- UseSystemTemp = 0
Change the ACL on the custom folder to:
- FC - service account
- FC - admins
- FC - system
After updating the registry, restart the Office SharePoint Server Search service (osearch)
- In a command line, type net stop osearch
- net start osearch
|
| Search |
On SPS 2003 to MOSS 2007 gradual upgrade, the v2 portal address is changed but not updated in the content sources list on v2. Due to this, the urls in the Search results are incorrect and user might see documents that are unreachable by them. |
Workaround is to:
- Go to the v2 search administration pages.
- Click Manage content sources.
- Click on edit of the content source that crawls the v2 portal.
- Fix up the start address to the new v2 portal start address post upgrade.
|
| Search |
Upon a clean install of Beta 2TR, if your Office SharePoint Servers farm includes separate Indexing and Query servers, the shared folder for search index propagation must be configured before starting a crawl.
Symptom: If this workaround was not performed: After the Search Service, in the Search Settings page in Shared Services Administration, the "Propagation Status" line will indefinitely display "Initializing" for each query server in the farm. Any search crawls will stop crawling new documents after crawling a limited ammount of content.
|
For each query server (a server running the Office SharePoint Server Search service, and is configured to "serve search queries" only):
Run the command:
stsadm -o osearch -propagationlocation <location>
where <location> is the desired file system path for the search index files.
|
| Search |
After gradual upgrade on a medium farm, Office SharePoint Server Search was not started on Query boxes |
Go to the Services in Server page in central admin.
Click Start for Office SharePoint Server Search Service.
Check the query role only.
Click OK.
|
| Search |
The spacing, alignment and styles on the search results page are incorrect. The "Go" button for search results is the green button with the arrow key instead of the magnifying glass. |
For the alignment issues:
Upload the latest version of the layouts pages to each portal through the following steps:
- Click Site Actions on the portal homepage and navigate to Site Settings -> Modify all site settings
- In the Galleries section, click Master pages and page layouts.
- Click upload.
- Click browse and navigate to <installdrive>\Program Files\Common files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\PortalLayouts\
- Select advancedsearchlayout.aspx and click OK.
- Click Check in.
- On the list page, find the advancedsearchlayout.aspx and from the ECB, select Publish a Major Version.
- Click OK.
- If you have workflow approval enabled, on the list page, find the advancedsearchlayout.aspx and from the ECB, select Approve/Reject. Change the radio button to Approved and click OK.
- Repeat 3-9 for searchmain.aspx, searchresults.aspx and peoplesearchresults.aspx.
For the search results go button icon:
The searchbox webpart properties need to be changed to match the new icon:
- Navigate to the searchcenter site and select edit page from site actions.
- For the search box webpart, click edit and select Modify shared webpart.
- In the miscellaneous section, change the 'search button right-to-left image URL and the 'Active search button right-to-left image URL' to /_layouts/imges/goRTL.gif
- In the miscellaneous section, change the 'search button image URL' and 'Active search button image URL' to /_layouts/images/gosearch.gif.
|
