SharePoint - SSO Error: You do not have the rights to perform this operation.

I get the error : You do not have the rights to perform this operation.  When
i tried to create the SSO database.  The problem i see is that it´s using old
credentials from a previous user and not accepting the new credentials i´m
declaring.  I get error: 1038 (an old username is display on the error
message).

User domain\Administrator failed to configure the single sign-on server. The
error returned was 0x80630005. Verify this account has sufficient permissions
and try again.

How do i modify this account?

  Manue replied...

Has anyone seen my issue? any ideas on how to tackle this problem?

sharepoint, I'm getting errors in the EventViewer stating it = cannot connect to a sharepoint database on the database server. I get = this error once every hour during the day. So my question is how can I = find out what is trying to connect to this sharepoint database? Its a = sharepoint site, but how can I find out which one? = 20 SharePoint is I'm getting errors in the EventViewer = stating = 20 it cannot connect to a sharepoint database on the database server. I get = this = 20 error once every hour during the day. So my question is, how can I = find = 20 out what is trying to connect to this sharepoint database? Its a = sharepoint = 20 site, but how can I find out which one? < / FONT> < / DIV sharepoint, I'm getting errors in the EventViewer = stating it cannot connect to a sharepoint database on the database = server. I get this error once every hour during the day. So my question = is

It starts but hangs on second stage. Looks like something went wrong with creation AdminContent database. SQL Databases show following databases:Sharepoint_config and long one having Admin_content. Did I miss something details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_AdminContent_6319df8d-b2ef-438d-89a1-c9e7fbeffde3 on machine \ instance. Check the database connection information and make sure that the database server is running. . - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2) Event Type: Error Event Source: Windows SharePoint Services 3 Event Category Description: The site / could not be created. The following exception occured: Unable to connect to database. Check database connection information and make sure the database server is running. . For more information, see Help and Support Center at http: / / go.microsoft Wizard Event Category: None Event ID: 104 Computer: SERVER Description: Failed to create the configuration database. An exception of type Microsoft.SharePoint.SPException was thrown. Additional exception information: Unable to connect

Sarah So something to be aware of, all information for SharePoint is kept in the database. So moving the location from the C drive to the D drive will not save any space. If you have not done this already, you should look into moving the database off the C drive if that is where it is located. Yes I know all the data is saved in the database which is not on the C drive but the web element of SharePoint is. I I'm sorry Sarah, this is still not quite making sense to me. If the database is not on the C drive and you have more that a few MB of is what would be installed. If this is the case check the size of the database. 2. Moving the site to the D drive sounds tricky. I would in IIS create use this document. On This Page Introduction About the Configuration and Content Databases Locating the Database Files Moving the Databases Introduction When you install Microsoft® Windows® SharePoint™ Services by using the Web sites. Installing Windows SharePoint Services in this way puts all the files, including the database, in your server computer's \ Program Files directory by default. You may want to move the drive containing the Program Files directory does not have enough disk space for your database requirements, move the databases to another drive on your server computer or to a separate

SharePoint EventID1000: #50070:Unable to Connect to Database - WSS 2.0 I've got a WSS 2.0 server with lots of SharePoint Web applications on it. Intermittently the event log shows the following errors: Check the database connection information and make sure that the database server is running. Where the DatabaseName varies - always a content database - never the configuration database. (the config db is on a local SQL server, the content databases are on a a user accessing the affected site will get an error on their screen saying the database is unavailable. Yesterday I wrote a c# test app that constantly reads from one of it has been running nearly 24 hours and has shown no errors reading from the database, although the Event Log shows that SharePoint has thrown lots of errors reading from that same database several times. Any suggestions? this has been going on for about 1 week most recently

Create a Web application using host header on the destination farm. 2. Backup the content database and restore to the destination farm using SQL tools. 3. Add the restore content database to the Web application created in step 1. Stsadm usage of deleting and adding content database: = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = a. Add content database: stsadm -o addcontentdb -url <url> -databasename <database name> [-databaseserver <database server name> ] [-databaseuser <database username> ] [-databasepassword <database password> ] [-sitewarning <site warning count> ] [-sitemax <site max count> ] b. Delete content database: stsadm -o