27 lug 2010

Unable to reinstall Intranet Sharepoint Database Engine on SBS 2003

During last Week I needed to reinstall our intranet "companyweb".  We have followed the kb 829114 and we have removed it succesfully.
Now, when I reinstall the intranet the SQL instance MSSQL$SHAREPOINT was not created and the folder not exist.
Microsoft SharePoint Administration seems works fine.
Companyweb Web Site and Companyweb folder in c:\Inetpub was created but are empty.
Only the database instance won't install itself.  How do I do to force the MSSQL$SHAREPOINT instance? 

In particular:

1. After installation using sbs 2003 setup the errorlog.txt contains:
[07/25/10,13:29:33] Server Configuration: [2] Admin: Couldn't get group container for [LDAP://CN=Internet Users,OU=Security Groups,OU=MyBusiness,DC=xxxx,DC=local]
[07/25/10,13:29:33] Server Configuration: [2] Admin: Couldn't get group container for [LDAP://CN=Internet Users,OU=Security Groups,OU=MyBusiness,DC=xxxx,DC=local]
[07/25/10,13:29:34] Server Configuration: [2] Admin: Couldn't get group container for [LDAP://CN=Internet Users,OU=Security Groups,OU=MyBusiness,DC=xxxx,DC=local]
[07/25/10,13:29:34] Server Configuration: [2] Admin: Couldn't get group container for [LDAP://CN=Internet Users,OU=Security Groups,OU=MyBusiness,DC=xxxx,DC=local]
[07/25/10,13:31:12] Intranet: [2] HrRegisterFaxRtExt failed in CClientX::DoInstall hr=  [80070057]
[07/25/10,13:31:56] Intranet: [2] Failed to grant db rights to sts worker
[07/25/10,13:31:57] Intranet: [2] Unable to Join the SharePoint Administrators Group to the STS_WPG Group with error 0x80004005.
[07/25/10,13:33:34] User Interface Wizard: [2] ISetupManager::GetGlobalCustomProperty() failed in CPageBase::GetGlobalProperty(): GUID = {63ECC03C-3D58-4074-903D-E80CFC5BDC25}

2. The folder C:\Inetpub\companyweb has been created but is empty.

3. Microsoft SQL Server Desktop Engine (Sharepoint) not appear in currently installed programs list

4. From Eventlog.txt

5/10,13:31:20] Server Configuration: CSuiteHelpComponentRoot::isSharePointUsingWMSDE setting the location of the cursor service.
[07/25/10,13:31:20] Server Configuration: CSuiteHelpComponentRoot::isSharePointUsingWMSDE opening the connection
[07/25/10,13:31:36] Server Configuration: CSuiteHelpComponentRoot::isSharePointUsingWMSDE Failed to get the computer name of the local machine.
[07/25/10,13:31:36] Server Configuration: Either: SharePoint is not installed or SharePoint is not currently being installed or SharePoint has been upgraded to full SQL or the SharePoint SP4 setup.exe already exists. Will not copy WMSDE SP4 Files to the disk
[07/25/10,13:31:37] Setup.exe: ISetupManager::RunInstallFromList(IP_INSTALL) completed
[07/25/10,13:31:37] Intranet: **************Entering ClientX PostInstall *****************
[07/25/10,13:31:37] Intranet: Entering PostInstall
[07/25/10,13:31:37] Intranet: CClientX::DoInstall, fax server is installed or being installed.
[07/25/10,13:31:37] Intranet: CClientX::DoInstall, Exchange is installed or being installed.
[07/25/10,13:31:40] Intranet: CClientX::HrRunSTSProvisionExe succeeded.
[07/25/10,13:31:56] Intranet: ***ERRORLOG EVENT*** : Failed to grant db rights to sts worker
[07/25/10,13:31:57] Intranet: ***ERRORLOG EVENT*** : Unable to Join the SharePoint Administrators Group to the STS_WPG Group with error 0x80004005.
[07/25/10,13:31:57] Intranet: ClientX Install: PostInstall succeeded.



5. On IIS Companyweb has been created but is empty and than SharePoint Central Administration is not present also Apllication Pool StsAdminAppPool is not present and finally none Windows SharePoint Services Web Extension.

Considerations:

When the Windows SharePoint Service 3.0 (WSS) installation begins, it does 2 things:

1. Install "SharePoint Central Administration" (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\template\admin\1033)
2. Install MSSQL$SharePoint.

The process is logged in 3 SharePoint setup MSI files in the %temp% folder:

#1. Microsoft Windows SharePoint Services 2.0 Setup(000n).txt
#2. Microsoft Windows SharePoint Services 2.0 Setup(000n)_Task(0001).txt
#3. Microsoft Windows SharePoint Services 2.0 Setup(000n)_Task(0002).txt

In the filename, the number that appears in parentheses after Setup is a number that corresponds with an attempt to install the Intranet component or WSS. For example, if you try to install the Intranet component four times unsuccessfully, four versions of this log file will appear with Setup numbers ranging from Setup(001) to Setup(004).

#1 is the summary of #2 and #3.
#2 is the setup log for "SharePoint Central Administration"
#3 is the setup log for MSSQL$SharePoint.

When you open #2, go all the way to the bottom, a successfully install will say: 
MSI (s) (70:44) [01:19:55:606]: Product: Microsoft Windows SharePoint Services 2.0 -- Installation operation completed successfully.

When you open #3, go all the way to the bottom, a successfully install will say:
MSI (s) (70:FC) [01:21:28:860]: Product: Microsoft SQL Server Desktop Engine -- Installation operation completed successfully.

If it's anything other than "Installation operation completed successfully", then we need to troubleshoot that based on that specific MSI log. Most of the time, we are failing on #3 - MSSQL$SharePoint portion, and that's what we are dealing with now.  

Solution adopted:

1.  Remove Intranet by KB 829114
2.  Remove Monitoring
3.  Manually remove a Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) instance
4.  Rename Default SQL Server instance directory and clean/delete Registry from Reg key related.
5. Reinstall Intranet and Monitoring by SBS integrated setup

Reference:
How to remove and how to install the Windows Small Business Server 2003 SharePoint Services 2.0 companyweb Web site

How to back up and restore http://companyweb data in Windows Small Business Server 2003

How to restore a Windows SharePoint Services 2.0 CompanyWeb database after the intranet component and SQL Server or MSDE 2000 have been removed on Windows Small Business Server

How to perform a disaster recovery operation of Windows SharePoint Services 2.0 Companyweb and Windows SharePoint Services 2.0 databases


2 commenti:

  1. Great article as I have the same issue, would you be available to do paid remote support to solve a similar problem on my server?How can
    I contact you?

    RispondiElimina
  2. Hi,
    Thank you for your interesting.
    You can write an email to my company.
    My company is in italy and can only manages the clients that reside in the UE.
    http://www.iquad.it

    RispondiElimina