[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.

Swetha_aJaXAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jens FiedererTest Developer/ValidatorCommented:
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.
0
Swetha_aJaXAuthor Commented:
Its not help full
i setup the enable log to 1 but no result
is there any onther way you can see
0
Jens FiedererTest Developer/ValidatorCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jens FiedererTest Developer/ValidatorCommented:
You could try hooking the
AppDomain.AssemblyResolve  event and see where it gets called....
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.