Archive

Archive for January, 2012

Steps for Creating a Shared Service Provider – MOSS 2007

January 6, 2012 Leave a comment
Login as domain\farmadmin
Open Central Admin SSP page Select Shared Services Administration

(in Quick Launch – left hand navigation pane)

New SSP

Create New SSP Page = Manage this Farm’s Shared Services

Select New SSP

Configure Shared Service Provider Page = New Shared Services Provider

Enter SSP Name = SharedServices1

Select – Create a new Web application

  • This opens the standard Create New Web Application page
Create New Web Application for SSP Select option = Create new IIS Web site

  • Port = 100
  • Description = SSP – 100
  • Host Header = <blank>
  • Authentication provider = NTLM
  • Allow Anonymous = No
  • SSL = No
  • Load Balance = (default)
  • Select option ‘Create new application pool’
  • Application pool name = SS2P – 100
  • App Pool Account (Configurable) = domain\farmadmin
  • Select option ‘Restart IIS Automatically’
  • Database Name = WSS_Content_SSP
NOTE – Will be returned to ‘Configure Shared Service Provider’ page with an error – this is normal.

Specify New Shared Services Provider

Web application = SSP – 100 (Web App created above)

My Site Location – Select Create New Web Application

Create Web Application for My Site Select option = Create new IIS Web site

  • Port = 101
  • Description = MySites – 101
  • Host Header = <blank>
  • Authentication provider = NTLM
  • Allow Anonymous = No
  • SSL = No
  • Load Balance = (default)
  • Select option ‘Create new application pool’
  • Application pool name = MySites – 101
  • App Pool Account (Configurable) = domain\farmadmin
  • Select option ‘Restart IIS Automatically’

Database Name = WSS_Content_MySite

NOTE – Will be returned to ‘Configure Shared Service Provider’ page with an error – this is normal.
Configure Shared Service Provider (cont.)
Page = New Shared Services Provider

Verify

  • SSP Name = Shared Services1
  • Web App = SSP – 100
  • My Site web app = MySites – 101

Relative URL = /

SSP Service Credentials = domain\SVC_SP_ShrdSvc

SSL = No

Verify –

  • Path for index location =E:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications
  • All remaining values are default
Stop Windows SharePoint Services Help Search Central Admin > Operations > Services on server

Select Stop

Select OK on warning dialog

Stop Office SharePoint Server Search Central Admin > Operations > Services on server

Select Stop

Select OK on warning page

Change Associations Select Shared Serviced Administration > Change Associations

  • Shared Services Provider = SharedServices2
  • Web application = select all
Change Default SSP Select Change Default SSP

SSP = SharedServices2

Select OK on warning page

Start Windows SharePoint Services Help Search Central Admin > Operations > Services on server

Select Start

  • Service Account = domain\farmadmin
  • Content Access Account = domain\farmadmin
  • Search Database Name = WSS_Search2_<computer name>
Start Office SharePoint Server Search Central Admin > Operations > Services on server

Select Start

  • Query and Indexing = both checked
  • Farm Search Service Account = domain\farmadmin
Configure Search Select SharedServices2

Select Search Aministration

Select Content Source

  • Schedule Full Craw Weekly, Mon-Friday, 9 PM 
  • Start full crawl = checked
Advertisements
Categories: SharePoint 2007

SharePoint 2007 Search Administration Page Error

January 6, 2012 Leave a comment

Problem – you can open Central Administration, the Shared Service Provider, and the Search Administration page. However, the Active crawls never return, and if you try to select Content Sources you get this error

An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.

http://support.microsoft.com/kb/962928

SharePoint partly uses SSL name resolution in the background between farm servers, which users generally do not need to be aware of. Evein if you don’t use SSL for the SSP, Microsoft uses it in the background.

1000 is the number of days that the certification will be valid. This problem will start about 1000 days from when you installed the SharePoint farm (about 2 years, 8 months, and a couple weeks).

Solution  – on all servers, run

net stop osearch

selfssl /s:951338967 /v:1000

net start osearch

This will replace expired ssl certificate.

Categories: SharePoint 2007