Strange exeption when connecting to WebService

[Ricky K. Rasmussen]

Hi NG,

When connecting to a local WebService one of our customers gets a very
strange exception:

"File or assembly name gaw9eaqv.dll, or one of its dependencies, was not
found."

The strange part is that the name of the assembly can vary, and has nothing
to do with the names of the assemblies used in neither the WebService or the
consumer of the WebService.

It looks to me as if the assembly is one of the Temporary assemplies created
by ASP.NET, but what could cause the error to occur?

Thanks for your time,

Ricky

[Steven Cheng[MSFT]]

Hi Ricky,

Thanks for your posting. As for the
"File or assembly name {random name}.dll, or one of its dependencies, was
not found." when calling webservice.
error you mentioned, based on my research, generally there're 2 possible
causes:
1. Permission issue, the process acount haven't read/write permission to
the temporary folder. Also, we also have two sub scenarios, clientside or
serverside issue.(If both the client side and serverside are based on
.net).

At Serverside, the asp.net webservice will do runtime compilation and
generate assembly in the asp.net temporary
folder({sysdir}:\windows\Microsoft.NET\Framework\v 1.1.4322\Temporary
ASP.NET Files)
Make sure what's the asp.net's running process account(whether the
impersonate is used) and whether it has the sufficient permission to the
temporary folder.

Also, as for clientside, the identity of the client app will also need to
have these same permissions
(read/execute on C:\winnt\microsoft.net\framework, and write on
C:\winnt\temp)
when the client app is web-based (asp, asp.net), you have to watch out for
this.

note it's the identity of the client *process* which is used here (not the
impersonated identity). so it's the IWAM, ASPNET, or NETWORK SERVICE
account (not
the IUSR account or end user's account).

2. There are compile errors in the XmlSerializer generated code(since
webservice using the XmlSerializer to generate dynamic codes on the fly)

To trouble shoot this reason we added the following Switch in
machine.config.
<system.diagnostics>
<switches>
<add name="XmlSerialization.Compilation" value="4"/>
</switches>
</system.diagnostics>

Now we executed the application and got _tmpname.00.cs and _tmpname.out
files added
in %temp% dir. This file may help provide some clues on the compile error.

Anyway, since the potential cause maybe one of the aboves, we may need some
further checks. I suggest you isolate the problem to serverside or
clientside first.

If you have anyother findings or need any assistance, please feel free to
post here. Thanks.
Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)