w3wp.exe problem (moved from .NET)

[mohamed27]

hi :

i have a server with OS (2003 server)
and i have a high usage of memory ,when i opened my task manger i found that w3wp.exe is the high application usage of memory

this make ths server very slow and i can not open . aspx pages
i need help plz

[RedSon]

How do you want us to help you?

[RedSon]

Aha never mind this will cure you:

http://support.microsoft.com/kb/900243

[mohamed27]

first i am sorry for my bad language and llittel experiance in discribeing the problem in right way
how can i decrease this usage of memory
it was work good for along time before.

ask me for the information you need to know
thanks

[RedSon]

Click on the link. You are experiencing a bug that Microsoft is aware of and has provided a hotfix.

[mohamed27]

thank you very much

[mohamed27]

i will try to get service pack 2 but i am afraid that this will affect the clients asp.net applications

[MMcCarthy]

i will try to get service pack 2 but i am afraid that this will affect the clients asp.net applications

Would you like me to move this question to the Windows forum where they may be better able to help.

Mary

[mohamed27]

yes sure

it is urgent i need helppppppppp

[RedSon]

Hold on one second now. What part of this solution is not working for you? Did you contact customer support to obtain the hotfix? Do you have the English language version? Did you compare your file's attributes to the ones in the table?

Also this will not affect the client's .net programs. The point is that .net is an interpreted language, it is designed to work the same on any system that runs .net. Its like java, making changes to executables on a linux box does not affect the way your java programs run, nor would it on a windows machine.

[MMcCarthy]

Hold on one second now. What part of this solution is not working for you? Did you contact customer support to obtain the hotfix? Do you have the English language version? Did you compare your file's attributes to the ones in the table?

Sorry RedSon

I'd already moved just as you posted. The reason I made the suggestion is that the OP seems concerned about the implications of the hotfix on the clients ASP.NET servers. I've left a redirect in the .NET forum so you can still participate. Sorry if I stepped on your toes.

Mary

[RedSon]

Ah well, no prob. I'm just surprised that the OP says they still need heeelllllp. It leads me to believe one of two things, either the OP has not clicked on the link I provided and followed the steps or the OP has a pirated version of the OS and doesn't want to call customer support. Which in either case is bad.

[MMcCarthy]

Ah well, no prob. I'm just surprised that the OP says they still need heeelllllp. It leads me to believe one of two things, either the OP has not clicked on the link I provided and followed the steps or the OP has a pirated version of the OS and doesn't want to call customer support. Which in either case is bad.

True although I got the impression this was for a client and they were wary of putting anything on the clients system. Could be wrong though.

Mary

[RedSon]

True although I got the impression this was for a client and they were wary of putting anything on the clients system. Could be wrong though.

Mary

I could be wrong but I read it as a client's application. Which means that the server is owned by the OP, or else he wouldn't be complaining about w3wp.exe sucking up all his resources. You are looking at two separate things here the server running w3wp.exe and the client's application which I assume to be a .net app since that was where the original post was. The performance of .net applications are affected by the version number of the .net framework that the server or development station provides. Updating or patching various executables on the server side are not going to have an affect on the .net application.

w3wp.exe is a process that is a part of the ISS application pool. The resource hangup comes from w3wp.exe using poorly designed routines in the Wldap32.dll module which is a dll used in the Exchange server services. Specifically the web access portion of the exchange server. So you can uninstall exchange server, remove the web access to exchange server, or you can install the hotfix and hope that it helps until the next service pack is released.

[MMcCarthy]

I could be wrong but I read it as a client's application. Which means that the server is owned by the OP, or else he wouldn't be complaining about w3wp.exe sucking up all his resources. You are looking at two separate things here the server running w3wp.exe and the client's application which I assume to be a .net app since that was where the original post was. The performance of .net applications are affected by the version number of the .net framework that the server or development station provides. Updating or patching various executables on the server side are not going to have an affect on the .net application.

w3wp.exe is a process that is a part of the ISS application pool. The resource hangup comes from w3wp.exe using poorly designed routines in the Wldap32.dll module which is a dll used in the Exchange server services. Specifically the web access portion of the exchange server. So you can uninstall exchange server, remove the web access to exchange server, or you can install the hotfix and hope that it helps until the next service pack is released.

You are probably right. Your knowledge of this area is a lot more extensive than mine.

Mary