Receiver 4.10: Grey Screen On Published Desktops After Upgrading To Receiver 4.10

Unknown error 0x887A0001 in DirectX API seen in CDF Traces collected from the Receiver side.

ProxyLogErrFunc,9,CDF_ERROR,”ctx::gfx::D3D11PresentDevice::CreateSwapChain :: IDXGIFactory1::CreateSwapChain Failed. hResult = 0X887A0001, msg = Unknown error 0x887A0001″,”

DXGI_ERROR_INVALID_CALL
0x887A0001

The application provided invalid parameter data; this must be debugged and fixed before the application is released.

Related:

  • No Related Posts

Rest API to create multiple resources

I opened a ticket for this, but perhaps someone already tried this before and can cut down the waiting line…

I’m in phase where I’m exploring and documenting Rest API usage… I kind of like it even though for normal human usage nsradmin is still your best friend. Still, I can see where Rest API would be better fit, especially when integrating with other platforms without any specific parts of NW package to be available.

One thing where I found myself stuck is handling multiple resources (if you wish to create it via POST). Consider following body:

{

“protectionGroups”: [

{

“comment”: “Backup group via RestAPI one”,

“name”: “RestAPIb”,

“workItemType”: “Client”,

“workItems”: []

},

{

“comment”: “Backup group via RestAPI two”,

“name”: “RestAPIc”,

“workItemType”: “Client”,

“workItems”: []

}

]

}

That doesn’t work for me, but error I get seems to suggest some kind of syntax error (or this simply not being supported in the first place). I can easily create one resource or have two calls for each resource too, but would prefer if I could use single call for multiple resources when building requests for the same type of resources.

Related:

  • No Related Posts

DLP 12.5 – Unable to start Aggregator

I need a solution

I am currently having an issue that my Endpoint server is not able to start up properly.

In fact, it is stuck at “starting”.

The only message in the console is:

Message
Code  1012
Summary  “Unable to start Aggregator
Detail  Cannot bind to the shutdown datagram socket. Will retry.

In the Aggregator.log, I can only see this as well in terms of errors:

“Oct 9, 2018 8:19:49 PM com.vontu.logging.LocalLogWriter write
SEVERE: “Unable to start Aggregator. Cannot bind to the shutdown datagram socket. Will retry.”

Besides, there are only INFO level entries in this logfile.
I can restart as many times I want, no change.

Unfortunately, I am out of ideas.
Any input or help appreciated.

0

Related:

  • No Related Posts

Hardware Acceleration for Linux endpoints with AMD GPUs

Sarting from version 2.5, HDX RTME supports hardware acceleration for video compression on Linux thin clients or fat clients with AMD GPU. Specifically, for video encoding RTME uses VCE 2.0 or higher. Video decoding has limited support because of some technical limitations, and it is disabled in RTME by default.

OMX IL is used for offload video processing to GPU.

Hardware video encoding on Linux could be disabled by registry key DisableOnboardHardwareH264Encoding (DWORD value 1-disabled or 0-enabled by default) in HKEY_CURRENT_USERSoftwareCitrixHDXRTConnectorMediaEngine

Ubuntu 16.04 environment set-up

Install AMD driver stack from https://support.amd.com/en-us/download/embedded?os=Linux_tmp%20x86_64

Install kernel (example command line, latest available version should be used):

sudo dpkg -i linux-image-4.4.11-289-amd+_4.4.11-289-amd+-10.00.Custom_amd64.deb linux-headers-4.4.11-289-amd+_4.4.11-289-amd+-10.00.Custom_amd64.deb

sudo reboot

Install userspace:

Create local repository as it is described in amdgpu_UserGuide.pdf or proceed manually with dpkg.

NOTE:

To verify available package versions:

apt-cache policy <package name>

To overwrite ‘man’ or header files:

-o Dpkg::Options::=”–force-overwrite” (apt-get)

–force-overwrite (dpkg)

In case of unmet dependencies, you can resolve them by installing strictly with dpkg -i, pulling needed packages alongside.

During these steps, please, prefer packages from AMD driver stack. For isntance you may install “llvm-5.0-dev=5.0-519”, while “llvm-5.0-dev” will set up the latest Ubuntu package.

libllvm5.0 llvm-5.0-dev llvm-5.0-runtime llvm-5.0

llvm-runtime llvm-dev llvm

libdrm-dev libdrm-amdgpu1 libdrm-radeon1 libdrm2

libdrm-dev libdrm-amdgpu1 libdrm-radeon1 libdrm2

libva-dev libva1 libva-drm1 libva-egl1 libva-glx1 libva-tpi1 libva-wayland1 libva-x11-1 vainfo apt-cache policy libva-dev libva1 libva-drm1 libva-egl1 libva-glx1 libva-tpi1 libva-wayland1 libva-x11-1 vainfo

libegl1-mesa-dev libegl1-mesa-drivers libegl1-mesa libgbm-dev libgbm1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles1-mesa-dev libgles1-mesa libgles2-mesa-dev libgles2-mesa libosmesa6-dev libosmesa6 libwayland-egl1-mesa libxatracker-dev libxatracker2 mesa-common-dev mesa-omx-drivers mesa-vdpau-drivers

gst-omx xserver-xorg-video-amdgpu

Install bellagio:

libomxil-bellagio0 (Generic core OMXIL implementation)

libomxil-bellagio-bin (to register available OMX components)

Register these components run omxregister-bellagio (from libomxil-bellagio-bin) with the noted above path.

  • Run omxregister-bellagio -l and you should get the following output:
  • *********************************
  • * List of registered components *
  • *********************************
  • Component OMX.mesa.video_decoder
  • supported formats:
  • OMX.mesa.video_decoder.mpeg2
  • OMX.mesa.video_decoder.avc
  • Component OMX.mesa.video_encoder
  • supported formats:
  • OMX.mesa.video_encoder.avc
  • Installed components and a path to the library are stored in an OMX registry file:
  • $ cat ~/.omxregister
  • /usr/lib/libomxil-bellagio0/libomx_mesa.so
  • ==> OMX.mesa.video_decoder ==> OMX.mesa.video_decoder.mpeg2:OMX.mesa.video_decoder.avc:
  • ==> OMX.mesa.video_encoder ==> OMX.mesa.video_encoder.avc:

Driver requirements:

These are described in AMD’s site https://support.amd.com/en-us/download/embedded?os=Linux_tmp%20x86_64

RTME uses OMX API for video encoding and decoding.

This API is implemented by Bellagio OpenMAX IL (libomxil-bellagio0 and libomxil-bellagio-bin).


Hardware requirements: AMD GPU with VCE 2.0 or above. Specifically, Citrix is using Mullins and Carrizo.

Known limitations:

video encoding is supported on Mullins series only. Carrizo series were tested too, but problems were found with unstable video bitrate. As a result, a stream was encoded with poor quality.

video decoding is disabled by default, and could be enabled from registry on VDA. It was done because HW decoder introduces high latency up to 500ms.

It was found that described limitations became visible only on Linux platforms. The same GPU works great on Windows endpoints.

Related:

Can not create new widget – last scan date

I need a solution

Every time I try to create any new widget I get: 

failure message: {“data”:{“errorCode”:761,”message”:”Unable to create new widget.”,”data”:{}}}

All I want is a widget that shows last scan date.  Other info might be useful too, but I can’t create ANY widgets.

Thanks,

– cjm

0

Related:

Re: Recovery Point for VM Failover through REST

Hi All,

Need a suggestion on Failing over VM through the REST API in RP4VM.Any leeds on it will be very helpful.

I came across the following :

1.The CLI might not be having all the functionalities

2.The API functionalities I came across in the Programming guide either does not cover all operations or might not be stated in the document.

3.We have the Swagger link , where we can test the Requests made : https://<ip>/deployer/swagger/#

4.There are two versions of the API i think : FAPI and deployer (however the FAPI contains methods like failover as i was searching online) and deployer contains more or less the same methods as in swagger. The Fapi documentation is old and for 4.0 , while deployer i could get for 5.1.

Question : How can we failover using the REST API ,present verion we are using is 5.1 , if you can mention the method and the wsdl/wadl , it would be great help.

Related:

HDX 3D Pro GPU Support and Deployment Considerations

This article lists the Graphics Processing Unit (GPU) platforms supported by Citrix for use with HDX 3D Pro. The article intends to provide guidance for customers when choosing GPU hardware to be used for graphics acceleration with HDX 3D Pro. Deployment considerations for XenDesktop and XenApp workloads are also included, in the context of HDX 3D Pro.

Hardware Support

Citrix currently supports the following GPU platforms from the main hardware vendors. Specific GPUs tested by Citrix during the development of HDX 3D Pro are included in this list. Citrix recommends that customers become familiar with different GPU vendor technologies and choose a GPU that meets the technical requirements for the use-case.

  • NVIDIA GRID
    • Tesla M10 / M60 / P40 / P100
  • AMD RapidFire
    • FirePro S7150 / S7150x2
  • Intel Iris Pro
    • Intel Xeon Processor E3 v5 Family

Note: This is not an all-inclusive list of all the GPU hardware that can be used with HDX 3D Pro. This is just a list of the hardware that Citrix includes as part of engineering testing during product development. Refer to the GPU vendor website for additional GPU models supported under each platform.

Cloud deployment options

HDX 3D Pro is supported when running on GPU-enabled virtual machines available from the following Cloud providers:

  • Microsoft Azure NV-Series
  • Amazon AWS EC2 G3

Deployment Considerations

It is important to understand the different deployment options for using GPU hardware acceleration with XenDesktop and XenApp. The following list includes supported deployment options and key design considerations for each:

XenDesktop (VDI)

HDX 3D Pro mode. Recommended for datacenter desktops with GPU hardware. This option is available with the VDA for Windows Desktop OS to leverage GPU vendor drivers and application program interfaces (APIs) for hardware rendering and graphics acceleration. There are two different ways to configure a virtual desktop with HDX 3D Pro depending on the product version used:

Desktop OS VDA versions 7.16 or newer

  • There is no installation mode for HDX 3D Pro.

  • VDA will detect the presence of supported GPU drivers automatically at runtime and leverage GPU for graphics rendering and acceleration if available.

  • Citrix optimizations can be enabled via Citrix policy “Optimize for 3D graphics workload.”

Desktop OS VDA versions 7.6 to 7.15 LTSR

  • HDX 3D Pro mode must be selected during installation of the VDA.
  • Required in order to utilize GPU vendor drivers as well as enable Citrix optimizations for 3D graphics workloads.
HDX 3D Pro Support NVIDIA AMD Intel
Display Driver GRID FirePro Iris Pro
Operating Systems Windows 7 and Windows 10 Windows 7 and Windows 10 Windows 10
Multi-monitor Up to 4

*NVIDIA License required
Up to 6 Up to 3 (tested with 7.6 – 7.15 LTSR)

Up to 8 (tested with 7.16 – newer)
H.264 hardware encoding GPUs must support NVENC hardware encoding. See NVIDIA video codec SDK for a list of supported GPUs. Not supported Intel Broadwell processor family and later required.

Intel Iris Pro hardware encoder SDK is required and can be downloaded from Intel website: Remote Displays SDK.

3D & Custom Driver extension APIs DirectX, OpenGL, OpenCL, CUDA

*May vary based on GPU vendor support

Standard mode. Recommended for virtual desktops without GPU and RemotePC access. This is the default installation option in the VDA for Windows Desktop OS versions 7.6 to 7.15 LTSR and default operating mode with versions 7.16 and newer. This mode will install and use the Citrix Display Driver for rendering. Note that if a GPU is available, hardware acceleration for applications is still possible in standard mode with the following limitations:

  • Windowed applications only, no full-screen application support.
  • DirectX feature levels up to 9.3 with Windows 7. Some DirectX 10, 11, 12 applications may not run if they do not tolerate fallback to DirectX 9.
  • DirectX 10, 11, and 12 with Windows 10 only.
  • OpenGL application acceleration with NVIDIA GPUs only

XenApp (RDS)

Note that there is no HDX 3D Pro mode option available when installing the VDA for Server OS. The VDA is installed in Standard mode and it uses a specialized Citrix Driver for display remoting only. GPU sharing and application graphics acceleration is supported on the Windows Server 2012 and 2016 operating systems, with the same limitations as listed under the XenDesktop standard mode section above.

Related:

Error: “3006” on Firefox and Safari Web Browsers When Using NetScaler Gateway EPA Scan

This issue is observed when the NetScaler Gateway plug-in is not installed on the client computer. The NetScaler Gateway plug-in must be installed before performing EPA scans. The NetScaler Gateway plug-in installer includes a fragment of the EPA components. The installer registers this fragment with the 32-bit EPA COM server (nsepa.exe) and the NPAPI plugin DLL, 32-bit or 64-bit, as appropriate.

If a Gecko-based web browser, such as Firefox is already installed, the NPAPI plugin DLL is copied to the Mozilla Plugins folder under the application data folder of the user. For example, the plugin DLL is copied to the C:Documents and Settings<username>Application DataMozillaPlugins folder. If a Gecko-based web browser is not installed, Citrix plugins are registered to ensure that the plugins are discovered by the browser when it is installed.

Related: