We help IT Professionals succeed at work.

RWW Stopped after upgrade to WSS 3 on SBS2003

Last Modified: 2008-07-16
Wierd Problem.  After installing WSS 3. side by side with WSS 2 on my SBS 2003 SP1 server all of a sudden I can't access the "connect to client" or "connect to server" section of RWW.  OWA works fine.  I can log into RWW and it displays fine but when I hit the connect to client or server I get a page cannot be displayed error.  All of the additional links work fine.  I can log into the help desk, owa, sbspackage.exe works everything else except for connecting to the client or server.  I can log into the server using rdp.  WSS 2 (companyweb) and WSS 3 both appear to be functioning fine.

I am sure this has something to do with WSS 3.

Any ideas??
Watch Question

Not an SBS expert, but have worked with WSS3, MOSS, Exchange 2003/2007 and IIS.

Is this the method you used to install WSS3?


or this?


Also, this may help:


I used the first method.
Does the problem listed here ring any bells?


It looks to me that the solution listed there might resolve your issue.


Well, trying to not be confused here.  Everything is working fine except for accessing the client and server from RWW from the internet.  I can access it perfectly from the server using .  I do have default web site and company web both using port 80 though.
In that case I'm going to recommend looking at published paths in ISA, and then bow out of this one if that doesn't help.
Philip ElderTechnical Architect - HA/Compute/Storage

Rerun the CEICW to reset the settings and reseat the SSL cert.



I did that last night after reading a post about that.  No effect.


OK when I attempt to access from outside the domain I have the following error show up in my SBS 2003 error log

Event Type: Error
Event Source: SBS.RWW
Event Category: None
Event ID: 0
Date: 7/8/2008
Time: 5:43:16 PM
User: N/A
Computer: BLAHBLAH
The following fatal error occurred in the Remote Web Workplace application:
URL: https://my.domain.net/Remote/signout.aspx
Error Message: A potentially dangerous Request.Cookies value was detected from the client (Microsoft.Sharepoint.AcceptHeaders="...&pps=TRUE&one=FALSE&mpp=FALSE").
Stack Trace: at System.Web.HttpRequest.ValidateString(String s, String valueName, String collectionName)
at System.Web.HttpRequest.ValidateCookieCollection(HttpCookieCollection cc)
at System.Web.HttpRequest.get_Cookies()
at remote.RAPLinks.TakeAwayOWACookies(HttpRequest httpClientRequest)
at remote.signout.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain()
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This one is on us!
(Get your first solution completely free - no credit card required)
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.