The print job uses the default tray to print documents even though you can choose a different tray from the Print dialog. $Location = “$ | Set-Content $Locationĭette indlæg blev udgivet i FAQ den septemaf Jan. After you upgrade XenApp and XenDesktop from Version 7.9 to Version 7.15, you might be unable to print documents to a different output printer tray. Open the file, nf, by using a simple text editor, such as. This article lists the steps to take to solve practically any problem. Solution Stop the Citrix XTE Server service.

or Citrix Receiver (Unable to connect to Server, Protocol driver error). For convenience you can copy the script from here: If you work with Citrix-based applications and keep getting protocol driver errors when you try to launch the app, you need to solve the problem fast. Contact your help desk with the following information: Cannot connect to the Citrix XenApp server.Protocol Driver error. Citrix Access Gateway URL in browser launches to Citrix NetScaler Gateway which. See for powershell script to change STA ID. External connections through the NetScaler fail with a protocol driver error while internal connections to the same XenApp server are still successful. When users connect on the first node they get a ticket from STA – when you failover netscaler flips the order of the STA’s and users will ask the STA with duplicate ID about the ticket, but the second STA does not know about the Tiket and refuses connection.

Identical STA IDs can occur when you clone servers (see bullet 13) from VM template and if XML service starts before the NIC (you should set XML service to delayed start on template). The cause of this can be duplicate STA IDs on STA servers in farm.

When accessing Citrix Wi through Netscaler HA pair, launcing applications Works on one of the Netscaler nodes but when you failover to the other HA node users get an ‘Unable to launch application….Protocol Driver error’ dialog box.

Citrix protocol driver error