asked on

[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Event Category:      None
Event ID:      0
Date:            11/12/2008
Time:            12:46:23 PM
User:            N/A
Computer:
Description:
Service cannot be started. System.TypeInitializationException: The type initializer for 'Microsoft.Practices.EnterpriseLibrary.Logging.Logger' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Common, Version=3.1.0.0, Culture=neutral, PublicKeyToken=5' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Practices.EnterpriseLibrary.Common, Version=3.1.0.0, Culture=neutral, PublicKeyToken=5'
at Microsoft.Practices.EnterpriseLibrary.Logging.Logger..cctor()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

--- End of inner exception stack trace ---
at Microsoft.Practices.Ente...

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Jens Fiederer

The application is trying to load a DLL, and failing.

If you set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1, a log will be kept of all DLLs loaded (you can use Fusion Log Viewer to see this) that will help you find out where the problem is.

Swetha_aJaX

ASKER

Its not help full
i setup the enable log to 1 but no result
is there any onther way you can see

ASKER CERTIFIED SOLUTION

Jens Fiederer

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jens Fiederer

You could try hooking the
AppDomain.AssemblyResolve event and see where it gets called....