Hi there,
I've got a WebService application that works fine under Windows 2000 with
Framework 1.0
Installing it on Windows 2003 results in SoapExceptions being thrown when
any of the methods are called. The error refers to a randomly named DLL
which changes each time eg :
Server was unable to process request --> File or assembly name random.dll or
one of its dependencies was not found.
WSDL requests however work - just not using the actual service.
Researching on the web throw up various posts about changing the security
permissions of the Windows\Temp and the Framework\Temporary ASP.Net files to
allow the NETWORK SERVICE full control.
I have done this - no joy. I have tried "EVERYONE" - no joy. I have changed
most of the various security policy options to see if they made any
difference. No joy.
ANy other suggestions on what security permissions to look at, or indeed
anything else that might allow me to run the application on Windows 2003?