Server Error in '/' Application.

Fellow SharePointers:

There have been a lot of posts regarding this error message and not a lot of
resolutions were identified in my experience. This is probably one of the
most annoying errors conditions because it is so easy to get to it if you use
some of the approved installation methods including in my case unattended
setup. To avoid this error condition you must complete the installation of
your server in the following order.

1. Initial setup.
2. Promote to Domain Controller
3. Then and only then install IIS
4. Install other software related to IIS such as SharePoint.

One of the reasons I chose to use unattended setup was that the manual,
granted it is wizard driven, setup method is time-consuming and tedious and
unattended setup really makes you think about what you do and do not want on
your server. Microsoft needs to beef up the installation documentation for
Server so that these kinds of gothchas can be avoided.

Enough venting and on to the solution. This error condition, its causes and
solutions are comendably well-documented by Microsoft. Hopefully they can do
an equally comendable job of documenting how to AVOID the error condition in
future releases of Server.

http://support.microsoft.com/kb/823379

Engelbert
Sun Nov 13 13:42:04 CST 2005

This is only one of the reasons for getting Server error in '/' Application.

You don't necessarily for instance need to have your WSS server as a DC to
get it.

See for instance
http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=214
which does not mention a DC at all.

The need to promote to DC first if you do have your WSS server as a DC has
been here
http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=52
since February 2004 (and as the same article in wss.collutions.com) and
should therefore by now be well-known.

Engelbert

"Outlook Integrator" <OutlookIntegrator@discussions.microsoft.com> wrote in
message news:A81836B5-7F06-44DE-9347-B7D0AFC9AA61@microsoft.com...
> Fellow SharePointers:
>
> There have been a lot of posts regarding this error message and not a lot
> of
> resolutions were identified in my experience. This is probably one of the
> most annoying errors conditions because it is so easy to get to it if you
> use
> some of the approved installation methods including in my case unattended
> setup. To avoid this error condition you must complete the installation of
> your server in the following order.
>
> 1. Initial setup.
> 2. Promote to Domain Controller
> 3. Then and only then install IIS
> 4. Install other software related to IIS such as SharePoint.
>
> One of the reasons I chose to use unattended setup was that the manual,
> granted it is wizard driven, setup method is time-consuming and tedious
> and
> unattended setup really makes you think about what you do and do not want
> on
> your server. Microsoft needs to beef up the installation documentation for
> Server so that these kinds of gothchas can be avoided.
>
> Enough venting and on to the solution. This error condition, its causes
> and
> solutions are comendably well-documented by Microsoft. Hopefully they can
> do
> an equally comendable job of documenting how to AVOID the error condition
> in
> future releases of Server.
>
> http://support.microsoft.com/kb/823379

OutlookIntegrator
Tue Nov 15 15:43:06 CST 2005

Engie:

Well-known to who? Since I bought the product from Microsoft I would think
that the place to look for solutions would be them! I am not familiar with
//www.asaris-matrix.com/ and given the number of other posts related to this
topic that have gone unsolved, neither is anyone else (including google)!
Thanks for posting the additional resource on a site where it is more likely
to get some traction.

MDJ


"Engelbert" wrote:

> This is only one of the reasons for getting Server error in '/' Application.
>
> You don't necessarily for instance need to have your WSS server as a DC to
> get it.
>
> See for instance
> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=214
> which does not mention a DC at all.
>
> The need to promote to DC first if you do have your WSS server as a DC has
> been here
> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=52
> since February 2004 (and as the same article in wss.collutions.com) and
> should therefore by now be well-known.
>
> Engelbert
>
> "Outlook Integrator" <OutlookIntegrator@discussions.microsoft.com> wrote in
> message news:A81836B5-7F06-44DE-9347-B7D0AFC9AA61@microsoft.com...
> > Fellow SharePointers:
> >
> > There have been a lot of posts regarding this error message and not a lot
> > of
> > resolutions were identified in my experience. This is probably one of the
> > most annoying errors conditions because it is so easy to get to it if you
> > use
> > some of the approved installation methods including in my case unattended
> > setup. To avoid this error condition you must complete the installation of
> > your server in the following order.
> >
> > 1. Initial setup.
> > 2. Promote to Domain Controller
> > 3. Then and only then install IIS
> > 4. Install other software related to IIS such as SharePoint.
> >
> > One of the reasons I chose to use unattended setup was that the manual,
> > granted it is wizard driven, setup method is time-consuming and tedious
> > and
> > unattended setup really makes you think about what you do and do not want
> > on
> > your server. Microsoft needs to beef up the installation documentation for
> > Server so that these kinds of gothchas can be avoided.
> >
> > Enough venting and on to the solution. This error condition, its causes
> > and
> > solutions are comendably well-documented by Microsoft. Hopefully they can
> > do
> > an equally comendable job of documenting how to AVOID the error condition
> > in
> > future releases of Server.
> >
> > http://support.microsoft.com/kb/823379
>
>
>

Engelbert
Tue Nov 15 23:32:11 CST 2005

//www.asaris-matrix.com/... is in fact the WSS FAQ mirror site
www.wssfaq.com; the WSS FAQ is also at wss.collutions.com (alias
www.sharepointtips.com). You ought to find lots of references to those. I
just prefer using the European mirror.

Even Microsoft refer to it as a source of WSS information in some of their
papers (usually the only non-Microsoft source they list).

As for Google I just went to google and wrote WSS and the first hit was the
wss.collutions.com site. (and third hit if you search with Windows
SharePoint Services) so it's well known to Google at least

Engelbert

"Outlook Integrator" <OutlookIntegrator@discussions.microsoft.com> wrote in
message news:970A47E6-B0B4-40F1-A963-2A32BF067AEA@microsoft.com...
> Engie:
>
> Well-known to who? Since I bought the product from Microsoft I would think
> that the place to look for solutions would be them! I am not familiar with
> //www.asaris-matrix.com/ and given the number of other posts related to
> this
> topic that have gone unsolved, neither is anyone else (including google)!
> Thanks for posting the additional resource on a site where it is more
> likely
> to get some traction.
>
> MDJ
>
>
> "Engelbert" wrote:
>
>> This is only one of the reasons for getting Server error in '/'
>> Application.
>>
>> You don't necessarily for instance need to have your WSS server as a DC
>> to
>> get it.
>>
>> See for instance
>> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=214
>> which does not mention a DC at all.
>>
>> The need to promote to DC first if you do have your WSS server as a DC
>> has
>> been here
>> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=52
>> since February 2004 (and as the same article in wss.collutions.com) and
>> should therefore by now be well-known.
>>
>> Engelbert
>>
>> "Outlook Integrator" <OutlookIntegrator@discussions.microsoft.com> wrote
>> in
>> message news:A81836B5-7F06-44DE-9347-B7D0AFC9AA61@microsoft.com...
>> > Fellow SharePointers:
>> >
>> > There have been a lot of posts regarding this error message and not a
>> > lot
>> > of
>> > resolutions were identified in my experience. This is probably one of
>> > the
>> > most annoying errors conditions because it is so easy to get to it if
>> > you
>> > use
>> > some of the approved installation methods including in my case
>> > unattended
>> > setup. To avoid this error condition you must complete the installation
>> > of
>> > your server in the following order.
>> >
>> > 1. Initial setup.
>> > 2. Promote to Domain Controller
>> > 3. Then and only then install IIS
>> > 4. Install other software related to IIS such as SharePoint.
>> >
>> > One of the reasons I chose to use unattended setup was that the manual,
>> > granted it is wizard driven, setup method is time-consuming and tedious
>> > and
>> > unattended setup really makes you think about what you do and do not
>> > want
>> > on
>> > your server. Microsoft needs to beef up the installation documentation
>> > for
>> > Server so that these kinds of gothchas can be avoided.
>> >
>> > Enough venting and on to the solution. This error condition, its causes
>> > and
>> > solutions are comendably well-documented by Microsoft. Hopefully they
>> > can
>> > do
>> > an equally comendable job of documenting how to AVOID the error
>> > condition
>> > in
>> > future releases of Server.
>> >
>> > http://support.microsoft.com/kb/823379
>>
>>
>>