Win SBS 2003, IIS, OWA problems

Ok, here we go:

Win SBS 2003
Email, DNS, DHCP, and AD "appear" ok.

Both sharepoint sites and the symantec mail security site starts (this was happening before symantec installed). Default web and company web wont start. Both generate events:

Event Type:     Error
Event Source:     HTTP
Event Category:     None
Event ID:     15005
Date:          9/8/2006
Time:          8:48:10 PM
User:          N/A
Computer:     JAYSTEEL
Description:
Unable to bind to the underlying transport for 0.0.0.0:80. 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 04 00 02 00 52 00   ......R.
0008: 00 00 00 00 9d 3a 00 c0   ....:.À
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 43 00 00 c0               C..À    


then event:

Event Type:     Error
Event Source:     W3SVC
Event Category:     None
Event ID:     1004
Date:          9/8/2006
Time:          8:48:10 PM
User:          N/A
Computer:     JAYSTEEL
Description:
Cannot register the URL prefix 'http://companyweb:80:10.250.190.100/_wpresources/' for site '4'. The site has been deactivated.  The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 20 00 07 80                ..€    


Also, the Exchange virtual server wont start...seeing as the default site wont start. If I try to start default or company web manually i get:
"the process cannot access the file because it is being used by another process."

Everything seems ok otherwise but due to all this I cannot get OWA to work.

Any help will be much appreciated...
LVL 4
NitrosysAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ImmediateActionCommented:
"Unable to bind to the underlying transport for 0.0.0.0:80."

Have you got another service listening on port 80?
netstat -an

Whats the name of the service?
netstat -v -b

NitrosysAuthor Commented:
netstat -an   gives me:
tcp 0.0.0.0:80  0.0.0.0   listening

netstat -v -b  yikes, thats a long list...I dont see 80 in there and I looked through a few times.
ImmediateActionCommented:
This may be relevant?

http://support.microsoft.com/default.aspx?scid=kb;en-us;890015

You might also want to let us know if that Sharepoint and Symantec site run on port 80. If that the case, confirm that the OWA site is bound to the correct ip(s) address in the IIS mmc.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Become a Microsoft Certified Solutions Expert

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

NitrosysAuthor Commented:
I will check out that article but to your other question...

Sharepoint admin on 6105
Sharepoint Central Admin 8081
Symantec on 8082
OWA under the default site on 80 (ssl on 443)
comapny web is also on 80 (ssl on 444)

As an FYI these are the defaults Windows set up with the exception of Symantec which I picked.
NitrosysAuthor Commented:
Well, problem solved!

The KB article and what you said for netstat helped. The part you were missing from your netstat was -o which the KB said to run "netstat -ano" this gave me the PID of the process and I was able to track it down in Task Manager.

My client installed a Belking UPS and, although I told them to let me hande all server relate stuff, installed it with the web interface using port 80. I changed that and everythign is working like a charm.

Thanks!!
ImmediateActionCommented:
Hi Nitrosys,

That's great to hear, and thanks for letting me know how adding the o to the end allowed you to find the solution; that will be a handy troubleshooting tool for me in the future. Cheers.

IA
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.