|
|
You're in the
visual studio .net enterprise tools
group:StackTrace not showing in ErrorMessageEvent in EventLog
visual studio .net enterprise tools:
Using the EIF logSink, when ErrorMessageEvents are raised,
the StackTrace information appears in the ApplicationLog of the Event viewer. However, using the Logging Code Block logSink, when ErrorMessageEvents are raised, the StackTrace information is blank (spaces) in the ApplicationLog of the Event viewer. I've tested this side by side - once raising event to EIF logSink, and next raising same event/eventsource to Logging Block logSink. This is just one field not persisted. Others are WindowsSecurity, ManagedSecurity, ProcessID, and ProcessName. I also have tried logging them to the basicLogSink and sqlSink. These values do not appear there either. How can I configure Logging Code Block logSink, basicLogSink, and sqlSink in order to persist these fields (StackTrace,WindowsSecurity, ect)? I have reviewed all the Logging Doc I have and haven't found the answer. Thank you, Tim Reynolds
Thanks for your reply, but I think you misunderstand the
issue. The sink for writing to the event log in logging block does work! It is just that the sink 'filters' or removes the values for some of the members - stacktrace - and the others mentioned. I used the same EnterpriseInstrumentation.config but used the sink provided in EIF and the values were present. I used the sink provided in the app block and they weren't. However, I am getting output in my Application Log fine - so the config file is working. There must be code in the log sink and sql sink in the Logging Block that restrict certain data. I would like to find it so I can modify it to allow that data through. Thank you, Tim Reynolds Verizon [quoted text, click to view] >-----Original Message-----
>Hi Tim, > >Thank you for using MSDN Newsgroup. I am Luke and I am review this issue >currently. As I understand, when you use Logging Block logSink, the >information hadn't been logged in the ApplicationLog. > >Normally, this knid of problem may be related to the configration in >app.config. You may refer to follow section to see if it will help: > >Validation errors not always logged for invalid >EnterpriseInstrumentation.Config files > >Normally, an event is logged to the Application log of the Windows Event >Log when an application instrumentation configuration file >(EnterpriseInstrumentation.Config) is successfully or unsuccessfully loaded >and validated. However, there are specific scenarios where the file will >be invalid but will still be successfully loaded. For instance, the >following XML fragment describes a filter element: > ><filter name="defaultSoftwareElementFilter" description="A default filter >for the Software Element event sources." /> > <eventCategoryRef name="All Events"> > <eventSinkRef name="wmiSink" /> > <eventSinkRef name="traceSink" /> > <eventSinkRef name="logSink" /> > </eventCategoryRef> > >Note that the filter tag has both the start and end tags thus excluding the >eventCategoryRef tag. This does not cause a validation error. Instead, >the "defaultSoftwareElementFilter" contains no event categories or event >sinks. The "All Events" event category reference is ignored. > >If above didn't help, can you post the app.config file you used? > >For more information on LogSink, you may refer to: > >http://download.microsoft.com/download/e/b/4/eb4fa948- f1c9-4cd1-9f93-2f259da >7de98/readme.htm >http://msdn.microsoft.com/library/default.asp? url=/library/en-us/dnpag/html/ >logging-ch03.asp > >Regards, > >Luke >Microsoft Online Support > >Get Secure! www.microsoft.com/security >(This posting is provided "AS IS", with no warranties, and confers no >rights.) > >.
Hi Tim,
Thank you for using MSDN Newsgroup. I am Luke and I am review this issue currently. As I understand, when you use Logging Block logSink, the information hadn't been logged in the ApplicationLog. Normally, this knid of problem may be related to the configration in app.config. You may refer to follow section to see if it will help: Validation errors not always logged for invalid EnterpriseInstrumentation.Config files Normally, an event is logged to the Application log of the Windows Event Log when an application instrumentation configuration file (EnterpriseInstrumentation.Config) is successfully or unsuccessfully loaded and validated. However, there are specific scenarios where the file will be invalid but will still be successfully loaded. For instance, the following XML fragment describes a filter element: <filter name="defaultSoftwareElementFilter" description="A default filter for the Software Element event sources." /> <eventCategoryRef name="All Events"> <eventSinkRef name="wmiSink" /> <eventSinkRef name="traceSink" /> <eventSinkRef name="logSink" /> </eventCategoryRef> Note that the filter tag has both the start and end tags thus excluding the eventCategoryRef tag. This does not cause a validation error. Instead, the "defaultSoftwareElementFilter" contains no event categories or event sinks. The "All Events" event category reference is ignored. If above didn't help, can you post the app.config file you used? For more information on LogSink, you may refer to: http://download.microsoft.com/download/e/b/4/eb4fa948-f1c9-4cd1-9f93-2f259da 7de98/readme.htm http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/ logging-ch03.asp Regards, Luke Microsoft Online Support Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.)
Luke,
Thanks for your reply. However, I am raising an ErrorMessageEvent which does, as you said, by default include the StackTrace member. Using the same event source/event, I have routed to traceSink and the stacktrace appears. Therefore, I know that for this event/event source, the stack trace is populated. I also tried using the same event/event source and routing to the EIF logSink and the stackTrace appears. There is some 'code' apparently in the Logging block that automatically filters off certain fields - like stacktrace. Here is the EIF config file being used. In this example, the event is writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). Only the entry in the logSink for LoggingBlock is missing the fields in question: <?xml version="1.0" encoding="utf-8"?><configuration xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/EnterpriseInstrumentation.xsd"><instrumentedApp name="VOSE.WebServices" mode="released" /><eventSources><eventSource name="VOSE Web Services" type="softwareElement" internalExceptionHandler="throw" description="This is just a test" /><eventSource name="Application" type="softwareElement" internalExceptionHandler="ignore" description="Application level event source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web Services"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef><eventSourceRef name="Application"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef></filterBindings><filters><filter name="defaultSoftwareElementFilter" description="Filter bindings for SimpleInstrumentation walkthrough."><eventCategoryRef name="All Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" /><eventSinkRef name="traceSink" /></eventCategoryRef></filter></filters><eventSinks><eventSink name="logSink" description="Outputs events to the Application Event Log." type="Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="enableFormatting" value="false" /><parameter name="machineName" value="." /></eventSink><eventSink name="EIFlogSink" description="Outputs events to the Windows Event Log." type="Microsoft.EnterpriseInstrumentation.EventSinks.LogEventSink"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="machineName" value="." /></eventSink><eventSink name="traceSink" description="Outputs events to the Windows Event Trace." type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink"><parameter name="sessionName" value="TraceSession" /></eventSink></eventSinks><eventCategories><eventCategory name="All Events" description="A category that contains all events."><event type="System.Object" /></eventCategory></eventCategories></configuration> I believe the logging block sinks are removing the values for these fields and I need the fields to log to DB. So, whatever help you find for Log Sink Logging Block, I'll need same help for basicLogSink & sqlSink of Logging Block since they also remove the values. Thank you, Tim REynolds Verizon
Luke
Posting again using registered email-ID as MSDN universal subscriber - getting used to new form for posting messages Also, I did not receive the typical reply email with your last Post, Luke. Thanks for your reply. However, I am raising an ErrorMessageEvent which does, as you said, by default include the StackTrace member. Using the same event source/event, I have routed to traceSink and the stacktrace appears. Therefore, I know that for this event/event source, the stack trace is populated. I also tried using the same event/event source and routing to the EIF logSink and the stackTrace appears. There is some 'code' apparently in the Logging block that automatically filters off certain fields - like stacktrace. Here is the EIF config file being used. In this example, the event is writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). Only the entry in the logSink for LoggingBlock is missing the fields in question <?xml version="1.0" encoding="utf-8"?><configuration xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/EnterpriseInstrumentation.xsd"><instrumentedApp name="VOSE.WebServices" mode="released" /><eventSources><eventSource name="VOSE Web Services" type="softwareElement" internalExceptionHandler="throw" description="This is just a test" /><eventSource name="Application" type="softwareElement" internalExceptionHandler="ignore" description="Application level event source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web Services"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef><eventSourceRef name="Application"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef></filterBindings><filters><filter name="defaultSoftwareElementFilter" description="Filter bindings for SimpleInstrumentation walkthrough."><eventCategoryRef name="All Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" /><eventSinkRef name="traceSink" /></eventCategoryRef></filter></filters><eventSinks><eventSink name="logSink" description="Outputs events to the Application Event Log." type="Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="enableFormatting" value="false" /><parameter name="machineName" value="." /></eventSink><eventSink name="EIFlogSink" description="Outputs events to the Windows Event Log." type="Microsoft.EnterpriseInstrumentation.EventSinks.LogEventSink"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="machineName" value="." /></eventSink><eventSink name="traceSink" description="Outputs events to the Windows Event Trace." type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink"><parameter name="sessionName" value="TraceSession" /></eventSink></eventSinks><eventCategories><eventCategory name="All Events" description="A category that contains all events."><event type="System.Object" /></eventCategory></eventCategories></configuration I believe the logging block sinks are removing the values for these fields and I need the fields to log to DB. So, whatever help you find for Log Sink Logging Block, I'll need same help for basicLogSink & sqlSink of Logging Block since they also remove the values Thank you Tim REynold
Hi Tim,
If a property group filter is not specified, Enterprise Instrumentation uses the default property group population behavior. This behavior differs from event to event. For example, events derived from TraceEvent will not, by default, populate the StackTrace property (part of the PopulateDebugInfo property group filter) since this is very expensive. However, events derived from ErrorEvent will, by default, populate this property. You can override the default population behavior for any event source by specifying the appropriate property group filter name and true/false value as an event source parameter. Each event source (including request event sources) can individually control which event fields are populated. The following example indicates that, for the SecureRequestTrace event source, Windows security context fields should be populated: <eventSource name="SecureRequestTrace" type="request" internalExceptionHandler="ignore" > <eventSourceParameter name="PopulateWindowsSecurityInfo" value="True" /> </eventSource> If above didn't help, can you post the EnterpriseInstrumentation.config you used for our research. Thank you for using MSDN Newsgroup. I am Luke and I am review this issue currently. Luke Microsoft Online Support Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.)
Tim,
I came across this post today, and I had the same issue you did. I looked in the source code of the logging application block and there is a bug in the CommonEvent code. The logging application block does some custom serialisation for raising the event into xml form and part of that serialisation (that EIF calls into) is a function called PrepareForSerialization. Go to the CommonEvent.cs file in the Logging AB solution's Schema project and have a look in: PrepareForSerialization(EventSource eventSource, RequestContext requestContext) function and remove the line that says: buffer = EventFormatter.BuildBuffer(this); This shouldn't really be building a cached buffer yet in PrepareForSerialization as not all the child classes have finished execution of their PrepareForSerialization (and populated their properties like StackTrace). The buffer call is redundant and not appropriate (IMHO) anyway here as the proper place for it (and where it is actually called anyway) is in the serialisation itself... see GetXmlStream in CommonEvent which actually checks if the buffer is built, and if not then builds it. This is my opinion, and although i've tested is somewhat, I can't take any responsibility for it. Also, the bug was raised in the gotdotnet site... see http://www.gotdotnet.com/Community/Workspaces/workspace.aspx?id=c1146b3a-3f9b-47b8-899e-f42e667cdccf in the BugTracker area, but nothing has moved there as far as I can tell. Once you get the stack trace working, you realise that some classes that are properties, like DiagnoticsEvent.ComPlus (which is ComPlusInfo) do serialise in EIF but not with the logging AB (also see WindowsSecurityInfo and ManagedSecurityInfo). My opinion is that this behaviour is lacking but it may not have been intended to work this way. I changed the EventFormatter.GetProperties to recursively call itself if the class has an InstrumentationType attribute. This is a bit tricky as you should possibly worry about circular references, but the code seems to work. I won't post here as its fairly extensive, but email me if you need the code. Essentially, my implementation used the same event schema and flattened the properties into (for example) <event:NameValuePair name="ComPlus.ActivityID" value="" /> Once these two changes were made, I intend to use the logging AB in production code and in mid-development now. Hope this helps. Doug Burke Infosys Australia [quoted text, click to view] Tim Reynolds <timreynolds@onlineverizon.com> wrote in message news:<01BD3957-6F68-4977-8070-A8BBFDBDDBC2@microsoft.com>... which does, as you said, by default include the StackTrace member. > Luke, > > Posting again using registered email-ID as MSDN universal subscriber - getting used to new form for posting messages: > Also, I did not receive the typical reply email with your last Post, Luke. > > Thanks for your reply. However, I am raising an ErrorMessageEvent Using the same event source/event, I have routed to traceSink and the stacktrace appears. Therefore, I know that for this event/event source, the stack trace is populated. I also tried using the same event/event source and routing to the EIF logSink and the stackTrace appears. There is some 'code' apparently in the Logging block that automatically filters off certain fields - like stacktrace. [quoted text, click to view] > xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/EnterpriseInstrumentation.xsd"><instrumentedApp> Here is the EIF config file being used. In this example, the event is writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). Only the entry in the logSink for LoggingBlock is missing the fields in question: > <?xml version="1.0" encoding="utf-8"?><configuration name="VOSE.WebServices" mode="released" /><eventSources><eventSource name="VOSE Web Services" type="softwareElement" internalExceptionHandler="throw" description="This is just a test" /><eventSource name="Application" type="softwareElement" internalExceptionHandler="ignore" description="Application level event source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web Services"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef><eventSourceRef name="Application"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef></filterBindings><filters><filter name="defaultSoftwareElementFilter" description="Filter bindings for SimpleInstrumentation walkthrough."><eventCategoryRef name="All Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" /><eventSinkRef name="traceSink" /></eventCategoryRef></filter></filters><eventSinks><eventSink name="logSink" description="Outputs events to the Application Event Log." type="Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="enableFormatting" value="false" /><parameter name="machineName" value="." /></eventSink><eventSink name="EIFlogSink" description="Outputs events to the Windows Event Log." type="Microsoft.EnterpriseInstrumentation.EventSinks.LogEventSink"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="machineName" value="." /></eventSink><eventSink name="traceSink" description="Outputs events to the Windows Event Trace." type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink"><parameter name="sessionName" value="TraceSession" /></eventSink></eventSinks><eventCategories><eventCategory name="All Events" description="A category that contains all events."><event type="System.Object" /></eventCategory></eventCategories></configuration> [quoted text, click to view] >
> I believe the logging block sinks are removing the values for these fields and I need the fields to log to DB. So, whatever help you find for Log Sink Logging Block, I'll need same help for basicLogSink & sqlSink of Logging Block since they also remove the values. > > Thank you, > Tim REynolds
Hi Tim,
I don't think there is any filter in the ApplicationBlock Logging. Here is the source code of WriteToEventLog private void WriteToEventLog(string message, EventLogEntryType entryType) { StringBuilder errorString; if( message == null ) { return; } if (message.Length < ResourceTable.EventlogMaxLogStringLength) { this.eventLog.WriteEntry(message, entryType); } else { errorString = new StringBuilder(message); errorString.Insert(0, "<eventLogData><![CDATA["); errorString.Remove(ResourceTable.EventlogMaxLogStringLength - 255, (errorString.Length - ResourceTable.EventlogMaxLogStringLength) + 255 ); errorString.Append("]]></eventLogData>"); this.eventLog.WriteEntry(errorString.ToString(), entryType); throw new SystemException(ResourceTable.GetString(ResourceTable.StringTooLongForEventL og)); } } And it will be called in WriteToLogWithRetry of BaseSink. I think you may add some debug code here and recompile the assembly, to check if the message passed here is null, or this method is never called for StackTrace. The possible reason for the problem may be that the message will missed when event message was formated or encode. Luke Microsoft Online Support Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.) 1
Luke,
I appreciate your research into this. However, the reason I am writing Microsoft about this bug is because they have produced this logging block. The team that put it together needs to determine if this is a bug, they should put the debug code in and recompile and test. I am the user of the product and would like Microsoft to support this product. You are basically doing what I was doing, looking in the code. I have done that and would like you (Microsoft) to confirm that they get the same results as me - that when they use the Logging Application Block sinks, for the errorMessageEvent, stack trace and other properties are not persisted. If that is the case, then they should either document that this was the design or fix. Please confirm that stacktrace as well as some other fields are not persisted using the Logging Application Block sinks for the ErrorMessageEvent. Please confirm if this is by design. If not, please provide the code fix. Thank you very much, Tim Reynolds
Doug,
Thanks alot for this code! I did comment out the one line in CommonEvent.cs, followed by uninstalling and reinstalling - and it did cause Stack Trace to appear. Then I made your other changes (the ones you emailed me) and got the other changes - the display of WindowsSecurityInfo & ManagedSecurityInfo. This was a big help! Thanks alot, Tim Reynolds Verizon Tampa, FL Microsoft, are you going to produce your own fix for these issues?
Hi Tim,
Currently I am finding more resource and trying to assist you on this issue. Once I made some progress, I will update you as soon as possible. Luke Microsoft Online Support Get Secure! www.microsoft.com/security (This posting is provided "AS IS", with no warranties, and confers no rights.)
Microsoft
Shall I expect the 2 day response from you on reply's or just on first time posts? I replied over 2 days ago to this last Microsoft reponse and have not heard back yet Also, can you please explain what this statement means "*MSDN Subscribers (excluding Library) should use a unique no-spam newsgroup alias for each program. Users should use their program specific unique no-spam newsgroup alias within the specific newsgroups for the designated program. You should also follow your respective program guidelines to assure that your posts are recognized. " from the Managed Newsgroups page Is this saying I should use one registered alias for each program as in logging block is a program, C# is a program, ??? and WHat are the respective program guidelines (or where are they) Thank you Tim Reynold Verizo Contact Us | MSDN Flash Newsletter | Legal
Tim, Luke
You may want to try the following email address: From an earlier posting.... -------------------- From: "Scott Densmore" <scottden@microsoft.com> Subject: Please read for info on Logging Application Block (Extensions to EIF) Date: Fri, 7 Nov 2003 10:22:10 -0800 Newsgroups: microsoft.public.vsnet.enterprise.tools 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. thanks, scott -------------------- I can help on the internals of EIF - but I dont really know anything about the internals on the Logging Block. There was an eariler reply in this thread by Doug Burke - I take it doesnt solve the problem for you? I will also email this thread directly to Scott Densmore @ microsoft and see if we can get some better turn around from the Logging Block people. Mike -------------------- | Luke, Thanks for your reply. However, I am raising an ErrorMessageEvent which does, as you said, by default include the StackTrace member. Using the same event source/event, I have routed to traceSink and the stacktrace appears. Therefore, I know that for this event/event source, the stack trace is populated. I also tried using the same event/event source and routing to the EIF logSink and the stackTrace appears. There is some 'code' apparently in the Logging block that automatically filters off certain fields - like stacktrace. Here is the EIF config file being used. In this example, the event is writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). Only the entry in the logSink for LoggingBlock is missing the fields in question: <?xml version="1.0" encoding="utf-8"?><configuration xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/Enterpri seInstrumentation.xsd"><instrumentedApp name="VOSE.WebServices" mode="released" /><eventSources><eventSource name="VOSE Web Services" type="softwareElement" internalExceptionHandler="throw" description="This is just a test" /><eventSource name="Application" type="softwareElement" internalExceptionHandler="ignore" description="Application level event source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web Services"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef><eventSourceRef name="Application"><filterRef name="defaultSoftwareElementFilter" /></eventSourceRef></filterBindings><filters><filter name="defaultSoftwareElementFilter" description="Filter bindings for SimpleInstrumentation walkthrough."><eventCategoryRef name="All Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" /><eventSinkRef name="traceSink" /></eventCategoryRef></filter></filters><eventSinks><eventSink name="logSink" description="Outputs events to the Application Event Log." type="Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"><parameter name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="enableFormatting" value="false" /><parameter name="machineName" value="." /></eventSink><eventSink name="EIFlogSink" description="Outputs events to the Windows Event Log." type="Microsoft.EnterpriseInstrumentation.EventSinks.LogEventSink"><paramete r name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter name="defaultEntryType" value="Information" /><parameter name="machineName" value="." /></eventSink><eventSink name="traceSink" description="Outputs events to the Windows Event Trace." type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink"><parame ter name="sessionName" value="TraceSession" /></eventSink></eventSinks><eventCategories><eventCategory name="All Events" description="A category that contains all events."><event type="System.Object" /></eventCategory></eventCategories></configuration> I believe the logging block sinks are removing the values for these fields and I need the fields to log to DB. So, whatever help you find for Log Sink Logging Block, I'll need same help for basicLogSink & sqlSink of Logging Block since they also remove the values. Thank you, Tim REynolds Verizon | -- 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
Hi, Tim
The engineer assigned to this issue works at our North Carolina Site, which is closed due to inclement weather. I apologise for the delay John Eikanger Microsoft Developer Support -------------------- | Newsgroups: microsoft.public.vsnet.enterprise.tools | From: lukezhan@online.microsoft.com (MSFT) | Organization: Microsoft | Date: Fri, 23 Jan 2004 09:02:34 GMT | Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog | X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools | MIME-Version: 1.0 | Content-Type: text/plain | Content-Transfer-Encoding: 7bit | | Hi Tim, | | Currently I am finding more resource and trying to assist you on this | issue. Once I made some progress, I will update you as soon as possible. | | Luke | Microsoft Online Support | | Get Secure! www.microsoft.com/security | (This posting is provided "AS IS", with no warranties, and confers no | rights.) |
Hi Tim,
I wanted to update you that we are working on this issue. I do understand that this is an imprortant issue for you, hopefully we should have more information in a couple of days. I apologize for the delay....please let us know if you have any questions.. Regards, Barath 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 -------------------- [quoted text, click to view] >X-Tomcat-ID: 560731155 <wgN$Ag02DHA.3532@cpmsftngxa07.phx.gbl> >References: <002201c3daca$49ac3f60$a501280a@phx.gbl> <042d01c3db6c$dc6e1a60$a001280a@phx.gbl> <vSfrEwA3DHA.432@cpmsftngxa08.phx.gbl> <86AC68E2-45A1-4B08-A293-2C6365B88480@microsoft.com> [quoted text, click to view] >MIME-Version: 1.0
>Content-Type: text/plain >Content-Transfer-Encoding: 7bit >From: mikehayt_@online.microsoft.com (Mike Hayton [MS]) >Organization: Microsoft >Date: Tue, 27 Jan 2004 18:07:42 GMT >Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog >X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools >Message-ID: <JSvE4BQ5DHA.2920@cpmsftngxa07.phx.gbl> >Newsgroups: microsoft.public.vsnet.enterprise.tools >Lines: 117 >Path: cpmsftngxa07.phx.gbl >Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.enterprise.tools:1681 >NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182 > >Tim, Luke > >You may want to try the following email address: > >From an earlier posting.... >-------------------- >From: "Scott Densmore" <scottden@microsoft.com> >Subject: Please read for info on Logging Application Block (Extensions to >EIF) >Date: Fri, 7 Nov 2003 10:22:10 -0800 >Newsgroups: microsoft.public.vsnet.enterprise.tools > >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. > >thanks, >scott >-------------------- > >I can help on the internals of EIF - but I dont really know anything about >the internals on the Logging Block. >There was an eariler reply in this thread by Doug Burke - I take it doesnt >solve the problem for you? >I will also email this thread directly to Scott Densmore @ microsoft and >see if we can get some better turn around from the Logging Block people. > >Mike > > >-------------------- >| Luke, >Thanks for your reply. However, I am raising an ErrorMessageEvent which >does, as you said, by default include the StackTrace member. Using the >same event source/event, I have routed to traceSink and the stacktrace >appears. Therefore, I know that for this event/event source, the stack >trace is populated. I also tried using the same event/event source and >routing to the EIF logSink and the stackTrace appears. There is some >'code' apparently in the Logging block that automatically filters off >certain fields - like stacktrace. > >Here is the EIF config file being used. In this example, the event is >writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). >Only the entry in the logSink for LoggingBlock is missing the fields in >question: ><?xml version="1.0" encoding="utf-8"?><configuration >xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/Enterpr i >seInstrumentation.xsd"><instrumentedApp name="VOSE.WebServices" >mode="released" /><eventSources><eventSource name="VOSE Web Services" >type="softwareElement" internalExceptionHandler="throw" description="This >is just a test" /><eventSource name="Application" type="softwareElement" >internalExceptionHandler="ignore" description="Application level event >source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web >Services"><filterRef name="defaultSoftwareElementFilter" >/></eventSourceRef><eventSourceRef name="Application"><filterRef >name="defaultSoftwareElementFilter" >/></eventSourceRef></filterBindings><filters><filter >name="defaultSoftwareElementFilter" description="Filter bindings for >SimpleInstrumentation walkthrough."><eventCategoryRef name="All >Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" >/><eventSinkRef name="traceSink" >/></eventCategoryRef></filter></filters><eventSinks><eventSink >name="logSink" description="Outputs events to the Application Event Log." >type="Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, >Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, >Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"><parameter >name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter >name="defaultEntryType" value="Information" /><parameter >name="enableFormatting" value="false" /><parameter name="machineName" >value="." /></eventSink><eventSink name="EIFlogSink" description="Outputs >events to the Windows Event Log." >type="Microsoft.EnterpriseInstrumentation.EventSinks.LogEventSink"><paramet e >r name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter >name="defaultEntryType" value="Information" /><parameter name="machineName" >value="." /></eventSink><eventSink name="traceSink" description="Outputs >events to the Windows Event Trace." >type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink"><param e >ter name="sessionName" value="TraceSession" >/></eventSink></eventSinks><eventCategories><eventCategory name="All >Events" description="A category that contains all events."><event >type="System.Object" /></eventCategory></eventCategories></configuration> > >I believe the logging block sinks are removing the values for these fields >and I need the fields to log to DB. So, whatever help you find for Log >Sink Logging Block, I'll need same help for basicLogSink & sqlSink of >Logging Block since they also remove the values. > >Thank you, >Tim REynolds >Verizon > > >| > >-- > >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 > >
Hi Tim,
I apologize for the delay in posting an update....I've been working on this issue and unfortunately the only information i have (which you already know) is that it is a bug in the LAB. I'll try to send you an update again this week. Thx Barath 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 -------------------- [quoted text, click to view] >X-Tomcat-ID: 57512981 <wgN$Ag02DHA.3532@cpmsftngxa07.phx.gbl> >References: <002201c3daca$49ac3f60$a501280a@phx.gbl> <042d01c3db6c$dc6e1a60$a001280a@phx.gbl> <vSfrEwA3DHA.432@cpmsftngxa08.phx.gbl> <86AC68E2-45A1-4B08-A293-2C6365B88480@microsoft.com> <JSvE4BQ5DHA.2920@cpmsftngxa07.phx.gbl> [quoted text, click to view] >MIME-Version: 1.0
>Content-Type: text/plain >Content-Transfer-Encoding: 7bit >From: bvasude@online.microsoft.com (Barath Vasudevan [MS]) >Organization: Microsoft >Date: Thu, 29 Jan 2004 04:52:41 GMT >Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog >X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools >Message-ID: <CKQj9Oi5DHA.3496@cpmsftngxa07.phx.gbl> >Newsgroups: microsoft.public.vsnet.enterprise.tools >Lines: 155 >Path: cpmsftngxa07.phx.gbl >Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.enterprise.tools:1690 >NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182 > >Hi Tim, > >I wanted to update you that we are working on this issue. I do understand >that this is an imprortant issue for you, hopefully we should have more >information in a couple of days. > >I apologize for the delay....please let us know if you have any questions.. >Regards, > >Barath >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 > >-------------------- >>X-Tomcat-ID: 560731155 >>References: <002201c3daca$49ac3f60$a501280a@phx.gbl> ><wgN$Ag02DHA.3532@cpmsftngxa07.phx.gbl> ><042d01c3db6c$dc6e1a60$a001280a@phx.gbl> ><vSfrEwA3DHA.432@cpmsftngxa08.phx.gbl> ><86AC68E2-45A1-4B08-A293-2C6365B88480@microsoft.com> >>MIME-Version: 1.0 >>Content-Type: text/plain >>Content-Transfer-Encoding: 7bit >>From: mikehayt_@online.microsoft.com (Mike Hayton [MS]) >>Organization: Microsoft >>Date: Tue, 27 Jan 2004 18:07:42 GMT >>Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog >>X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools >>Message-ID: <JSvE4BQ5DHA.2920@cpmsftngxa07.phx.gbl> >>Newsgroups: microsoft.public.vsnet.enterprise.tools >>Lines: 117 >>Path: cpmsftngxa07.phx.gbl >>Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.enterprise.tools:1681 >>NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182 >> >>Tim, Luke >> >>You may want to try the following email address: >> >>From an earlier posting.... >>-------------------- >>From: "Scott Densmore" <scottden@microsoft.com> >>Subject: Please read for info on Logging Application Block (Extensions to >>EIF) >>Date: Fri, 7 Nov 2003 10:22:10 -0800 >>Newsgroups: microsoft.public.vsnet.enterprise.tools >> >>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. >> >>thanks, >>scott >>-------------------- >> >>I can help on the internals of EIF - but I dont really know anything about >>the internals on the Logging Block. >>There was an eariler reply in this thread by Doug Burke - I take it doesnt >>solve the problem for you? >>I will also email this thread directly to Scott Densmore @ microsoft and >>see if we can get some better turn around from the Logging Block people. >> >>Mike >> >> >>-------------------- >>| Luke, >>Thanks for your reply. However, I am raising an ErrorMessageEvent which >>does, as you said, by default include the StackTrace member. Using the >>same event source/event, I have routed to traceSink and the stacktrace >>appears. Therefore, I know that for this event/event source, the stack >>trace is populated. I also tried using the same event/event source and >>routing to the EIF logSink and the stackTrace appears. There is some >>'code' apparently in the Logging block that automatically filters off >>certain fields - like stacktrace. >> >>Here is the EIF config file being used. In this example, the event is >>writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). >>Only the entry in the logSink for LoggingBlock is missing the fields in >>question: >><?xml version="1.0" encoding="utf-8"?><configuration >>xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/Enterp r >i >>seInstrumentation.xsd"><instrumentedApp name="VOSE.WebServices" >>mode="released" /><eventSources><eventSource name="VOSE Web Services" >>type="softwareElement" internalExceptionHandler="throw" description="This >>is just a test" /><eventSource name="Application" type="softwareElement" >>internalExceptionHandler="ignore" description="Application level event >>source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web >>Services"><filterRef name="defaultSoftwareElementFilter" >>/></eventSourceRef><eventSourceRef name="Application"><filterRef >>name="defaultSoftwareElementFilter" >>/></eventSourceRef></filterBindings><filters><filter >>name="defaultSoftwareElementFilter" description="Filter bindings for >>SimpleInstrumentation walkthrough."><eventCategoryRef name="All >>Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" >>/><eventSinkRef name="traceSink" >>/></eventCategoryRef></filter></filters><eventSinks><eventSink >>name="logSink" description="Outputs events to the Application Event Log." >>type="Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, >>Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0, >>Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"><parameter >>name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter >>name="defaultEntryType" value="Information" /><parameter >>name="enableFormatting" value="false" /><parameter name="machineName" >>value="." /></eventSink><eventSink name="EIFlogSink" description="Outputs >>events to the Windows Event Log." >>type="Microsoft.EnterpriseInstrumentation.EventSinks.LogEventSink"><parame t >e >>r name="entryTypeFieldName" value="EventLogEntryTypeID" /><parameter >>name="defaultEntryType" value="Information" /><parameter >name="machineName" >>value="." /></eventSink><eventSink name="traceSink" description="Outputs >>events to the Windows Event Trace." >>type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink"><para m >e >>ter name="sessionName" value="TraceSession"
Hi Tim,
I found from the the LAB team that this behavior will be fixed in the next release of the LAB. There is no ETA on when the re-release would happen,hopefully at the earliest. I apologize for the delay in getting you this answer. Please let us know if you have any questions. Thx Barath 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 -------------------- [quoted text, click to view] >Newsgroups: microsoft.public.vsnet.enterprise.tools Log." >From: bvasude@online.microsoft.com (Barath Vasudevan [MS]) >Organization: Microsoft >Date: Tue, 03 Feb 2004 21:54:37 GMT >Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog >X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools >MIME-Version: 1.0 >Content-Type: text/plain >Content-Transfer-Encoding: 7bit > >Hi Tim, > >I apologize for the delay in posting an update....I've been working on this >issue and unfortunately the only information i have (which you already >know) is that it is a bug in the LAB. > >I'll try to send you an update again this week. >Thx > >Barath >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 > >-------------------- >>X-Tomcat-ID: 57512981 >>References: <002201c3daca$49ac3f60$a501280a@phx.gbl> ><wgN$Ag02DHA.3532@cpmsftngxa07.phx.gbl> ><042d01c3db6c$dc6e1a60$a001280a@phx.gbl> ><vSfrEwA3DHA.432@cpmsftngxa08.phx.gbl> ><86AC68E2-45A1-4B08-A293-2C6365B88480@microsoft.com> ><JSvE4BQ5DHA.2920@cpmsftngxa07.phx.gbl> >>MIME-Version: 1.0 >>Content-Type: text/plain >>Content-Transfer-Encoding: 7bit >>From: bvasude@online.microsoft.com (Barath Vasudevan [MS]) >>Organization: Microsoft >>Date: Thu, 29 Jan 2004 04:52:41 GMT >>Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog >>X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools >>Message-ID: <CKQj9Oi5DHA.3496@cpmsftngxa07.phx.gbl> >>Newsgroups: microsoft.public.vsnet.enterprise.tools >>Lines: 155 >>Path: cpmsftngxa07.phx.gbl >>Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.enterprise.tools:1690 >>NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182 >> >>Hi Tim, >> >>I wanted to update you that we are working on this issue. I do understand >>that this is an imprortant issue for you, hopefully we should have more >>information in a couple of days. >> >>I apologize for the delay....please let us know if you have any questions.. >>Regards, >> >>Barath >>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 >> >>-------------------- >>>X-Tomcat-ID: 560731155 >>>References: <002201c3daca$49ac3f60$a501280a@phx.gbl> >><wgN$Ag02DHA.3532@cpmsftngxa07.phx.gbl> >><042d01c3db6c$dc6e1a60$a001280a@phx.gbl> >><vSfrEwA3DHA.432@cpmsftngxa08.phx.gbl> >><86AC68E2-45A1-4B08-A293-2C6365B88480@microsoft.com> >>>MIME-Version: 1.0 >>>Content-Type: text/plain >>>Content-Transfer-Encoding: 7bit >>>From: mikehayt_@online.microsoft.com (Mike Hayton [MS]) >>>Organization: Microsoft >>>Date: Tue, 27 Jan 2004 18:07:42 GMT >>>Subject: RE: StackTrace not showing in ErrorMessageEvent in EventLog >>>X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools >>>Message-ID: <JSvE4BQ5DHA.2920@cpmsftngxa07.phx.gbl> >>>Newsgroups: microsoft.public.vsnet.enterprise.tools >>>Lines: 117 >>>Path: cpmsftngxa07.phx.gbl >>>Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.enterprise.tools:1681 >>>NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182 >>> >>>Tim, Luke >>> >>>You may want to try the following email address: >>> >>>From an earlier posting.... >>>-------------------- >>>From: "Scott Densmore" <scottden@microsoft.com> >>>Subject: Please read for info on Logging Application Block (Extensions to >>>EIF) >>>Date: Fri, 7 Nov 2003 10:22:10 -0800 >>>Newsgroups: microsoft.public.vsnet.enterprise.tools >>> >>>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. >>> >>>thanks, >>>scott >>>-------------------- >>> >>>I can help on the internals of EIF - but I dont really know anything >about >>>the internals on the Logging Block. >>>There was an eariler reply in this thread by Doug Burke - I take it >doesnt >>>solve the problem for you? >>>I will also email this thread directly to Scott Densmore @ microsoft and >>>see if we can get some better turn around from the Logging Block people. >>> >>>Mike >>> >>> >>>-------------------- >>>| Luke, >>>Thanks for your reply. However, I am raising an ErrorMessageEvent which >>>does, as you said, by default include the StackTrace member. Using the >>>same event source/event, I have routed to traceSink and the stacktrace >>>appears. Therefore, I know that for this event/event source, the stack >>>trace is populated. I also tried using the same event/event source and >>>routing to the EIF logSink and the stackTrace appears. There is some >>>'code' apparently in the Logging block that automatically filters off >>>certain fields - like stacktrace. >>> >>>Here is the EIF config file being used. In this example, the event is >>>writtent to tracesink (EIF), logsink(EIF), and logSink(Logging Block). >>>Only the entry in the logSink for LoggingBlock is missing the fields in >>>question: >>><?xml version="1.0" encoding="utf-8"?><configuration >>>xmlns="http://www.microsoft.com/schema/EnterpriseInstrumentation/v1/Enter p >r >>i >>>seInstrumentation.xsd"><instrumentedApp name="VOSE.WebServices" >>>mode="released" /><eventSources><eventSource name="VOSE Web Services" >>>type="softwareElement" internalExceptionHandler="throw" description="This >>>is just a test" /><eventSource name="Application" type="softwareElement" >>>internalExceptionHandler="ignore" description="Application level event >>>source." /></eventSources><filterBindings><eventSourceRef name="VOSE Web >>>Services"><filterRef name="defaultSoftwareElementFilter" >>>/></eventSourceRef><eventSourceRef name="Application"><filterRef >>>name="defaultSoftwareElementFilter" >>>/></eventSourceRef></filterBindings><filters><filter >>>name="defaultSoftwareElementFilter" description="Filter bindings for >>>SimpleInstrumentation walkthrough."><eventCategoryRef name="All >>>Events"><eventSinkRef name="logSink" /><eventSinkRef name="EIFlogSink" >>>/><eventSinkRef name="traceSink" >>>/></eventCategoryRef></filter></filters><eventSinks><eventSink >>>name="logSink" description="Outputs events to the Application Event
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |