Re: Sharepoint re-install failure - FINAL RESULTS

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Cliff Corder (CliffCorder_at_discussions.microsoft.com)
Date: 08/26/04


Date: Thu, 26 Aug 2004 13:37:03 -0700

Hi Marina,

I have had two servers running Win2k server S1 and S2. We have a small
office and I wanted to use SBS2003 with Exchange to run our email. S1 is
currently our development server, domain controller, dinky email server, etc.
S2 is just and extra machine we recently acquired.

So the idea was to install SBS2003 on S2 and make it the domain controller
and email server. S1 would remain a development server. Since SBS must be the
head of the forest then S2 must be the head before upgrading. So I promoted
S2 and had it take control of the FSMO roles. Now it is the head. Then I
proceeded to upgrade S2 to SBS2003. During the installation of the Server
Tools, including Intranet, I received the error about "could not install
Intranet" that is addressed in MS article 832880. However, I don't get the
message about "you are not authorized to view this page." Instead, I have an
empty companyweb folder and get a 404 not found message when trying to go to
the CompanyWeb site. Various registry keys like Intranet and t he Port key
don't exist.

If I try to follow the steps to reinstall Intranet one of them says to go to
Add/Remove of SBS. Choose Maintenaince for Server Tools and Remove for
Intranet. In my case Intranet doesn't have a Remove option only an Install
option as it didn't install properly in the first place. I can't get anything
to work. It is all very frustrating. Does this help to make things clearer?

Thanks
Cliff

"Marina Roos [SBS-MVP]" wrote:

> Hi Cliff,
>
> Sorry, but this doesn't really make sense to me at all. Can you start from
> the beginning? Are you doing a fresh install or an upgrade?
>
> --
> Regards,
>
> Marina
> Microsoft SBS-MVP
>
> "Cliff Corder" <Cliff Corder@discussions.microsoft.com> schreef in bericht
> news:324549AB-1014-49F5-867A-591845E57EDE@microsoft.com...
> > This sounds great but I still can't seem to figure it all out. I
> currently
> > have no files in companyweb and the registry entries never seemed to have
> > installed with the failure of the Intranet install. In following these
> great
> > instructions I have a problem on step 1. If I disconnect the cables I get
> a
> > message that the SBS 2003 installer will not continue. If I plug it back
> in
> > and get to the Server Tools choice screen then there is no option to
> remove
> > Intranet. It never seems to fully install. I have never been able to get
> > companyweb to work from any source at all. I get 404 file not found
> messages.
> >
> > I started with a win2k server. I had it grab all of the domain
> > responsibilities so that SBS2003 would believe it was the first controller
> in
> > the domain. Then I went through the upgrade process. several things failed
> > during installation. The main one I was focused on was Exchange. I tried
> > various things and nothing worked. I had my othe 2k machine grab the
> domain
> > responsiblities. Then I wiped out the machine and reinstalled win2k. I
> > installed sql server2k and updated it to sp3a. Then had that machine grab
> > responsibilities. Then did the upgrade again. Things went a little better
> but
> > Exchange still didn't work. I finally found that if I did the exchange
> setup
> > with domainprep then it finally started working.
> >
> > So I was happy. Then I started looking at companyweb. That's where I am
> now
> > and nothing seems to fix it. I could go through the lengthy reformat and
> > install process all over again but it don't have any confidence that that
> > will do any good. Does anyone have any suggestions. Thank you.
> > Cliff
> >
> > "Curt" wrote:
> >
> > > Success - but not without a surprise
> > >
> > > Thank you all for your assistance and hints through this process. I was
> > > hoping for a method that would not require the re-installation of the
> > > intranet, and although it was not possible at this time I believe I
> > > found the culprit to this problem.
> > >
> > > The procedure I used was basically what Eric Sun and Marina Roos
> > > suggested with minor differences. Jeff, in my case the registry keys
> > > were restored through the process except that I had Port/LM/W3SVC/2 and
> > > Port/LM/W3SVC/3 which were deleted and didn't show up again.
> > > Port/LM/W3SVC/4 was recreated as well as all other keys and directories.
> > > There was a wwwroot\companyweb directory which was not recreated either.
> > >
> > > The procedure itself went without major surprises and had minor
> > > differences compared to KB829114. I listed what I did at the end of this
> > > message. The amazing part was what screwed it up again. I called
> > > Companyweb in the end and the standard home page came up without a
> > > problem. Afterwards I ran Windows Update which detected I needed
> > > KB829358, which is a patch supposed to solve interaction problems
> > > between Sharepoint services and its SQL database. To my surprise, after
> > > running the update, instead of getting the standard home page I was
> > > getting the page for the Default Web Site. Although I am using an
> > > updated disk 3, I ran KB832880 which didn't change anything.
> > >
> > > I than selected to reinstall the intranet (not uninstall & install, just
> > > reinstall without removing, deleting or renaming anything else) and it
> > > worked like a charm (the reinstall is what was failing originally). I
> > > noticed that the MSSQL$SHAREPOINT directory was the only one affected.
> > > The old one had a subdirectory called JOBS which is not in the new one.
> > > The new one has a subdirectory tree called headed BINN which was not in
> > > the old one.
> > >
> > > Also they both have a subdirectory called INSTALL. But while the new one
> > > has 35 files in it, the old one is empty. I believe the important
> > > difference is in the DATA subdirectory. Except for Msdbdata.mdf and
> > > Msdblog.ldf, all the other files were affected by the last procedure
> > > (reinstall). My conclusion is that this problem is being generated
> > > through SQL which is being corrupted by KB829358, which in turn is
> > > supposed to fix these problems. I would guess that simply renaming the
> > > MSSQL$SHAREPOINT directory and reinstalling Microsoft SQL Server Desktop
> > > Engine (SHAREPOINT) would solve the problem.
> > >
> > > I hope this helps someone else. Here is the revised procedure and thank
> > > you all again.
> > >
> > >
> > > Procedure: removing and installing sharepoint service
> > > Type: destructive
> > > Time required: about 80 minutes
> > > Requirements: updated W2003 disk 3 or old disk three (before Jan.
> > > 2004) and KB832880
> > > server must be taken off line
> > > Risk to other OS sections: small
> > > Recommendation: don't start it if you can't finish it in one sitting.
> > >
> > > 0:00
> > > 1 - Disconnect all server external connections like network cables and
> > > phone.
> > > 2 - Export the following Keys (shouldn't be necessary, but just in case)
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SHAREPOINT
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
> > > Extensions\Ports
> > >
> > > 0:05
> > > 3 - Start > Control Panel > Add/Remove Programs > Windows SBS 2003 >
> > > Change/Remove > Next > Next > Change Server Tools to maintenance and
> > > Intranet to remove > Next > Next > over 10 minutes later click Finish.
> > >
> > > 0:17
> > > 4 - Start > Control Panel > Add/Remove Programs > Microsoft SQL Server
> > > Desktop Engine (SHAREPOINT) > Remove > Yes.
> > >
> > > 0:20
> > > 5 - Delete the following Keys
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SHAREPOINT
> > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
> > > Extensions\Ports\Port /LM/W3SVC/X: where X is any number except for 1
> > > (i.e. do not delete Port /LM/W3SVC/1:) Delete also the corresponding
> > > string values.
> > > 6 - Confirm that SharePoint Central Administration and Companyweb
> > > virtual directories were deleted.
> > > 7 - Delete any application pools other than DefaultAppPool,
> > > ExchangeApplicationPool, ExchangeMobileBrowseApplicationPool,
> > > MSSharePointAppPool, and pools needed for other services like PBSAppPool
> > > if you installed the FTP service.
> > > 8 - Rename C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT and
> > > confirm that C:\Inetpub\companyweb was deleted.
> > >
> > > 0:25
> > > 9 - Reboot
> > >
> > > 0:35
> > > 9 - Start > Control Panel > Add/Remove Programs > Windows SBS 2003 >
> > > Change/Remove > Next > Next > Change Server Tools to maintenance and
> > > Intranet to install > Next > Next > over 10 minutes later click Finish.
> > > If the installation fails apply KB832880
> > >
> > > 0:47
> > > 10 - Reboot
> > >
> > > 0:57
> > > 11 - Confirm that Companyweb is now functioning correctly
> > > 12 - IExplorer > Tools > Windows Updates > Scan for Updates > Review and
> > > Install Updates > Install
> > > 13 - Reboot
> > >
> > > 0:67
> > > 14 - Confirm that Companyweb is not correct anymore.
> > > 15 - Start > Control Panel > Add/Remove Programs > Windows SBS 2003 >
> > > Change/Remove > Next > Next > Change Server Tools to maintenance and
> > > Intranet to install > Next > Next > over 10 minutes later click Finish.
> > > If the installation fails apply KB832880
> > >
> > > 0:73
> > > 16 - Reboot
> > >
> > > 0:83
> > > 17 - Confirm that Companyweb is now working correctly. Done
> > >
> > >
>
>
>



Relevant Pages

  • Re: REDIR.ASP file in use - access denied when installing Exchange 2003 SP1
    ... To resolve the problem i gave the 'Server Operators' group Full Control ... As soon as this was done the install worked fine. ... > Installation Instructions for Service Pack 1 for Windows Small Business ... What's the exact error message when you are installing the Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Blackberry and MS Exchange Administrator
    ... I understand that you want to install the Exchange ... System Manager components onto a server other than the SBS box. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 2003 and NT4 trusted domain
    ... > If you run Exchange 2003, you will need to install AD on at least on ... > use the server for Exchange. ... There would be no need to have a server at the remote ... There is a Linux box at each site ...
    (microsoft.public.exchange.admin)