Strange exeption when connecting to WebService

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,

RickyHi 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.)

Strange exeption when connecting to WebService

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,
RickyHi 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\v1.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.)

Strange parse error calling ASP.Net WebService

By making a call to a webservice I receive the following error page, we did a
complete new build but the error still exist:

The installation of the webservice is on an win 2003 standard service pack 1
server.

Server Error in '/BackupAgentServices' Application.

------------------------

Parser Error

Description: An error occurred during the parsing of a resource required to
service this request. Please review the following specific parse error
details and modify your source file appropriately.

Parser Error Message: The check of the module's hash failed for file
'System.EnterpriseServices.Thunk.dll'.

Source Error:

Line 1: <%@dotnet.itags.org. Application Codebehind="Global.asax.cs"
Inherits="BAWebService2.Global" %>

Source File: C:\Program Files\BackupAgent Server
2006\BackupAgentServices\global.asax Line: 1

------------------------

Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET
Version:1.1.4322.2300 --. For more information, see Help and Support Center
at http://go.microsoft.com/fwlink/events.asp.

--
rvangeldropHello Rvangeldrop,

From your description, you have an ASP.NET web service project which is
reporting the following exception at startup time on a windows 2003
server/sp1 box, correct?

====================
Parser Error Message: The check of the module's hash failed for file
'System.EnterpriseServices.Thunk.dll'.
====================

Based on my experience, since the project is built without problem and the
error occurs at very begining of the appilcation's startup time(intialize
global.asax), it is likely an environment specific issue. Before we perform
detailed troubleshooting, I'd like to confirm the following things:

** Is the webservice project developed upon .net framework 1.1/vs2003 or
..net framework 2.0/vs 2005

** Before deploying on the windows 2003 server/sp1, is it being developed
on another box and works without any problem on it?

** Though the problem is specific to the windows 2003 server machine, you
can still create a very simple webservcie project and test it on the
problem server to see whether the problems also ocurs.

I've also searched some former issues with similar symtom, however, seems
the cause are not quite matching your case. So we need to do some general
problem isolation tests first.

Please feel free to let me know if there is any new finding or any question
you wonder.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...rt/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
Hello Rvangeldrop,

How are you doing on this issue, have you got any progress or does the
suggestion in my last reply helps some?

If there is anything else we can help, please feel free to let me know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.
the solution was to completely reinstall the server. Appearently some HP
server went bad and this was one of them.

So the problem was at HP for some reason... At least that was what the
customer told me.

--
rvangeldrop

"Steven Cheng[MSFT]" wrote:

Quote:

Originally Posted by

Hello Rvangeldrop,
>
How are you doing on this issue, have you got any progress or does the
suggestion in my last reply helps some?
>
If there is anything else we can help, please feel free to let me know.
>
Sincerely,
>
Steven Cheng
>
Microsoft MSDN Online Support Lead
>
>
This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>