Error on User Profiles and Properties Page and Event ID: 7888
In a brand new three server farm, I'm opening up the User Profiles and Properties page from the SSP Admin site.
I get the red "X" with 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.
The only log entry I can attribute to this action is in the WFE's Application log and I've copied the error below.
Source: Office SharePoint Server
Category: Office Server General
Event ID: 7888
Description:
A runtime exception was detected. Details follow.
Message: The request failed with HTTP status 503: Service Unavailable.
Techinal Details:
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
at Microsoft.Office.Server.Search.Administration.SearchApi.RunOnServer[T](CodeToRun`1 remoteCode, CodeToRun`1 localCode, Boolean useCurrentSecurityContext, Int32 versionIn)
at Microsoft.Office.Server.Search.Administration.SearchApi..ctor(WellKnownSearchCatalogs catalog, SearchSharedApplication application)
at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.get_SearchApi()
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.<>c__DisplayClass3.<GetImportStatus>b__0()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
So, in digging around, I got this one hint from an acquaintance at MindSharp.com:
IIRC, this is a permissions error in that the particular SharePoint Server 2007 service cannot access the SQL database.
Which leads me to the following questions:
-
What's IIRC
-
Which MOSS 2007 service would we be talking about, the SSP Admin service?
-
Which SQL Database?
So to work past all of these questions, I added every service account to a group on the SQL Server and then created a SQL Server Login for that group with the sysadmin server role and made it dbowner of every database.
Alas, to no avail. Apparently, there's something between the server that's running the SSP Admin service and the SQL Server that acting gnarly.
I'll fix it. It'll rue the day…
JK
Tags: