How can we help you today? How can we help you today?
aswilbourn
Hi Thomas, Thanks for your reply. In answer to your questions: On the first attempt I tried to set the UAS ina seperate website on a dedicated port (because as you said its not wise to mess with default site on a SBS server), however I got the error I mentioned. I tried a couple more times before I decided to bite the bullet and install on the default website on port 80 (no need to worry its a test server not a live one), however same message again. I have opened up the ISS manangement console and the ISS admin service appears to be running fine and can be accessed. The ISS admin service is activated and running in services. The default website Node can be accessed fine with no errors in the ISS MMC. Able to access default website, companyweb and other ISS webites fine from a client PC attached to the server. The only thing I can think might effect the configuration is we have a bit of a strange configuration on IIS. We wanted to install sharepoint Service 3.0 on the SBS server but had to install it side by side with 2.0. This is because Companyweb runs on 2.0 and if we over wrote company web it would completly cock up our SBS installation. The process we used is in the websites mentioned below: http://technet.microsoft.com/en-us/libr ... 71966.aspx and part 4 of this guide: http://msmvps.com/blogs/cgross/archive/ ... art-4.aspx We have since also upgraded Sharpoint Services 3.0 to Sharepoint Server 2007. Not sure if this is relevant but I believe it is the only other thing that can be affecting IIS. Thanks Andy / comments
Hi Thomas, Thanks for your reply. In answer to your questions: On the first attempt I tried to set the UAS ina seperate website on a dedicated port (because as you said its not wise to mess with de...
0 votes