D_Hartup
asked on
OWA 2003 and SBS2003 websites on IIS Not Working Anymore
Hi,
I've got a SBS2003 with OWA2003 on it, and up until yesterday if you went to either http://server/exchange or http://server.fully.qualified.domainname/exchange it would automatically redirect to https://server/exchange or https://server.fully.qualified.domainname/exchange
This has stopped working. OWA still works if you manually type in https.
Also, the other http SBS sites seem to have stopped working too - SharePoint, ConnectComputer, Remote.
Everything did work until yesterday, and there's been no changes to the system. There's no errors in teh error log, no errors in the IIS website logs, but the requests for the site show up as 404 not found. When I look at the websites in IIS, all the required parts are still there (Exchange, exadmin etc etc)
Cheers,
Dave
I've got a SBS2003 with OWA2003 on it, and up until yesterday if you went to either http://server/exchange or http://server.fully.qualified.domainname/exchange it would automatically redirect to https://server/exchange or https://server.fully.qualified.domainname/exchange
This has stopped working. OWA still works if you manually type in https.
Also, the other http SBS sites seem to have stopped working too - SharePoint, ConnectComputer, Remote.
Everything did work until yesterday, and there's been no changes to the system. There's no errors in teh error log, no errors in the IIS website logs, but the requests for the site show up as 404 not found. When I look at the websites in IIS, all the required parts are still there (Exchange, exadmin etc etc)
Cheers,
Dave
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The next number is 0 which means this is a 404.0 response which translates to "the file isn't here".
Apparently something significant has changed on the system.
Can you restart IIS, hit the sites that aren't working and then post the w3svc logs showing the various responses?
Dave Dietz
Apparently something significant has changed on the system.
Can you restart IIS, hit the sites that aren't working and then post the w3svc logs showing the various responses?
Dave Dietz
By the way, did you mean to accept my question as an answer?
Dave Dietz
Dave Dietz
ASKER
yep, can't delete so I thought I'd give you the points...
Found out what the error was - basically the owahttps.asp script someone had changed to point at a different url that pointed at the same server, but for some reason that url is no longer working. So changed it to a working url and hey presto.
The other directories like /remote and /connectcomputer were due to iis being reinstalled a few weeks ago, and didn't twig that of course an iis reinstall doesn't regenerate those directories on sbs2003
Found out what the error was - basically the owahttps.asp script someone had changed to point at a different url that pointed at the same server, but for some reason that url is no longer working. So changed it to a working url and hey presto.
The other directories like /remote and /connectcomputer were due to iis being reinstalled a few weeks ago, and didn't twig that of course an iis reinstall doesn't regenerate those directories on sbs2003
ASKER
2004-11-17 09:38:35 192.168.4.10 GET /ConnectComputer - 80 - 192.168.4.10 Mozilla/4.0+(compatible;+M
Oddly, the other websites that are running on the server are working ok (ie. sites separate to the Default Web Site)
Not sure what you mean by next number - does the above answer that question?