Empty company web folder after Intranet reinstall

Discussion in 'Windows Small Business Server' started by EricS, Jan 11, 2005.

  1. EricS

    EricS Guest

    I have the updated disk 3 and I followed the steps in article 829114 to
    remove and reinstall the intranet. The setup reports an error at the end
    related to the sharepoint services intranet installation. The
    C:\inetpub\companyweb folder is emtpy. What is strange, is that if I stop the
    company web site in IIS, I can pull up a page on http://companyweb that saus
    Welcome to Windows Small Business Server 2003. If I start the site, then it
    gives me a virtual directory error when trying to browse it.
    How do I get the companyweb files back intact since the reinstall doesn't
    seem to do it? This is a fairly new install ofhte whole server so I don't
    have or really need and backups to restore. Thanks
     
    EricS, Jan 11, 2005
    #1
    1. Advertisements

  2. Try connecting to Windows Update to see if it detects that you need the
    832880 update. If so, install it and then see if companyweb is accessible.

    Chris Puckett, MCSE
    Microsoft Small Business Server Support


    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
     
    Chris Puckett [MSFT], Jan 11, 2005
    #2
    1. Advertisements

  3. EricS

    EricS Guest

    I think that update may be part of the problem. In my first attempts at
    fixing the companyweb problem, I saw recommendations to install the 832880
    update, however this update only applies to the older CD's that have an
    expired certificate, and I have verified that I don't have an older CD. So,
    maybe I made things worse by installing that update. I ended up removing the
    832880 update on my last attempt to remove and reinstall the Intranet
    component. The main problem seems to be that it is not installing the files
    to the company web folder. The RWW works just fine, and so does
    http://local:8081.
     
    EricS, Jan 12, 2005
    #3
  4. I understand that the 832880 update only applies to the older SBS CD 3.

    Despite the fact that you have verified that you have the newer CD 3, the
    symptoms of your issue are very similar
    to the ones resolved by the 832880 update. When you browse for updates on
    Windows Update (WU) from an SBS 2003 server, WU scans your system and uses
    some logic to determine whether or not you need the 832880 update.

    So, as a troubleshooting step I would like you to try connecting to Windows
    Update to see if it detects that your server is in the state where WU
    determines that you need the 832880 update. If it does determine that you
    need the update, install it and then see if companyweb is accessible.

    If it does not detect the need for 832880, then we can try some other
    troubleshooting steps.

    Thank you,

    Chris Puckett, MCSE
    Microsoft Small Business Server Support


    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
     
    Chris Puckett [MSFT], Jan 12, 2005
    #4
  5. EricS

    EricS Guest

    Hello Chris,
    I'm sorry to say that the SBS Setup routine for the Intranet component is
    far from bullet proof. I suspected that perhaps the C: drive on the machine
    was bad, so I replaced it and started with a fresh install of SBS 2003.
    The base setup of Windows went just fine. When running the SBS Setup, it got
    all the way through and then reported a warning setting up the Intranet
    component. The message was to create a test group in active directory and
    rerun setup. Well, I did that and was able to add a group no problem. I ran
    the setup again and chose to reinstall the Intranet component. It went
    through without errors.
    I was able to complete the internet wizard and it installed every updated
    except it fails on update 832880 no matter what I try. Lo and behold,
    companyweb still doesn't work and it appears as if the files and folders
    installed to the C:\inetpub\companyweb folder are incomplete. I get 'Access
    Forbidden' on the server, and 'Server Error in '/' Application' when trying
    to manage the site. Back to square one again...

    Today I received the quarterly update pacakge, which included new disks for
    SBS Std. My current install is Premium, but I think I will ditch that and
    start over with Std edition. I hope the new CDs corrects the problems on the
    new install. It's really frustrating to have a new product from Microsoft
    that just doesn't work out of the box, and then get solutions that just seem
    to make the problem worse and irreversible. The feature concept of companyweb
    is great...
     
    EricS, Jan 19, 2005
    #5
  6. just follow KB 829114 to reinstall companyweb, a format and reinstall of the
    OS is a bit overreactive.

    Use CD3 from your latest set, it doesn't matter that it is from Standard and
    the system is Premium.

    When doing 829114 this AM it failed. I uninstalled SQL Server and ran the
    procedure again, it worked.
     
    SuperGumby [SBS MVP], Jan 19, 2005
    #6
  7. EricS

    EricS Guest

    Hello SG,
    I was never able to get the steps in 829114 to correct the problem. I must
    have tried it at least a dozen times, and every time it got an error when
    installing the intranet component, and the companyweb folder was empty. Thus,
    my conclusion that the setup is flawed. I followed the steps in the article
    to the letter. I recall the steps mention removing sharepoint services, and
    sql server sharepoint, but they also say not to remove the sharepoint
    administration. It seems to me that completely removing sql server would
    remove the sharepoint admin, but if removing it is what worked for you, then
    KB article 829114 is wrong and it's no wonder that so many people can't get
    company web to work.
    The SBS setup is flawed because uninstalling and reinstalling the intranet
    is not removing and reloading all of the dependencies, and somehow this
    prevents it from doing a simple copy of files to a folder upon the
    installation. Anyhow, thanks for the suggestion..I'm hoping the new server
    install does the trick, but it it doesn't I'll try your workaround.
     
    EricS, Jan 19, 2005
    #7
  8. The KB does not reference SQL in any way and note: I'm talking SQL Server
    2000, not msde.

    Explicitly:
    I did not remove MS Sharepoint Administration.
    I did not remove MSSharePointAppPool.

    The KB article defines the correct procedure if you have not upgraded the
    sharepoint instance to SQL Server.

    NOTE: There is one additional step I performed before starting the
    reinstall. I restarted the server. IMHO many problems occur because people
    (even MS people) don't believe restarts are necessary. I've seen a man I
    consider technically more capable than I fight with a problem for several
    hours with me saying 'Will you just please restart the box' and he saying
    'it's not necessary', after restart the failing procedure worked.
     
    SuperGumby [SBS MVP], Jan 19, 2005
    #8
  9. what AD DNS domain name did you use?

     
    SuperGumby [SBS MVP], Jan 21, 2005
    #9
  10. Also, as a test, can you disable hyperthreading in the system BIOS.
    Then remove the Intranet component by following the steps in 829114.
    Then install the Intranet component using sbs setup.

    Chris Puckett, MCSE
    Microsoft Small Business Server Support


    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
     
    Chris Puckett [MSFT], Jan 21, 2005
    #10
  11. EricS

    EricS Guest

    Hello SG,
    The DNS name is eMarketFocus, making the domain name emarketfocus.local. Is
    that name too long or something?
    Also, I will try disabling the hyperthreading through the bios per Chris's
    suggestion.
     
    EricS, Jan 21, 2005
    #11
  12. kewl, namespace is not the issue then. It was a long shot anyway.
     
    SuperGumby [SBS MVP], Jan 21, 2005
    #12
  13. EricS

    EricS Guest

    Hello SG,
    Well, I finally had success! whew.
    I don't know what the silver bullet was, but I suspect it was the Hyper
    Threading. Here's what I did:
    1) Disabled hyperthreading in the bios
    2) Reinstalled OS again from scratch & re-formatted drive
    3) Installed device drivers
    4) Ran SBS setup. Completed no errors...first time for that.
    5) Ran Windows Updates.
    Companyweb folder is populated and the site even works. Very cool.
     
    EricS, Jan 22, 2005
    #13
  14. EricS

    EricS Guest

    Well, I finally had success! whew.
    I don't know what the silver bullet was, but I suspect it was the
    HyperThreading. Here's what I did:
    1) Disabled hyperthreading in the bios
    2) Reinstalled OS again from scratch & re-formatted drive
    3) Installed device drivers
    4) Ran SBS setup. Completed no errors...first time for that.
    5) Ran Windows Updates.
    Companyweb folder is populated and the site even works. Very cool.
    Now, previously when I ran SBS setup, I had already installed Windows
    Updates. I actually got the companyweb to work once before on my initial
    install of SBS a month ago, when I had also not installed Windows Updates
    before running SBS setup. The companyweb ran about a week on that install
    before it just stopped working and the problems began.
    SO, my question now becomes, should I just leave hyperthreading disabled?
    Does HT offer any advantages for an SBS server, or would I just be enabling
    something that SBS server won't use but might not be fully compatible with?
    Thanks again for your help...and I hope it helps development of the product
    somehow as well to know that HT may be an issue.
     
    EricS, Jan 22, 2005
    #14
  15. Ahhh. Eric, I think running WU before completing the setup, and running the
    CEICW from the TODO list is not a good idea. As soon as the CEICW is run,
    the server automatically goes to WU.

    I'm fairly certain slipping in updated files will upset the very tightly
    integrated SBS setup, which of course was written and tested with the
    existing file set of mid 2003.
     
    Les Connor [SBS Community Member - SBS MVP], Jan 22, 2005
    #15
  16. hmmm, odd, I don't think we've seen this cause grief before but as Les
    mentions completing the integrated setup then updating is the right
    approach.

    I'd now enable HT, SBS will use it and you should get a performance gain.

    <snip>
     
    SuperGumby [SBS MVP], Jan 22, 2005
    #16
  17. I've run accross similar issues before (in the newsgroup), not with
    hyperthreading - I think that was a red herring - but with difficulties
    encountered running WU between the OS install and the SBS setup.
     
    Les Connor [SBS Community Member - SBS MVP], Jan 22, 2005
    #17
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.