"Configuration Error"

[Chris Hoare]

Hello all,

I occasionally get a "configuration error" in components
when copying a new dll component into the main
application. The error reports a problem in
machine.config - which is unchanged from install ...

The error is on line 258
<add assembly="*"/>

I have done some obvious things like checked the
permissions are ok and mycomputer\ASPNET has access to
the folder.

The problem corrects itself after about 10 minutes -
which leads me to wondering if it is active directory ?

Any suggestions how to resolve this - as when the
application goes live this sort of thing would be
unacceptable !

Chris

---Error

Configuration Error
Description: An error occurred during the processing of a
configuration file required to service this request.
Please review the specific error details below and modify
your configuration file appropriately.

Parser Error Message: Access is denied: 'S106'.
....
Source File: c:\windows\microsoft.net\framework\v1.1.4322
\Config\machine.config Line: 258
....


=== Pre-bind state information ===
LOG: DisplayName = S106
(Partial)
LOG: Appbase = file:///C:/Inetpub/wwwroot/STNet
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===

LOG: Policy not being applied to reference at this time
(private, custom, partial, or location-based assembly
bind).
LOG: Post-policy reference: S106
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Tempo
rary ASP.NET Files/stnet/e1af402b/db217927/S106.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Tempo
rary ASP.NET Files/stnet/e1af402b/db217927/S106/S106.DLL.
LOG: Attempting download of new URL
file:///C:/Inetpub/wwwroot/STNet/bin/S106.DLL.
LOG: Policy not being applied to reference at this time
(private, custom, partial, or location-based assembly
bind).
LOG: Post-policy reference: S106, Version=1.0.1363.16937,
Culture=neutral, PublicKeyToken=null

 

[Gary]

Try turning off active directory.

Gary

 

[Scot Rose [MSFT]]

I suppose that depending on how large your network is it could take that long to propagate the information to Active directory. I have found no previous issues reported that are
similar to your problem however. You may try something like Filemon to see what error is occuring when the attempt is made to access the DLL (www.sysinternals.com) and see if it
is a permission error. Where are you installing the file to? Another machine? It is a preexisting Application? Is this a New DLL or are you replacing a preexisting DLL?


Scot Rose, MCSD
Microsoft Visual Basic Developer Support
Email : (e-mail address removed) <Remove word online. from address>

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

Get Secure!
http://www.microsoft.com/security
http://www.microsoft.com/protect


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