Information message in standard error output

[Brent]

We're getting this message in our standard error output:

EagleServer.exe Information: 0 : Unit.DotsPerInch = 96

EagleServer.exe is our application.

 

This happens on the bold line below:

  using (XmlReader xmlReader = XmlReader.Create(new StringReader(entity.ReportDefinitionXml)))
                {
                    ReportXmlSerializer xmlSerializer = new ReportXmlSerializer();
                    report = (Telerik.Reporting.Report)xmlSerializer.Deserialize(xmlReader);
                }

 

The message in the standard error output causes our application to think that something failed. Is there any way we can prevent this from happening?

[Katia]

Hello Brent,

We are using TraceInformation to log the notification:

Trace.TraceInformation("Unit.DotsPerInch = {0}", Unit.dotsPerInch);

It is an informational message and should not be treated as an error by the application. I recommend checking how the output information is handled in the code, e.g. if it can recognize the type of trace information correctly.

 

Regards,
Katia
Progress Telerik

[Tursunkhuja]

Hello Katia,

Every quarter we use new Telerik.Reporting NuGet and recently in our project we updated Telerik.Reporting NuGet to R2.2020 version. After that, on starting our server app, we're getting more different messages in our standard error output.

We're getting these messages created by Telerik.Reporting:

  "Telerik Reporting Assembly Information",
   "======================================",
   "Name: Telerik.Reporting, Version=14.1.20.513, Culture=neutral, PublicKeyToken=a9d7983dfcc261be; Location:..."

Is there any way to avoid showing that message?

 

[Ivan Hristov]

Hello Tursunhuja,

These trace messages contain information with important details about Telerik Reporting assembly. This information is valuable to us because it helps us determine if our product is used on a specific platform or under specific conditions, ultimately improving the support service. The message are output with Trace.WriteLine instead of Trace.WriteInformation on purpose. However, in case you want to filter these messages, a custom EventListener could help - see this article for more information: Suppress Trace Messages From Specific DLL.

Regards,
Ivan Hristov
Progress Telerik