Citrix Receiver for Web: Error “Cannot complete your request”

There can be multiple reasons behind this issue as the error message we are getting on Web browser is very generic. To isolate and resolve this issue please follow these steps:

1. From test machine ping the base URL and confirm the IP you are getting:

  • Case 1: Unable to resolve any IP
Make sure the URL in base URL is correct and make sure there is a DNS entry for the URL
  • Case 2: Able to resolve Load Balancing VIPs IP
In this case we have to isolate whether it’s a Storefront issue or NetScaler. We also need to verify all the StoreFront servers.
  1. Browse “Store for Web” using IP address of StoreFront/localhost on StoreFront server and confirm if you are able to login and see resources, check this on all the StoreFront servers
  2. If you are able to login and see resources then it should be a configuration on LB VIP causing the issue then troubleshooting should be done on NetScaler.
  3. If you are still getting same error then troubleshooting should be done on StoreFront.
  • Case 3: IP resolving to one of the StoreFront’s IP
We have to troubleshoot Storefront and check why it’s causing issue.
  • Case 4: Incorrect Trusted domain Configured
Incorrect trusted domain configured for NetScaler Passthrough

To resolved: Correct the domain name or select “All Domains” under “Manage Authentication Methods” for NetScaler Passthrough

Troubleshooting StoreFront:
  1. Ping the base URL from StoreFront servers, each StoreFront server should resolve the base URL to it’s own IP if now then create a host entry (
  2. Make sure you are able to browse default IIS page as StoreFront is dependent on IIS.
  3. Make sure that the Default Store was never deleted from the StoreFront server. Deleting the default Store can corrupt StoreFront and we may need to reinstall StoreFront.
  4. Confirm if StoreFront services are running, Citrix Cluster join service can be in disable state(only works when we add a new server to Server Group).
  5. Check event viewer on StoreFront server. There can be multiple Receiver for Web events, e.g. “Failed to run discovery” or “Unable to resolve/find URL at 443/80”.
    • This can happen because of bindings on IIS. Make sure if the base URL is https then there should be https binding on StoreFront server with valid certificates if not then change base URL to http and confirm you have http/port 80 binding on IIS.
      • User-added image
  6. Check authentication methods in Store> Manage Authentication Methods
    • If authentication method available is Username and Password and you have selected Smart Card in Manage Authentication Methods then StoreFront will not find a way to authenticate users and give errors


  • No Related Posts

Printers fail to map with errors when using UPS on Windows Server 20122016

The following workaround is available –

Add “LimitRequestLine 8190” in the next line after the “LimitRequestFieldSize 65535” to the httpd.conf file located at:

C:Program Files (x86)CitrixXTEconf

The LimitRequestLine directive decides the limit on the allowed size of HTTP request line (which contains HTTP Method, URI and Protocol version). Since 8190 is the default value, having it in the httpd.conf file should not make any difference.


  • No Related Posts

Cisco IOS XR Software Enhanced Preboot eXecution Environment Unsigned Code Execution Vulnerability

A vulnerability in the enhanced Preboot eXecution Environment (PXE) boot loader for Cisco IOS XR 64-bit Software could allow an unauthenticated, remote attacker to execute unsigned code during the PXE boot process on an affected device. The PXE boot loader is part of the BIOS and runs over the management interface of hardware platforms that are running Cisco IOS XR Software only.

The vulnerability exists because internal commands that are issued when the PXE network boot process is loading a software image are not properly verified. An attacker could exploit this vulnerability by compromising the PXE boot server and replacing a valid software image with a malicious one. Alternatively, the attacker could impersonate the PXE boot server and send a PXE boot reply with a malicious file. A successful exploit could allow the attacker to execute unsigned code on the affected device.

Note: To fix this vulnerability, both the Cisco IOS XR Software and the BIOS must be upgraded. The BIOS code is included in Cisco IOS XR Software but might require additional installation steps. For further information, see the Fixed Software section of this advisory.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

This advisory is available at the following link:

Security Impact Rating: High

CVE: CVE-2020-3284


  • No Related Posts

Problem with iPXE when using a USB Ethernet Adapter

I need a solution


Wondering if anybody else has come across this

We recently upgrade to Ghost 3.3 RU2 with iPXE (faster way of connecting devices to imaging sessions) 

Laptops and PCs with dedicated Ethernet ports are working (when secure boot is disabled) 

We have some new devices that have no Ethernet ports – we have a mixture of USB Ethernet adapters

The drivers have been added and if you use PXE they work and image fine 

However if we try using iPXE they boot and download the wim file but then freeze and dont load the WinPE – we have tried leaving it all afternoon but nothing happens

If we try it again and wait until the ipxe starts and the wim file download reaches 100% and then remove the USB Ethernet adapter for a few seconds then plug it back in the WinPE session loads and the device joins the session and images fine. Its as if it gets stuck trying to pass some type of security check – maybe UEFI related. 

Just wondering if anybody else has come across this issue ? 




Unable to upgrade to GSS 3.3 RU3 with iPXE?

I do not need a solution (just sharing information)

When trying to upgrade from GSS 3.3 to GSS 3.3 RU 3, I kept getting this error when selecting the iPXE configure option – It stops at 50% with error message “Failed to install iPXE Addon for PXE Server”

From what I can tell, it was a problem in the past and it appears to be a problem again:

This is even after going over the system requirements for iPXE and had everything installed and configured (Dot.Net 4.5 Framework, IIS, all the Microsoft goodies):

So, I went through and manually installed each one of the MSI installers based on what this article had stated:

And then went back and re-configured the authentication methods in IIS manager based on what this article had stated as well:

TA-DA! iPXE is now working!

Quite a pain to get it all working, but it lives….

Has this been everybody else’s experience trying to get this all to work as well?



Issues with ipxe failing to boot

I need a solution

Hi, We recently upgraded to 3.3 ru2 And installed the ipxe adons to try and use 2 servers have worked fine with no issue They boot to ipxe and image The servers are running server 2016 with full version of sql The 3rd server is failing to boot to ipxe – it keeps coming up with an error pxe-e53 I tried searching and tried some of the solutions but no joy Pxe works and boots a machine to winpe and images When we set it to ipxe it goes through the process but as its about to start pulling the winpe it fails with an error and boots to windows All 3 servers are identical- all running same version of the console and the pxe and pxe utility I have recreated a new pxe boot file using the ipxe option and saved it to the pxe config utility and checked it’s the correct one being used to connect to by the pc Any ideas would be much appreciated Thanks This is a selection on the error from the log file 2019-08-15 09:23:45.9845|ERROR|Altiris.DSSDK.Server|GetPxeBootInfo : Exception while GetPxeBootInfo executing Input string was not in a correct format. 2019-08-15 09:23:46.1876|ERROR|GetPxeBootInfo.GetPxeBootInfo|Request : 107B441AFDA6P1210288128 2019-08-15 09:23:46.3126|ERROR|GetPxeBootInfo.GetPxeBootInfo|Failed to read PXEBootInfo Error Message: Input string was not in a correct format. Stack Trace:   at Altiris.DSSDK.Server.GetPxeBootInfo(String resourceUUID, String resourceMacAddress, String resourceSerialNumber, String resourceIP)    at GetPxeBootInfo.GetPxeBootInfo.Page_Load(Object sender, EventArgs e) 2019-08-15 09:24:32.4869|ERROR|Altiris.DSSDK.Server|GetPxeBootInfo : Exception while GetPxeBootInfo executing Input string was not in a correct format. 2019-08-15 09:24:32.5025|ERROR|GetPxeBootInfo.GetPxeBootInfo|Request : 107B441AFDA6P1210288128 2019-08-15 09:24:32.5025|ERROR|GetPxeBootInfo.GetPxeBootInfo|Failed to read PXEBootInfo Error Message: Input string was not in a correct format. Stack Trace:   at Altiris.DSSDK.Server.GetPxeBootInfo(String resourceUUID, String resourceMacAddress, String resourceSerialNumber, String resourceIP)    at GetPxeBootInfo.GetPxeBootInfo.Page_Load(Object sender, EventArgs e)



No PXE-Boot when assigning job, otherwise PXE works

I do not need a solution (just sharing information)


PXE is set up and works in my opinion.

On all clients, PXE-Boot is set as the first boot method, each client first queries the PXE server at boot time and then executes the PXE-Boot according to my settings: For clients known in the console, the PXE-Boot-Menu waits 5 seconds, then the boot from the local HDD with the locally installed operating system takes place. Clients not known in the console wait 10 seconds in the PXE boot menu and then start the Automation Agent via PXE.

If I assign an image deployment-job to a client known in the console, this client will restart as it should be. Then it should boot the Automation Agent via PXE so that the new image can be transferred to the hard disk. However, this is not the case. Instead, the PXE boot menu is displayed for max. 1 second, but it is exited immediately and the local operating system is booted from the local hard disk. The deployment-job is then shown as failed at the end.

What is the reason / What should I do?

Thanks in advance!



Citrix Hypervisor – Paravirtualized VM won't boot after upgrade to Hypervisor 7.0

Updated the following files that are used to boot the XS installer to match the current version being installed, on this particular case, files on the TFTP server were from previous Hypervisor version 6.x



These files are needed on a TFTP server according to the Network Boot Installation process described here:


PXE / DHCP / Lease-Time

I need a solution


I´m in the Process of migrating from W7 to W10. To do so, among a lot of other things, I rolled out GSS-Client to all my Machines (~230)  and change Bootorder to place Network-Boot first on every Machine. For Clients known to the GSS-Console (all my Clients) “Next Device” is default in PXE, so my Clients boot their local OS after 5 Seconds waiting when no job is assigned (what is the default case)

So during PXE-boot, every Client aks my DHCP for an IP-Address, which the Client normally needs only for the above mentioned 5 Seconds. After that the local OS boots where I have configured staticIP´s on every Client.

In this configuration I need a reltivly big IP-Range (in the past I had a Range of only about 20 IPs for special things) in DHCP.
What should I use as Lease-Time in this configuration?
How do you “solve” this Problem in your Environments?

Thanks in Advance!