Comments on: Moving or Renaming the WSS Central Administration Content Database http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/ insights from managing a microsoft enterprise infrastructure Thu, 11 Feb 2010 17:46:11 -0500 http://wordpress.org/?v=2.8.3 hourly 1 By: David http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-132 David Tue, 07 Apr 2009 20:10:33 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-132 This article just saved me from what could have been the worst day of my life, THANK YOU !!!!!!!!!!!!!!!!!!!!!! This article just saved me from what could have been the worst day of my life, THANK YOU !!!!!!!!!!!!!!!!!!!!!!

]]> By: Lou http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-113 Lou Thu, 26 Mar 2009 05:17:30 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-113 Wish i saw this before I deleted and had to reinstall. BTW if you have to force an uninstall check out this link. http://geekswithblogs.net/shehan/archive/2008/07/23/manually-uninstalling-wss.aspx Wish i saw this before I deleted and had to reinstall. BTW if you have to force an uninstall check out this link.

http://geekswithblogs.net/shehan/archive/2008/07/23/manually-uninstalling-wss.aspx

]]> By: Chandima.Net:Avoid those GUID database names | Rickey Whitworths Blog http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-108 Chandima.Net:Avoid those GUID database names | Rickey Whitworths Blog Tue, 24 Mar 2009 19:19:50 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-108 [...] Thanks to Chandima for this tip on how to avoid having GUIDs in your database names. I have a post here that details how to change the database name after the fact, but Chandima tells us how to avoid [...] [...] Thanks to Chandima for this tip on how to avoid having GUIDs in your database names. I have a post here that details how to change the database name after the fact, but Chandima tells us how to avoid [...]

]]> By: The Sean Blog http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-44 The Sean Blog Sat, 14 Mar 2009 18:43:25 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-44 <strong>Renaming crazy SharePoint Database Names...</strong> When SharePoint 2007 creates new Content Databases, by default it adds a GUID to the end of the database... Renaming crazy SharePoint Database Names…

When SharePoint 2007 creates new Content Databases, by default it adds a GUID to the end of the database…

]]> By: Aaron Wiggans http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-59 Aaron Wiggans Fri, 09 Nov 2007 14:28:12 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-59 That worked. Thank you so much for creating this blog. Very use full. That worked. Thank you so much for creating this blog. Very use full.

]]> By: Toby Statham http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-58 Toby Statham Thu, 13 Sep 2007 14:27:02 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-58 I have discovered a little gotcha which you may need to be aware of. You can only do this if the account you are logged onto the server is also the server farm accountThis account is also referred to as: Database access account, The application pool account for the SharePoint Central Administration Web site, The process account for the Windows SharePoint Services Timer serviceThe content database for Central administration stores all the users who are Farm Administrators using the standard Sharepoint groups. If you remove this content database it is unable to verify your account is a farm administrator and you get the "Access Denied" message.Not particulary useful if you are using a service account that has had "Logon" rights removed! I have discovered a little gotcha which you may need to be aware of. You can only do this if the account you are logged onto the server is also the server farm accountThis account is also referred to as: Database access account, The application pool account for the SharePoint Central Administration Web site, The process account for the Windows SharePoint Services Timer serviceThe content database for Central administration stores all the users who are Farm Administrators using the standard Sharepoint groups. If you remove this content database it is unable to verify your account is a farm administrator and you get the "Access Denied" message.Not particulary useful if you are using a service account that has had "Logon" rights removed!

]]> By: Vicente Sanchez http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-57 Vicente Sanchez Fri, 06 Apr 2007 14:26:15 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-57 Great post! Thanks for the tip.Toby Statham,I had the same error. The cause was that I try using the Admin UI to create the new content database. Then, I deleted the database with the hash in its name. Next, when I try to add the content database using the instructions above, I got the error.The solution is to run the deletecontentdb command for the STSADM.exe tool. This will remove the registration of the database in the config database. After doing this step, you can follow Rickey's instructions above.Hope this helps and the answer doesn't come to late. It took me a few minutes to realize what I had done to cause the error. Great post! Thanks for the tip.Toby Statham,I had the same error. The cause was that I try using the Admin UI to create the new content database. Then, I deleted the database with the hash in its name. Next, when I try to add the content database using the instructions above, I got the error.The solution is to run the deletecontentdb command for the STSADM.exe tool. This will remove the registration of the database in the config database. After doing this step, you can follow Rickey’s instructions above.Hope this helps and the answer doesn’t come to late. It took me a few minutes to realize what I had done to cause the error.

]]> By: Cornelius J. van Dyk http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-56 Cornelius J. van Dyk Fri, 30 Mar 2007 14:25:47 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-56 Great post!Thanks for the useful tip.LaterC Great post!Thanks for the useful tip.LaterC

]]> By: Toby Statham http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-55 Toby Statham Mon, 26 Feb 2007 14:25:12 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-55 Hi, I tried the above, but when I try to add the content db using stsadm I get the the following errorSharepoint_AdminContent on databaseserver contains user-defined schema. Databases must be empty before they can be used. Delete all of the tables, stored procedures and other objects or use a different database.Do you know how to resolve this?CheersToby Hi, I tried the above, but when I try to add the content db using stsadm I get the the following errorSharepoint_AdminContent on databaseserver contains user-defined schema. Databases must be empty before they can be used. Delete all of the tables, stored procedures and other objects or use a different database.Do you know how to resolve this?CheersToby

]]> By: BPA http://www.whitworth.org/2006/08/07/moving-or-renaming-the-wss-central-administration-content-database/comment-page-1/#comment-54 BPA Wed, 29 Nov 2006 14:24:44 +0000 http://www.whitworth.org/Blog/PermaLink,guid,fa4f11e2-221a-4321-a01e-cd466016d534.aspx#comment-54 Thanks for the post. I couldn't stand the naming convention used on this db either. Thanks for the post. I couldn’t stand the naming convention used on this db either.

]]>