Issue when trying to reinstall MOSS on a single server

Charles Lee
  • Issue when trying to reinstall MOSS on a single server Charles Lee

    I am not an expert on the installation of SharePoint, but I have been trying to configure the MOSS installation on one of our DEV servers.

    The first problem was found when trying to set up an SSP. The SSP was created OK but there was an issue with finding the SQL Report Viewer assemblies which are required to view the SSP admin pages.

    My environments team have kindly looked into this and decided to completely re-install MOSS on that box.

    I have tried to re-run the config wizard to hook this server up to the existing config database and to re-create the central admin site. However I now get a security exception when the config wizard is run.

    These are the relevant lines from the config wizards log file:

    • 05/05/2010 09:43:45 8 INF Creating connection string for admin content db SharePoint_AdminContent_1c2efc32-a7c8-4e97-93d6-447c3ea5cd29 server XXXXXXXX\lob

    • 05/05/2010 09:43:45 8 INF Using NTLM for sql connection string

    • 05/05/2010 09:43:45 8 INF Openning configdb so that I can join it at server XXXXXXXX\lob database XXX_SharePoint_Config in farm mode

    • 05/05/2010 09:43:45 8 INF Now joining to farm at server XXXXXXXX\lob database XXX_SharePoint_Config

    • 05/05/2010 09:43:47 8 ERR Task configdb has failed with an unknown exception

    • 05/05/2010 09:43:47 8 ERR Exception: System.Security.SecurityException: Access denied.

    The account that I am using as the central admin db access account has access to the config database (I have admin access so can check this) but I cannot ascertain if it has access to the existing admin content database.

    Is this a known problem? Am I following a red herring with the db access? Is it worth blowing the whole configuration away and starting again?

  • The solution was because the config wizard had originally been run by another user. I was trying to re-run it and my user account did not have appropriate access to the content database.

    I had to re-run the config wizard using the account of the user who had run it the first time. I suspect that any account with dbowner priviliges on the admin content database would have done the job though.

    Still got the report viewer issue though. I think that the SSP must need Report Viewer 2005 installed.

  • The required rights for the user accounts are public, dbcreator and securityadmin. No need to give him full dbowner rights.

    This blog post explains the difference in Report Viewer webparts:

installation configuration-wizard database 2007
Related questions and answers
  • the Central Admin app pool account can write to the config database But then we lose the whole point - I want my site collection administrators to be able to manage the schedule! The only alternative solution...I have run into a problem several times now where I have developed a custom timer job, and I want my site collection administrators to manage the schedule of this job with a custom application page but I keep running into security related obstacles. Since timerjobs are child objects of SPWebApplication, they are stored in the config database. If you have set up your farm properly in such a way

  • , we were lucky enough to still have the soon to be decommisioned server that previously ran Central Admin (Server1). So, I added the server to the farm. Removed the Central Admin from the new Server... that existed prior to the upgrade. This is also the case in a retract,delete,add,deploy scenario. Note: Our server topology has changed over time. Our Central Admin machine reached its End of Life, so we added another server to the farm, moved the central admin with the stsadm tool, and removed the old server from the farm. Here is what I have tried: Deployed to two other farms: successfully deployed

  • server are starting and are using the FARM account. The ILMMA and MOSS- folders are NOT present in %Programfiles%\Microsoft Office Servers \14.0\Synchronization Service\MaData. A similiar thread... attempting to start and run the UPS Sync) and eventually fails: Error ID: 22 - The Forefront Identity Manager Service cannot connect to the SQL Database Server. The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured

  • without any particular rights: SPF_DATABASE for database credentials SPF_ADMIN for farm credentials Added domain administrator in SQL Server 2008 R2 with sysadmin rights started Sharepoint Powershell as domain administrator (so I have rights to access domain accounts) I didn't install SQL Server 2008 KB 970315 x64, because I'm running R2 version - as I understand this is SQL Server 2008 SP2..." -AsPlainText -Force) When I run it, I'm prompted for database credentials and I enter mydomain\SPF_DATABASE and password I'm also prompted for farm credentials and I enter mydomain\SPF_ADMIN with password

  • My HOST PC is Windows 7 and using VirtualBox I have setup a Virtual Machine having: Windows 2008 Server R2 Enterprise (Standalone - there is no AD/DC) SQL Server 2008 R2 Express SharePoint 2010 Server Enterprise Trial Now, I want to install SPS 2010 and make use of the existing SQL Server 2008 R2 Express. During the Installation, I selected Server Farm and then Complete option. So far, so good. Next, it started PSConfig Wizard and asked me to specify the DB details. I provided the local Server Name and gave a New DB name. Now, it throws error saying that it needs a User ID in Domain

  • We have several WSS Servers: WSS1 WSS2 WSS3 WSS4 SharePoint thinks that Central Administration is on WSS3 and that it can be access via SSL on port 22641. The problem is that central administration is not there. It was removed using the config wizard. We removed central admin from all servers to clean everything out, and we tried installing Central Admin on WSS1. The alternate access mappings... servers and tried creating the Central Admin website on WSS3, where SharePoint already thinks it is. But for some reason SharePoint is creating the alternate access mappings using SSL, and we don't have

  • Service: Office SharePoint Server Search Issue: The search service is using an account assigned to the Farm Administrators group to crawl content for Shared Services Provider SharedServices2... Issue:Web Front End servers in the server farm are not consistent in the services they run. Impact:Users may have intermittent failures while trying to access Web pages in this server farm. Update...I have successfully configured a SharePoint farm of 4 nodes but I got intermittent database connection failure errors. I have to restart SharePoint services and IIS to fix the database errors. Mostly

  • . The Reporting Services URL has been set within Central Administration. When I fill in the "Grant Database Access" form with a user account and click OK, the following message displays: 'A connection...On a single Windows 2008 Server I'm running SharePoint 2007 Enterprise (SP2, December 2009 CU) and SQL Server 2005 (SP3, CU 7). Authentication is NTLM. I've been trying to get SharePoint Reporting... and SharePoint (as it is impossible to only uninstall the Reporting Services component with SQL Server 2005) used the same service account for all SQL services and the same for all SharePoint services given all

  • I have a new SharePoint 2010 server farm that I'm trying to configure. Installation went fine. But I'm having trouble getting the user profiles to import. I've created the User Profile service... trying to set up a connection to one of the child domains. The connection service account has been granted "Replicate Directory Changes" permission on both the root and the target child domain. Can... because the client side timeout limit was exceeded." In the SharePoint logs, when I filter based on the correlation ID, I get the following messages: Name=Request (POST:http://poc-bi-sp:8080/_layouts

Data information