Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Error message 7888 when deploying a new SSP

  Asked By: Imran    Date: Sep 21    Category: Sharepoint    Views: 3662

I'm coming across an error message during SSP deployment that's
making me gnash my teeth. In the screen 'New Shared Services
Provider', after specifying all

the details and clicking 'OK', SharePoint attemps several times to
accomplish the tasks, but uncessufully. In the Application logs
within event viewer,

around 20 times, we get generated:

<ERROR>

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date: 1/27/2009
Time: 5:02:08 PM
User: N/A
Computer: MOSS
Description:
A runtime exception was detected. Details follow.
Message: Windows NT user or group 'sharepoint.local\spservice' not
found. Check the name again.

Techinal Details:
System.Data.SqlClient.SqlException: Windows NT user or
group 'sharepoint.local\spservice' not found. Check the name again.
at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError
(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning
(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, TdsParserStateObject
stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader
(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds
(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean
returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader
(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean
returnStream, String method,

DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery
(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery
(SqlCommand command)
at Microsoft.Office.Server.Data.SqlServerManager.GrantLogin(String
user)
at
Microsoft.Office.Server.Administration.SharedResourceProvider.Synchron
izeConfigurationDatabaseAccess(SharedComponentSecurity security)
at
Microsoft.Office.Server.Administration.SharedResourceProvider.Synchron
izeAccessControl(SharedComponentSecurity sharedApplicationSecurity)
at
Microsoft.Office.Server.Administration.SharedResourceProvider.Microsof
t.Office.Server.Administration.ISharedComponent.Install()
at
Microsoft.Office.Server.Administration.SharedResourceProvider.Provisio
n()

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp.

</ERROR>

<ERROR IN CENTRAL ADMIN SITE>

Shared Services Provider creation failed
Reason: Thread was being aborted.

Check the event log for details.

Note: SSP provisioning will be retried periodically. If you correct
the error that caused this failure, provisioning will subsequently
succeed. To stop

provisioning from being retired, delete the SSP.

</ERROR IN CENTRAL ADMIN SITE>


I'm deploying MOSS 2007 in the following scenario:

# Server Products:

Windows Server 2003 Enterprise SP2 R2 x86
Office SharePoint Server 2007 x86 (12.0.0.4518) without Service Pack
SQL Server 2008 Enterprise
.NET Framework 2 SP2 (Beta)
.NET Framework 3 SP2 (Beta)
.NET Framework 3.5 SP1 (Beta)

# Virtual environment: Sun VirtualBox installed on my MAC OS X Leopard

# Farm Details: Single Server Install

# Machine Roles: Domain Controler, IIS, SQL Server, DNS, MOSS

ATTEMPTS:
==========

1) Central Admin:

<ERROR IN CENTRAL ADMIN SITE>

Shared Services Provider creation failed
Reason: Thread was being aborted.

Check the event log for details.

Note: SSP provisioning will be retried periodically. If you correct
the error that caused this failure, provisioning will subsequently
succeed. To stop

provisioning from being retired, delete the SSP.

</ERROR IN CENTRAL ADMIN SITE>

Besides that error message aforementioned in the event viewer

2) Command line:

stsadm -o createssp -title "MOSS_SSP" -url
http://moss:8080/ssp/admin -mysiteurl http://moss:1989 -
ssplogin "sharepoint\spservice" -indexserver "moss"

-indexlocation "c:\program files\microsoft office servers\12.0
\data\office server\applications" -ssppassword PaSsWoRd -
sspdatabaseserver "moss"

-sspdatabasename "MOSS_SSP_DB" -searchdatabaseserver "moss" -
searchdatabasename "MOSS_SSP_Search" -ssl no

Windows NT user or group 'sharepoint.local\spservice' not found.
Check the name
again.

The SSP is created in the end, but it is displayed with Failure
Status and is unmanageable

# The account 'sharepoint\spservice' does exist in SQL Server and is
DBCREATOR and SECURITYADMIN

# The Application Pool Identity for the Central Admin Application
Pool is 'sharepoint\sql'

# The SharePoint Services Timer Service runs under 'sharepoint\sql'

# By looking at the Windows Services snap-in, I saw that:

- Windows SharePoint Services Search => sharepoint.local\spservice

- Windows SharePoint Services Timer => sharepoint\sql

3) In order to update / synchronize the farm credentials, I followed
the KB934838

Different from what the KB states, the job definition 'Administration
Application Pool Credential Deployment' remained in its respective
Admin site

Then, when I went to update the account credential, I failed with the
below error message in teh event viewer:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 5767
Date: 1/27/2009
Time: 6:09:16 PM
User: N/A
Computer: MOSS
Description:
Error updating the account password for process identity Id 2c87236e-
6399-4965-866c-e136e413621c, please fix manually. There was an error
encrypting or

decrypting credentials. Either a credential update is currently being
performed, or you must update the farm account credentials on this
server before you

can perform this task.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp.

Refreshing the Timer Job definition site, the job was still there

I went for step 4 below

4) To run the Configuration Wizard, maintaining the existing farm and
that unique machine as the Admin Site host

The operation failed with the following error in the log:

01/27/2009 18:17:47 1 INF
Entering function PsconfigLabel.PsconfigLabel
01/27/2009 18:17:47 1
INF Entering function
PsconfigLabel.CommonStuff
01/27/2009 18:17:47 1
INF Created a label,
name is FinishForm, text is An exception of type

System.InvalidOperationException was thrown. Additional exception
information: There was an error encrypting or decrypting credentials.
Either a credential

update is currently being performed, or you must update the farm
account credentials on this server before you can perform this task.
01/27/2009 18:17:47 1
INF Leaving function
PsconfigLabel.CommonStuff
01/27/2009 18:17:47 1 INF
Leaving function PsconfigLabel.PsconfigLabel

I decided to run, again, the command to update the farm credentials
as suggested in the error message

I still bumped into the same error message:

"There was an error encrypting or decrypting credentials. Either a
credential update is currently being performed, or you must update
the farm account

credentials on this server before you can perform this task."

The job definition remained there. Note: it was not there before
running the first command of the KB

5) I decided to begin from scratch and make sure that <netbios domain
name>\<account name> was used in all settings, instead of fully
qualified domain name

as shown for the Windows SharePoint Services Search in the Services
snap-in

5.a) I stopped the Office SharePoint Server Search and Windows
SharePoint Services Help Search

5.b) I deleted the SSP: stsadm -o deletessp -title MOSS_SSP -
deletedatabases -force

5.c) I started the Office SharePoint Server Search service

5.d) I deleted the existing Web Application for MySites on port 1989
as well as the one for the SSP Web Application on port 8080,
including their respective content databases and IIS web sites

5.e) In order to make sure everything would be set alike from the
outset, I deleted the Web Application on port 80 as well

6) Brand new deployment of Search:

6.a) Configuring the Office SharePoint Server Search => The Farm
Search Service Account was set to 'sharepoint\spservice'

I failed and got stuck at the error message:

"An unhandled exception occurred in the user interface.Exception
Information: There was an error encrypting or decrypting credentials.
Either a credential update is currently being performed, or you must
update the farm account credentials on this server before you can
perform this task."

The Administration Application Pool Credential Deployment job
definition was still present and I deleted manually, followed by an
IISReset

Trying again step 6:

6.a) Configuring the Office SharePoint Server Search => The Farm
Search Service Account was set to 'sharepoint\spservice'

Success this time

6.b) Configuring the Windows SharePoint Services Search => Both the
Service Account and the Content Access Account were set
to 'sharepoint\spservice'

Success

7) New SSP Deployment:

7.a) I created 3 empty Web Applications

- Port 80 (users' content): success
- Port 8080 (SSP): success
- Port 1989 (MySite):

- For the 3 Application Pool identities, it was
specified 'sharepoint\spservice'
- After each creation, IISReset /noforce was run

7.b) Through STSAdm, I deployed the SSP:

stsadm -o createssp -title "MOSS_SSP" -url
http://moss:8080/ssp/admin -mysiteurl http://moss:1989 -
ssplogin "sharepoint\spservice" -indexserver "moss"

-indexlocation "c:\program files\microsoft office servers\12.0
\data\office server\applications" -ssppassword PaSsWoRd -
sspdatabaseserver "moss"

-sspdatabasename "MOSS_SSP_DB" -searchdatabaseserver "moss" -
searchdatabasename "MOSS_SSP_Search" -ssl no

I ended up with the error message

"The specified credentials are invalid.
Parameter name: account"

I tried the same thing via the Admin Site, and the SSP Service
Credential was set to 'sharepoint\spservice'

Share: 

 

No Answers Found. Be the First, To Post Answer.

 
Didn't find what you were looking for? Find more on Error message 7888 when deploying a new SSP Or get search suggestion and latest updates.




Tagged: