SharePoint:Recurring Meeting Workspace error: ‘g_InstanceID’ is undefined

Scenarios:

After changing the master page on a Meeting Workspace site, the recurring meeting workspace hyperlinks under “Select a date from the list below” do not work and throw a JavaScript error.

If you create a custom master page and use it for your Meeting Workspaces, a JavaScript error is thrown.

Error:
‘g_InstanceID’ is undefined

Cause:
The g_instanceId global JavaScript variable is declared in a script registered runtime by the Microsoft.SharePoint.Meetings.PropertyBag web control. This control is used in the master page that’s used by Meeting Workspace sites called “MWSDefault.master” (located on server in 12 hive\TEMPLATE\GLOBAL\).

Steps to Reproduce:

1.Create a new Workspace: Site Actions-> Create Site -> Select [Meetings] Basic Meeting Workspace, click Create.
2.On Workspace site, add a Calendar list: Site Actions -> Create -> [Tracking] Calendar.
3.Add a new event to Calendar list, make recurring event, and select [x] Use a Meeting Workspace to organize attendees, agendas, documents, minutes, and other details for this event. Click OK.
4.Follow steps to create workspace for Calendar event. Go to workspace.
5.Change master page for workspace: Site Actions -> Site Settings -> [Look and Feel] Master page -> select any master page for Site Master Page and System Master Page. Click OK. Go back to workspace.
6.Now the links under “Select a date from the list below:” do not work and throw a JavaScript error message: ‘g_InstanceID’ is undefined .
Workaround:

1.Open SharePoint Designer 2007. Go to File Open Site and connect to SharePoint site.
2.Expand out _catalogs -> masterpage -> open master page used on Meeting Workspace.
3.In Code View, add the following line of code under tag:


4.Add the following line of code after opening tag:
5.Save master page, check in (if necessary), and publish major version.

** Change the settings in master page
if this is not working also change in the meeting workspace master page

SharePoint:Unknown Error While accessing to Search Settings in SSP

If you are facing this issue, check the following services are running are not in the server


1. Office SharePoint Server Search
2. Windows SharePoint Services Search.

SharePoint:Unable to Services on Server in Operations tab

If you are not seeing Services on server in Operations tab in central admin
follow these steps:

Go to Central admin-->Operations

add _admin/server.aspx in the url

you can see the services on server under operations tab

SharePoint:Incremental Crawl Vs Full Crawl

Full Crawl: “Full crawl” crawls entire content under a content source (depending upon two settings specified at the time of creating the content source. These settings are “Content Source type” and “Crawl Settings”).

Incremental Crawl: “Incremental crawl” crawls the content which has been added/modified after last successful crawl.

Why do we need incremental Crawl?
Though “Full crawl” crawls every bit and piece of content under a content source but we surely need Incremental crawl as it crawls content which has been added/modified after last successful crawl.
Full crawls will take more time and resource to complete than Incremental crawls. You should consider following facts before going for full crawl instead of incremental crawl.


1.As compared with incremental crawls, full crawls chew up more memory and CPU cycles on the index .
2.Full crawls consume more memory and CPU cycles on the Web Front End servers when crawling content in your farm.
3.Full crawls use more network bandwidth than incremental crawls.

Crawling puts an overhead on resources. If some content is already been crawled and indexed, why do we need to crawl it again? Therefore incremental crawl is used in such cases to take care of any added/modified content after last successful crawl.
There are some scenarios where incremental crawl doesn’t work and you need to run full crawl.

Why do we need Full Crawl?

1. Software updates or service packs installation on servers in the farm.
2. When an SSP administrator added new managed property.
3. Crawl rules have been added, deleted, or modified.
4. Full crawl is required to repair corrupted index. In this case, system may attempt a full crawl (depending on severity of corruption)
5. A full crawl of the site has never been done.
6. To detect security changes those were made on file shares after the last full crawl of the file share.
7. In case, incremental crawl is failing consecutively. In rare cases, if an incremental crawl fails one hundred consecutive times at any level in a repository, the index server removes the affected content from the index.
8. To reindex ASPX pages on Windows SharePoint Services 3.0 or Office SharePoint Server 2007 sites. The crawler cannot discover when ASPX pages on Windows SharePoint Services 3.0 or MOSS sites have changed. Because of this, incremental crawls do not reindex views or home pages when individual list items are deleted.

The system does a full crawl even when an incremental crawl is requested under the following circumstances:
· A shared services administrator stopped the previous crawl.
· A content database was restored. This applies to MOSS and Windows SharePoint Services 3.0 content databases only.


Note: You should not pause content source crawls very often or pause multiple content source crawls as every paused crawl consumes memory on index server.