Using the EIF Publisher for EMAB

Using the EIF Publisher for EMAB - Please Help

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bill44077 - 06 Jul 2004 22:57 GMT

From the Logging Block documentation it seems that it would be quite simple to use the EIF Publisher for an application that already employs the EMAB. The problems seems to be that although I have made the necessary additions to the web.config file for the publisher - I get an Application Event Log error that the custom publisher could not be found. The EIF Publisher sample works correctly on my server. Are there additional things that need to be done, for example, logging dll's or something that needs to be placed in the same directory as the project? Hopefully I am just missing something simple - but I have gone over the instructions from the Logging Block - "Using the EIF Publisher for EMAB" several times with no luck.

Any thoughts or suggestions would be greatly appreciated as I need to get this working this week.

thanks in advance!
Bill

Reply to this Message

Mike Hayton [MS] - 12 Jul 2004 16:14 GMT

I dont know the answer to the question below. But I do know that there was
a separate thread about logging block questions where the team that
produced the logging block (a different one from EIF) said:

For any feedback to this please send to devfdbck@microsoft.com. We
(patterns & practices [1] )developed these extensions to EIF and would like
to here any feedback or help in anyways we can.

The title of the thread was "Please read for info on Logging Application
Block (Extensions to EIF)" from Scott Densmore (scottden@microsoft.com).

A different thread says:
----------------------------------------------------------
From: "Tom Hollander [MSFT]" <tomholl@online.microsoft.com>
Subject: Re: Where to make Inquiries?
Date: Tue, 23 Mar 2004 14:42:11 -0800
Newsgroups: microsoft.public.vsnet.enterprise.tools

Actually the preferred workspace for the Logging Application Block is:
http://workspaces.gotdotnet.com/excep
Note that this workspace is also used for discussion about the Exception
Management Application Block, given the close relationship between the two
blocks.

This workspace is monitored by Microsoft PAG, and also by other users of the
blocks who are often able to provide answers to questions.

Regards,
Tom Hollander
Microsoft PAG
------------------------------------------------------------

I think that either/both should be a place to start.
Perhaps you could post their reply?
Maybe you might like to suggest that they check this newsgroup and reply to
the logging block / EMAB questions directly?
Possibly there's someone else out there in the community who knows the
answer to this?

Sorry I couldnt be of more help

Mike

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

| From the Logging Block documentation it seems that it would be quite simple to use the EIF Publisher for an application that already employs the

EMAB. The problems seems to be that although I have made the necessary
additions to the web.config file for the publisher - I get an Application
Event Log error that the custom publisher could not be found. The EIF
Publisher sample works correctly on my server. Are there additional things
that need to be done, for example, logging dll's or something that needs to
be placed in the same directory as the project? Hopefully I am just missing
something simple - but I have gone over the instructions from the Logging
Block - "Using the EIF Publisher for EMAB" several times with no luck.

| Any thoughts or suggestions would be greatly appreciated as I need to get this working this week.
|
| thanks in advance!
| Bill

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Reply to this Message

Bill44077 - 12 Jul 2004 16:56 GMT

Hi Mike,

Thanks for the reply on this.

I am pretty confident that I have just done something incorrect in the installation of this since it appears that other folks are using the EIFPublisher. It's a little confusing since the instructions for installation in the Logging Block documentation talks mostly about installing the Logging.sln, not the EMABLogging.sln. There were references that needed to be added to this project - Common.dll had to be built and a reference added as well as both of the ExceptionManagementand .Interfaces. I had installed EMAB and needed to build those dll's as well. Then the Logging install created another directory for each of these projects (ExceptionManagement & ExceptionManagement.Interfaces).

Thanks for the suggestions. I had already posted this to the GotDotNet group and hadn't received a reply. I have actually called in for support so once I figure out what's going wrong I'll post it here in case any one else runs into the same problem as me.

thanks,
Bill

> I dont know the answer to the question below. But I do know that there was
> a separate thread about logging block questions where the team that
[quoted text clipped - 56 lines]
> | thanks in advance!
> | Bill

Reply to this Message

Mike Hayton [MS] - 12 Jul 2004 22:51 GMT

Cool :)

Thanks in advance for posting what you find out.

Mike

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

| Hi Mike,
|
| Thanks for the reply on this.
|
| I am pretty confident that I have just done something incorrect in the installation of this since it appears that other folks are using the

EIFPublisher. It's a little confusing since the instructions for
installation in the Logging Block documentation talks mostly about
installing the Logging.sln, not the EMABLogging.sln. There were references
that needed to be added to this project - Common.dll had to be built and a
reference added as well as both of the ExceptionManagementand .Interfaces.
I had installed EMAB and needed to build those dll's as well. Then the
Logging install created another directory for each of these projects
(ExceptionManagement & ExceptionManagement.Interfaces).

| Thanks for the suggestions. I had already posted this to the GotDotNet group and hadn't received a reply. I have actually called in for support so

once I figure out what's going wrong I'll post it here in case any one else
runs into the same problem as me.

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Reply to this Message

Bill44077 - 15 Jul 2004 01:30 GMT

Hi Mike,

I called in an incident with MS to help with this issue. As I had thought, it was a problem with the way that I had installed things. For one thing, you don't need to install the EMAB first since the Exception projects are actually part of the EMABLogging.sln. You do have to reference them both in the project and Common.dll needs to be built and the reference removed and re-added. It was necessary to make a logging key and install the schema and eventsinks dll's as the logging install instructions suggest.

Once this was working, we attempted to get the MSMQSinkSample working to no avail. I ended up uninstalling the samples and logging completely (including removing the dll's from the GAC). I reinstalled logging from scratch and this time both the EIFPublisher sample and the MSMQSink sample worked.

I am now working with MS to try to figure out if you can use the EIFPublisher to publish to an MSMQSink. That is my real end goal - to have the following occur:

Application using EMAB --> EIFPublisher --> MSMQSink

This should be able to be done by just installing EIF, the Logging component and then making the appropriate changes to the EnterpriseInstrumentation.config file and never touching the original application. I'll post if, with MS's help, we can get this working. Now, that would really be cool!! :)

thanks,
Bill

> Cool :)
>
[quoted text clipped - 104 lines]
> | > Use of included script samples are subject to the terms specified at
> | > http://www.microsoft.com/info/cpyright.htm

Reply to this Message

Using the EIF Publisher for EMAB - Please Help

Free Magazines