Web access to exchange stopped working after Windows Server Updates
Issue: IIS/Exchange, Web Exchange stopped working with Error: The requested resource is in use.
No event logs regarding this.
Running Server 2003 with SBS, IIS v6.0, Exchange v6.5.7226.0 all up to date with latest service packs.
This occurred after running complete windows updates on the server.
I've tried unchecking Cache ISAPI extensions, this didn't work.
Tested the web exchange locally as well as externally, with the same result.
All required services are started.
There are no related errors in the event logs.
This may be an Exchange error because the companyweb works locally, and the Server Welcome page comes up when connecting to the external address, however the web exchange doesn't work in any form.
Example: 'http://0.0.0.0' comes up with the welcome page, 'http://0.0.0.0/exchange' comes up with the error message: The requested resource is in use. or 404 error, depending on the browser version.
Any ideas?
No event logs regarding this.
Running Server 2003 with SBS, IIS v6.0, Exchange v6.5.7226.0 all up to date with latest service packs.
This occurred after running complete windows updates on the server.
I've tried unchecking Cache ISAPI extensions, this didn't work.
Tested the web exchange locally as well as externally, with the same result.
All required services are started.
There are no related errors in the event logs.
This may be an Exchange error because the companyweb works locally, and the Server Welcome page comes up when connecting to the external address, however the web exchange doesn't work in any form.
Example: 'http://0.0.0.0' comes up with the welcome page, 'http://0.0.0.0/exchange' comes up with the error message: The requested resource is in use. or 404 error, depending on the browser version.
Any ideas?
ASKER
After trying this I get this error:
Unable to bind to the underlying transport for 192.168.0.2:8080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
I cannot find another instance with that port. we also have sharepoint server. MyCompanyWeb is running on port 80.
Unable to bind to the underlying transport for 192.168.0.2:8080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
I cannot find another instance with that port. we also have sharepoint server. MyCompanyWeb is running on port 80.
Check the IP Address ... Select the correct one .... ( exchange web properties )
ASKER
I'm not sure what you mean.
The IP of the exchange server is selected(typed in) on the Default web site.
Apart from that , there is no selections for the sub-webs including exchange web properties, there's no option to select or type an IP address.
Although I'm not sure what was changed but it is now displaying the web address as an FTP listing rather than Exchange web access ...
The IP of the exchange server is selected(typed in) on the Default web site.
Apart from that , there is no selections for the sub-webs including exchange web properties, there's no option to select or type an IP address.
Although I'm not sure what was changed but it is now displaying the web address as an FTP listing rather than Exchange web access ...
ASKER
another note. Changing the default port to 8080 stopped the Default web site entirely.
I cannot restart it unless changing back to port 80
I cannot restart it unless changing back to port 80
Can you restart your Server ? .. Also check the event viewer and post the error you get after rebooting ....
Manu
Manu
ASKER
Here's a few:
Cannot register the URL prefix 'http://192.168.0.2:8080/ExchWeb/' for site '1'. The site has been deactivated. The data field contains the error number.
AND
Unable to bind to the underlying transport for 192.168.0.2:8080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
Now this is when I had changed it to port 8080..
The error above stopped after chaning back to port 80
I did another restart and I can log into web access, BUT after login it takes me to an FTP type file listing rather than the usual exchange web mail ???
Cannot register the URL prefix 'http://192.168.0.2:8080/ExchWeb/' for site '1'. The site has been deactivated. The data field contains the error number.
AND
Unable to bind to the underlying transport for 192.168.0.2:8080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
Now this is when I had changed it to port 8080..
The error above stopped after chaning back to port 80
I did another restart and I can log into web access, BUT after login it takes me to an FTP type file listing rather than the usual exchange web mail ???
ASKER
This problem is still unresolved :(
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Go to IIS manager , Check your Default Website, right click take properties and change the PORT from 80 to 8080 ..
Then restart the IIS Service , it should come up ...
Make sure the ExchangeWeb uses the port 80
You cant use same port 80 for both your defualt website and exchange website ... That is why this conflict ..
Hope this helps
Manu