| Author |
Message |
almoendale
Guest
|
 Posted:
Mon Jan 17, 2005 12:47 pm Post subject:
woes with multiple SSL WSS sites |
|
|
Let's start here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 (don't be
fooled by the seemingly blank web page ... this is an error, and the
contents are there if you scroll down). Now the statement made in this KB is
"IP-bound virtual servers are not supported in SharePoint Portal Server 2003
or in Windows SharePoint Services. You can use the (All Assigned) IP address
option to configure IIS Host Header Web sites that do not cause this
problem."
That statement in itself is an eye-opener. We have had a WSS site and
non-WSS IIS 6.0 on the same machines for quite some time, and of course host
headering in any way at all is impossible with "HTTPS required" which we
must do because our site is an extranet and uses basic auth which cannot go
clear. The site worked fine like this for quite some time, although we found
we couldn't apply WSS SP1 a few months back, because our data server is on
another lan segment, and WSS doesn't like this too much.
Recently, I attempted to upload a Web Part with VS.Net 2003, creating a
package as is recommended in several articles. Because one "workaround" to
the above is to register Web Parts in the GAC, I created a strong named
assembly and added it to the package. From this point forward, none of the
other web parts worked, such as the rich text editor. They fail with the
SOAP error seen in the KB 830342.
Looks to me as though SSL is the culprit; I cannot use "all unassigned" and
am not sure that can be done retroactively on a WSS site (many posts have
claimed that SSL must be defined and working at root site creation time).
Any help appreciated,
Alex |
|
| Back to top |
|
 |
Mike Walsh
Guest
|
| Posted:
Mon Jan 17, 2005 3:16 pm Post subject:
Re: woes with multiple SSL WSS sites |
|
|
Apart from the missing (here) first paragraph, this is identical to a
message you posted to the subnewsgroup for WSS programming questions.
Please in future post the same (or very similar :) ) messages to only one of
the two newsgroups so that people do not waste their time answering in one
newsgroup waht has already been answered in the other newsgroup.
Thanks for your understanding of the necessity to keep the different
newsgroups focused.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"almoendale" <no_spam@nowhere.net> wrote in message
news:uxe8mBG$EHA.600@TK2MSFTNGP09.phx.gbl...
| Quote: | Let's start here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 (don't be
fooled by the seemingly blank web page ... this is an error, and the
contents are there if you scroll down). Now the statement made in this KB
is
"IP-bound virtual servers are not supported in SharePoint Portal Server
2003
or in Windows SharePoint Services. You can use the (All Assigned) IP
address
option to configure IIS Host Header Web sites that do not cause this
problem."
That statement in itself is an eye-opener. We have had a WSS site and
non-WSS IIS 6.0 on the same machines for quite some time, and of course
host
headering in any way at all is impossible with "HTTPS required" which we
must do because our site is an extranet and uses basic auth which cannot
go
clear. The site worked fine like this for quite some time, although we
found
we couldn't apply WSS SP1 a few months back, because our data server is on
another lan segment, and WSS doesn't like this too much.
Recently, I attempted to upload a Web Part with VS.Net 2003, creating a
package as is recommended in several articles. Because one "workaround" to
the above is to register Web Parts in the GAC, I created a strong named
assembly and added it to the package. From this point forward, none of the
other web parts worked, such as the rich text editor. They fail with the
SOAP error seen in the KB 830342.
Looks to me as though SSL is the culprit; I cannot use "all unassigned"
and
am not sure that can be done retroactively on a WSS site (many posts have
claimed that SSL must be defined and working at root site creation time).
Any help appreciated,
Alex
|
|
|
| Back to top |
|
|
Todd Klindt
Guest
|
| Posted:
Tue Jan 18, 2005 1:35 am Post subject:
Re: woes with multiple SSL WSS sites |
|
|
We only have one WSS virtual server on our boxes, but we added SSL much
after the installation and it hasn't been any trouble at all. We left port
80 open, but it redirects to 443 so there are no password issues. Because
of that we are not using the "SSL required" setting. This way people that
have bookmarks to http:// links can still use them. Our helpdesk
appreciates that. :)
tk
"almoendale" <no_spam@nowhere.net> wrote in message
news:uxe8mBG$EHA.600@TK2MSFTNGP09.phx.gbl...
| Quote: | Let's start here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 (don't be
fooled by the seemingly blank web page ... this is an error, and the
contents are there if you scroll down). Now the statement made in this KB
is "IP-bound virtual servers are not supported in SharePoint Portal Server
2003 or in Windows SharePoint Services. You can use the (All Assigned) IP
address option to configure IIS Host Header Web sites that do not cause
this problem."
That statement in itself is an eye-opener. We have had a WSS site and
non-WSS IIS 6.0 on the same machines for quite some time, and of course
host headering in any way at all is impossible with "HTTPS required" which
we must do because our site is an extranet and uses basic auth which
cannot go clear. The site worked fine like this for quite some time,
although we found we couldn't apply WSS SP1 a few months back, because our
data server is on another lan segment, and WSS doesn't like this too much.
Recently, I attempted to upload a Web Part with VS.Net 2003, creating a
package as is recommended in several articles. Because one "workaround" to
the above is to register Web Parts in the GAC, I created a strong named
assembly and added it to the package. From this point forward, none of the
other web parts worked, such as the rich text editor. They fail with the
SOAP error seen in the KB 830342.
Looks to me as though SSL is the culprit; I cannot use "all unassigned"
and am not sure that can be done retroactively on a WSS site (many posts
have claimed that SSL must be defined and working at root site creation
time).
Any help appreciated,
Alex
|
|
|
| Back to top |
|
|
almoendale
Guest
|
| Posted:
Tue Jan 18, 2005 8:35 am Post subject:
Re: woes with multiple SSL WSS sites |
|
|
OK thanks for the reply. I guess I miss the distinction between the two
groups, and where would you post one such as mine that is half dev (custom
web parts) and half insfrastructure (WSS craps out after deploying web
parts)? That is my motivation for posting in both places. Anyway here are
the facts for my case:
1) Host headers seem to solve this issue for many who have posted here;
*however*, I cannot use host headers under HTTPS because they are ignored by
IIS because it cannot read the encrypted packets.
2) The 1000 type errors refer to Microsoft.Sharepoint.dll, not just my
custom web parts, and there are about ten of them every time I try to save a
page that uses the "Content Editor Web Part".
3) The content editor and custom wp dll were both working fine until I
decided to try to register the custom parts in the GAC by using "STSADM -o
addwppack ..."
4) I am also trying to finish up a support case with MS having to do with
putting a SQL server in another LAN segment, preventing me from upgrading to
WSS SP1.
5) I am curious exactly when MS decided that multiple-homed IPs were
officially "not supported" rather than fixing the underlying issue. I am one
of many who tried out the earlier betas of WSS, perhaps as far back as June
2003. The fact is the earlier revs had no issues with incorrect registration
of web parts using multiple IPs and HTTPS on a single IIS 6.0 server.
Any help or experience anyone can relate / give is much appreciated.
Alex
"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:OMl4GVH$EHA.2580@TK2MSFTNGP15.phx.gbl...
| Quote: | Apart from the missing (here) first paragraph, this is identical to a
message you posted to the subnewsgroup for WSS programming questions.
Please in future post the same (or very similar :) ) messages to only one
of
the two newsgroups so that people do not waste their time answering in one
newsgroup waht has already been answered in the other newsgroup.
Thanks for your understanding of the necessity to keep the different
newsgroups focused.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"almoendale" <no_spam@nowhere.net> wrote in message
news:uxe8mBG$EHA.600@TK2MSFTNGP09.phx.gbl...
Let's start here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 (don't be
fooled by the seemingly blank web page ... this is an error, and the
contents are there if you scroll down). Now the statement made in this KB
is
"IP-bound virtual servers are not supported in SharePoint Portal Server
2003
or in Windows SharePoint Services. You can use the (All Assigned) IP
address
option to configure IIS Host Header Web sites that do not cause this
problem."
That statement in itself is an eye-opener. We have had a WSS site and
non-WSS IIS 6.0 on the same machines for quite some time, and of course
host
headering in any way at all is impossible with "HTTPS required" which we
must do because our site is an extranet and uses basic auth which cannot
go
clear. The site worked fine like this for quite some time, although we
found
we couldn't apply WSS SP1 a few months back, because our data server is
on
another lan segment, and WSS doesn't like this too much.
Recently, I attempted to upload a Web Part with VS.Net 2003, creating a
package as is recommended in several articles. Because one "workaround"
to
the above is to register Web Parts in the GAC, I created a strong named
assembly and added it to the package. From this point forward, none of
the
other web parts worked, such as the rich text editor. They fail with the
SOAP error seen in the KB 830342.
Looks to me as though SSL is the culprit; I cannot use "all unassigned"
and
am not sure that can be done retroactively on a WSS site (many posts have
claimed that SSL must be defined and working at root site creation time).
Any help appreciated,
Alex
|
|
|
| Back to top |
|
|
Mike Walsh
Guest
|
| Posted:
Tue Jan 18, 2005 10:23 pm Post subject:
Re: woes with multiple SSL WSS sites |
|
|
If you really were asking me, what I'd do would be to write two messages.
The infrastructure one would go here (i.e. the comment about the KB article
being odd) and the uploading a web part with VS.Net (as not part of standard
WSS usage) one would go there.
What I wouldn't do is duplicate them (almost).
The audience for the main group is I would guess 90% people who don't read
the programming newsgroup (and most of who aren't interested in programming
issues) whereas I suspect that most of the programming newsgroup readers
visit here too.
So both your messages would be seen by the programming guys and those of us
here would have the benefit of you spotting an oddity in the KB article.
(Speaking only for me I rarely make it to the end of long messages with
different things in them so two shorter ones are anyway better).
Mike Walsh, Helsinki, Finland
"almoendale" <no_spam@nowhere.net> wrote in message
news:#27NtZQ$EHA.2568@TK2MSFTNGP11.phx.gbl...
| Quote: | OK thanks for the reply. I guess I miss the distinction between the two
groups, and where would you post one such as mine that is half dev (custom
web parts) and half insfrastructure (WSS craps out after deploying web
parts)? That is my motivation for posting in both places. Anyway here are
the facts for my case:
1) Host headers seem to solve this issue for many who have posted here;
*however*, I cannot use host headers under HTTPS because they are ignored
by
IIS because it cannot read the encrypted packets.
2) The 1000 type errors refer to Microsoft.Sharepoint.dll, not just my
custom web parts, and there are about ten of them every time I try to save
a
page that uses the "Content Editor Web Part".
3) The content editor and custom wp dll were both working fine until I
decided to try to register the custom parts in the GAC by using "STSADM -o
addwppack ..."
4) I am also trying to finish up a support case with MS having to do with
putting a SQL server in another LAN segment, preventing me from upgrading
to
WSS SP1.
5) I am curious exactly when MS decided that multiple-homed IPs were
officially "not supported" rather than fixing the underlying issue. I am
one
of many who tried out the earlier betas of WSS, perhaps as far back as
June
2003. The fact is the earlier revs had no issues with incorrect
registration
of web parts using multiple IPs and HTTPS on a single IIS 6.0 server.
Any help or experience anyone can relate / give is much appreciated.
Alex
"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:OMl4GVH$EHA.2580@TK2MSFTNGP15.phx.gbl...
Apart from the missing (here) first paragraph, this is identical to a
message you posted to the subnewsgroup for WSS programming questions.
Please in future post the same (or very similar :) ) messages to only
one
of
the two newsgroups so that people do not waste their time answering in
one
newsgroup waht has already been answered in the other newsgroup.
Thanks for your understanding of the necessity to keep the different
newsgroups focused.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"almoendale" <no_spam@nowhere.net> wrote in message
news:uxe8mBG$EHA.600@TK2MSFTNGP09.phx.gbl...
Let's start here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 (don't
be
fooled by the seemingly blank web page ... this is an error, and the
contents are there if you scroll down). Now the statement made in this
KB
is
"IP-bound virtual servers are not supported in SharePoint Portal Server
2003
or in Windows SharePoint Services. You can use the (All Assigned) IP
address
option to configure IIS Host Header Web sites that do not cause this
problem."
That statement in itself is an eye-opener. We have had a WSS site and
non-WSS IIS 6.0 on the same machines for quite some time, and of course
host
headering in any way at all is impossible with "HTTPS required" which
we
must do because our site is an extranet and uses basic auth which
cannot
go
clear. The site worked fine like this for quite some time, although we
found
we couldn't apply WSS SP1 a few months back, because our data server is
on
another lan segment, and WSS doesn't like this too much.
Recently, I attempted to upload a Web Part with VS.Net 2003, creating a
package as is recommended in several articles. Because one "workaround"
to
the above is to register Web Parts in the GAC, I created a strong named
assembly and added it to the package. From this point forward, none of
the
other web parts worked, such as the rich text editor. They fail with
the
SOAP error seen in the KB 830342.
Looks to me as though SSL is the culprit; I cannot use "all unassigned"
and
am not sure that can be done retroactively on a WSS site (many posts
have
claimed that SSL must be defined and working at root site creation
time).
Any help appreciated,
Alex
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in