Hyperledger Fabric and Monitoring

Hyperledger is an open source collaborative effort created to advance cross-industry blockchain technologies. It is a global collaboration, hosted by The Linux Foundation, including leaders in finance, banking, Internet of Things, supply chains, manufacturing and Technology.

Hyperledger Meetup groups have an informal relationship with Hyperledger, and make up a key part of the Hyperledger ecosystem. Participation in a Hyperledger Meetup group is open to anyone–employees of a Hyperledger member company, Hyperledger contributors and developers, and people just passionate about blockchain technology.

Hyperledger Fabric and Monitoring

A technical meetup that will look at the tools for monitoring a production grade Hyperledger Fabric farm, including but not limited to:

– Hyperledger Explorer

– Hyperledger Fabric operation service

– Fabric and Prometheus integration

– Fabric and Grafana metrics



Information & Registration

DATE & TIME: 26th August 2021 / 17:00

VENUE: Online


Book Your Ticket or Find Out More About this Event

IrishDev.com publishes details of this event for information only which are correct at the time of publication. IrishDev.com accepts no responsibility for cancellation, inaccuracies, amendments and / or loss for whatever reason.

For weekly event email

complete Green Box (top right)

Get Instant Irish Tech News from our Social Channels….


Join IrishDev.com at Facebook Join IrishDev.com at LinkedIn Follow IrishDevdotcom on Twitter


  • No Related Posts

Error on Studio: “A working instance for the Configuration Logging Service could not be found”

1. Restart the Citrix services with the following PowerShell commands and then close and reopen Studio:

  • Get-Service Citrix* | Stop-Service -Force
  • Get-Service Citrix* | Start-Service

Note: Studio is not going to show the same error message anymore, and it should prompt for a Mandatory upgrade again. Do not proceed with the upgrade yet, and make sure you have a good backup of the database before continuing with the following steps.

2. Re-register the Log and Monitor services connection strings with the following PowerShell commands:

Set-MonitorDBConnection -DataStore Monitor -DBConnection $nullSet-MonitorDBConnection -DBConnection $nullSet-LogDBConnection -DataStore Logging -DBConnection $nullSet-LogDBConnection -DBConnection $null
$cs="Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True"$csLogging= "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True"$csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True"
Set-LogDBConnection -DBConnection $csSet-LogDBConnection -DataStore Logging -DBConnection $csLoggingSet-MonitorDBConnection -DBConnection $csSet-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring

3. Proceed with the Mandatory upgrade on Studio by clicking the “Start the automatic Site upgrade” button. If prompted, enter the credentials used by the controllers to connect to the database.

4. Wait for the upgrade to finish, and then Studio should start to work properly.


  • No Related Posts

Unable to Remove XenDesktop Delivery Controllers from the XenDesktop Site

Complete the steps to remove the orphaned Delivery Controller (Controller) from a XenDesktop 7.x site:

  1. Run the Get-BrokerController command from PowerShell to get the SID of the orphaned Controller.

    User-added image

  2. Execute the following PowerShell script, replacing the XenDesktopDatabase with your XenDesktop database and the DCSID with your SID of the Controller you want to remove:

asnp Citrix*$DBName = "XenDesktopDatabase"$EvictedSID = "DCSID"## Generate Database 'Evict' Scripts for XenDesktop DataStore##Get-ConfigServiceStatusGet-LogSite Get-BrokerController -Filter {(SID -eq $EvictedSID)} -MaxRecordCount 2147483647Add-Content "$PWDevict_$sid.txt" (Get-AcctDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-HypDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-ProvDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-BrokerDBSchema -DatabaseName $DBName -ScriptType 'Evict' -SID $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-MonitorDBSchema -DatabaseName $DBName -DataStore 'Site' -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-SfDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-EnvTestDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-ConfigDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-LogDBSchema -DatabaseName $DBName -DataStore 'Site' -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-AdminDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-AnalyticsDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-AppLibDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-TrustDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)Add-Content "$PWDevict_$sid.txt" (Get-OrchDBSchema -DatabaseName $DBName -ScriptType 'Evict' -Sid $EvictedSID)# Script completed successfully# Generate Database 'Evict' Scripts for 'Logging' DataStore##Get-ConfigServiceStatus Get-LogSite Get-BrokerController -Filter {(SID -eq $EvictedSID)} -MaxRecordCount 2147483647Add-Content "$PWDevict_$sid.txt" (Get-LogDBSchema -DatabaseName $DBName -DataStore 'Logging' -ScriptType 'Evict' -Sid $EvictedSID)# Script completed successfully# Generate Database 'Evict' Scripts for 'Monitor' DataStore##Get-ConfigServiceStatus Get-LogSite Get-BrokerController -Filter {(SID -eq $EvictedSID)} -MaxRecordCount 2147483647Add-Content "$PWDevict_$sid.txt" (Get-MonitorDBSchema -DatabaseName $DBName -DataStore 'Monitor' -ScriptType 'Evict' -Sid $EvictedSID)# Script completed successfully

After running the script, the evict.txt file is created under the users profile. The file could also be generated under C:Windowssystem32, if ran in IDE PowerShell as administrator. The file contains a script required to run on the SQL server.


  • No Related Posts

CVAD-While Installing the Citrix components (Delivery Controller, Storefront,License )/, it prompts for reboot. Error “You must restart the machine before continuing ” “

– On the DDC VM, run the below steps to identify the pending reboot registry.

-1. Open an elevated PowerSell session.

2. Install-Module PendingReboot ( Internet access required on DDC machine )

3 . Set-ExecutionPolicy -ExecutionPolicy “Unrestricted”)

4. Import-Module PendingReboot

5. Test-PendingReboot -detailed

6 – Delete the registry key mentioned in the Powershell output.

7- Now the DDC, can be upgraded without restart prompt.


  • No Related Posts

Powershell Snap in giving error when Authenticating: “[New-SfClient], HttpRequestException + FullyQualifiedErrorId : System.Net.Http.HttpRequestException,ShareFile.Api.Powershell.NewSfClient”

When User tries to authenticate the Powershell snap in with the New-SfClient command.

Powershell gives the following error:

PS C:Windowssystem32> New-SfClient New-SfClient : An error occurred while sending the request. At line:1 char:1 + New-SfClient + ~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [New-SfClient], HttpRequestException + FullyQualifiedErrorId : System.Net.Http.HttpRequestException,ShareFile.Api.Powershell.NewSfClient


  • No Related Posts

When Launching an App-V Application, This Message is Shown “Cannot Start”.

On the VDA, open PowerShell as an Admin and verify that the application information is listed by running command:

Get-AppvClientPackage -All

The command output shows a failure, and the message “The Microsoft Application Virtualization Service may not have been started. Verify that the service is running.

That may indicate that App-V is not enabled on the VDA.

Run command Enable-App-V and restart Desktop service.

NOTE: If VDAs are not persistent, run the command in master image and update the catalog.


XenApp/Xendesktop 7.X Exception “Cannot Connect To Database Server” Of Type “Citrix.Fma.Sdk.Dal.DALConnectionFailedException”. Ensure that the database is correctly configured and accessible.

  • Collect Wireshark logs from Delivery Controller and SQL server to check if the issue is due to intermittent network issues.
  • Collect PSSDIAG logs from SQL Database Server to check if there are any SQL Performance issue.
  • As a workaround you can increase the Connection Pool size of Monitor Service.

1. Take a backup of Delivery controller and the Database Server.

2. On the Delivery Controller, launch Powershell as an admin.

3. Run asnp citrix*

4. Run Get-MonitorDataStore and copy the ConnectionString value.

5. Then run the below powershell cmdlets to Nullify the Monitor DB Connection:

Set-MonitorDBConnection -DataStore Monitor -DBConnection $null

Set-MonitorDBConnection -DBConnection $null

6. Then run the below powershell cmdlets to reset the ConnectionString value with Max Pool Size parameter added and value set to 200.


Set-MonitorDBConnection -DataStore Monitor -DBConnection “Server=SQL;Initial Catalog=xxxxx;Integrated Security=True;Max Pool Size=200”

Set-MonitorDBConnection -DBConnection “Server=SQL;Initial Catalog=xxxxx;Integrated Security=True;Max Pool Size=200”

7. Modify the String value as per the ConnectionString output you get from Step No. 4 and then restart the Citrix Monitor service.


Citrix Cloud – Unable to delete hosting connection, Error Connection “Connection name” cannot be deleted because it is being used by the following Objects and/or background actions.

1. Download and install Citrix Remote PowerShell SDK


Note: It recommend not to install Remote PowerShell SDK with any other Citrix Components installed.

2. Add the Citrix snap-ins:

asnp Citrix*

3. Authenticate to Citrix Cloud.

Note: If you have multiple Customers associated to your account you will get a drop down to select the correct one that you are targeting.


4. Get the PS Path of the hosting connection and resource(s)

ls XDHyp:Connections
ls XDHyp:HostingUnits

Example hosting connection path: “DHyp:ConnectionsHosting Connection Name”

Example Resource path: “XDHyp:HostingUnitsResource Name”

5. Remove the Resource(s) Path:

Remove-Item -Path "XDHyp:HostingUnitsResource Name"

6. Remove Hosting Connection Path:

Remove-Item -Path "XDHyp:ConnectionsHosting Connection Name"

7. Removing Hosting connection Entry:

Remove-BrokerHypervisorConnection -Name "Hosting Connection Name"