Problem:

One may encounter the following error when configuring the Geneos Citrix Integration template for the first time:

<Fri Apr 16 19:12:39> ERROR: TOOLKIT2 ConvertTo-SecureString : The system cannot find the path specified.

At C:\Program Files\NetprobeNT gelo 6371\citrix-sessions.ps1:18 char:14

+ $secpasswd = ConvertTo-SecureString -String $password

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (:) [ConvertTo-SecureString], CryptographicException

+ FullyQualifiedErrorId : ImportSecureString_InvalidArgument_Cryptographic

Error,Microsoft.PowerShell.Commands.ConvertToSecureStringCommand

New-Object : Exception calling ".ctor" with "2" argument(s): "Cannot process

argument because the value of argument "password" is null. Change the value of

argument "password" to a non-null value."

At C:\Program Files\NetprobeNT gelo 6371\citrix-sessions.ps1:21 char:12

+ $mycreds = New-Object System.Management.Automation.PSCredential($user ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvoca

tionException

+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.Power

Shell.Commands.NewObjectCommand

Invoke-RestMethod : The URI prefix is not recognized.

At C:\Program Files\NetprobeNT gelo 6371\citrix-sessions.ps1:24 char:15

+ ... essions = $(Invoke-RestMethod -Uri $($endpoint + '/Sessions/' + $ses ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotImplemented: (:) [Invoke-RestMethod], NotSupportedException

+ FullyQualifiedErrorId : WebCmdletIEDomNotSupportedException,Microsoft.Po

werShell.Commands.InvokeRestMethodCommand

Possible cause(s):

This can happen when the Citrix password is encrypted by a Windows user and the Netprobe is being run by the Local System account.

Possible solution(s):

The Netprobe should be run by the user that encrypted the Citrix password.

If you need further help:

[Guide: Please specify what the client should provide if they have followed the guide without finding a solution (e.g., diagnostic file, sampler name, rule name, rule.xml, screenshot, etc.).]

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.