Getting "Could not find file --------C:\WINDOWS\temp\ms78sjs8.dll" while accessing web service from windows application.
-
25 января 2010 г. 13:59Getting "Could not find file --------C:\WINDOWS\temp\ms78sjs8.dll" while accessing web service from windows application.
My client is a windows application accessing a web service through code. For that it instantiates the proxy class which extends SoapHttpClientProtocol. But when the control tries to instantiate this class it is getting the above mentioned error. I digged the internet to find that csc.exe is the one which generates dynamic dll's for serialization of web services.
But this error I am getting for only one of my client machine. There are other client machines which has got same C:\WINDOWS\temp folder permissions works fine. I am clueless why this is happening only in one machine. Any help would really be appreciated.
The following link shows the exact error which I am facing:
http://blogs.msdn.com/andreal/archive/2009/04/18/could-not-find-file-c-windows-temp-dll.aspx
First I need to diagonize the exact problem why I am getting this error. I read the xml serialization compiler switch in the above link but dropped the idea of implementing as I need to change the code just for finding in this machine.
Can anyone please specify steps to diagonize the possibilities why it is not working in this particular machine.
Thanks
Maavu
Все ответы
-
25 января 2010 г. 14:01
Hi, I think your link specifies "how-to?" solve it.
Check again:
http://blogs.msdn.com/andreal/archive/2009/04/18/could-not-find-file-c-windows-temp-dll.aspx
Coder24.com- Предложено в качестве ответа Asif 262 13 января 2011 г. 6:17
-
25 января 2010 г. 14:20Yes. But if you can see the first image, thats the same error which I am also getting. They say if csc.exe dont have access to folder then this can occur. I have checked other machines too. They all have same permission for running IIS Admin and WWW publishing services. So I ruled out this possibility. So first I need to check why this is happening. Then I can resolve it based on the diagnosis.
-
25 января 2010 г. 20:24
I'm not sure why you say "say if csc.exe dont have access to folder then this can occur". The issue as I understand is that the NETWORK SERVICE account needs access to the Windows temp folder. It's true that csc.exe will generate a serialization assembly in that folder, but then the assembly also needs to be accessed by code running with the Network Service account.
Phil Wilson -
26 января 2010 г. 14:22I also have the same problem, however it's not tied to a single client.
After restart of the server all works fine again but after some time the problem resurface again. I've checked all the security settings mentioned in the linked article and this is not the problem.
The other suggestion in the article is to look into the Desktop Heap, however I'm runing Windows Server 2008 and I'm not able to find a suitable tool for that. Does anyone know how this is done?
Any leads in this matter is very much appreciated. -
28 января 2010 г. 9:02Модератор
The other suggestion in the article is to look into the Desktop Heap, however I'm runing Windows Server 2008 and I'm not able to find a suitable tool for that. Does anyone know how this is done?
Hello Jonsson,
Maybe this article from NTdebugging team blog could help you:
http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx
It introduced what a Desktop Heap is and recommended tools to diagnose issue about it. As you can see, Dheapmon (Desktop Heap Monitor) is the best bet for us. The Tool could be downloaded from here.
Best regards
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework! -
28 января 2010 г. 13:46Hi Roahn,
i'm sure Dheapmon is a great tool but it doesn't run on Vista or Windows Server 2008.
Best regards
Jonsson -
9 августа 2012 г. 6:46
I also have the same problem, web services is hosted in IIS7.5 (Win2008 R2). performing IISRESET didn’t solve the problem but rebooting the server did. but after some time the problem resurface again.
Any ideas?
thanks!

