G
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,
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,