Exc 2k3 - OWA stopped working, locked by process 1

[MakeItSo]

Hi friends,

running Windows Server 2003 Standard, Exchange Server 2003 SP2.
For some reason, OWA has stopped working; I suspect some Windows/Exchange update as the culprit; can't think of anything else.
The problem is that the default website cannot be started.
I have re-started HTTP services and the related ones, also re-created the virtual directories, yet I cannot start the virtual Exchange Server. It always errors with "cannot access file as it is in use by another process".
I have made sure, all unnecessary software is deinstalled and no other web process is running.

Any of you know this behaviour and can help me?

Thanks a lot!
MiS

[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[58sniper]

What's your AV software scanning? Are you excluding the correct directories as recommended by Microsoft?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[MakeItSo]

Hi Pat,

yes, I've excluded the Exchange directories as well as the inetsrvr directory.
I realized though, that these exclusions had not been in effect before. I had added them but overlooked that the AV software was set to protect it from any tampering. Funny it didn't notify me of it.
Well, that's the "fun" that comes with using McAfee VS Enterprise. )

Anyway: made the AV allow me to change these settings, added the exclusions, but still get the "in use by another process" error. Restarted the server - no effect.


[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[MakeItSo]

What the f.... ???!!

After restart, McAfee has resetted to 0 exclusions?!
I think we have located the culprit now!
What in freak's name does MA think it is?


[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[MakeItSo]

The problem seems to be with McAfee VSE version 8.70i.
I am now downloading 8.5 from the McAfee Server, will expect this to fix the issue.
will let you know in half an hour...

Thanks for (not) letting me know, McAfee!!!!!!



[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[MakeItSo]

%&$%&$
Still won't work
..
..

[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[MakeItSo]

Yeah!!!!!!!!!

Got it!!!!!!!!!!!!!!!!!!!!!!!!!!

Incredible but true: it was McAfee; to be precise: that fecking ePolicyOrchestrator.

Well, that cures me from using THAT biatch!





[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell

 

[58sniper]

There are generally two things that can cause these problems. AV and backup apps. Glad to see you got it working.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[MakeItSo]

Yeah.
The funny thing is, that we've had McAfee enterprise & the server app running for almost two and a half years now and OWA stopped working only recently.

Must have been some "hotfix"... *shivers*

[navy]"We had to turn off that service to comply with the CDA Bill."[/navy]
- The Bastard Operator From Hell