473,405 Members | 2,287 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,405 software developers and data experts.

Microsoft Application Blocks for .Net - Logging Block

Hi

I am trying to use the Logging Module provided by Microsoft Application Blocks for .Net .

I installed everything as per the Instructions given in the 'Development Using the Logging Block'.

But when i am trying to run the sample, i am getting the following error in the Event Viwer.
Kindly help me on this.

Waiting for your reply.

Thanks and regards

---------------Error Messge in Event Viewer------------------------

Unable to read and validate the configuration file C:\Program Files\Microsoft Application Blocks for .Net\Logging\Samples\VB\LogLevelSample\bin\Enterpr iseInstrumentation.config. The following type(s) cannot be loaded:

Microsoft.ApplicationBlocks.Logging.EventSinks.Wmi EventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.EventSinks.Bas icLogEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.EventSinks.Log EventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.EventSinks.Log EventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.EventSinks.Msm qEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.EventSinks.Sql ServerEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Meterin gEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Adminis trativeEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AdminMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AuditEv ent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AuditMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AuditOp erationEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.BaseEve nt, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.CommonE vent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.ComPlus Info, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Diagnos ticEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.ErrorEv ent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.ErrorMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Externa lErrorEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Externa lErrorMessageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Interna lErrorEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Interna lErrorMessageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Managed SecurityInfo, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceCa llEnterEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceCa llEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceCa llReturnEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceDa tabaseCommandEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceDa tabaseEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEv ent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEx ternalCallEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEx ternalEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEx ternalReturnEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Windows SecurityInfo, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Adminis trativeEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AdminMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AuditEv ent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AuditMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.AuditOp erationEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.BaseEve nt, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.CommonE vent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.ComPlus Info, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Diagnos ticEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.ErrorEv ent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.ErrorMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Externa lErrorEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Externa lErrorMessageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Interna lErrorEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Interna lErrorMessageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Managed SecurityInfo, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceCa llEnterEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceCa llEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceCa llReturnEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceDa tabaseCommandEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceDa tabaseEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEv ent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEx ternalCallEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEx ternalEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceEx ternalReturnEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.TraceMe ssageEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Windows SecurityInfo, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Microsoft.ApplicationBlocks.Logging.Schema.Meterin gEvent, Microsoft.ApplicationBlocks.Logging.Schema, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd42fb0c69be8a79

Please check the event & eventSink element's type attribute in the configuration file, and that these types are correctly installed on the system.

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

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

---
Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/
Jul 21 '05 #1
0 2204

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

3
by: Karuppasamy | last post by:
Hi I am trying to use the Logging Module provided by Microsoft Application Blocks for .Net . I installed everything as per the Instructions given in the 'Development Using the Logging Block'. ...
0
by: karthick | last post by:
Hi: I have an n- tier application where a web app calls a web service to get/set info. My web app is configured to use the caching, exception and logging block of the june version of Enterprise...
5
by: Steven Nagy | last post by:
Hi All, I just wanted some feedback about which Application blocks people are using and why. Are they worth the time to learn? Do they increase development speed over time? I just want your...
0
by: kplkumar | last post by:
Hi I am new to Application blocks. I started playing around with logging. It's pretty cool, but the TextFormatter provided with it has limited options. Like for example, I need the namespace and...
7
by: amitos | last post by:
Hi! I consider using the Logging Application Block, Enterprise Library, Jan 2006 in a major project. To date, I've found that some of its features are not very well documented. One important...
3
by: Dick | last post by:
How do I integrating ASP.NET Tracing with the Enterprise Library Logging Application Block? I guess this should be possible and in a similar way to the way ASP.NET Tracing is integrated with...
5
by: lds | last post by:
I am in the process of trying to migrate some of our existing .NET applications from version 1.1 to 2.0. In our 1.1 apps we have a common assembly that uses the sqlhelper.vb class from the...
4
by: Mukesh | last post by:
Hi I m using microsoft application blocks Enterprise Library june 2005 with .net framework 1.1 and VStudio2003 And C# as coding language Sql server 2000 database the project is running...
3
by: Mukesh | last post by:
Thx Sloan for the solution. It is working properly under Full trust When i tried it under Medium trust it was giving error Parser Error Message: Required permissions cannot be acquired....
2
by: Anup Daware | last post by:
Hi Group, Can somebody tell me where I can find the internals of Logging application block 2.0/3.0. I need answers for the questions like: What best practices have followed in the...
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
0
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
0
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.