Event ID 27745

I was working on production environment and this error was appearing each couple of minutes and i go mad as we uninstall some windows updates, disable teaming on the SharePoint and SQL servers but the error appears the next day

Event ID:      27745

Description:

The description for Event ID 27745 from source Windows SharePoint Services 3 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

#50071: Unable to connect to the database xxx  sql database.  Check the database connection information and make sure that the database server is running.

After digging more and more I found these errors in the SQL servers’ logs:

The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

Error: 17806, Severity: 20, State: 2.

SSPI handshake failed with error code 0x80090304 while establishing a connection with integrated security; the connection has been closed. [CLIENT: IP]

Error: 18452, Severity: 14, State: 1.

Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: IP]

The resolution was setting SPN for the SQL server

setspn -A MSSQLSvc/FQDN:1433 accountname

setspn -A MSSQLSvc/FQDN accountname

Configuring your Sharepoint farm by Command Line

If you need to install SharePoint server 2007 by command line not by GUID and this is useful when you creating farms in multiple domains , more information about psconfig http://technet.microsoft.com/en-us/library/cc263093.aspx. psconfig tool is located at c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN

Create Your Farm

You have to run the below commands on the Index server or the central admin server, and fore sure you have to install SharePoint first before this commands

• psconfig -cmd configdb -create -server “SERVER\INSTANCE” -database “MOSS_FarmConfig” -admincontentdatabase “MOSS_AdminWebSite_Content” -user DOMAIN\FARMACCOUNT -password PASSWORD
• psconfig -cmd helpcollections –installall
• psconfig -cmd secureresources
• psconfig -cmd services –install
• psconfig -cmd services –provision
• psconfig -cmd installfeatures
• psconfig -cmd adminvs -provision -port PORT -windowsauthprovider onlyusentlm
• psconfig -cmd applicationcontent -install
• stsadm -o spsearch -action start -farmserviceaccount DOMAIN\SEARCHService -farmservicepassword PASSWORD databaseserver “SERVER\INSTANCE” -databasename “MOSS_WSS_SearchDB”
• stsadm -o osearch -action start -role Index -farmcontactemail “EMAIL” -farmperformancelevel Reduced -farmserviceaccount DOMAIN\SEARCHSERVICE -farmservicepassword PASSWORD

Add Servers to the Farm

After you created the farm if you need to add more servers to the farm apply the below commands

• psconfig -cmd configdb -connect -server “SERVER\INSTANCE” -database “MOSS_FarmConfig” -user DOMAIN\FARMACCOUNT -password PASSWORD
• psconfig -cmd helpcollections -installall
• psconfig -cmd secureresources
• psconfig -cmd services install
• psconfig -cmd installfeatures
• psconfig -cmd applicationcontent -install

Managed Metadata Service or Connection is currently not available

You may face the below error when you try to manage service application:

The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started

Microsoft issued new KB for this issue you can find it here

Change AAM of Mysite in SharePoint 2007

Follow these steps to change AAM for Mysite:

• Go to “Alternate Access Mappings” in SharePoint Central Administration > Operations.
• Click on the URL that corresponds to your My Site.
• Go to “Edit Internal URLs” page, and change it to your new DNS name
• Go to “My Site Settings” which can be found in the Shared Service you configured in Shared Services Administration. Again, enter your new My Site URL.
• Modify your IIS site host header value to match the URL your entered in Central Administration.
• Open the command prompt and go IISreset.

The farm is not available

While installing one of the feature ,you got the following error

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa

dm -o installfeature -name AKS -force

The farm is unavailable.

Solution:

1.
This happens when you do not have permissions on the database server. Make sure you have the necessary permissions.

2.
If you have recently updated your MOSS version to 12.0.0.6318 i.e. MOSS 2007 or WSS 3.0 Infrastructure Update (KB951695 & KB951297) then you might need to restart the PC/DB services.

3.
If you have updated SQL Server Express Edition to SQL Server then you need to restart the PC/DB services.

In my case just restarting machine helped. But in some cases you cannot restart server machine just like that. So in that case restarting the services might do well

Error when you try to edit the content source schedule “Access is denied”

To work around this issue, you must add the WSS_WPG group to the Tasks folder. To do this, follow these steps:

1. Use an account that has administrative permissions to log on to the computer that is running the Office SharePoint Server 2007 indexing service.
2. Click Start, click Run, type cmd, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
   attrib –s %windir%\tasks
   Note In this example, %windir% is the path of the Windows folder. For example, the path can be C:\Windows.
   Note If Windows Explorer is open when you make this change, you will not see the extra tab in Windows Explorer. If Windows Explorer is already open, close and then reopen it before you perform step 4.
4. In Windows Explorer, right-click the Tasks folder, and then click Properties.
5. In the Tasks Properties dialog box, click the Security tab, and then click Add
6. In the Select Users, Computers, or Groups dialog box, type WSS_WPG in the Enter object names to select box, and then click OK.
7. Grant the following permissions for the WSS_WPG account, and then click OK: Read & Write
8. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
9. In Internet Information Services (IIS) Manager, right-click ComputerName (local computer), click All Tasks, and then click Restart IIS.
10. Click Start, click Run, type cmd, and then click OK.
11. At the command prompt, type the following command, and then press ENTER:
    attrib +s %windir%\tasks
    Note This resets the Tasks Property back to the default view.

The search service is currently offline

Error ”  The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress “

Solution :

1. Stop and start search services on new index server and all servers running the query role
2. Then restarted the search service via central administration under operations tab>>Services
3. Went into Services.msc and found the Office Search Service and restarted it manually
4. Checked to make sure that the search service account had correct rights to SQL.

None of the above worked so…

1. Going into the SSP settings (clicking on SSP administration not the SSP link itself) within the left quick launch navigation from within central administration.
2. Selecting the dropdown arrow next to the SSP where I was having the search issue
3. Select edit properties
4. Within the properties screen of the SSP look for the “Process accounts”
5. Make sure that your search account is in there!

People Picker Bug

When adding new User in the Site Collection administrator, you cannot find the user ” cannot find mached ” from another domain , and you have one way trust between these domains

Solution

Run the two commands

1 Stsadm.exe -o setapppassword -password <password>
2 stsadm.exe -o setproperty -pn “peoplepicker-searchadforests” -pv “domain:yourdomain.local;domain:trusted domain.local”,username,password -url “http://serverip:port&#8221;