RE: trouble installing companyweb

thanks for helping me with this. as i read the response from you, i realize
that i had made a couple of mistakes. probably the worst being that i had
gone ahead and patched the server before continuing with step 13 of KB884453.
so I have followed the steps from your post, I completely removed all of the
sbs components that I could, renaming folders and registry keys. i also found
another kb on how to clear an instance of msde, did this for both sharepoint
and sbsmonitoring. removed all patches. removed IIS. and attempted the
install again. I ended up in basicly the same spot.
I decided to forfeit the game at that point. removed all sbs using
add/remove programs. transferred GC, fsmo roles and licensing back to the old
server. I then gracefully removed it from the domain and rebuilt from
scratch.
so here I am running KB884453 to the letter this time. as I start on
step 13 with the sbs install, I get a couple of new errors. 1.more than 2
processors - i know this one can bve safely ignored and i have been getting
it all along, just wanted to be accurate. 2.your paging file may be
insufficient - it is a default 2gb to 4gb variable page file on the C drive.
3.the directory services restore password will be syncronized... - also
completely normal, i know. and 4. you must ensure that additional domain
controllers running 2000 server meet basic requirements. this one had me
worried, checked the old server, it is at SP3, oops. should i apply sp4 on
that now or can i continue with it at SP3. the server will be going away very
soon. i had never gotten this error before so i never noticed the SP missing.
the kb does not specify. i will try to wait for your response and thanks
again for helping on this holiday.



"Terence Liu [MSFT]" wrote:

Hello Bill,

Thank you for posting here. Let's also thank Claus for the input.

According to your description, I understand that you get error when you do
the SBS integrated of Networking and Intranet. If I have misunderstood the
problem, please don't hesitate to let me know.

Claus's questions are good to narrow down this issue. Please let's know the
answers of them.

Based on my research, this is a complex issue, it may cause long time to
troubleshooting. I suggest we try the following steps to see if we can
resolve this issue:

Step 1: Please ensure you perform the steps in the kb884453 properly.
Properly transfer the FSMO roles to the SBS 2003 computer, properly change
the DNS settings on all domain controllers to point to the new SBS 2003
computer as the primary DNS server. The FSMO roles or the DNS settings
improperly settings may related to this integrated installation issue.

Step 2: After you finish the steps in kb884453, you need to perform the
integrated Setup of SBS 2003 immediately. Please do not do any update or
install any 3rd-party software before you finish the installation.

On the SBS 2003 computer, insert the SBS 2003 CD 1 into the CD or DVD drive
and continue with the integrated Setup of SBS 2003 and its components

Step 3: Please try reinstall the companyweb thru the following KB to see if
it help:

How to perform a disaster recovery operation of SharePoint Services
Companyweb and SharePoint Services Databases
http://support.microsoft.com/?id=827701

Step 4: This issue may caused by the some DLLs do not register properly
when the installation. Please perform the following steps:

Note: Please make a complete backup before you continue.

1. Rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
2. Rename Program Files\Microsoft Integration\Windows Small Business Server
2003 (If you are in the middle of RC to RTM upgrade, rename Program
Files\Microsoft Integration\Windows Small Business Server 2003\Release
Candidiate instead)
3. Rename Program Files\Microsoft Windows Small Business Server
4. Verify Program Files\Windows for Small Business Server exists on the
server. If not, you need to send him a copy of the folder from your SBS
2003 server. (Or you can manually rebuild the files from CD1\Setup\i386)
5. Once the Windows for Small Business Server folder is recreated register
the following dll's using Regsvr32:
a. Program Files\Windows for Small Business
Server\Administration\wizchain.dll.
b. Program Files\Windows for Small Business Server\Licensing\actwizdll.dll,
ckupwizdll.dll, licdlgctrl.dll and sbslicsnap.dll
c. Program Files\Windows for Small Business Server\Monitoring\mssbsmsgs.dll
6. Rerun SBS setup to reinstall all the Networking tools.

Note: Once we rename the registry keys and folders, SBS setup is going to
be running like the first time except it won't run DCPROMO again. (i.e AD
will still be the same)

For the failed intranet component

Uninstall the intranet component
1. Click Start, click Control Panel, and then click Add or Remove Programs.
2. Select Windows Small Business Server 2003 and then click Change/Remove.
The Setup Wizard appears.
3. Click Next to start the wizard.
4. On the Windows Configuration page, click Next.
5. On the Component Selection page, in the Action column, change Server
Tools to Maintenance, change Intranet component to Remove, and then click
Next.
6. On the Component Summary page, click Next.
7. Click Finish.

Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT)
In Add or Remove Programs, select Microsoft SQL Server Desktop Engine
(SHAREPOINT) and then click Remove. A dialog box appears. To confirm that
you want to remove, click Yes.

Delete Registry Keys
1. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet
2. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SHAREPOINT
3. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
Extensions\Ports\Port /LM/W3SVC/4: (Do not delete "Port /LM/W3SVC/1:"
because it is FronPage Server Extension 2002 which is installed on the
Default WebSite. If you
see additional "Port /LM/W3SVC/X:", backup and then remove them)

Delete IIS Virtual Directory
1. Delete SharePoint Central Administration (Do Not Delete Microsoft
SharePoint Administration. It belongs to FronPage Server Extension)
2. Delete Companyweb

Note: If AV software install any extra IIS virtual directory, also remove
them if possible. They sometimes use port 8081 which will conflict with our
SharePoint Central Administration virtual directory. Delete Application Pool

There should be only 4 application pools (DefaultAppPool,
ExchangeApplicationPool, ExchangeMobileBrowseApplicationPool, and
MSSharePointAppPool). Besides those 4,
delete all the extra.

Rename Folders
Rename C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT
Rename C:\Inetpub\companyweb

Install the intranet component
1. In Add or Remove Programs, select Windows Small Business Server 2003 and
then click Change/Remove. The Setup Wizard appears.
2. Click Next.
3. On the Windows Configuration page, click Next.
4. On the Component Selection page, in the Action column, change Server
Tools to Maintenance, change Intranet component to Install, and then click
Next.
5. On the Logon Information page, click Next.
6. On the Component Summary page, click Next.
7. Click Finish.

If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

Please gather and send all log files in the folder C:\Program
Files\Microsoft Integration\Windows Small Business Server 2003\Logs\ to me
at v-terliu@xxxxxxxxxxxxx

I hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: trouble installing companyweb
| thread-index: AcgscWqyx/QYqoDkSxaD+4SoxbedWg==
| X-WBNR-Posting-Host: 207.46.193.207
| From: =?Utf-8?B?YmlsbA==?= <bill@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: trouble installing companyweb
| Date: Wed, 21 Nov 2007 11:05:01 -0800
| Lines: 135
| Message-ID: <6E846B3D-15DC-452F-9E47-C721D6F7847B@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:77375
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| background: domain has a 2000 DC, adding an SBS 2003 to it using
kb884453. I
| cannot get Networking or Intranet components to install. I have compared
the
| groups like sts_wpg and sharepoint administrators to a known good SBS.
also
| gave rights to log on as a service etc. to network service and local
serivce,
| there are several other rights assigned to these, based off of a working
sbs.
| I have followed KB829114 many times, with mostly the same results. for
the
| networking component, i get " An error occurred while configuring the
| Microsoft Connector for POP3 Mailboxes. See C:\Program Files\Microsoft
| Integration\Windows Small Business Server 2003\Logs\Setup.log for
details.
| Rerun Setup and retry installing the connector." of course that log file
is
| useless. for the Intranet component, i get "An error occurred while
| installing Windows SharePoint Services and creating your intranet site."
and
| a final error of "MSDE 2000 Service Pack 4 did not install. For
additional
| instructions, see the SQL Server 2000 Service Pack Web site at
| http://go.microsoft.com/fwlink/?LinkId=46241."; I understand this one
since
| the databases are not running. here is more info on what I have now: in
IIS,
| I have 3 web sites, Default, Microsoft SharePoint Administration, and
| Sharepoint Central Administration(stopped). when i try to start this one,
i
| get Parameter incorrect. there is no StsAdminAppPool listed.
| C:\Inetpub\companyweb is completely empty.
| I renamed the errorlog.txt file and ran through the KB again, here is the
| contents of that file:
|
| [11/19/07,22:12:32] setup.exe: [2] ModuleID not found in map in
| GetSetupComponentByModuleID() -- [{DA943894-7A14-4FFF-BBDC-C004FAE2310B}]
| [11/19/07,22:12:32] setup.exe: [2] ModuleID not found in map in
| GetSetupComponentByModuleID() -- [{94B7AD3E-0B63-42AC-A542-082ED1F78787}]
| [11/19/07,22:12:32] setup.exe: [2] ModuleID not found in map in
| GetSetupComponentByModuleID() -- [{ECD1A63D-DBAF-442C-BF46-904364A96B00}]
| [11/19/07,22:21:53] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/19/07,22:36:10] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/19/07,22:38:36] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,10:57:57] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,11:35:23] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,11:39:07] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,11:40:49] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/19/07,22:12:32] setup.exe: [2] ModuleID not found in map in
| GetSetupComponentByModuleID() -- [{DA943894-7A14-4FFF-BBDC-C004FAE2310B}]
| [11/19/07,22:12:32] setup.exe: [2] ModuleID not found in map in
| GetSetupComponentByModuleID() -- [{94B7AD3E-0B63-42AC-A542-082ED1F78787}]
| [11/19/07,22:12:32] setup.exe: [2] ModuleID not found in map in
| GetSetupComponentByModuleID() -- [{ECD1A63D-DBAF-442C-BF46-904364A96B00}]
| [11/19/07,22:21:53] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/19/07,22:36:10] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/19/07,22:38:36] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,10:57:57] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,11:35:23] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,11:39:07] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,11:40:49] Intranet: [2] CClientX::InitializeModule found STS
not
| installed by SBS.
| [11/21/07,12:15:34] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {F205AE18-9D39-4E3C-A4BA-12FBA060ED91}
| [11/21/07,12:15:36] Licensing: [2] Failed to call
| UpdateMediaPackageRegistration() for Licensing with error [80070002].
| [11/21/07,12:15:37] Licensing: [2] FindLinkByTarget failed to find the
| licensing link with error [-2147024894].
| [11/21/07,12:15:37] Licensing: [2] UpdateLinkPath failed to update the
| licensing link with error [-2147024893].
| [11/21/07,12:15:40] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {FBCCE6F3-9E2D-464D-A4E7-12FBFD515395}
| [11/21/07,12:15:40] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {FBCCE6F3-9E2D-464D-A4E7-12FBFD515395}
| [11/21/07,12:15:43] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
.

Relevant Pages

  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • RE: Sharepoint Service, company web reinstallation
    ... Welcome to SBS newsgroup. ... I understand that you want to reinstall the companyweb on your SBS 2003 ... Business Server 2003 (If you are in the middle of RC to RTM upgrade, ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... slip stream SBS you would have had it ages ago. ... How did they buy this Server? ... My main reason for slipstreaming the install is because I cannot get the ...
    (microsoft.public.windows.server.sbs)