Service trace Viewer tool (svctraceviewer.exe)-WCF-http://blogs.msdn.com/wcftoolsteamblogcn/

The Windows Communication Foundation (WCF) Service Tracking Viewer tool helps you analyze diagnostic tracing generated by WCF. The service tracing Viewer provides a way to easily merge, view, and filter trace messages in logs to diagnose, fix, and verify WCF Service problems.

Configuration tracking

The information provided by the Diagnostic trail shows what happens during application operations. As the name suggests, you can track the operation from the operation source to the target, or through the intermediate point.

You can use the application configuration file (Web. config of the Web-hosted application orAppname. Config) to configure the trail. The following is an example:

Copy code

<system.diagnostics><trace autoflush="true" /><sources><source name="System.ServiceModel"switchValue="Information, ActivityTracing"propagateActivity="true"><listeners><add name="sdt"type="System.Diagnostics.XmlWriterTraceListener"initializeData= "SdrConfigExample.e2e" /></listeners></source></sources></system.diagnostics>

The WCF trail will be written toSystem. servicemodel.

Tracking levelSwitchvalueSet control. The following table describes the Available Trace levels.

Tracking level	Description
Severe	Record fail-fast and Event Log items, and track relevant information. The following are some examples of when "severe" levels can be used: Your appdomain fails due to an unhandled exception. Your application cannot be started. The message that causes the fault is from the myapp.exe process.
Error	Record all exceptions. The "error" level can be used in the following situations: Your code crashes due to an invalid forced conversion exception. The "failed to create an endpoint" exception causes the application to fail at startup.
Warning	There may be errors or serious faults subsequently. This level can be used in the following situations: The number of requests received by the application is more than the number allowed by the limit setting. The receiving queue accounts for 98% of its configured capacity.
Information	Generates messages that are useful for monitoring and diagnosing system status, measuring performance, or performing analysis. You can use this information to plan capacity and management performance. This level can be used in the following situations: An error occurs when the message arrives at the appdomain and is deserialized. An error occurred while creating the HTTP binding.
Details	It also tracks the debugging level of user code and services. Set this level in the following cases: You are not sure which method in the Code is called when an error occurs. You have configured an incorrect endpoint and the service cannot be started because the items in the reserved storage are locked.
Activity Tracking	Process Flow events between activities and components. This level allows administrators and developers to associate applications in the same application domain. Activity Boundary Tracking: start/stop. Transmission tracking.

AvailableAddSpecifies the name and type of the trace listener to be used. In the sample configuration, name the listener "SDT" and add the standard. NET Framework trace listener (System. Diagnostics. xmlwritertracelistener) As the type to be used. UseInitializedataSet the name of the log file of the listener. In addition, you can use a simple file name to replace the fully qualified path.

Use the service tracking Viewer tool to open and view the WCF tracking File

The Service Tracking Viewer supports three file types:

• WCF trace file (. svclog)
• Event tracking file (. ETL)
• Crimson trace file

The service trace Viewer allows you to open any supported trace files, add and integrate additional trace files, or simultaneously open and merge a group of Trace files.

Open a trail File

1. Use the command window to locate the WCF installation location (c: \ Program Files \ microsoft sdks \ windows \ v6.0 \ bin), and then typeSvctraceviewer.exeTo start the service trace viewer.

Note:

The Service Tracking Viewer tool can be associated with two file types:. svclog and. stvproj. In the command line, you can use two parameters to register and deregister the file extension. /Register: register the file extensions ". svclog" and ". stvproj" as associated with svctraceviewer.exe. /Unregister: unregister the association between the file extensions ". svclog" and ". stvproj" and svctraceviewer.exe.

 

1. When the service tracking viewer is started, click"File"And then point"Open". Locate the storage location of the tracking file.
2. Double-click the trail file to open.

Note:

Shift and click multiple trace files to select and open these files at the same time. The Service Tracking viewer merges the content of all files and displays them as a view. For example, you can open a trace file for both the client and the service. This feature is useful if message logging and activity propagation are enabled in the configuration. In this way, you can check the message exchange between the client and the service. You can also drag multiple files to the viewer or use"Project"Tab. For more information, see "manage projects.

 

1. To add more trace files to an opened collection, click"File"And then point"Add". In the displayed window, locate the tracking file and double-click the file to be added.

Warning:

We recommend that you do not load trace log files larger than 200 MB. If you try to load a file that exceeds this limit, the loading process may take a long time, depending on the computer resources. The Service Tracking Viewer tool may not respond for a long time, or it may exhaust the computer's memory. We recommend that you configure partial loading to avoid this situation. For more information about how to configure this, see the "load large tracking files" section.

 

Event tracking and crimson tracking

The local format of the viewer is the activity tracking format sent by WCF. For traces sent in other formats, you must first convert them so that the viewer will display them. Currently, in addition to the activity tracking format, the viewer also supports event tracking and crimson tracking.

When you open a file that does not contain an activity trace, the viewer will try to convert the file. The name and location must be specified for the file that contains the converted trace data. After the data is converted, the viewer displays the content of the new file.

Note:
The conversion requires disk space to store the converted tracing data. Before starting the conversion, make sure that you have sufficient disk space to store data. Otherwise, the conversion fails.

 

Manage projects

The viewer supports projects to view multiple trace files. For example, if there are client trace files and service trace files, you can add them to the project. When you open the project, all the trace files in the project are loaded at the same time.

There are two ways to manage projects:

• In"File"You can open, save, and close a project.
• In"Project"Tab to add files to the project.

View a WCF trail

WCF uses the activity tracking format to issue a trail. In the activity tracking model, each trace is grouped in the activity for its purpose. The logical control flow is transmitted between activities. For example, in the lifetime of an application, many "message sending activities" appear and disappear. For more information about viewing tracking and activities and the Service Tracking viewer user interface, see using service trace viewer for viewing correlated traces and troubleshooting.

Switch to different views

The service trace Viewer provides the following different views. They are displayed as tabs in the left pane of the viewer, from"View"Menus can also access these views.

• Activity View
• Project View
• Message View
• Graphical View

Activity View

After the trail file is opened, you can view the group to the activity and display it in the left-side pane."Activity"View.

"Activity"The view displays the activity name, number of trails in the activity, duration, and start and end times.

Click any activity listed. The trail in this activity is displayed in the right trace pane. Then, select a trail to view its details.

By pressing"Ctrl"Or"Shift"Key and click the expected activity to select multiple activities. The trail pane displays all the trails for the selected activity.

Double-click an activity on"Graphics"This activity is displayed in the view. Another way is to select an activity and switch"Graphics"View.

Note:
Activity 000000000000 is a special activity and cannot be displayed in the graphic view. Because all other activities are linked to it, it is displayed that this activity seriously affects performance.

 

Click the column title to sort the activity list. An activity that contains a warning trace has a yellow background, and an activity that contains an error trace has a red background.

Activities have different types, and each type corresponds to an icon on the left of each activity. For more information, see the "learn more about tracking icons" section.

Project View

In this view, you can manage trace files in the current project. For more information, see "manage projects.

Graphical View

One of the most powerful functions of the Service Tracking viewer is"Graphics"View, which displays the trace data for a given activity in a chart. In the form of charts, you can view the progressive execution process of events, and view the relationships between activities when data is moved between multiple activities.

To switch"Graphics"View, see"Activity"Select activity in the view, and then click"Activity"Tab, or"Message"Click message log tracking in the view. If multiple trace files are loaded and the activity involves a trace from multiple files, all related traces are displayed in the "graphics" view. Double-click activity and message log tracking to switch"Graphics"View.

In"Graphics"In the view, each vertical column represents an activity, and each block in the column represents a trail. Activities are grouped by processes (or threads. A Small Arrow between activities indicates transmission. A large Arrow between processes indicates message exchange. The selected activity is always yellow.

Select a trail in the graph

1. Click a block in the image.
2. Use the up key and down key to select its adjacent trace.
3. View the trace information in the trace pane and details pane.

Expand or collapse activity Transmission

When the selected activity is transferred to another activity, the activity transmission can be expanded. In this way, we can track these transmissions.

To expand or collapse the active transmission,

1. Go to transfer trace with "+" on the left of the transfer icon.
2. Click "+" or press"Ctrl"And "+ ".
3. The next activity appears in the graph.
4. A "-" sign is displayed on the left side of the transfer icon. Click the minus sign (-) or press Ctrl and minus sign (-) to collapse the active transmission.

Note:
When an activity has multiple transfers to it, if you expand one, the activity from the root activity to the new activity is displayed. These new activities are displayed in folding form. To view the details of these activities, click the expand icon in the graphic title to expand them vertically.

 

Vertical expand or collapse Activity

The viewer hides unnecessary details in the active image by folding the activity. Each trace is not displayed in the folding activity. Only the transmission trace is displayed. To view all the trails in an activity, you can expand the activity vertically by clicking the expand symbol of the activity in the graphic title.

To expand or collapse vertically,

1. Click the "+" icon in the Activity title to expand the activity vertically.
2. Note that all traces are displayed in the graph.
3. Click the "-" icon in the Activity title to vertically collapse the activity.
4. Note that only important transmission, message logs, warnings, and exception tracking are displayed in the activity.

Option

In the "graphics" view, you can"Option"Select two options in the menu.

• Show activity boundary trace: If this option is not selected, the activity boundary trace in the graph is ignored.
• Show non-message detail trace: If this option is not selected, other detail level traces except message Trace are ignored. In most cases, detailed tracking is not very important for analysis. This option is useful if you do not want to analyze detailed-level tracing, but only want to focus on more important tracing.

Layout mode

The viewer has two layout modes:"Process"And"Thread". This setting defines the maximum organization unit. The default Layout mode is"Process"In this mode, activities are grouped by processes in the graph.

Execution list

From the drop-down list, you can select the process or thread to display in the graph. For example, if you have two client (a and B) trace files and a service is opened, and you only want to display the service and Client A in the image, you can deselect client B from the list.

View trace details

To view the details of a trail, select the trail in the trail pane. Details are displayed in the details pane.

Trail pane

The upper right window of the Service trace viewer is the trace pane. It lists all the traces and additional information in the selected activity, such as the Trace Level, thread ID, and process name.

Right-click the trail and select"Copy tracing to clipboard"To copy the original XML of the trail to the clipboard.

Details pane

The lower-right window of the Service trace viewer is the details pane. It provides three option cards to view detailed information about a trail.

"Format"The view displays information in a more ordered manner. It lists all known XML elements in the form of tables and trees, making it easier to read and understand information.

"XML"The view displays the XML corresponding to the selected trail. It supports highlighted display and syntax coloring. When using"Search"When you search for a string, the search results are highlighted.

"Message"The view displays the XML message in the message log trace. This view is invisible when you select non-message tracing.

Filter WCF Trails

To make Tracking Analysis easier, you can filter it in the following ways:

• The Filter toolbar provides access to pre-defined filters and custom filters. You can use"View"Enable the toolbar.
• The pre-defined filter of the viewer can be used to selectively filter some WCF trails. By default, this filter is set to allow all infrastructure trails to pass. This filter is set in"View"Under the menu"Filter options"Sub-menu.
• Custom XPath filters give users full control over filtering. You can"View"Menu"Custom filter"Define these filters.

Only the trail with all filters is displayed.

Use the Filter toolbar

The Filter toolbar is displayed at the top of the tool. If it is not displayed, you can"View"Activate it in the menu. This toolbar has three components:

• Search:"Search"Define the topic to be searched in the filter operation. For example, if you want to find all the trails that are generated in the context of process X, set this field to X and"Search range"Set the field to "process name ". If a time-based filter is selected, this field is changed to the datetime selector control.
• Search range: this field defines the filter type to be applied.
• Level: The level setting defines the minimum trace level allowed by the filter. For example, if the level is set to "error and severe error", only "error" and "severe" Trace are displayed. This filter is used with conditions specified by "Search" and "search range.

"Filter now"Click to start the filter operation. Some filters, especially when they are applied to large datasets, take a long time to complete the operation. You can press"Operation"The"Stop"To cancel filtering.

"Clear"Click to reset the predefined and custom filters to allow all trails to pass.

Filter options

The viewer can automatically remove the WCF trail from the view. It can selectively remove a trail from a specific area of WCF, for example, removing a transaction-related trace from the view.

This filter is set in"View"Under the menu"Filter options"Sub-menu.

Custom Filter

If you are familiar with the XML Path Language (XPath), you can use it to construct custom filters to search tracking data for any relevant XML element. You can access these filters through the Filter toolbar.

Custom filters can include parameters. You can also import pre-existing custom filters.

Create a custom filter

You can create a filter in two ways:

Use the template Wizard to create a custom filter

You can click an existing trail and create a filter based on the structure of the trail. This example creates a custom filter based on the thread ID.

1. In the Trail pane in the upper-right area of the viewer, select a trail that contains the elements to be filtered.
2. Click"Create custom filter"Button.
3. In the displayed dialog box, enter the Filter Name. In this example, enterThread ID. You can also provide filter descriptions.
4. The Tree View on the left is displayed in the structure of the trace record selected in step 1. Browse to the element for which you want to create conditions. In this example, browse to the threadid at the XPath:/e2etraceevent/system/execution/@ threadid node. Double-click the threadid attribute in the Tree View. In this way, you can create an expression for this attribute on the right side of the dialog box.
5. Change the parameter field of the threadid condition from "NONE" to "{0 }". Through this step, you can configure the threadid value when applying the filter. (See "how to apply a filter".) up to four parameters can be defined. Conditions are combined by the "or" operator.
6. Click"OK"Create a filter.

Note:Once a filter is created using the template wizard, you can only manually edit the filter. The Wizard cannot be activated for filters created earlier. In addition, the XPath filter conditions created in the template wizard are combined with the "or" operator. If you need the "and" operation, you can edit the filter expression after the filter is created.

Manually create a custom filter

You can use the "custom filter" menu to manually enter the XPath filter.

1. On the "View" menu, click"Custom filter"Menu item.
2. In the displayed dialog box, click"New".
3. At least the Filter Name and XPath expression should be specified.
4. Click"OK".

Application custom filter

After creating a custom filter, you can access it through the Filter toolbar. In the Filter toolbar"Search range"Select the filter to be applied in the field. Select "thread ID" for the previous example ".

1. In"Search content"Field specifies the value to be searched. In this example, enter the ID of the thread to be searched.
2. Click"Filter now"And then observe the operation results.

If the filter uses multiple parameters, use ";" as the separator."Search content"Field. For example, the following string defines three parameters: "1; findvalue; text ". The viewer applies "1" to the {0} parameter of the filter. "Findvalue" and "text" are applied to {1} and {2} respectively }.

Shared custom filter

You can share custom filters between different sessions and users. You can export a filter to a definition file and then import it to another location.

Import custom filter:

1. In"View"Click"Custom filter".
2. In the displayed dialog box, click"Import"Button.
3. Go to the custom filter file (. stvcf), click the file, and then click"Open"Button.

Export custom filter:

1. Click"Custom filter".
2. In the displayed dialog box, select the filter to export.
3. Click"Export"Button.
4. Specify the name and location of the custom filter definition file (. stvcf), and then click"Save"Button.

Note:
These custom filters can only be imported and exported from the service trace viewer. Other tools cannot read these filters.

 

Search for Data

The viewer provides the following methods to find data:

• You can use the "Search" toolbar to quickly access the most frequently used search options.
• The "Search" dialog box provides more search options. Pass"Edit"You can access this dialog box by pressing CTRL + F.

The "Search" toolbar is displayed at the top of the viewer. If it is not displayed, you can"View"Activate it in the menu. This toolbar has two components:

• Search content: You can enter a search keyword.
• Search range: You can enter a search range. You can choose to search for all activities, or you can choose to search only for the current activity.

The Search dialog box provides two additional options:

• Search target:
  • If you select the "raw Log Data" option, a keyword is searched for all raw data.
  • If you select the "XML text" and "XML attributes" options, you can only search for them in the XML element.
  • If you select the Recorded Message option, you can only search for keywords in the message.
• Ignore root activity: searches ignore the trail in the 000000000000 activity. If the root activity has thousands of trails, most of which are transfer traces, selecting this option improves the performance of large trace files.

Locating and tracking

Because tracing is recorded gradually during the application running period, locating tracing helps to debug the application. The Service Tracking Viewer provides multiple locating and tracing methods.

Move forward or backward

If you think of each trace as a line of code in the program, it is very similar to "process-by-process" in the integrated development environment (IDE) of Visual Studio ". The difference is that tracking can be performed gradually. Moving forward gradually means moving to the next trail in the activity.

• Step by step: Use"Activity"Menu, or press "F10 ". You can also use the downward arrow in the trace pane.
• Step by step: Use"Activity"Menu, or press "F9 ". You can also use the up arrow in the trace pane.

Note:
This operation may jump to activities that occur in other processes or even on other computers, because WCF messages can send cross-computer activity IDs.

 

Tracking Transmission

A transfer trace is a special trace in a trace file. One activity can be transmitted to another activity through transmission tracking. For example, "activity a" can be transferred to "Activity B ". In this case, there is a transfer trace named "to: Activity" in "activity a" with a transport icon. This transfer trace is a link between two traces. In "Activity B", a transmission trace may also be transmitted back to "activity a" at the end of the activity ". This is similar to the function call in the program: A calls B and B returns.

"Tracing transmission" is similar to "one-step execution" in the debugger ". It traces the transmission from A to B. It has no impact on other trails.

There are two ways to track transmission: use the mouse or keyboard:

• Use the mouse: Double-click transfer trail in the trail pane.
• Use the keyboard: Select transfer tracking, and then use"Activity"Or press "F11"

Note:

In many cases, when activity A is transferred to Activity B, activity a waits until Activity B is transferred back to activity. This means that activity A does not record the trail during active tracking of Activity B. However, it is also possible that activity A does not wait, but keeps recording and tracking. In addition, Activity B may not be transferred back to activity. Therefore, in this sense, the activity transmission and function call are still different. Activity transmission can be better understood in the graphic view.

 

Jump to the next or previous Transmission

When analyzing the current activity or selected activity (if multiple activities are selected), you may want to quickly find the activity to which it is transmitted. You can click "Jump to next transmission" to locate the next transmission trace in the activity. Once a transfer trace is found, you can use track transfer to perform the next activity in one step.

• Jump to the next transmission: Use"Activity"Or press Ctrl + F10 ".
• Jump to the previous transmission: Use"Activity"Or press Ctrl + F9 ".

Locate in the graphic view

Although positioning in the activity window and the trace pane is similar to debugging, use"Graphics"The view can still provide a better positioning experience. For more information, see the graphic view section.

Load large tracking files

The trace file may be very large. For example, if "Detailed" level tracing is enabled, after several minutes of running, the result Tracing file can easily reach hundreds of megabytes or even larger, depending on the network speed and communication mode.

System performance may be negatively affected when a very large trace file is opened in the service trace viewer. Loading Speed and response time after loading may be slow. The actual speed is not always the same, depending on the hardware configuration. In most PCs, loading a trace file larger than 200 MB seriously affects performance. For trace files larger than 1 GB, this tool may use up all available memory or stop responding for a long time.

To avoid loading and slow response when analyzing large trace files, the Service trace Viewer provides a feature called "partial loading", that is, loading only a small part of a trace at a time. For example, you may have a trace file larger than 1 GB, which has been running on the server for several days. When an error occurs and you want to analyze the trace, you do not need to open the entire trace file. You can load a trail in a certain period of time when an error may occur. As the scope is reduced, the Service Tracking Viewer tool can load files more quickly, and you can identify these errors using a small dataset.

Enable partial loading

You do not need to manually enable partial loading. If the total size of the trail file to be loaded exceeds 40 MB, the Service trail viewer automatically displays the "partially loaded" dialog box for you to select the part to be loaded.

Note:
Because the tracking is not necessarily evenly distributed within the time span, the length of the specified time period in the "partial loading" toolbar is not necessarily proportional to the displayed loading size. The actual load size can be smaller than the "estimated size" in the partial load dialog box ".

 

Adjust partial loading

You may want to change the loaded dataset after partially loading the trace file. You can perform this operation by adjusting the "partial loading" toolbar at the top of the viewer.

1. Move the toolbar with the mouse, or enter "Start Time" and "End Time ".
2. Click"Adjustment"Button.

Learn more about the trail icon

The service trace Viewer tool is used in"Activity"View,"Graphics"View and"Tracking"Icon indicating different items in the pane.

Note:
Some unclassified trails (for example, "messages are closed") do not have icons.

 

Activity Tracking

Icon	Description
	"Warning" trail: A trail issued at the warning level
	"Error" Trace: a trace issued at the error level.
	"Activity start" trail: a trail that begins with an activity. It contains the name of the activity. The Application Designer or developer should define an activity "START" trace for each activity ID of each process or thread. If the activity ID is propagated between the tracing source associated with the trail, multiple "starts" (one for each trail source) will be displayed for the same activity ID ). If activitytracing is enabled for the tracing source, a "start" trace is issued.
	"End of activity": a trail that marks the end of an activity .. It contains the name of the activity. Application designers or developers Define an "end" trail for each activity ID of each tracing source. No trace in this trace source is displayed after the end of an activity sent from a given trace source, unless the trace interval is small enough. In this case, the two tracks with the same time (including the "end" TRACE) may be staggered during display. If the activity ID is propagated between the trace sources associated with the trail, multiple "Ends" (one for each trail source) are displayed for the same activity ID ). If activitytracing is enabled for the tracing source, an "end" trace is issued.
	"Activity suspension" trail: a trail that marks the pause time of an activity. No trail is triggered during a pending activity until the activity continues. A Pending activity indicates that no processing is performed within the tracking source range of the activity. "Pending"/"continue" tracing is very useful for analysis. If activitytracing is enabled for the tracing source, a "Suspend" trace is issued.
	"Activity continuation" trail: this trail marks the time when the activity continues after it is paused. You can send a trail again in this activity. "Pending"/"continue" tracing is very useful for analysis. If activitytracing is enabled for the tracing source, a "continue" trace is issued.
	Transfer: the trail that is triggered when the logical control flow is transmitted from one activity to another. Activities that serve as transmission sources can continue to work in parallel with those that serve as transmission targets. If activitytracing is enabled for the tracing source, a "transfer" trace is issued.
	Transmission customization: defines the transfer trace from another activity to the current activity.
	Transfer to: defines the trail that the logical control flow transmits from the current activity to another activity.

WCF tracking

Icon	Description
	"Message Log" TRACE: The Trace sent when the message logging function records the WCF message (if enabledSystem. servicemodel. messageloggingTracking source ). Click this trail to display messages. A message has four configurable logging points: servicelevelsendrequest, transportsend, transportreceive, and servicelevelreceiverequest.MessagesourceThey are also specified in the property.
	"Received message" Trace: The Trace sent when a WCF message is received (if it is enabled at the "information" or "details" LevelSystem. servicemodelTracking source ). This trail is applicable to activities"Graphics"View is required to view the message-related arrows.
	"Sent message" Trace: The Trace sent when a WCF message is sent (if it is enabled at the "information" or "details" LevelSystem. servicemodelTracking source ). This trail is applicable to activities"Graphics"View is required to view the message-related arrows.

Activity

Icon	Description
	Activity: indicates that the current activity is a general activity.
	Root Activity: indicates the root activity of the process.

WCF Activity

Icon	Description
	"Environment" activity: You can create, open, or close the activity of a WCF host or client. Errors occurring in these phases will appear in this activity.
	"Listener" activity: activities that can be recorded for listeners. You can view the listener information and connection requests during this activity.
	"Receive Byte" activity: An activity that groups all traces related to received bytes over the connection between two endpoints. This activity is required when it is associated with a transport activity (such as HTTP. sys) that broadcasts its activity ID. Connection errors such as abort will appear in this activity.
	"Message Processing" activity: An activity that groups trails related to creating WCF messages. Errors Caused by incorrect encapsulation or message format will appear in the activity. You can detect the message header in this activity to determine whether the activity ID is propagated from the caller. If it has been propagated, when it is transferred to the "processing operation" activity (the next icon), we can also assign a promotional activity ID to the activity, to establish an association between the caller and the called trace.
	"Processing operation" activity: An activity that groups all traces related to the WCF requests between two endpoints. IfPropagateactivitySetTrue, All the traces from the two endpoints are merged into an activity for Direct association. Such activities will contain errors that occur due to transmission or security processing, extending to the user code boundary, and rollback (if a response exists.
	"Execute user code" activity: An activity that groups user code traces to process requests.

Troubleshooting

If you do not have permission to write data to the Registry,Svctraceviewer/register"When registering the tool, you will receive the following error message:" Microsoft Service Tracking viewer is not registered in the system ". In this case, you should use an account with write access to the registry to log on.

In addition, the Service trace Viewer tool writes some settings (such as custom filters and filter options) to the svctraceviewer.exe. settings file in its Assembly folder. If you do not have the permission to read the file, you can still start the tool, but cannot load the settings.

If an error message "Unknown error occurs when one or more traces are processed" is received when the. ETL file is opened, the format of the. ETL file is invalid.

If you enable the trace log created using the Arabic operating system, you may notice that the time filter does not work. For example, 2005 corresponds to 1427 in the Arabic calendar. However, the time range supported by the Service Tracking Viewer tool filter does not support dates earlier than January 1, 1752. This may mean that you cannot select the correct date in the filter. To solve this problem, you can use an XPATH expression to create a custom filter ("View"/"custom filter") To include a specific time range.