How to enable/collect logs on WEM Broker

TYPES OF LOGS AVAILABLE:

FOR LOGGING INFORMATION RELATING TO WEM AGENTS, SEE CTX220635

There are a number of logs that can be collected from the WEM Broker to help with troubleshooting/diagnosing an issue

A: WEM Infrastructure Broker Service issues:

#1: WEM Infrastructure Broker Event logs

These logs are created be default in Event viewer. This event viewer log is where the Infrastructure Broker Service will log all basic errors.

a: Norskale Broker Service

This log can be found inside Event Viewer under the “Applications and Services logs” section.

#2: WEM Infrastructure Debug Log

This log must be manually enabled for the WEM Infrastructure Broker Service.

a: Citrix WEM Infrastructure Service Debug.log

To enable Debug logging for the Infrastructure Broker Service, go to the “Advanced Settings” tab in the Infrastructure Broker Service Configuration console (a/k/a “WEM Infrastructure Service Configuration Utility”), tick the “Enable Debug Mode” checkbox & click “Save Configuration”.

#3: WCF Trace:

This WCF trace must be manually configured and is normally helpful when there is a communication issue which involves the WEM Broker.

a: Norskale Broker Service.exe

B: WEM Console issues:

This is the main log for the WEM Administration Console; If the WEM Administration Console is erroring out, this log will likely contain the cause of the error. This log is NOT enabled by default.

#1: Citrix WEM Console Trace.Log:

To enable verbose logging (debug mode), open the WEM Administration Console, click on the “Options” tab in the top ribbon, tick the “Enable Debug Mode” checkbox & click “Apply”.

#2: WCF Trace

This WCF trace must be manually configured and is normally helpful when there is a communication issue between any WEM Console and the WEM site/database.

a: Norskale Administration Console.exe


C: WEM Database issues:

This log is created whenever the Database Management Console/Utility attempts a database creation or upgrade & logs all errors pertaining to those operations.

#1: Citrix WEM Database Management Utility Debug Log.log:

This log is created by default and is located in the following default location: “C:Program Files (x86)NorskaleNorskale Infrastructure Services”

HOW TO IMPLEMENT AND GATHER LOGS:

A: WEM Infrastructure Broker Service issues:

#1: WEM Infrastructure Broker Event logs

***Created by default during normal WEM Broker operations***

Filename: Norskale Broker Service

Location: Event Viewer >> “Applications and Services Logs”

#2: WEM Infrastructure Debug Log

***Must be manually enabled***

Filename: Citrix WEM Agent Host Service Debug.log

Location: “%PROGRAMFILES(X86)%NorskaleNorskale Agent Host”

#3: WCF Traces:

***Must be manually enabled***

a: Norskale Broker Service

Filename: NorskaleInfrastructureBrokerService-Traces.svclog

Location: “C:Trace”

#1: Stop the “Norskale Infrastructure Service”.

#2: Make a backup copy of the “Norskale Broker Service.exe.config” file located in the default location of “%PROGRAMFILES(X86)%NorskaleNorskale Infrastructure Services”.

#3: Using Notepad or Wordpad, edit the original .config file adding the multiple lines of code from the attached document named “Norskale Infrastructure Broker Service.txt” to the file. Paste the code into the file starting on the 2nd line just after the <configuration> marker, then save the file.

#4: Create a directory on the root of the C: drive called “trace” if one does not already exist.

#5: Start the “Norskale Infrastructure Service”.

Here are contents of the attached file:

User-added image

B: WEM Console issues:

#1: WEM Console Debug Log

***Must be manually enabled***

Filename: Citrix WEM Console Trace.log

Location: “%userprofile%”

a: Citrix WEM Console Trace.Log

#1: To enable verbose logging (debug mode), open the WEM Administration Console, click on the “Options” tab in the top ribbon, tick the “Enable Debug Mode” checkbox & click “Apply”.

#2: Launch the WEM Administration Console

#2: WCF Trace:

***Must be manually enabled***

a: Norskale Broker Service

Filename: WEMConsole-Traces.svclog

Location: “C:Trace”

#1: Close the WEM Administration Console if open.

#2: Make a backup copy of the “Norskale Administration Console.exe.config” file located in the default location of “%PROGRAMFILES(X86)%NorskaleNorskale Administration Console”.

#3: Using Notepad or Wordpad, edit the original .config file adding the multiple lines of code from the attached document named “WEM Administration Console.txt” to the file. Paste the code into the file starting on the 3rd line just after the <configuration> marker, then save the file.

Here are contents of the attached file:

User-added image

#4: Create a directory on the root of the C: drive called “trace” if one does not already exist.

#5: Launch the WEM Administration Console and connect to the WEM site, reproduce issue & close the console to write the logs.

C: WEM Database issues:

#1: Citrix WEM Database Management Utility Debug Log.log:

***Created by default when performing any database creation/upgrade from the WEM Broker server***

Filenames: Citrix WEM Database Management Utility Debug Log.log

Location: “%PROGRAMFILES(X86)%NorskaleNorskale Infrastructure Services”

****REVERT ALL CHANGES AFTER COLLECTING THE APPROPRIATE LOGS****

FOR LOGGING INFORMATION RELATING TO WEM AGENTS, SEE CTX220635

Related:

Error: “No servers available for disk” When Booting from vDisk

When configuring a vDisk for private mode, any device booting from that vDisk gets the “No servers available for disk” error.

For example, when connecting to the Provisioning Services (PVS) console on the first server, the vDisk is listed as private mode. When the console is connected to PVS console on the second server, the error appears when viewing the vDisk.

Related:

SD Times news digest: Microsoft launches Windows Terminal, Hyperledger Iroha 1.0 is available …

Microsoft launched Windows Terminal, a command-line app for Windows that supersedes the company’s original command-line user experience, the Windows console host.

Windows Terminal offers support for tabs, rich text, globalization, configurability, theming & styling, and more.

The limitations of the original console host, which was aimed at maintaining backward compatibility, led the Microsoft team to develop the new terminal that added community-requested features, according to the company.

In addition to having a modernized codebase, Windows Terminal’s logical entities are separated into modules and classes, new key extensibility points are available, and home-grown collections and containers are replaced with safer, more efficient STL containers.

Hyperledger Iroha 1.0 is available

Hyperledger Iroha 1.0, the distributed ledger project that is hosted by The Linux Foundation, is now available.

The project aims to provide a development environment where C++ and mobile application developers can contribute to Hyperledger, according to a post by the company.

New Hyperledger Iroha 1.0 features include YAC Consensus, a safety consensus protocol, multisignature options for transaction settlement, support for writing apps on many platforms from mobile to mainframe with a variety of languages and native Windows support.

Hyperledger Iroha is the fourth active Hyperledger project to reach 1.0, following Hyperledger Fabric, Sawtooth and Indy.

.Inc domains are now available

.Inc are generally available at noon today and more than a fifth of Fortune US 100 Companies and Forbes 100 World’s Most Valuable Brands have already registered their own.

Participating retailers, such as GoDaddy and Name.com, are including free .inc benefits like Microsoft Office 365 and Google G Suite for their respective customers. WeWork, Square, Intuit, Google Ads, Delta Air Lines also adding their own benefits to getting a .inc domain.

“The great thing about a .inc domain name is that when a customer sees it, they’ll know they are headed to a business website,” said Paul Bindel, the vice president of product marketing at GoDaddy. “In addition to a great name, businesses get valuable services to complete their online presence.”

All .inc domains can be registered for a flat fee of $1,999, which ensures that cybersquatters won’t buy the best domains.

Related:

Shifting Computer Name

I need a solution

Hi Everyone,

I have a single computer entry my Ghost console that keeps shifting, for lack of a better word, between two different computers on my network. First it starts out as Computer1, then on a refresh of the console, all the information (in the SAME entry) shift to Computer2, then back again.

Both computers have previously been attached to Ghost, but Computer2 has a brand new installation of Windows 10 on it. None of them have any information in common.

Has anyone run into this before? If so, what was the solution?

Thanks for any help!

0

Related:

VxRail: Unable to open JViewer console on Quanta nodes with error “Connection failed”

Article Number: 524478 Article Version: 3 Article Type: Break Fix



VxRail Appliance Family

After logging in normally to BMC interface, when navigating to Remote Control > Console Redirection and pressing Java console, the Console screen is able to open. However, JViewer crashed with error “Connection Failed!”

BMC ports are not open on the network.

Please make sure that at least ports 80, 443, 7578, 5120 and 5123 are open for inbound and outbound connections.

Full list of services and their associated ports is in the following screenshot:

User-added image

Related:

Unable to open PVS Console after upgrade to 7.17

Unable to open PVS Console after upgrade to PVS 7.17 with error

An unhandled exception occurred and the application will exit. Please report the information below. Press Ctrl-C to copy the data to the clipboard.

Method not found: ‘!!0[] System.Array.Empty()’.

Stack Trace:

at ADSupport.PublicFunctions.GetOneTimeADInfo() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

User-added image

Related:

ATP 3.0 & SEPM 14

I need a solution

Dear All,

regarding ATP 3.0 can anyone help me with below points.

1 How may SEPM integrate in Single ATP console.

2 How we can configure DC-DR SEPM console in single ATP console, concern is both Database is separate but working in Active –passive configuration.

Thanks in advance.

0

Related:

  • No Related Posts

7021585: Verastream Host Integrator 7.1 Service Packs 1 and 2 – Features, Fixes, and Release Notes

What’s New in 7.1 SP2?

This release includes the previous SP1 features and fixes, plus the following additional updates:

Web Builder Updates

  • Multiple improvements for Web Builder-generated “rejuvenation” applications that display host terminal screens (Project Properties > Screens > Unrecognized or Recognized screens > Display: Terminal):
    • Web Builder has simplified Aid Key Settings (Enable or Disable). In previous versions, the options were “Always show aid keys,” “Always hide aid keys,” and (for Recognized Screens) “Hide aid keys when operations are available.”
    • When the aid keys are enabled in Web Builder, the generated web pages have more flexibility for users and do not display the aid key buttons by default. The web page Actions menu contains a Show Aid Keys or Hide Aid Keys link. When navigating across screens in the host application, this state is remembered for the session. (In previous versions, the on-screen aid key buttons were always displayed when aid key mapping was enabled.)
    • When the aid keys are enabled in Web Builder, in the resulting generated web application pages, it is easier for the user to send an Enter aid key to the host application:

The Ctrl+Enter keystroke always invokes Enter.

The Enter key by itself can also invoke Enter, if either no operations are available for the current entity screen (such as an unrecognized screen), or by configuring Enter Key Behavior to send Enter Aid Key instead of the entity default operation (Project Properties > Screens > Recognized Screens > Display: Terminal > your entity > Operations).

Exception Details: System.ArgumentException: Item has already been added. Key in dictionary: 'ProcedureName' Key being added: 'ProcedureName'

Administrative Console Improvements

  • Improved performance when Administrative Console is connecting to management server over a VPN or low-bandwidth network link. After entering credentials, the Administrative Console user interface is available more quickly. If loading the management server data takes longer than 0.8 sec, a progress dialog is displayed. In versions 7.0 through 7.1.1142, loading the management server data after connecting could cause Administrative Console to go into an unresponsive state.
  • In Administrative Console, in session server and pool properties, the “Create pooled sessions concurrently” option has been removed. To achieve the same functionality as disabling this option (version 6.x behavior), set “Max pending sessions” to 1 (although higher values are recommended for optimal performance). In versions 7.0 through 7.1.1142, after disabling the check box option, it would later display as re-enabled.
  • Administrative Console properly closes, exits, or disconnects when a Session Monitor view is open (displaying host screens). In previous versions, this situation may cause the Administrative Console application to become unresponsive (Windows task “not responding”).
  • In Administrative Console, usability is improved if incorrect administrative credentials are entered. In versions 7.0 through 7.1.1142, if incorrect credentials were entered, the dialog would close and re-display with blanked out fields, so the user name had to be re-entered.
  • In Administrative Console, there are no longer sessions displayed with the status Uninitialized. In versions 7.0 through 7.1.1142, under certain timing scenarios, uninitialized sessions may display and cannot be terminated. (Typical normal status values are Idle, Active, Rogue, or Suspended. Also, when idle sessions are created, they may briefly display Not Connected before connecting to the host.)
  • Both Administrative Console and Design Tool Deployment Options disallow the same non-alphanumeric characters in pool names, such as hyphen and dot. In previous versions, these components behaved inconsistently.
  • If a model package with pool(s) is undeployed, it will no longer cause a NullPointerException in Administrative Console. In previous versions, if the deactivatemodel command is run while a session server view is open in Administrative Console, it causes a console error such as the following:
ERROR [SessionImpl]: An unhandled exception occured while handling a JMX Notification: null java.lang.NullPointerException

at com.attachmate.vhi.vmc.ui.providers.DomainSessionServersTableViewContentProvider.modelChanged(Unknown Source)

Security and Other Updates

CSW >>>>> : VHI configuration: setting the admin password...

CSW >>>>> : The command returned 42

CSW >>>>> : VHI configuration: registering the Session Server...

CSW >>>>> : The command returned 42

CSW >>>>> : VHI configuration: registering the Host Emulator Server...

CSW >>>>> : The command returned 42

CSW >>>>> : end of VHI configuration.
  • In the installed jconsole.bat (Windows) and jconsole.sh (UNIX/Linux) script files, the CLASSPATH has been corrected. These undocumented scripts are used to run the JConsole application and access the management server via JMX.
  • Attachmate’s use of updated development tools effected other internal product changes.

What’s New in 7.1 SP1?

Service Pack 1 includes the following key features and product updates:

Key Features

  • Web services WSDLs are easier to find:
    • WSDL links are conveniently available in Administrative Console (in Server, Model, and Pool Properties > Web Services category).
    • To view the list of web service WSDLs, you can use a shorter URL http://sessionserver:9680 that will redirect. In versions 7.0 and 7.1.221, you had to use the longer URL http://sessionserver:9680/vhi-ws.
  • Security improvements:
    • Multiple security vulnerability fixes. For more information, see Technical Note 2700.
    • Expanded FIPS 140-2 SSL encryption support. Administrative Console and management server communications are automatically encrypted using components that comply with US Government standards (see Technical Note 2400). Note: Host communications must still be separately enabled for FIPS mode encryption as described in Technical Note 10068.
    • To enhance security, each session server instance generates a unique private key and certificate for SSL encrypted communication with connectors, if enabled. (Connector-to-session server encryption is enabled by calling the RequireSecureConnection API method before connecting, enabling the “Require secure connection” option in Web Builder Project Properties, or enabling security in Session Server Properties in Administrative Console.)
  • IBM AIX support added. Server Kit version 7.1.221 was not available for this UNIX platform, but AIX support has been restored for version 7.1.1142. For more information about supported platforms and system requirements, see Technical Note 10030.

Design Tool Updates

  • The Model Debug Messages dialog in Design Tool allows opening up to 50 .vmr files simultaneously. In versions 6.0 through 7.1.221, only 4 files could be open per Design Tool instance.
  • Resolved an issue where Design Tool could terminate ungracefully when applying certain changes to Recordset Field Operations.
  • In Design Tool Settings, if you have configured the 3270 Numeric Input Field Character Set option to “Numeric Characters Only” or “All Characters,” field input is properly restricted when the model is deployed to a session server. In version 7.1.221 and earlier, the setting was not saved, so the default “Numeric and Uppercase Characters” was always used.

Administrative Console Updates

  • If pool schedules are configured in Administrative Console, they are properly displayed in the pool properties for the appropriate session server only. In versions 7.0 through 7.1.221, the pool schedules could improperly display in other pool properties (if the same pool name was used on other session servers in the management cluster).
  • Repeatedly refreshing Administrative Console (with F5 function key) no longer causes a significant session server performance impact. Multiple refresh requests are coalesced instead of queued up.

Installer Improvements

Other Fixes

  • When Session Server is started or exits ungracefully, its configuration is automatically backed up as a sesssrvr.config.backup file in the %VHI_ROOT%/etc directory. This file can be used to restore the previous configuration state (by renaming it to sesssrvr.config when the service is stopped).
  • Improved authentication handling when management server is running on a Windows system with multiple network interfaces. In versions 7.0 and 7.1.221, errors could occur when authentication is required, such as:
    • When deploying models (with Design Tool, or running the activatemodel or deactivatemodel commands), the following errors may display:
[VHI 3852] Deployment of model failed: Cannot establish management session

[VHI 3852] Deployment of model failed: Token binding is invalid
[VHI 4814] Access to Reflection for the Web session configuration information http://hostname failed: The data area passed to a system call is too small.

[VHI 4810] The Reflection for the Web security proxy server that the session connects to is configured without client authorization. This is not supported.

Obtaining Your Product Update

Customers with a current maintenance plan are eligible to download Verastream Host Integrator 7.1 SP2 from the Attachmate Download Library at http://download.attachmate.com/Upgrades/.

For more information on using the Download Library, see Technical Note 0200.

Note: The product download is a full product “7.1+SP2” package that can be used for new installations or to upgrade existing installations.

Installing Your Product Update

For more information about installing the update on an existing installation, refer to the appropriate Technical Note:

Related:

Log entries of multiple instance jobs on Datastage Director Client on ver11.5 (FP2)

Hi everyone – Does anyone notice you can’t see the log entries of more than 5 multiple instance jobs on Datastage Director Client or CLI output on IIS v11.5 FP2? Do you know whether this is a new feature on IIS v11.5 (FP2) or not?

Is there any way to increase the number of visible multi-instance instead of just 5 jobs?

PS: I’m aware of Datastage Operations Console you’ll be able to see the multiple instance jobs and their job logs.

Regards,

Ozgur G

![alt text][1]

[1]: /answers/storage/temp/19692-screen-shot-2018-01-13-at-183800.png

Related:

  • No Related Posts