RE: Single Sign On Database Connection Issues
- From: Trevor Conn <TrevorConn@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Apr 2006 13:32:04 -0700
Fantastic! This appears to have worked! Thanks very much!
Trevor
"cwogle" wrote:
Trevor,.
Your first problem sounds like the dreaded Quote-Marks-In-The-Registry-Key
error. Never fear ... it's Not Your Fault. This MS article describes it
pretty well and tells you how to fix it -- or at least -- work around it.
http://support.microsoft.com/default.aspx?scid=kb;en-us;901203
hth,
Chris
"Trevor Conn" wrote:
Hello --
I am attempting to set up the Single Sign-on Service for a proof of concept.
I have been walking through the steps outlined at the link below in order to
get this going.
http://www.microsoft.com/technet/prodtechnol/sppt/reskit/c2661881x.mspx#ENF
After assigning all the appropriate permissions to the account used by
SSOSrv, I'm having difficulty on the "Manage Server Settings for Single
Sign-On" screen. There are two scenarios occuring with regard to my attempts
to define the necessary database. The database will live in an instance of
SQL Server 2000 SP3 on the same machine hosting SharePoint. As I said, this
is a proof of concept.
So after assigning the appropriate security to the user account, I'm
currently stuck between these two scenarios.
1.) The database I wish to associate with SSOSrv doesn't exist, so I'm
attempting to create it through the "Manage Server Settings" screen. After I
specify all of my values and submit them, I get the following red error
message:
"Failed to connect to the database server. Verify connectivity and rights
for the configuration account and try again."
This additional information is in the application event log in chronological
order:
"The Microsoft Single Sign-on (SSOSrv) service failed to connect to
SQLServer host SPS-DEMO. The error returned was 0x8007007b."
Followed by:
"User DOMAIN\tconn failed to configure the single sign-on server. The error
returned was 0x80630009. Verify this account has sufficient permissions and
try again."
After checking and re-checking the user account rights and permissions based
on the documentation, I move to #2.
2.) Because I can't get around #1, I go to create the database myself via
Enterprise Manager using the account that SSOSrv will eventually use. This
grants "dbo" privileges to the service account which should allow it to do
anything. In addition, I check the "public" role access box since the
documentation says to do so.
When I submit the "Manage Server Settings" screen, I'm prompted with a
confirmaion dialog box that asks me if I wish to overwrite the SSOSrv
settings in the already existing database. It also advises me that I'll need
to regenerate my encryption key in order to preserve the data in the
database. I don't really care about that, so I click 'OK'. The fact that this
dialog is appearing proves that I can connect to the SQL Server and that
SSOSrv can see the database I've created. However the page comes back and
there's a red error at the top saying "The database already exists". When I
look in the application event log, I see the following:
"User DOMAIN\tconn failed to configure the single sign-on server. The error
returned was 0x806300b9. Verify this account has sufficient permissions and
try again."
I am totally stuck and cannot understand how I don't have the necessary
permissions if the SSOSrv service account has dbo permissions to the
database. I don't discount the possibility that I'm missing something though.
Any help is appreciated. Thanks!
Trevor Conn
- References:
- Single Sign On Database Connection Issues
- From: Trevor Conn
- RE: Single Sign On Database Connection Issues
- From: cwogle
- Single Sign On Database Connection Issues
- Prev by Date: Re: Service Packs and the Order of Installation
- Next by Date: Re: SharePoint Template different Language
- Previous by thread: RE: Single Sign On Database Connection Issues
- Next by thread: Re: Service Packs and the Order of Installation
- Index(es):
Relevant Pages
|
