RE: "companyweb" not working since Windows Server 2003 Sp2 installed



Hello Dwayne,

Thank you for posting here.

From your post, I understand that when attempting to reinstall intranet, an
error is encountered.

If the issue is urgent to your business, it is recommended that you contact
Microsoft Customer Support Services (CSS) via telephone so that a dedicated
Support Professional can assist you recover the server in a more efficient
manner. Please be advised that contacting phone support will be a charged
call.

For a complete list of Microsoft Customer Support Services phone numbers
and information about support costs, visit the following Microsoft Web
site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

To continue working in the newsgroups, please see the following:

In order to narrow down this issue, please perform the following steps to
manually remove and install intranet:

A. Rename the registry keys and folders:
--------------
1. Rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer

2. Rename Program Files\Microsoft Integration\Windows Small Business Server
2003

3. Rename Program Files\Microsoft Windows Small Business Server

B. Once we rename the registry keys and folders, SBS setup is going to be
running like the first time.
--------------
1. Insert SBS setup CD 1, and then run setupsbs.exe to rerun the setup.

2. In the 'Component Selection' page, make sure 'Server Tools' and all the
sub-components (including 'Intranet') are selected to INSTALL.

3. Once it is completed, click Start, click Control Panel, and then click
Add or Remove Programs.

4. Select Windows Small Business Server 2003 and then click Change/Remove.
The Setup Wizard appears.

5. Click Next to start the wizard.

6. On the Windows Configuration page, click Next.

7. On the Component Selection page, in the Action column, change Server
Tools to Maintenance, change Intranet component to Remove, and then click
Next.

8. On the Component Summary page, click Next.

9. Click Finish.

10. 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.

C. 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 FrontPage Server Extension 2002 which is installed on the
Default WebSite. If you see additional "Port /LM/W3SVC/X:", backup and then
remove them)

D. 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 Antivirus 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.

3. Delete Application Pool

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

E. Rename Folders:
--------------
1. Rename C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT

2. Rename C:\Inetpub\companyweb

NOTE: Location of the MSSQL$SHAREPOINT folder is determined by

HKLM\Software\Microsoft\SmallBusinessServer\Monitoring\MSDE_Location. Check
out this registry key and determine the real location of the folder.

F. Clear the contents of the %temp% folder. If you are not able to clear
the contents then reboot the server or reboot into safe mode. Other
contents to clear would be in the c:\program files\Microsoft
Integration\Windows Small Business Server 2003\Logs everything inside of
the Logs folder.

Then do the following steps.

G. 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.

H. If the Installation still fails, apply the patch located at:

http://www.microsoft.com/downloads/details.aspx?FamilyId=CB7E90A1-DE9D-4A83-
85F8-951E9F055BF0&displaylang=en

I. If companyweb still doesn't work, open up a command prompt and navigate
to the directory 'C:\Program Files\Microsoft Windows Small Business
Server\Client Experience\Provision', and then run the following commands:

Note: It may take several minutes for this installation to complete; it is
a silent command. You can bring up task manager and look at the process
graph, when it stabilizes, it should be done.

stsprovision -path C:\Program Files\Microsoft Windows Small Business
Server\Client Experience\Provision -oeminstall -exch

stsprovision -path C:\Program Files\Microsoft Windows Small Business
Server\Client Experience\Provision -install -exch

J. Please also note that, if you have installed SBS SP1, you will receive
the following message after you insert SBS Disc 3:

"The drive contains a disc for Windows Small Business Server 2003 with no
service packs. When the prompt appears, insert a disc for Windows Small
Business Server 2003 with Service Pack 1."

Since Disc 3 for SBS SP1 doesn't include the Monitoring/Companyweb part,
the installation cannot proceed.

We'll then use the steps below to work around this problem:

1. Start a cmd prompt and change directory to the SP1 download folder (or
the SBS03_SP1 folder on PKG_CD2).

2. Type "SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and
press Enter.

3. Specifying a path for the extracted files (such as C:\SBSSP1)

4. Run the SBS Integrated setup, and when the setup program prompts for the
CD3, point it to the folder created above.

In addition, this issue can be caused by that SBS SP1 is not installed
properly. Let's perform following steps to check it:

On the SBS server, click Start, click Run, type "regedit" (without the
quotation marks) and click OK. Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer, and check the
data of the registry value ServicePackNumber. Is it set to "1"? If not,
then this problem will occur because SBS 2003 SP1 has not been completely
installed. To successfully install SBS 2003 SP1, we must install all five
updates listed below. Additionally, the updates must be installed in the
sequence listed.

Downloading and Installing Windows Small Business Server 2003 Service Pack 1
http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0
b3fc3/ToDownLoadFilesandReadInstructions.htm

If it does not work, please help me gather following information:

1. Send all the logs from the C:\Program Files\Microsoft Windows Small
Business Server\Support folder to my mailbox v-mzhuan@xxxxxxxxxxxxxx

2. Send all the logs from C:\Program Files\Microsoft Integration\Windows
Small Business Server 2003\Logs to my mailbox (you can zip them to make the
email smaller).

3. Sharepoint Error Log: %programfiles%\Microsoft SQL
Server\MSSQL$Sharepoint\LOG\errorlog.

4. Please help me capture screenshots of all error messages you
encountered and send them to v-mzhuan@xxxxxxxxxxxxxx

To capture the image, we can perform the steps below:

(a) When the error message appears, press the Print Screen key several
times (this key is located to the right of the F12 key on the keyboard)

(b) Open Paint ['start' => 'All Programs' => 'Accessories' => 'Paint'].

(c) Click Edit (menu) -> Paste or press Ctrl + V.

(d) Click File (menu) -> Save. Save it as a .jpg or .gif file and send it
to me as an attachment.

5. Setup MPS Report

1) Please download the MPSRPT_SETUPPerf.EXE from the following link and
then run this tool to gather some information from the problematic computer:
http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f-
88b7-f9c79b7306c0&displaylang=en

2) Double-click on the MPSRPT_SETUPPerf.EXE file.

[Note] This process may take some time; however, it will not have a
negative effect on the performance.

3) A CAB file will be generated in the
%systemroot%\MPSReports\Setup\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.

Best regards,

Manfred Zhuang(MSFT)
Microsoft 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: "companyweb" not working since Windows Server 2003 Sp2
installed
| thread-index: AcfvXNlvZpq4zMs1T7ey7M5XzZsf5g==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?RHdheW5lIEtlbGx5?= <DwayneKelly@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: "companyweb" not working since Windows Server 2003 Sp2 installed
| Date: Tue, 4 Sep 2007 18:34:06 -0700
| Lines: 68
| Message-ID: <229897BC-C607-4A95-BE66-ECA4DBD35A09@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.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:60833
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hey, I'm at a loss with this one so pls help. I recently tried to
| uninstall/reinstall the companyweb website as per Kb829114 and the
intranet
| install fails no matter if I start it from the original CD or from
Add/remove
| programs. The error log shows the following:
|
| [09/04/07,21:16:34] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {63ECC03C-3D58-4074-903D-E80CFC5BDC25}
| [09/04/07,22:41:29] : [2] Clean type install detected but file call
returned
| an error.
| [09/04/07,22:41:29] : [2] Failed to read the Bobcat PID from file.
| [09/04/07,22:41:36] : [2] Clean type install detected but file call
returned
| an error.
| [09/04/07,22:41:36] : [2] Failed to read the Bobcat PID from file.
| [09/04/07,22:41:37] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {F205AE18-9D39-4E3C-A4BA-12FBA060ED91}
| [09/04/07,22:41:40] Licensing: [2] Copying sbsmor.chm failed (error = 5).
| Check for the file in %winroot%\help directory.
| [09/04/07,22:41:40] Licensing: [2] Copying sbslic.chm failed (error = 5).
| Check for the file in %winroot%\help directory.
| [09/04/07,22:41:41] Licensing: [2] Copying sbsart.chm failed (error = 5).
| Check for the file in %winroot%\help directory.
| [09/04/07,22:41:41] Licensing: [2] Copying sbsshared.chm failed (error =
5).
| Check for the file in %winroot%\help directory.
| [09/04/07,22:41:43] Licensing: [2] FindLinkByTarget failed to find the
| licensing link with error [-2147024894].
| [09/04/07,22:41:44] Licensing: [2] UpdateLinkPath failed to update the
| licensing link with error [-2147024893].
| [09/04/07,22:41:47] : [2] Clean type install detected but file call
returned
| an error.
| [09/04/07,22:41:47] : [2] Failed to read the Bobcat PID from file.
| [09/04/07,22:41:50] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {FBCCE6F3-9E2D-464D-A4E7-12FBFD515395}
| [09/04/07,22:41:50] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {FBCCE6F3-9E2D-464D-A4E7-12FBFD515395}
| [09/04/07,22:41:55] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {FBCCE6F3-9E2D-464D-A4E7-12FBFD515395}
| [09/04/07,22:41:57] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {FBCCE6F3-9E2D-464D-A4E7-12FBFD515395}
| [09/04/07,22:42:00] WizardUI: [2]
ISetupManager::GetGlobalCustomProperty()
| failed in CPageBase::GetGlobalProperty(): GUID =
| {F205AE18-9D39-4E3C-A4BA-12FBA060ED91}
| [09/04/07,22:42:22] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=taxonwheels,DC=local]
| [09/04/07,22:42:22] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=taxonwheels,DC=local]
| [09/04/07,22:42:23] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=taxonwheels,DC=local]
| [09/04/07,22:42:23] Server Configuration: [2] Admin: Couldn't get group
| container for [LDAP://CN=Internet Users,OU=Security
| Groups,OU=MyBusiness,DC=taxonwheels,DC=local]
| [09/04/07,22:43:35] Intranet: [2] Admin: HrInstallSTS failed w/ error [0]
| [09/04/07,22:43:35] Intranet: [2] HrInstallSTS failed in
CClientX::DoInstall
| . hr= [80004005]
| [09/04/07,22:43:35] Intranet: [2] CClientX::HrInstallSTS, CreateProcess
| failed.
|
| Feedback and solutions would be greatly appreciated.
|
| Tks...
|

.



Relevant Pages

  • Re: after installing KB011829 OWA is not working anymore
    ... Windows Vista or IE 7.0 no longer includes support for the ActiveX control ... The resolution for this issue is to install hotfix KB 911829. ... and to the back-end server. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.exchange.connectivity)
  • Re: Fax on Terminal Server from SBS2K3
    ... > activity logging in the shared fax in the server box. ... Event Source: Microsoft Fax ... For Microsoft newsgroup user, please do not hesitate to contact ... Follow the wizard to install ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS SP1 Install Fails
    ... Windows Small Business Server 2003 Service Pack 1 ... You may need to closely follow the document to install SBS SP1: ... Microsoft CSS Online Newsgroup Support ... | Component Name: Server Configuration ...
    (microsoft.public.windows.server.sbs)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: cant connect to TS after install sp1 on SBS
    ... Please take you time to install ISA 2004, if you have any update, please ... Microsoft CSS Online Newsgroup Support ... Try to logon the Terminal Server with another account, ... <on our SBS server we can't connect to our terminalserver anymore via ...
    (microsoft.public.windows.server.sbs)