web.config <assemblies> section being modified

[Guest]

Hi there,

I am having a strange problem which I have actually seen on 2 different
servers now. The problems manifests itself as a ConfigurationException, and
upon inspection, a new (invalid/non-existent) assembly reference is added in
the <assemblies> element of web.config.

In both cases, the assemblies being referenced have never existed on the
servers. In one case, a reference to System.Web.Extensions was added, and in
the other, a reference to a third-party UI component was added.

ACL's on the web directories look good and the only users with write access
are System and Administrators.

Any ideas would be appreciated!

Thanks,

 

[Steven Cheng[MSFT]]

Hi Steven,

From your description, you're encountering some ConfigurationException when
running your ASP.NET application and the exception is related to some
registered assemblies in web.config ,correct?

Regarding on the assemblies, you said that those problem assembies are
automatically added into the web.config file and your application does not
originally use them? Also, what's your web application's virtual directory
hierarchy in the deployed IIS server, is there any web application at its
super level or nested child node? If so, you can try move it out to a
single alone virtual directory (with a separate application pool if it is
IIS6 server) to see whether the problem remain.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



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

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.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/subscriptions/support/default.aspx.

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



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

 

[Guest]

Hi Steven,

Thanks for your reply. Just to clarify the issue, it is a
ConfigurationException, however the real "problem" is that the web.config is
being modified (not by a person), which in turn causes the
ConfigurationException.

In both cases, the websitse are their own website instances with a few child
virtual directories. All of the sites operate within their own application
pool.

 

[Steven Cheng[MSFT]]

Thanks for your reply.

So the web.config file is modified by other program instead of developer or
admin? Is there any ASP.NET/.NET 2.0 configuration API used in your web
application or any pages in your application's sub directory? So far I
haven't found any built-in ones that will automatically add assemblies
binding at runtime. Some control (such as reportviewer) may add such
assemblies record at design-time in IDE.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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

 

[Guest]

Hi Steven,

Yes that is correct about the web.config being modified by a process. The
configuration API is used for reading the appSettings element and a few other
custom configuration sections.

One of the projects uses the ReportViewer however the other does not.

 

[Steven Cheng[MSFT]]

Thanks for your reply.

If it does be changed by a certain process, you can use some file monitor
tool or the .NET FileSystemWatcher class to monitor which process access
that file.

However, I still suggest you try put the application to another isolated
site or virutal directory so that no other web application will affect it.
this can help determine which application is modifying it.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


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