Re: SBS 2003 upgrade problems with RWW and CompanyWeb

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

OK, Steve,

I'm getting no where quickly.

Follow your steps in last email, but nothing has changed.

In Step B.7, intranet does not show installed in components.

C.1 key does not exist

C.3 key does not exist

D.1 Company web virtual server does not exist

D.3 Cannot delete application pool

After installation completes in a failed state, messages are the same
and event log messages are the same as previously referenced.

I'm also seeing near constant errors in the application log:

Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date: 11/21/2006
Time: 10:07:44 PM
User: N/A
Computer: JUPITER
Description:
#50070: Unable to connect to the database STS_Config on
JUPITER\SharePoint. Check the database connection information and make
sure that the database server is running.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



Please help!

Thanks,

Jay Poules




Steven Zhu [MSFT] wrote:
Hi Jay,

Thanks for your reply.

From your description, I understand that you get the following error
message:
===============================
Step 5. I have a pool listed as StsAppPool1 that I cannot delete.
Message is "You cannot delete an application pool that contains
applications. You need to reassign all applications in this application
pool to another application pool or delete the applications."
===============================

Please check Application Pools in IIS, refer to the following steps:

IIS Manager -> Server name -> Application Pools -> StsAppPool1

If the other web sites are using this application pool, then you cannot
delete it. According your reply, this issue may caused you don't follow the
step's order to perform reinstall SharePoint Service. So please refer to
the following step's ORDER to manually remove and install SharePoint and
CompanyWeb:

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.

Please let me know the result, I am looking forward to your reply.

Have a great day.

Best Regards,

Steven Zhu
MCSE/MCDBA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
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.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

.

Relevant Pages

  • Re: How do I fix OMA on SBS2003?
    ... Some of the earlier WM5 devices through Verizon & Sprint required you to run a special utility on the phone to install your self-signed cert successfully ... As far as OMA is concerned - I would double check to make sure it is using the same ASP.NET version as the other apps in whatever IIS Application Pool it is using. ... "Activesync encountered a problem on the server. ...
    (microsoft.public.windows.server.sbs)
  • w3wp.exe - Application Error (IIS 6, ASP.Net 2.0)
    ... I tried moving the application into a new pool, ... I can't reproduce the error. ... This error is happening on a new server with a clean install of Windows ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: SBS 2003 migration blues
    ... it seems you encountered problem when install the ... intranet components, for your issue, I suggest you refer to the suggestion ... Business Server 2003 (If you are in the middle of RC to RTM upgrade, ... Uninstall Microsoft SQL Server Desktop Engine. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharepoint re-install failure - FINAL RESULTS
    ... currently our development server, domain controller, dinky email server, etc. ... So the idea was to install SBS2003 on S2 and make it the domain controller ... Intranet" that is addressed in MS article 832880. ... The main one I was focused on was Exchange. ...
    (microsoft.public.windows.server.sbs)
  • Unable to reinstall Intranet component
    ... Server 2003 running on our SBS system and finally resorting to calling MS ... As we looked into what seemed to be causing the SP1 install to ... we realized that the broken monitoring and intranet components appeared ...
    (microsoft.public.windows.server.sbs)