Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

MES Web API diagnostic log flags

  • Last UpdatedAug 07, 2025
  • 2 minute read

Use the following flags to log MES Web API diagnostic information.

FactMES.Server.TransactionAdaptor Assembly

Most flags in this assembly are common to trace the calls originating from the MES Web API or from database maintenance activities.

Flag

Description

LogDeadlocksAndTimeouts

Logs the information when the transaction is deadlocked (intermediate transactions) or timed out. This logging applies to calls that originate from the MES Web API or from the middleware maintenance services. While the XML request might be retried several times and is finally successful, enabling this flag logs the intermediate failures and retries.

LogMesServiceCalls

Logs the information about the calls that originated from the database maintenance service. This logging applies to calls that are requesting datasets or the calls that change data in the database.

LogTimeZoneConversionAmbiguities

Logs time zone conversion ambiguities.

When converting the local time to UTC, the local time could be ambiguous when the local region is changing between standard time and daylight savings time. For example, in the U.S.:

  • When changing from daylight savings time to standard time, there will be two instances of the hour from 1–2 am.

  • When changing from standard time to daylight savings time, there will be no hour from 2–3 am.

    The middleware will identify these ambiguities and adjust the times accordingly. Turning this flag on will log the adjustment information.

LogTransactionCompleteExecCmdTransId

Logs the information only when the execution (data write) is successful from the middleware. This logging applies to calls that originate from the MES Web API or from the middleware maintenance services. The information contains how long the execution took to complete the transaction along with the XML request.

LogTransactionCompleteGetDSTz

Logs the information only when the dataset (data read) is successfully retrieved (post) from the middleware. This logging applies to calls that originate from the MES Web API or from the middleware maintenance services. The information includes how long the execution took to retrieve the dataset, how long the execution took to convert the UTC times into time zone of the client, and the XML request to the middleware.

MES.WebApi Assembly

Flag

Description

LogIncomingRequestBody

Logs the request body for MES Web API calls.

LogIncomingRequestHeaders

Logs the headers for MES Web API calls. For authorization headers, only the first 5 characters of the bearer token are included for security reasons. They are included to confirm that a bearer token was provided for the call.

LogIncomingRequestUri

Logs the URI for MES Web API calls.

LogSSOServerInfo

Logs the name of the SMS server used by the MES middleware.

MES.WebApi.MiddlewareAdaptor Assembly

Flag

Description

LogDeadlocks

Logs the number of deadlock retries and the database error information.

LogTransactionCompleteGetDS

Logs the information that indicates whether the dataset request was successful. The information includes how long the call took to retrieve data, how long it took to serialize data into Json format, and how long it took to convert the data into JArray format.

LogXmlForWebApi

Logs the information that indicates whether the execution request was successful. The information includes how long the execution took to complete the entire round-trip.

In This Topic
TitleResults for “How to create a CRG?”Also Available in