Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 822265 - Last Review: May 31, 2007 - Revision: 4.5
You receive a "Cannot generate SSPI context" error message and the configuration database is not created when you run SharePoint Portal Server 2003 Setup
When you run SharePoint Portal Server Setup to install
SharePoint Portal Server 2003 to a server in a server farm, you may find that
the configuration database is not created, and you receive the following error
message:
Error
Cannot generate SSPI context.
This issue may occur in situations when there are entries
that exist in Active Directory from a previous installation of SharePoint
Portal Server, and these entries prevent Microsoft SQL Server from registering
itself correctly in Active Directory.
To resolve this issue, follow these steps:
- On the server in the server farm, that is running Microsoft
SQL Server, click Start, and then click
Run.
- In the Open box, type
cmd, and then click OK.
- Type the following line at the command prompt, where
ServerName is the name of the server that is running
Microsoft SQL Server 2000, and then press ENTER:
setspn –l ServerName
A list of service principal names that are currently registered
for the server are displayed. - From the list of currently registered service principal
names that is displayed earlier in step 3, make a note of each service
principal name that starts with the following text:
MSSQLSvc
- Delete each service principal name entry that starts with
MSSQLSvc. To do so, type the following line at the command
prompt, where ServicePrincipalNameEntry is the
service principal name entry that starts with MSSQLSvc and
ServerName is the name of the server that is running
Microsoft SQL Server, and then press ENTER:
setspn –d ServicePrincipalNameEntryServerName
Repeat this step for each service principal name entry that starts
with MSSQLSvc. - Restart the server.
- Create the configuration database.
Note If the symptoms that are described earlier in the "Symptoms"
section of this article persist after you perform this procedure on the server
that is running SQL Server, perform this procedure on each server in the server
farm.
In Microsoft Windows Server 2003, the Setspn.exe
command-line tool is included with the Windows Support Tools. You can install
the Windows Support Tools from the Support\Tools folder of the Microsoft
Windows Server 2003 CD-ROM.
In Windows 2000, the Setspn.exe
command-line tool is included with the Windows 2000 Resource Kit. For more
information about the Windows 2000 Resource Kit, visit the following Microsoft
Web site:
For more information about how to deploy, how to configure,
and how to administer SharePoint Portal Server, see the
Microsoft Office SharePoint Portal Server 2003 Administration Guide. The
Microsoft Office SharePoint Portal Server 2003 Administration Guide (Administrator's Help.chm) is located in the
Docs folder in the root folder of the Microsoft Office
SharePoint Portal Server 2003 CD-ROM.
For more information about
SharePoint Portal Server, visit the following Microsoft Web site:
APPLIES TO
- Microsoft Office SharePoint Portal Server 2003
| kbdatabase kbsetup kberrmsg kbbug KB822265 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate