Configuration Error SSO on SPS 2003 SP1

Discussion:

(too old to reply)

m***@yahoo.com

2005-05-01 15:54:09 UTC

Hi,

I'm experiencing a problem configuring SSO on my SPS Server.

Running Windows Server 2003 SP1, WSS SP1, and SPS2003 SP1.

I have created a user and added it to the following groups local
Administrators, STS_WPG and SPS_WPG.

On the SPS Central Admin page: Manage Server Settings for Single
Sign-On. I get the following error "Failed to connect to the database
server. Verify connectivity and rights for the configuration account
and try again."

Viewing the errors in the event log I have two errors

Error 1 Description
The Microsoft Single Sing-On(SSOSrv) service failed to connect to
SQLServer host SERVER. The error returned was 0x8007007b

Error 2 Description
User DOMAIN\USER failed to configure the single sign-on server. The
error returned as 0x80630009. Verify this account has sufficient
permissions and try again.

I have checked connectivity to the database and experience no problems.

I have the exact same configuration on another VPC without any service
packs and on that VPC the SSO Configuration works without and problems.

Does someone have a work around for this problem?

Thanks in advance.

kll

2005-05-02 21:05:57 UTC

Permalink

I have the exact same problem and Microsoft have looked at the problem
and cant find the problem. Everything is correct, but its not working.

The MS conclusion is that the configuration database is corrupted and
we need to create a new one.

/Peter Mazzarella

Post by m***@yahoo.com
Hi,
I'm experiencing a problem configuring SSO on my SPS Server.
Running Windows Server 2003 SP1, WSS SP1, and SPS2003 SP1.
I have created a user and added it to the following groups local
Administrators, STS_WPG and SPS_WPG.
On the SPS Central Admin page: Manage Server Settings for Single
Sign-On. I get the following error "Failed to connect to the database
server. Verify connectivity and rights for the configuration account
and try again."
Viewing the errors in the event log I have two errors
Error 1 Description
The Microsoft Single Sing-On(SSOSrv) service failed to connect to
SQLServer host SERVER. The error returned was 0x8007007b
Error 2 Description
User DOMAIN\USER failed to configure the single sign-on server. The
error returned as 0x80630009. Verify this account has sufficient
permissions and try again.
I have checked connectivity to the database and experience no problems.
I have the exact same configuration on another VPC without any service
packs and on that VPC the SSO Configuration works without and problems.
Does someone have a work around for this problem?
Thanks in advance.

Tony Cutlan

2005-05-04 13:11:02 UTC

Permalink

Manjos,

I'm pleased to tell you that after a week of trying workaround after
workaround we've managed to crack this problem.

First things first, you need to make sure that you have Kerberos running
correctly, especially if you're using domain accounts as the SharePoint
application pool identities. This means you will need to set up your
websites to negotiate user authentication and use setspn to create SPN's for
your service accounts. Mail back if this is relevant to you or you need
further help.

The major problem though, is (wait for it) Windows Server 2003 SP1. To get
around the problem, we needed to back-out SP1, uninstall SharePoint Portal
and Services, uninstall IIS. Then reload IIS, reload SharePoint, apply the
two SharePoint service packs (one for services, the other for portal), then
configure the SSO. Like magic it all works. We only found it because we
have a set of servers in the UK which were unpatched, and worked, and a set
of servers running w2k3 SP1 in the US that didn't.

Best of luck...

Tony

P.S. Please, please, please Microsoft - get the error reporting for
SharePoint sorted out. Practically any problem gives the same error message
and the logging facility is useless. It makes debugging connection and
configuration problems practically impossible and means find a solution is
more luck than skill, which just isn't acceptable these days.

m***@yahoo.com

2005-05-04 18:22:03 UTC

Permalink

Thank you Tony for the update,

After trying what Tony mentioned it appears that W2K3 SP1 is the
problem and so installing the service packs(WSS SP1, SPS SP1, and W2K3
SP1 in the order they where released) does solve the problem.

Thanks again Tony

Nil Ratan Sahoo

2005-05-11 12:28:05 UTC

Permalink

Hi,

I have A Production server Installed with Windows Server 2003 SP1, and I
can't rollback the service pack. and the sharepoint portal is running fine.
but when I want to configure the Single signon service. I t gives error as
Cannot connect to the database server, check that u have access , this aone
error, and if I am using an existing database name then it Instantly detects
that the database exists. and If I continue( Clicl "OK") then it shhows error
"Database Exists".

Please help ....

For Some Webpart component we want Single signon service..

Thanks..

Post by Tony Cutlan
Manjos,
I'm pleased to tell you that after a week of trying workaround after
workaround we've managed to crack this problem.
First things first, you need to make sure that you have Kerberos running
correctly, especially if you're using domain accounts as the SharePoint
application pool identities. This means you will need to set up your
websites to negotiate user authentication and use setspn to create SPN's for
your service accounts. Mail back if this is relevant to you or you need
further help.
The major problem though, is (wait for it) Windows Server 2003 SP1. To get
around the problem, we needed to back-out SP1, uninstall SharePoint Portal
and Services, uninstall IIS. Then reload IIS, reload SharePoint, apply the
two SharePoint service packs (one for services, the other for portal), then
configure the SSO. Like magic it all works. We only found it because we
have a set of servers in the UK which were unpatched, and worked, and a set
of servers running w2k3 SP1 in the US that didn't.
Best of luck...
Tony
P.S. Please, please, please Microsoft - get the error reporting for
SharePoint sorted out. Practically any problem gives the same error message
and the logging facility is useless. It makes debugging connection and
configuration problems practically impossible and means find a solution is
more luck than skill, which just isn't acceptable these days.

Atul

2005-05-23 10:38:05 UTC

Permalink

Hi Tony,

As per you suggested, I executed the steps. But failed to configure.
I am running on following configuration:
Windows 2003 Server (Without SP1 )
Sharepoint 2003 with SP1
SQL server 2000 with SP3

I have one domain user (spsadmin) that I used while installing SPS 2003 and SQL Server. Sharepoint services are running using this account.

The same account I want to configure for Single Sign On. To achieve this, Single Sign-On service is running under spsadmin account. I logged on to the machine as spsadmin and tried to configure SSO from the page http://localhost:xxx/sso/ManageServer.aspx by giving Domain\spsadmin for the text boxes:

Single sign-on Settings and Enterprise Application Definition settings.

Rest all the settings are the default settings. Database server is local machine .

I am getting following error while I click OK.

Failed to connect to the database server. Verify connectivity and rights for the configuration account and try again.

I dont know what I am missing here.

Can you help me out?

thanks a lot.

Regards,
Atul

Ash Wainwright

2005-06-02 17:12:08 UTC

Permalink

This worked for me

http://www.winserverhelp.com/ftopic32593.html
--
Ash

Post by Atul
Hi Tony,
As per you suggested, I executed the steps. But failed to configure.
Windows 2003 Server (Without SP1 )
Sharepoint 2003 with SP1
SQL server 2000 with SP3
I have one domain user (spsadmin) that I used while installing SPS 2003 and SQL Server. Sharepoint services are running using this account.
Single sign-on Settings and Enterprise Application Definition settings.
Rest all the settings are the default settings. Database server is local machine .
I am getting following error while I click OK.
Failed to connect to the database server. Verify connectivity and rights for the configuration account and try again.
I dont know what I am missing here.
Can you help me out?
thanks a lot.
Regards,
Atul

s***@hotmail.com

2005-06-22 21:09:42 UTC

Permalink

I confrunted this problem early on in dealing with Sharepoint. As
stated before the only thing you can do is to uninstall SP1 and
reinstall SharePoint or start from the ground up and install and
configure both SQL and then SharePoint before installing ST1.

Steve