SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Sunday, February 15, 2009

Errors in SharePoint Search

Error in SharePoint search...

You may get an error similar to this:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (5fef29c9-308d-4817-bee0-13e39773b7da).
Reason: Object ea615eb7-2b01-4f8c-8db2-ebb2aa357519 not found.

To fix this, you will have to recreate (create a new) SSP; move all applications to point to the new SSP then delete the old one.

Note: After doing so, you must open SQL and under Tasks, remove the SSP Job:

SSPName_Configuration_Job_DeleteExpiredSessions

(Where SSPName is the name SSP you deleted)

If you don't you will start seeing Failure Audit errors in the event log:
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: ]

Monday, February 9, 2009

MOSS and Windows 2008, Event IDs 6875, 7888 and 4965

If you have just installed MOSS on Windows 2008 and have a problem creating Publishing Sites (the create never finishes), check your event log - if you see Events 6875, 7888 and 4965 these indicate permissions problems, etc.

As it turns out, the fix is simply to update the MOSS Farm Account as follows:

Login to one of the servers in the farm, open a command window and change to the SharePoint hive directory:

cd c:\program files\common files\microsoft shared\web server extensions\12\bin

Run the STSADM Command to update the account info:

stsadm -o updatefarmcredentials -userlogin acctname -password acctpassword

Then run an IISReset /noforce

If you have only a single server setup (or standalone server instance), you are done - if in a farm, login to each of the remaining servers and repeat the above adding the "-local" switch:

stsadm -o updatefarmcredentials -userlogin acctname -password acctpassword -local