How to make Windows SharePoint Services use a preexisting database as the content database
From the link below. I am trying to find in Central Administration the following: Replace each instance of AdminVsAppPoolIdentity in the query with the account that is the SharePoint Central Administration virtual server application pool identity. This account is also the database owner (dbo) of the database. Replace each instance of ContentVsAppPoolIdentity in the query with the account that is the content virtual server application pool identity. http://support.microsoft.com/default.aspx/kb/888041Where do I find the AdminVsAppPoolIdentity and ContentVsAppPoolIdentity ??
February 23rd, 2010 11:14pm

Karla Ponce,Thank you for responding. To answer you:You already have sharepoint installed on the server as well as a Web appplication instance right? ---YES On the IIS, both central admin and you web application, are running in two different IIS web sites. --- YES The problem started when I started working before my 1st cup of coffee one morning and someone requested a new site to be added to our Sharepoint site (all internal). I added a site but realized that I needed to add a document site instead, so I went to delete the site, instead, I am sure you can figure out where I am going, I deleted the whole site. I did not have a backup thru Central Administration but I did have a backup of the Sharepoint database using my nightly backup process. I restored it, finally. Now the problem is, when I go to add a user to a site, under site actions, site settings, advance permissions, it comes up and says ErrorUnknown Error Troubleshoot issues with Windows SharePoint Services. I also noticed that there are no authentication providers under:1: Launch Central Administration2: Go to Application Managementand in the Application Security sectionAuthentication ProvidersSomeone replied to the posting that I posted ( http://social.msdn.microsoft.com/Forums/en-US/sharepointadmin/thread/42a61f98-4e47-494b-b813-723ac4aa4935) with the below solution.In summary - since you want to start over and create a new web application using the same name you want to delete the existing web application so yes you should delete the IIS websites.Make sure that you have documented specific information concerning the web application you are going to delete, so that when you create it its easier.Make sure you read this topic and understand the nature of the delete a web application. Do NOT delete the content databases.---------------------That brings me to the question that I posted from the http://support.microsoft.com/default.aspx/kb/888041
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2010 1:52am

Robspwing,You should be able to get the accounts if you go to IIS manager (Start >run > type inetmgr). Under application pools, right click on the application pool for Central administration and select the identity tab. If you want to know the app pool ur central admin is running under, you need to right click on the IIS website and in the general tab u should be able to see the app pool.However, looking at ur problem descruition and if I understand correctly, just detaching the old content database and reattaching the new one it to SharePoint should do the trick for you. You can do so from the Central Admin under content databases. Give it a try and let me know if this works.
February 24th, 2010 11:11pm

The first part in the article states if you need to add the service account to the existing database. In your case since it is the same database, you should be good by skipping the first part.
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2010 12:56am

I am not sure what caused the authentication providers to disappear unless you did a restore of the config database which caused this issue.
February 25th, 2010 8:26pm

Here is the error that I get.Attaching this database requires upgrade, which could time out the browser session. You must use the STSADM command 'addcontentdb' to attach this database
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2010 10:32pm

Try this command Stsadm -o addcontentdb -url <URL name> -databasename <database name>
February 27th, 2010 12:13am

When I try to add the content database back thru Central Administration, Application Management, Add Content Database: This is what I receive:The attach operation cannot continue because another object in this farm already contains the same ID. Each object in a farm must have a unique ID. In order to proceed with the attach operation you must assign a new ID to this database. To attach this database with a new ID, use the "stsadm.exe -o addcontentdb" operation with the -assignnewdatabaseid parameter. Note that if this new database and an existing database contain the same site collections, attaching this database will likely result in orphaned site collections due to conflicts between the two databases.
Free Windows Admin Tool Kit Click here and download it now
February 27th, 2010 12:33am

Are you sure that http://server1 is the url of your web application to which the content db will be attached? - normally we go to http://server1 and the sharepoint site comes up for the end userBefore adding the content database, did you delete the existing db as estated in step number 3? - yes
February 27th, 2010 6:44am

@VikSrini Hope I'm not too late. If you're having SQL server on the same box as SharePoint 2010 (single-server deployment), the problem can be that server's loopback check. I've written about this here: http://www.sharepointboris.net/2009/12/unable-to-authenticate-crawl-errors-on-moss-on-windows-server-2008/ It is regarding other problem, but this solution helped me also when upgrading. Read more about SharePoint...
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2010 8:06am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics