Debug

I need a solution

I’m having an issue with one of my workflow that’s been working fine for years.  It’s actually a fairly simple flow.  It reads data from a database, displays a list the the user, allows the user to select an item from the list and then displays the data.  There’s one item from all of them that doesn’t display the data.  The path thru the workflow is exactly the same for all of the items.  Now the debug question..  when I run the workflow thru debug it won’t display the data as it does in all my other workflows so I can’t see where the issue is.  Is there a setting thats needed or not needed that shows responsible for this?

0

Related:

  • No Related Posts

I am at a loss: SEP client gets 404 when connecting to the manager

I need a solution

cve.log debug output:

[2019-Jun-06 18:27:39.405925] [DEBUG] Loading data.
[2019-Jun-06 18:27:39.405925] [DEBUG] Loading data.
[2019-Jun-06 18:27:39.405925] [DEBUG] Attempting connection to server $MANAGER
[2019-Jun-06 18:27:39.405925] [INFO ] CallOneServer: Heartbeat pass <1> for $MANAGER
[2019-Jun-06 18:27:39.405925] [DEBUG] Heartbeat status: [complete: false] [successful: false]
[2019-Jun-06 18:27:39.405925] [DEBUG] Attempting to get Index2.xml file.
[2019-Jun-06 18:27:39.405925] [DEBUG] Current syed while downloading ssstem proxy is:
[2019-Jun-06 18:27:39.405925] [DEBUG] Setting CURL to use system proxy =
[2019-Jun-06 18:28:00.687198] [DEBUG] Interruptction=12&hostid=$HOSTID&chk=$CHK&ck=$CK&uchk=$UCHK&uck=$UCK&hid=$HID&groupid=$GROUPID&ClientProductVersion=14.2.3332.1000&mode=0&hbt=600&as=4770&cn=[hex]$CN&lun=[hex]$LUN&udn=[hex]$UDN
Downloaded 0 and uploaded 0 bytes.

I have tried pushing a new syslink from the SEPM, using the import function from the troubleshooting menu, and using syslinkdrop program, no joy.

In the past, reimporting the syslink was enough to restore the connection, but not this time.  I’m about ready to just do a nuke and repave on the clients that are having this problem, but would like to avoid the hassle of scheduling the downtime to do so.

Any ideas?

0

Related:

  • No Related Posts

Elastic Layering Logs

Debugging Elastic Layering problems is described in the documentation here (scroll down to Debug an Elastic Layer):

https://docs.citrix.com/en-us/citrix-app-layering/4/layer/assign-elastic-layers.html

Get the ELM logs first. Then:

1.Collect the data from these logs in the end-user VM after producing the problem:

  • Windows Application Event log: In the Windows Event Viewer under Windows Logs, export the Application event log as an EVTX file.
  • Unidesk Layering Service log (ulayersvc.log): C:ProgramDataUnideskLogsulayersvc.log
  • Unidesk LayerInfo log (layerinfo.log): %LOCALAPPDATA%UnideskLogslayerinfo.log (note, this is in the current user profile)

2.Collect the values of these Registry keys from the end-user VM:

  • HKEY_LOCAL_MACHINESOFTWAREUnideskULayerAssignmentFile
  • HKEY_LOCAL_MACHINESOFTWAREUnideskULayerRepositoryPath
  • HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsNTCurrentVersionWinlogonUserInit

3.Collect the contents of the JSON files, including at least the Assignment (ElasticLayerAssignments.json) and Layers (Layers.json) files from the Repository Path.

Enabling Debug Logging in Ulayer

By default, ulayersvc.log only logs events INFO or higher. You may determine that you want more detailed logging. To turn on DEBUG logging, you need to edit a configuration file. This can be done in a layer (preferably the Platform Layer) or by editing a published image after the fact. The setting must be present before Ulayer.exe starts, which normally means it must be present before the machine boots. So you cannot set it from a GPO, for instance.

Edit C:Program FilesUnideskLayering Servicesulayer.exe.config. Scroll down to find this block in the Log4Net Appender section:

<root>

<level value=”INFO“/>

<appender-ref ref=”LogFileAppender”/>

</root>

Change INFO to DEBUG and save.

Related:

  • No Related Posts

How to enable extension PATCH method

Procedure to enable PATCH method:

1. Connect to active CSM by ssh

2. Access to “bmcli” and execute the following commands:

root@r8-lab> en

root@r8-lab# config

root@r8-lab(config)# hidden

Enabling hidden commands

root@r8-lab(config)# / enable-kw debug

enable debug-kw

root@r8-lab(config)# / cfgElem osn webgrp/webproxy.xml . add-child extension_methods PATCH

Added Element osn:webgrp/webproxy.xml ..extension_methods[PATCH]

root@TestLab(config)# cfg commit

Updating configuration ….

3. Verify that the changes have been sent to the ASMs, connect to one ASM by rsh and execute the following command:

# grep “extension_methods” /opt/bmi/etc/webgrp/webproxy.conf

extension_methods PATCH

Procedure to rollback the change:

1. Connect to active CSM by ssh

2. Access to “bmcli” and execute the following commands:

root@r8-lab> en

root@r8-lab# config

root@r8-lab(config)# hidden

Enabling hidden commands

root@r8-lab(config)# / enable-kw debug

enable debug-kw

root@r8-lab(config)# / cfgElem osn webgrp/webproxy.xml extension_methods delete

Deleted Element osn:webgrp/webproxy.xml extension_methods​

root@TestLab(config)# cfg commit

Updating configuration ….

3. Verify that the changes have been sent to the ASMs, connect to one ASM by rsh and check that the line “extension_methods PATCH” added previously is not on the /opt/bmi/etc/webgrp/webproxy.conf file.

Related:

  • No Related Posts

7023218: Error in OES NWClient authentication causes problem with passive mode ZEN login or DLU enforcement

This document (7023218) is provided subject to the disclaimer at the end of this document.

Environment

ZENworks Configuration Management 2017 Update 2

Situation

ERROR (from zennotify.log):

[DEBUG] [07/19/2018 14:19:32.477] [9220] [ZenNotify] [5272] [] [ZENNOTIFY] [] [Entered IsNDSUserLoggedIn] [] [] [] [ZENworks Agent]
[DEBUG] [07/19/2018 14:19:32.477] [9220] [ZenNotify] [5272] [] [ZENNOTIFY] [] [CLXWIN32LoadDLL called!] [] [] [] [ZENworks Agent]
[DEBUG] [07/19/2018 14:19:32.477] [9220] [ZenNotify] [5272] [] [ZENNOTIFY] [] [NETWIN32LoadDLL called!] [] [] [] [ZENworks Agent]
[DEBUG] [07/19/2018 14:19:32.477] [9220] [ZenNotify] [5272] [] [ZENNOTIFY] [] [GetLoggedOnUserInfo entered] [] [] [] [ZENworks Agent]
[DEBUG] [07/19/2018 14:19:32.477] [9220] [ZenNotify] [5272] [] [ZENNOTIFY] [] [Ought Oh!! We did a successful passive mode login but now we can’t find an authenticated identity.] [] [] [] [ZENworks Agent]
[DEBUG] [07/19/2018 14:19:32.477] [9220] [ZenNotify] [5272] [] [ZENNOTIFY] [] [GetLoggedOnUserInfo returning 0x00008866] [] [] [] [ZENworks Agent]

Resolution

Confirm that user can login to nwclient / OES client manually. If so then logging is needed for why OES client isn’t logging in during boot. To get more logging for client, see https://novell.com/support/kb/doc.php?id=7007070

In one such case the computer was configured for “Computer Only Login if not Connected” and failed to populate “Use Lists for Novell Login” so no matching network was found.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Re: Object content being dumped to logs

Let me start with apologizing for the lengthy post. Just want to make sure all the details are provided in one go…

We use com.emc.atmos.api.jersey.AtmosApiClient class to call getObjectMetadata and readObjectStream methods to retrieve the objects from the storage. Functionality is working absolutely fine and we don’t have any issue with that. However, on the catalina.out log file we see below log debug information for getObjectMetadata:

DEBUG: Connection request: [route: {}->http://<host>:<port>][total kept alive: 0; route allocated: 0 of 200; total allocated: 0 of 200]

DEBUG: Connection leased: [id: 1][route: {}->http://<host>:<port>][total kept alive: 0; route allocated: 1 of 200; total allocated: 1 of 200]

DEBUG: Connecting to <host>:<port>

DEBUG: CookieSpec selected: best-match

DEBUG: Target auth state: UNCHALLENGED

DEBUG: Proxy auth state: UNCHALLENGED

DEBUG: Attempt 1 to execute request

DEBUG: Sending request: HEAD /rest/objects/<object_ID> HTTP/1.1

DEBUG: >> “HEAD /rest/objects/<object_ID> HTTP/1.1[r][n]”

DEBUG: >> “x-emc-utf8: true[r][n]”

DEBUG: >> “Date: Mon, 9 Jul 2018 21:10:25 UTC[r][n]”

DEBUG: >> “x-emc-date: Mon, 9 Jul 2018 21:10:25 UTC[r][n]”

DEBUG: >> “x-emc-uid: <UID>[r][n]”

DEBUG: >> “x-emc-signature: <signature>[r][n]”

DEBUG: >> “Host: <host>:<port>[r][n]”

DEBUG: >> “Connection: Keep-Alive[r][n]”

DEBUG: >> “User-Agent: Apache-HttpClient/4.2.6 (java 1.5)[r][n]”

DEBUG: >> “[r][n]”

DEBUG: >> HEAD /rest/objects/<object_ID> HTTP/1.1

DEBUG: >> x-emc-utf8: true

DEBUG: >> Date: Mon, 9 Jul 2018 21:10:25 UTC

DEBUG: >> x-emc-date: Mon, 9 Jul 2018 21:10:25 UTC

DEBUG: >> x-emc-uid: <UID>

DEBUG: >> x-emc-signature: <signature>

DEBUG: >> Host: <host>:<port>

DEBUG: >> Connection: Keep-Alive

DEBUG: >> User-Agent: Apache-HttpClient/4.2.6 (java 1.5)

DEBUG: << “HTTP/1.1 200 OK[r][n]”

DEBUG: << “Date: Mon, 09 Jul 2018 21:10:19 GMT[r][n]”

DEBUG: << “x-emc-mtime: 1531164643814[r][n]”

DEBUG: << “x-emc-meta: <the_metadata>[r][n]”

DEBUG: << “x-emc-listable-meta: filename=Test%20New%20Download%20Cloud%20Storage.xlsx[r][n]”

DEBUG: << “x-emc-useracl: <uid>=FULL_CONTROL[r][n]”

DEBUG: << “x-emc-groupacl: other=READ[r][n]”

DEBUG: << “x-emc-policy: default[r][n]”

DEBUG: << “x-emc-utf8: true[r][n]”

DEBUG: << “x-emc-request-id: <request_id>[r][n]”

DEBUG: << “Content-Type: application/octet-stream[r][n]”

DEBUG: << “Content-Length: 1219856[r][n]”

DEBUG: << “[r][n]”

DEBUG: Receiving response: HTTP/1.1 200 OK

DEBUG: << HTTP/1.1 200 OK

DEBUG: << Date: Mon, 09 Jul 2018 21:10:19 GMT

DEBUG: << x-emc-mtime: 1531164643814

DEBUG: << x-emc-meta: <the_metadata>

DEBUG: << x-emc-listable-meta: filename=Test%20New%20Download%20Cloud%20Storage.xlsx

DEBUG: << x-emc-useracl: <uid>=FULL_CONTROL

DEBUG: << x-emc-groupacl: other=READ

DEBUG: << x-emc-policy: default

DEBUG: << x-emc-utf8: true

DEBUG: << x-emc-request-id: <request_id>

DEBUG: << Content-Type: application/octet-stream

DEBUG: << Content-Length: 1219856

DEBUG: Connection can be kept alive indefinitely

DEBUG: Connection [id: 1][route: {}->http://<host>:<port>] can be kept alive indefinitely

DEBUG: Connection released: [id: 1][route: {}->http://<host>:<port>][total kept alive: 1; route allocated: 1 of 200; total allocated: 1 of 200]

And for readObjectStream:

All of the above debug logs plus –

DEBUG: << Content-Type: application/octet-stream

DEBUG: << Content-Length: 1219856

DEBUG: Connection can be kept alive indefinitely

DEBUG: << “PK[0x3][0x4][0x14][0x0][0x8][0x8][0x8][0x0][0xd4]s[0xe9]L[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x11][0x0][0x0][0x0]docProps/core.xml[0xad][0x91]MK[0xc4]0[0x10][0x86][0xef][0xfd][0x15]![0xf7]v[0xd2][0xad][0xe8][0x1a][0xda].[0xa2],[0x8][0x8a][0xb][0xae]([0xde]B:[0xb6][0xc5][0xe6][0x83]$[0xda][0xf5][0xdf][0x9b][0xed][0xae][0x15][0xc5][0xa3][0xc7][0xc9][0xfb][0xbc][0xf][0xc3][0xa4][0xed][0xd4]@[0xde][0xd1][0xf9][0xde][0xe8][0x8a][0xe6][0x19][0xa3][0x4][0xb5]4M[0xaf][0xdb][0x8a]>l[0xd7][0xe9][0x92][0xae][0xea]$)[0xa5]q[0xb8]q[0xc6][0xa2][0xb]=z[0x12][[0xda]W[0xb4][0xb][0xc1]r[0x0]/;T[0xc2]g1[0xd6]1y1N[0x89][0x10]G[0xd7][0x82][0x15][0xf2]U[0xb4][0x8][0xb][0xc6]NAa[0x10][0x8d][0x8][0x2][0xf6][0xb6][0xd4][0xce]:z[0xf0]qi[0xff]][0xd9][0xc8]Yi[0xdf][0xdc]0[0x9][0x1a][0x9]8[0xa0]B[0x1d]<[0xe4]Y[0xe][0xdf]l@[0xa7][0xfc][0x9f][0x85])[0x99][0xc9][0x9d][0xef]gj[0x1c][0xc7]l,&.n[0x94][0xc3][0xd3][0xed][0xcd][0xfd][0xb4]|[0xda]k[0x1f][0x84][0x96]H[0xeb][0x84][0x90][0xf2]h[0xe7][0xd2][0xa1][0x8][0xd8][0x90][0xe8][0xe0][0xe1][0xc3]bE[0xbf][0x92][0xc7][0xe2][0xf2]j[0xbb][0xa6][0xf5][0x82][0xe5][0xcb][0x94][0x9d][0xa5][0xec]|[0x9b][0x9f][0xf0][0x82]qV<[0x97][0xf0][0xab]t[0x1e]F[0xe3][0xea][0x8b]x[0x96][0xe][0xc9][0xe6][0xee]z[0x8f][0xce][0xcf]I[0x9]?[0xbf][0xae]N>[0x1]PK[0x7][0x8][0x9d][0xf0][0x7][0x1e][0x5][0x1][0x0][0x0][0xf4][0x1][0x0][0x0]PK[0x3][0x4][0x14][0x0][0x8][0x8][0x8][0x0][0xd4]s[0xe9]L[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0xb][0x0][0x0][0x0]_rels/.rels[0xad][0x92][0xc1]N[0xc3]0[0xc][0x86][0xef]}[0x8a]([0xf7][0xd5][0xdd][0x90][0x10]BMwAH[0xbb]Mh<@H[0xdc]6j[0x13]G[0x89][0x7][0xe5][0xed][0x9][0x7][0x4]C[0xc]v[0xe0][0x18][0xe7][0xf7][0xe7]O[0xb2][0xdb][0xed][0xe2]g[0xf1][0x8c]);[n]”

DEBUG: << “J[0xae][0xeb]F[n]”

DEBUG: << “[0xc][0x86][0xac][0xb][0x83][0x92][0x8f][0x87][0xfb][0xd5][0x8d][0xdc]vU[0xd5]>[0xe0][0xac][0xb9]d[0xf2][0xe8]b[0x16][0xa5])d%G[0xe6]x[0xb][0x90][0xcd][0x88]^[0xe7][0x9a]”[0x86][0xf2][0xd3]S[0xf2][0x9a][0xcb]3[r][0x10][0xb5][0x99][0xf4][0x80][0xb0]i[0x9a]kH_[0x19][0xb2][0xab][0x84]8[0xc1][0x8a][0x9d]U2[0xed][0xec]Z[0x8a][0xc3]k[0xc4]K[0xf0][0xd4][0xf7][0xce][0xe0][0x1d][0x99][0xa3][0xc7][0xc0]?L[0xf9][0x96](d[0x9d][0x6]d%[0x97][0x19]^(MODS][0xa0][0x12][0xce][0xea]l[0xfe]S[0x7][0x17][0xc6]`[0xd1][0xae]b*[0xfd][0x89][0x1d][0xe6]O’Kf_[0xca][0x19]t[0x8c]H]].u~[0x5][0xe0][0x91][0xb5][0xd5][0xac][0xc1]P[0xc2][0xdf][0x95][0xde][0x13][0x1f]N-[0x9c]CW[0xbd][0x1]PK[0x7][0x8]W(^#[0xe3][0x0][0x0][0x0]F[0x2][0x0][0x0]PK[0x3][0x4][0x14][0x0][0x8][0x8][0x8][0x0][0xd4]s[0xe9]L[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x13][0x0][0x0][0x0][Content_Types].xml[0xad][0x93][0xcb]N[0xc3]0[0x10]E[0xf7][0xf9][n]”

So basically the API is dumping even the binary content of the file to logs. This debug log is what we want to avoid being written to logs.

In order to fix this we created a log4j.properties file with entries shown below, made sure that the file is getting read properly by removing the entry log4j.appender.A1.layout from the file and we got a warning indicating this entry is missing. When I debug just before calling readObjectStream method the Atmos Client object created was (com.emc.atmos.api.jersey.AtmosApiClient) – So we tried to set the logger level to ERROR for this package – but still we can see all the binary content being dumped to catalina.out!! Any hints to solve this is greatly appreciated!! Thanks in advance.

# Set root logger level to DEBUG and its only appender to A1.

log4j.rootLogger=ERROR, A1

# A1 is set to be a ConsoleAppender.

log4j.appender.A1=org.apache.log4j.ConsoleAppender

# A1 uses PatternLayout.

log4j.appender.A1.layout=org.apache.log4j.PatternLayout

log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x – %m%n

# Print only messages of level INFO or above in the package com.emc.

log4j.logger.com.emc=ERROR

log4j.logger.com.emc.atmos.api.AtmosApi=ERROR

log4j.logger.com.emc.atmos.api.jersey=ERROR

Jars being used: atmos-client-3.0.1.jar, commons-httpclient-3.0.1.jar, jersey-apache-httpclient4-1.18-CUSTOM.jar

, jersey-client-1.19.jar, jersey-core-1.18.jar

Related:

Citrix RTOP 2.4: lync.exe freezes during a video call

Citrix support has a fix created after making changes so that GetProcessByID is called in debug build [LC9845]. Contact Citrix support to get the private fix.

Private File Disclaimer: This private fix (Private) was targeted only at your affected functionality, and regression and stress testing were minimal. Therefore, this fix might cause undesirable and unknown side effects. Introduce this Private to a test environment for evaluation before deploying it to a production environment. Your use of this Private is at your own risk. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND CITRIX AND ITS SUPPLIERS SPECIFICALLY DISCLAIM WITH RESPECT TO THE PRIVATE ANY CONDITIONS OF QUALITY, AVAILABILITY, RELIABILITY, SECURITY, LACK OF VIRUSES, BUGS OR ERRORS, OR SUPPORT AND ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER CITRIX, ITS SUPPLIERS SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, MULTIPLE, PUNITIVE OR OTHER DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF DATA, LOSS OF INCOME, LOSS OF OPPORTUNITY, LOST PROFITS, COSTS OF RECOVERY OR ANY OTHER DAMAGES), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT FOR BREACH OF CONTRACT, NEGLIGENCE OR OTHERWISE, AND WHETHER OR NOT CITRIX, ITS SUPPLIERS, OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Citrix offers no assurance that this Private will be incorporated into the commercial version of the associated Citrix product or that it will work with future versions of such product.

Related:

7022828: How to debug Enhanced Access Control (EAC) policies for Linux / Unix

To print debug session initialization details from cmdctrl to the terminal, add one of the following to the cmdctrl rule’s user message field:

  • For XML output: $<>$
  • For JSON output: ${}$


For client-trace debugging of commands (similar to strace), append the following to the cmdctrl rule’s Script Arguments, in the Value field:

trace <number>

Note: Replace <number> with a number ranging from 1-3, with 3 providing the highest level of detail. Debug output should then be printed to the client’s terminal.

Related:

7021543: Using Model Debug Messages in Verastream Host Integrator

Recording Model Debug Messages

Model debug messages can be recorded in Design Tool or Session Server.

Design Tool

Model debug messages recording is always enabled for models you open in Design Tool.

Session Server

The Session Server can be configured to record model debug messages at runtime. This feature is designed to minimize performance impact on the server. The recorded .vmr files can be later opened in Design Tool for analysis.

You can configure the recording level using one of the following methods:

Choose one of the following options:

Record nothing: No model debug messages are recorded. This option is the default behavior.

Record errors: Model debug message files are only retained when an error is encountered. However, this option only captures the last error event, such as the procedure that failed, not the entire session.

Record error sessions: This option is available beginning in version 7.7. When an error is encountered, the entire session is captured from the beginning.

Record everything: All model debug message files are retained. This setting may be appropriate when debugging a model under development. However, on a production server, this option may generate a large number of .vmr recording files and have an impact on server performance.

You can change the recording file directory or file retention behavior in Administrative Console (Session Server Properties > General > Model Debug). See also http://docs2.attachmate.com/verastream/vhi/7.7/en/topic/com.attachmate.vhi.vmc.help.online/tasks/vhi_mc_srv_prop_general.xhtml.

Opening Model Debug Messages

To open the Model Debug Messages dialog box in Design Tool, click Debug > Model Debug Messages. Alternatively, you can press Ctrl+Alt+M to open the Model Debug Messages dialog box.

To open a model debug messages .vmr file previously saved in Design Tool or recorded by a Session Server, do one of the following:

  • In the Model Debug Messages dialog box, click the Open button.
  • In Windows Explorer (on a system with Development Kit install), double-click the .vmr file.

Note the following:

Using Model Debug Messages

The Model Debug Messages dialog box displays a message list on the left, and message details on the right.

Message List

See Figure 1 below for a sample model debug message list. Use the following toolbar buttons to manipulate the messages list:

10065_1.gif

Display all messages.

10065_2.gif

Display only datastream messages.

This option displays only messages that relate to the terminal exchanging data with the host, such as transmit, receive, and data processing messages. This option also displays entity arrival and departure, operation start and end, and errors associated with the datastream messages.

10065_3.gif

Display relative time for descendants (toggle option).

By default, descendant messages associated with an action such as navigating to another entity are displayed with the time of the descendant message. Click this option to show time that elapsed relative to the action’s start. This option helps identify abnormal delays associated with specific messages.

10065_4.gif

Find a message.

Click this option and type in a string to locate a specific message. You can also use the Find Message dialog box to find other occurrences of the messages, or to find messages of the same type as the selected message.

10065_5.gif

Find next error.

Click this button to locate the messages that are tagged as errors in the model debug messages list.

10065_6.gif

Clear all messages. (Actions that are in progress will not be cleared.)

Use this option when you are debugging a development version of a model and want to see the model’s behavior after making some changes. You can save the previous collection of model debug messages before you use this option.

10065_7.gif

If you have opened an additional model debug message .vmr file, click this button to close the file. (The Current Model tab cannot be closed.)

Message Details

The right panel of the Model Debug Messages dialog box shows the details of the message selected on the left. Depending on what type of message is selected, the right panel will show one or more of the following:

Datastream Panel

When a datastream message is selected, the datastream panel provides the following functionality:

  • You can view the raw data sent to and received from the host. Nonprintable characters, such as control functions, appear in blue text.
10065_11.gif
  • When debugging a VT model, use the Suggest Escape Sequence button to have the model debug messages utility suggest a unique trailing escape sequence (if present) that can be used to help synchronize the model.
  • Use the Next Match button to move to the next occurrence of the entered string.
10065_13.gif
  • Use the Previous Match button to move to the previous occurrence of the entered string.

Locating and Solving a Synchronization Problem

If your model does not reach an expected entity or cursor location, review the model debug messages. The example below shows a sequence on a VT host for a PageDown operation.

The final message, indicating unexpected bytes received from the host, is a strong indicator of a synchronization problem with the host. By reviewing the messages preceding this message, you can narrow down the source of the problem.

The highlighted message, “Operation AddressBook.PageDown arrived at AddressBook (primary)” has the associated ending snapshot on the lower-right panel:

Figure 2: Ending Snapshot

Figure 2: Ending Snapshot

With a PageDown operation, a full screen of data should have been processed, but the action and the associated snapshot shows only a subset of the host screen (with a gray background) was actually received.

To ensure that all of the expected data is processed before proceeding, you can add a WaitForCommString command to the operation. Use the Suggest Escape Sequence button as described in Datastream Panel section above.

Note: There may be cases where a synchronization issue does not produce a message that unexpected bytes were received from the host, especially when running on the server. It is a good idea to look for partial operation snapshots similar to the one above whenever the model does not reach an expected entity or cursor location.

Related: