Smart Response – Custom Payloads in Cloud Applications

I need a solution

I and trying to find ways to recreated Automated Response rules as custom payloads. Documentation on custom payloads is very elusive.

A normal Automatic Response Rules have a rich set of options to remediate issues. In contrast, the Smart Response rules are very limited. Is there a way to use the custom payload to perform similar actions.

Example:

  • Cloud Application and API Appliance (Data-at-Rest) 
    • Option: Remove Shared Links in Data-at-Rest
  • Cloud Application and API Appliance (Additional Data-at-Rest Actions) 
    • Option: Remove Collaborator Access

I can’t find much documentation but the { “action”: “collab_access_remove” } does not work and there is no error or debug logs I can find.

Any help would be valuable.

0

Related:

  • No Related Posts

Delete File Component causes System.UnauthorizedAccessException

I need a solution

Hello,

We are using a workflow form to import computers into our environment (yes, still 7.5, we’re working on that).

We create a predefinedcomputers.csv as it can be found in \servernscapbinWin32X86DeploymentSamplePreDefinedComputers, and to be correct, we create a copy of that file in that specific location.

Everything works fine when I try it in the debugger, but after publishing and when using the published workflow, I get a System.UnauthorizedAccessException for the path.

Any ideas?

0

1527153601

Related:

  • No Related Posts

Hotfix XS71ECU1016 – For XenServer 7.1 Cumulative Update 1

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 1. All customers who are affected by the issues described in CTX234679 – Citrix XenServer Multiple Security Updates should install this hotfix.

This hotfix does not apply to XenServer 7.1. You must apply Cumulative Update 1 before you can apply this hotfix.

Note: XenServer 7.1 Cumulative Update 1 and its subsequent hotfixes are available only to customers on the Customer Success Services program.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks* Restart Host
Content live patchable** No
Revision History Published on May 8, 2018
* Important: If you have previously disabled microcode loading on your XenServer host or pool. You must enable microcode loading again after applying this hotfix. For more information, see How to disable microcode loading on a XenServer pool.
** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS71ECU1016-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Before installing this hotfix, we recommend that you update your version of XenCenter to the latest available version for XenServer 7.1 CU 1.

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the section Applying Automated Updates in the XenServer 7.1 Cumulative Update 1 Installation Guide.

For information about installing a hotfix using the Download update from Citrix option, see the section Applying an Update to a Pool in the XenServer 7.1 Cumulative Update 1 Installation Guide.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS71ECU1016.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS71ECU1016.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    93364429-91e6-4c71-a761-a19269642d1c

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=<UUID_of_file>

    Alternatively, if you want to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe upload-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS71ECU1016

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this hotfix was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU1016.iso
Hotfix File sha256 fc5f77170f261a308dda34624e67fd4704cbe1d7a48e58f2d83dd8c06f4e1942
Hotfix Source Filename XS71ECU1016-sources.iso
Hotfix Source File sha256 def6fdd14ad790760d7a7f2a5017fa3895871e64b6ad6418f6b3fd1af02f84c2
Hotfix Zip Filename XS71ECU1016.zip
Hotfix Zip File sha256 4e63fd5525554fda8a98c40473cb48c4891560b915dfff4be3e56a9c5794d709
Size of the Zip file 31.67 MB

Files Updated

dracut-033-360.el7.centos.xs13.x86_64.rpm
dracut-network-033-360.el7.centos.xs13.x86_64.rpm
kexec-tools-2.0.4-31.x86_64.rpm
linux-firmware-20170622-3.noarch.rpm
microcode_ctl-2.1-22.xs1.x86_64.rpm
xen-dom0-libs-4.7.5-1.17.x86_64.rpm
xen-dom0-tools-4.7.5-1.17.x86_64.rpm
xen-hypervisor-4.7.5-1.17.x86_64.rpm
xen-libs-4.7.5-1.17.x86_64.rpm
xen-tools-4.7.5-1.17.x86_64.rpm

More Information

For more information see, the XenServer 7.1 Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

7022954: How to collect JAVA dumps for taskomatic debugging

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

Environment

SUSE Manager 3

Situation

When debugging taskomatic related issues, a JAVA dump may be useful for further debugging.

Resolution

Please run the command:

kill -3 `ps aux | grep Taskomatic | head -1 | awk ‘{print $2}’`

The core dump file will be saved to /var/crash/javacore.YYYYMMDD.*

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:

  • No Related Posts

Hotfix XS74E001 – For XenServer 7.4

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.4. All customers who are affected by the issues described in CTX234679 – Citrix XenServer Multiple Security Updates should install this hotfix.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks Restart Host
Content live patchable* No
Baselines for Live Patch N/A
Revision History Published on May 08, 2018
* Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS74E001-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the section Applying Automated Updates in the XenServer 7.4 Installation Guide.

For information about installing a hotfix using the Download update from Citrix option, see the section Applying an Update to a Pool in the XenServer 7.4 Installation Guide.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS74E001.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS74E001.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    85893d4f-4ab6-460d-9074-ebd4847078c0

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=<UUID_of_file>

    Run the following command if you would like to apply the hotfix for a individual host:

    xe update-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe upload-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS74E001

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS74E001.iso
Hotfix File sha256 82a41f4610ae03051215df0a22baba5c374eb868ecfe49711737ca93859893dc
Hotfix Source Filename XS74E001-sources.iso
Hotfix Source File sha256 fe721e2fe6b8453bcc707981e3b214f052d8c8abb653964541c6487253477107
Hotfix Zip Filename XS74E001.zip
Hotfix Zip File sha256 3d4f51cbcd76155ae1ec521f4ecee3ffef40c40f1f42d8abc8804915f518fe25
Size of the Zip file 5.59 MB

Files Updated

microcode_ctl-2.1-22.xs1.x86_64.rpm
xen-dom0-libs-4.7.5-4.2.x86_64.rpm
xen-dom0-tools-4.7.5-4.2.x86_64.rpm
xen-hypervisor-4.7.5-4.2.x86_64.rpm
xen-libs-4.7.5-4.2.x86_64.rpm
xen-tools-4.7.5-4.2.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Hotfix XS73E004 – For XenServer 7.3

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.3.

All customers who are affected by the issues described in CTX234679 – Citrix XenServer Multiple Security Updates should install this hotfix.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks* Restart Host
Content live patchable** No
Baselines for Live Patch N/A
Revision History Published on May 8, 2018
* Important: If you have previously disabled microcode loading on your XenServer host or pool. You must enable microcode loading again after applying this hotfix. For more information, see How to disable microcode loading on a XenServer pool.
** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfix:

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS73E004-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the section Applying Automated Updates in the XenServer 7.3 Installation Guide.

For information about installing a hotfix using the Download update from Citrix option, see the section Applying an Update to a Pool in the XenServer 7.3 Installation Guide.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS73E004.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS73E004.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    ba963670-fd85-4530-82c1-a1f70c401e34

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=<UUID_of_file>

    Run the following command if you would like to apply the hotfix for a individual host:

    xe update-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe upload-apply host-uuid=<UUID_of_host> uuid=<UUID_of_file>

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS73E004

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, carry out any specified post-update task on each host, starting with the master.

Files

Hotfix File

Component Details
Hotfix Filename XS73E004.iso
Hotfix File sha256 8888537f03ce37a90fe29ee03fa5e33f19d9bc180abd889b709f8550c6ef6421
Hotfix Source Filename XS73E004-sources.iso
Hotfix Source File sha256 a8f9ed98a1fdf8b8b42f009291503ee91ea622f8ca040cfc82e00fdc8899a0f0
Hotfix Zip Filename XS73E004.zip
Hotfix Zip File sha256 fb3979beeeddaeceb879db9a259a5ff5fa2c2b1ab5922ca924e380cb402c8172
Size of the Zip file 31.65 MB

Files Updated

linux-firmware-20170622-3.noarch.rpm
dracut-033-360.el7.centos.xs13.x86_64.rpm
dracut-network-033-360.el7.centos.xs13.x86_64.rpm
xen-libs-4.7.5-3.4.x86_64.rpm
xen-tools-4.7.5-3.4.x86_64.rpm
xen-hypervisor-4.7.5-3.4.x86_64.rpm
microcode_ctl-2.1-22.xs1.x86_64.rpm
xen-dom0-tools-4.7.5-3.4.x86_64.rpm
xen-dom0-libs-4.7.5-3.4.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

Related:

  • No Related Posts

Getting latest release while in trial period

I need a solution

Firstly, I think it is unreasonable for Symantec not to offer support to trial users in setting up what is a very complex product. I have spent several days getting the server and managed desktop components working and finally it is starting to make sense. However, I have experienced the BSOD referred to in article TECH248240 when accessing Office documents and am hoping that the suggested hotfix 10.4.1 MP2 HF2 may help (although I am generating the desktop installer from the server so not sure if the hotfix only applies to unmanaged installations).

However, as a trial user not only do I get no support but also no serial number so I can’t access fileconnect to download any updates.

Here’s hoping someone from Symantec can help.

0

Related:

  • No Related Posts

7021506: Performing a Trace in an IBM Host session with Reflection Desktop 16, Reflection 2014, or Reflection 2011

Generating a Host-Data (*.HST) or Command (*.CMD) Trace

A host-data trace captures information passed between a terminal, or printer, and the host during a 3270 or 5250 session. This type of trace is useful when a host connection is working, but the terminal or printer session does not behave as expected. For instance, a host-data trace would be useful when troubleshooting problems with colors, cursor movements, print job formatting, or IND$FILE transfer problems (for 3270 sessions). Host traces are not useful when a connection to the host cannot be established.

Note: HST traces capture both *.HST and *.RIT data.

Command traces capture actions within Reflection. An action taken, such as clicking a button or entering text, each represents an individual command. Command traces are useful in determining if commands are correct in a script, macro, or program using OLE automation.

Command traces also can be used to determine which command to use when writing a script. Use a text editor to view the command trace and determine which commands are needed to accomplish the task.

Follow the steps below to generate a host-data or command trace.

  1. In the Reflection Workspace, open or create a new session document.
  2. On the Tools ribbon, from the Tracing group, click Start Trace.
  3. Specify a name for the trace file. Save as type:
    • Host Data (*.HST)
    • Commands (*.CMD)

Note: If you have spoken with a support technician about this issue, you can use your call ID number as the name of your trace file.

  1. Click Save. “Tracing started…” will display in the Reflection status bar, indicating the trace is active.
  2. Perform the actions that reproduce the problem you want recorded in the trace.
  3. To end the trace, click Stop Trace from the Tracing group.

To upload the file to Support, go to https://upload.microfocus.com.

Generating a HLLAPI Trace (.TMP)

HLLAPI is a standard API for automating terminal tasks. HLLAPI traces are available in Reflection Desktop 16, Reflection 2014, or Reflection 2011 products. A HLLAPI trace will enable you to see the HLLAPI calls the application is making, including return codes.

Included below are instructions to generate a HLLAPI trace with Reflection 2014 R1 SP1 or higher or Reflection 2014 R1 or Reflection Standard Suite 2011.

Reflection 2014 R1 SP1 or higher (Including Reflection Desktop 16)

Follow the steps below to generate a HLLAPI trace with Reflection 2014 R1 SP1 or higher:

  1. In the Reflection Workspace Settings, select the Configure Workspace Attributes. Then check the box to Enable HLLAPI logging, and specify a HLLAPI log file name in a location where the user has the appropriate permissions to create and save a file.
View Full Size

Figure 1. Configure Workspace Attributes screen with Enable HLLAPI logging selected
Figure 1. Configure Workspace Attributes screen with Enable HLLAPI logging selected
  1. In the Reflection Workspace, open or create a session document to connect to your IBM host, and start the HLLAPI application. Perform the actions that you want recorded in the trace.
  2. Close the HLLAPI application.
  3. The trace file is automatically saved under the default name of hllapi.log and is located in the folder selected when the trace was started.

To upload the file to Support, go to https://upload.microfocus.com.

Reflection 2014 R1 or Reflection 2011

Follow the steps below to generate a HLLAPI trace with Reflection 2014 R1 or Reflection 2011:

  1. Click Start. In the Start Search box, type win.ini and press Enter. This will open your Win.ini file in Notepad.
  2. Add the following two lines to the end of the Win.ini file:
[Reflection HLLAPI]

ExtTraceOn=1
  1. Save the Win.ini file (click File > Save).
  2. In the Reflection Workspace, open or create a session document to connect to your IBM host, and start the HLLAPI application. Perform the actions that you want recorded in the trace.
  3. Close the HLLAPI application.
  4. The trace file is automatically named Hll*.TMP. The * is a randomly generated hex number. The file is located in the PC’s TEMP directory, if a TEMP directory has been defined in the System Environmental settings. Otherwise, it is located in the root Windows directory.
  5. Re-open the Win.ini file (see step one) and set the ExtTraceOn setting to zero:

[Reflection HLLAPI]

ExtTraceOn=0

Related:

  • No Related Posts

7021679: Generating a Rumba formatted Trace

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

Environment

Rumba Desktop 9.x

Situation

At times it may be necessary to provide Customer Support with diagnostic information in the form of a RUMBA formatted trace. How is this done?

Resolution

On a test machine which you can use to replicate the reported problem:

  1. Close all RUMBA sessions including any RUMBA software items that may be present in the Windows System Tray.
  2. Click Start > Programs > RUMBA Folder > RUMBA Administrative Tools > RUMBA Trace.

    On Windows 10, click the Windows icon, navigate to the Micro Focus Rumba group and select “Rumba 9.x Trace”
  3. In the RUMBA Trace console click File > Clear Formatted File. This will ensure that no previous data is in the trace from past attempts.
  4. In the RUMBA Trace console click Options > Configuration.
  5. On the API Selection tab, click the Select All button.
  6. Click on the Output tab and check the Formatted File check box. Make sure there is no checkmark next to Binary, as we want only a Formatted trace. Make a note of the folder where the Formatted File (e.g. RUMBATRC.FMT) will be saved. You may wish to redirect the output of this file to the desktop to make it easy to locate. Click the OK button when finished on this tab.
  7. Minimize the RUMBA Trace console.
  8. Using a minimal amount of steps, reproduce the issue. If taking simultaneous AS/400 communications trace and/or ODBC traces, or WireShark traces, please be sure that these tracing tools have been setup and started before you start reproducing the problem.
  9. Log-off of the host if necessary, and close the RUMBA display session if possible.
  10. Maximize the RUMBA Trace console and choose File > Exit to end the trace.

Note: You may need to take a trace using the most current version of RUMBA. Check with your SupportLine Specialist if you are not running the most current version of the software. Make sure no other RUMBA or 5250 data stream activity is present on test PC at time of tracing.

Lastly, put the trace file into a ZIP archive and attach it to your support incident.

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:

  • No Related Posts