Re: WSS Can't Extend New Web Sites Created In IIS



Thank you for being a most gracious host. Your generosity is
appreciated and of great value. I will pass it forward and hope it
comes back to you too.

Sincerly, Michael Angelo

Engelbert wrote:
Answering only the good check list (single server)

Windows 2003 Server (server edition or upwards)
Add Applications Server role specifying ASP.NET and not specifying FPSE
Install SQL Server 2K SP3a at least (seems to be easier to get to work even
though 2005 is faster) if you are planning to use that
Install WSS v2 from the download specifying web farm option (lower) if
planning to use the SQL server 2K copy otherwise default (which will install
WMSDE and you have no search functionality)
Get it working (it should come up automatically with the home page) and then
install WSS SP2.

-----------------

uninstall of WSS v2 and install will not save your sites ...

consider full disk backup including backup of databases; just backup of
databases; use of stsadm or use of smigrate; or a combination of all/most of
those before doing an uninstall. If you are having problems with the
existing installation probably smigrate (losing your authorizations and
customizations) might be the safest bet.

and with that I'm out. I'll leave it to someone else to come up with full
answers.

Engelbert

<angelo327@xxxxxxxxx> wrote in message
news:1155794844.216625.284530@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Starting Over. Well, I have another 2003 Box I could build WSS on. Do
you know a good check list for building from scratch?

I also could use my old STS DC and then smigrate to the 2003 server
This stuff isn't easy for those of us that don't eat, drink, and sleep
WSS.

I just don't see why IIS is stamping new sites with Version 5. If I
could blind WSS to the version number, it might just upgrade the newly
created site. Even the /forceupgrade failed.

Any suggestions short of killing my working server are appreciated.

Can I uninstall IIS and reinstall it. Or should I install frontpage
2002 extensions and then remove them in the hope IIS will stop stamping
Version 5 on new sites?

Is it possible to UNinstall WSS 2.0 and reinstall WSS 2.0 without
loosing all 12 existing web sites?

Thanks again.

Mike
www.mikeangelo.com (<my problem child) I should have taken up
professional Golf.

Engelbert wrote:
I see that in my IIS Web Service Extensions List
active server pages allowed
asp.net v1.1.4322 allowed

That's v1 - I just wanted to exclude ASP.NET 2.0 (it works but there are
issues connected to it).

I haven't any ideas on the other stuff except that your still having sts
(itself a superset of FPSE) is surely causing problems.

I don't suppose you could start again on a *really* clean machine ?

Engelbert


<angelo327@xxxxxxxxx> wrote in message
news:1155791245.749585.59770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for replying;

Clean Install: Yes The server was new hardware with 2003 server
enterprise edition and was a DC. I honestly don't remember if I was
asked to promote to DC before IIS installed. I can only say that most
of my sites were migrated from an older server that was in-place
upgraded to 2003. But I know I have created WSS V.6 sites on this box
from scratch.

I did spend qite a bit of time trying to get sts and wss to run
together on the same box. (Dumb).

The single server has 12 virtual sites (5 on the Internet) using host
headers. I have no problem creating sub webs in FP2003. This kind of
started after having no problems for over a year. I can't find any
trace of frontpage 2002 extensons, at liest in ad remove programs or in
windows setup.

Note that when I create the initial virtual site in IIS and go into WSS
Admin, it shows up as a version 5 site. This is of course the problem.
I wouldn't mind migrating the sts version 5 except we're talking about
a newly created site; so there is nothing to migrate.

ASP v1 ??? I don't know how to tell what verson of asp.net I'm using.
I see that in my IIS Web Service Extensions List
active server pages allowed
asp.net v1.1.4322 allowed

Engelbert wrote:
Was this a clean installation of 2003 Server when you started the
whole
WSS
installation process? (Thinking about bits of FPSE from previous
installations)

Did you specify the DC before IIS (this order is essential) ?

Did you - when in the Applications Server wizard (or IIS) - when not
specifying FPSE, specify ASP.NET support and was this v1) ?

Engelbert



<angelo327@xxxxxxxxx> wrote in message
news:1155760638.879324.79900@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Windows 2003 Server (DC) WSS 2.0
It's important to note here that (Frontpage Extensions 2002 ARE NOT
INSTALLED)

I create a site in IIS, the local path is C:\Inetpub\SampleSite,
then I
right click the new site and launch Sharepoint Central Admin to
extend
the new site. Note, I notice the site at this point is NOT Runing
and
won't start. Also, there are no files or folders in the \sampleSite
directory.

In Central Admin I have my new site listed:

VERSION
Default Web Site http://spserver/ 6.0.2.
6.0.2.6568
SampleSite http://www.samplesite.com
5.0.2.6738
Upgrade

Notice the Versions of the two sites thus far.
I click SampleSite to Upgrade and the process runs and ends with a
help
window telling me the following:

To upgrade your server to Microsoft Windows SharePoint Services, run
Setupsts.exe to manually upgrade. I do that but it fails with a
message that I need to remove FrontPage 2002 extensions. I have 8
WEBs
working just fine. I managed to create a site by scrapping an
existing
site I didn't need any more.

CAN ANYONE PLEASE HELP DIRECT ME TO A CURE!

Thank you.




.



Relevant Pages

  • Re: I hate IIS - "Server Application Unavailable" error message
    ... I would but there is not "Application Pools" underneath the local ... Did you install, at least, the Web or Standard versions of Windows Server 2003? ... except when you choose to install IIS on a domain controller. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: IIS Key pairs (how to export an IIS 4.0 self-issued Root CA a nd import into new IIS 4.0 box)
    ... IIS key to an Intel SSL acelerator ... it issues client certificates to the end users. ... Step I - Installing the New Server ... Install NT SP 3 ONLY ...
    (Focus-Microsoft)
  • RE: Internet printing
    ... Configuring the IPP Print Server: ... (IIS is synonymous with PWS, Peer Web Services, which is what ... -This will install and configure basic IIS on the current machine. ...
    (microsoft.public.windows.server.sbs)
  • Re: No DHCP in administrative tools
    ... OK, we need to install the DHCP service, but we're gonna hold of a mo' on ... In computer management, expand IIS, expand websites, which sites do you ... SQL Server Config ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA 403 Forbidden, POP3,
    ... Is there a way to just re-install the IIS components to a set of Default ... incorrect type of install of Trend not in a virtual directory was probably ... From your post, I understand you after you rebuild SBS Server, you ... Go to your "%SystemRoot%\IIS Temporary Compressed Files" ...
    (microsoft.public.windows.server.sbs)