Link to home
Create AccountLog in
Avatar of kitechgroup

asked on

Remote Web Workplace / IIS problems in SBS 2003

I have a client that is continually have a connection issue with RWW.

Randomly access to this site will be lost, this includes https://server/exchange and http://server/remote.
I have read that .NET 2.0 may cause this problem and i have uninstalled that.  I tried restarting all websites listed in IIS with not luck.  I also tried restarting the IIS admin service and its dependants also with no luck.

I also tried creating a virtual directory in the default website but could not browse to that either which leads me to believe it is an IIS issue but i am unsure of what is cuasing it.  These sites cannot be browsed internally or externally, all that is displayed is a "Page cannot be displayed" error and the generic information asscociated with it.

One thing that does resolve this issue is a server reboot.  However this only resolves the problem for a few days maybe a week at best.

Any insight or troubleshooting steps regarding this would be much appreciated.
Avatar of Dave Stringfellow
Dave Stringfellow
Flag of United Kingdom of Great Britain and Northern Ireland image

As its SBS box, did you do the simple thing of running the Internet Connection Wizard? and did you check that the IIS is using for its default website IP Addressed (all unasigned) and TCP port 80 with SSL 443?
Avatar of Jeffrey Kane - TechSoEasy
I'd suspect that the error displayed when access is lost to RWW is a VBScript Error.

If so, it may be related to having the new Terminal Services Client v6 installed on both the Server and/or remote workstation.  So far, I've not seen a fix for this issue other than uninstalling that update ( and reverting back to the v5 RDP Client.

Avatar of kitechgroup


I have ran all the wizards and checked everything during the time of failure.  Nothing but a reboot seemed to resolve the issue.  After a reboot all is well for up to a week the next failure could be from a few hours to a few days away.

As far a being a VBScript error i am not sure you may be right  will check in to that and report back with whatever I find.  Will also try removing that patch.
Still having the problem and there is nothing in the logs that say there is anything wrong.  It is not a vbscript error and the patch is not the problem.

Like I said earlier OWA stops, companyweb stops, and so does RWW.  There are no errors indicating IIS has had a problem and all appears to be running fine.

Any further suggestions would help tremendously.
If you had .NET 2.0 installed and uninstalled it, you also need to make sure that .NET 1.1 is properly applying itself to each virtual directory.

To do this, please delete all the files in C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files

Then run the following command at a CMD prompt:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

I have had this exact same problem on my own SBS server and have just started getting the problem on a clients server. The problem occured on our server every 8 days and 2 hours exactly and everything powered by IIS would stop working although IIS appeared to be fine when you looked at the admin panel. There were no errors in the event logs and nothing wrong to a trained eye but IIS would not display any web pages; just the standard "Page cannot be displayed" error.

I tried EVERYTHING to solve this issue. I got several other IT people to take a look with no luck and even got Microsoft on the case (who were useless). In the end I had to re-install the server from scratch which obviously solved the issue.

The problem is I now have the same problem on a clients server and I don't want to have to rebuild that from scratch.  I have posted on several forums and have spoken to few others with the problem but so far have found no fix. MS recomended re-installing IIS but with SBS this is so integrated with Exchange and the OS I felt it was just as easy to start from scratch which is what I did. Currently I am just re-booting my clients server every Saturday which solves the problem temporerily but obviously this is not a long term fix.

What 3rd party software are you using btw (Virus, backup etc). I'd like to build a picture of the similarities/differeneces between our systems.
Applogies if I overstepped the bounds of EE. The reason for posting in this topic was not to 'piggyback' someone elses question (Because I wasn't actually asking for help if you re-read my post) but to ask kitechgroup what 3rd party programs he was using and to let him know that others out there also have seen this issue and are working on a resolution. In my travels I have only found 4 other people with the exact same issue and so I wanted to take the opportunity to see what 3rd party programs he was using in an atrempt to correlate some similarities and potentially help the originator of this topic in the process.

I do understand that the question was perhaps older than would have been ideal but as the question was asked directly to the originator of the topic and not to other experts on the board I didn't see this as a problem. Obviously I was wrong and I applogise for that!
Good points... I will follow your advice and structure a detailed question for the correct zones!
I did get Microsoft involved as well and this was their resolution.

"created disabletaskoffload dword value =1 on the following path
On the same location set the value for EnableRSS to 0
Disable offloading features from the network card.
Rebooted the server."

It worked for 3 weeks after this but the problem eventually reoccured.  I am not sure if it was a legitimate server problem this time but I will keep watching it.

I will try registering ASP and see if that helps as well.  Sorry for the delayed response but things have been hectic here!
There's actually a patch available for this situation if you've installed Windows Server 2003 SP2

Thanks for that link. I shall give that a go and report back!

It takes about a week before the problem occurs and I want to wait until it occurs again before I patch so it may well be several weeks before I can give a yes or no on this one.
Just to confirm. The above patch (936594) did not resolve the issue I am having.
Then, this is exactly why you should post your own question.

Avatar of John_Seele

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account